We normally suggest using black pages as separators. However you could also use white pages but these can get confused with the document pages, and blank pages. Any colour that scans bitonally as black (i.e. red, blue etc) could be used as a separator page. We suggest setting the percentage white space for separators at 10%.

Direct link to FAQ

A blank page is a page that is usualy around 99.80% white. The operator can change this percentage value of white for a blank page can adjusted in the Admin->Jobs->Enhancement tab. It is recommended not to set this setting below 99.70% as pages that may contain a small amount of content could be deleted.

To remove blank pages at scan time simply tick the 'Delete Blank Pages' option tickbox on the Enhancement tab of the Operator Actions form (F2). Otherwise you can use the Shift and Delete keys to delete blank pages from a batch set of images.

If an image has a dark line around the edge of the page or has black spots from the hole punch and EzeScan is not deleting it, the H Area % and V Area % can also be set in the Enhancement tab. H Area is for Horizontal and V Area is for Vertical. i.e. if setting the V area to around 85% EzeScan will ignore the top and bottom 7.5% of the page therefore not picking up the black coverage and deleting the page correctly.

Direct link to FAQ

According to the ScanSoft Knowledge base you simply need to rename the opodma.dll file as opodma.old.

Direct link to FAQ

What Scanners Are Supported By EzeScan?

TWAIN Scanners

EzeScan PRO includes built in TWAIN scanning support, so it will work directly with most TWAIN compliant scanners. Scanners supporting the TWAIN 1.9 specification or higher should work with EzeScan. Most well maintained TWAIN drivers are now at least TWAIN 2.0/2.1/2.2 compliant.. We suggest using TWAIN for production batch scanning.

ISIS Scanners

There is an optional ISIS scanning module available for purchase which will provide ISIS support for ISIS compliant scanners. There is no real need to use ISIS if you already have a TWAIN compliant scanner.

WIA Scanners

EzeScan PRO includes built in WIA scanning support, so it will work with most WIA compliant scanners. WIA (Windows Imaging Acquisition) is very lightweight and best suited to scanning single pages at a time, not batch scanning of multiple pages or documents. We suggest to only use WIA when no other drivers exist for your scanner.

Digital Photocopiers, MFP's and Network Scanner Devices

Simply scan to a network file share, and then use the standard import file/folder functionality in EzeScan PRO to import your scanned images into EzeScan for processing.

Choosing Your Scanning Device

Below is a list of scanners/devices that should work with the latest release of EzeScan 4.3:

Some newly released scanners may be absent from the list below, because they have not gone through our Scanner Certification process.

Some older scanner models have struck through because the Scanner Manufacturer has announced them as being End of Life (EOL), so we no longer accept support calls related to these scanners.

Highly Recommended Scanners

The following scanners are highly recommended by us because these Scanner Vendors regularly update their scanner drivers with new features and fixes.

We regualarly test that these scanners will work with EzeScan.


  • Canon Lide 20
  • Canon 330P
  • Canon 340P
  • Canon DR-2010C
  • Canon DR-2080C
  • Canon DR-2085C
  • Canon DR-2510C
  • Canon DR-3010C
  • Canon DR-4010C
  • Canon DR-5010C
  • Canon DR-5020 / DR-5080C
  • Canon DR-6010C
  • Canon DR-6030C
  • Canon DR-6050C
  • Canon DR-7080C
  • Canon DR-7550C
  • Canon DR-9050C
  • Canon DR-9080C
  • Canon DR-G1100
  • Canon DR-G1130
  • Canon DR-G2090
  • Canon DR-G2110
  • Canon DR-G2140
  • Canon DR-M140/M140II
  • Canon DR-M160/M160II
  • Canon DR-X10C



  • Fujitsu fi-4120C/4120C2
  • Fujitsu fi-4340C
  • Fujitsu fi-4530C
  • Fujitsu fi-4860C/4860C2
  • Fujitsu fi-5015C
  • Fujitsu fi-5110C
  • Fujitsu fi-5120C
  • Fujitsu fi-5220C
  • Fujitsu fi-5530C/5530C2
  • Fujitsu fi-5650C
  • Fujitsu fi-5750C
  • Fujitsu fi-5900C
  • Fujitsu fi-5950
  • Fujitsu fi-60F
  • Fujitsu fi-6130/6130Z
  • Fujitsu fi-6230/6230Z
  • Fujitsu fi-6140/6140Z
  • Fujitsu fi-6240/6240Z
  • Fujitsu fi-6670/6670A
  • Fujitsu fi-6770/6770A
  • Fujitsu fi-6400/fi6800
  • Fujitsu fi-7030
  • Fujitsu fi-7160/fi-7180
  • Fujitsu fi-7260/fi-7280
  • Fujitsu fi-7600/fi-7700
  • Fujitsu fi-7900



  • Kodak i920
  • Kodak i1120/i1150/i1180
  • Kodak i1210/i1220 Plus
  • Kodak i1310/i1320 Plus
  • Kodak i1405/i1410/i1420/i1440
  • Kodak i150/i160
  • Kodak i1840/i1860
  • Kodak i2400/2600/2800
  • Kodak i2900/i2950
  • Kodak i3200/i3250
  • Kodak i3400/i3450
  • Kodak i4200/i4200+/i4250
  • Kodak i4600/i4600+/i4650
  • Kodak i5200/i5250
  • Kodak i5600/i5650
  • Kodak i5800/i5850
  • Kodak Ngenuity 9090DB/9090DC/9125 - New!
  • Kodak Sidekick 1400u
  • Kodak SCANMATE i920
  • Kodak Truper 3210/3610


Other Supported Scanners

For the scanners listed below , our testing is normally done against the TWAIN driver.


  • Avision 121
  • Avision 122
  • Avision 210
  • Avision 220/220C2/AV220D2+
  • Avision 320/320D2+
  • Avision 600U
  • Avision 610
  • Avision 820C
  • Avision 830C
  • Avision 3200C
  • Avision 3200SU
  • Avision 3750
  • Avision 3850SU
  • Avision 8050
  • Avision 8300
  • Avision 8350
  • Avision IT8300



  • Brother MFC 9100C
  • Brother ADS-2600
  • Brother ADS-2400N
  • Brother ADS-2800W
  • Brother ADS-3000N
  • Brother ADS-3600W
  • Brother PDS-6000



  • Colortrac SmartLF Ci 24 (m, c and e models)
  • Colortrac SmartLF Ci 40 (m, c and e models)
  • Colortrac SmartLF Gx+ 42 (m, c and e models)
  • Colortrac SmartLF Gx+ T42 (m, c and e models)
  • Colortrac SmartLF Gx+ 56 (m, c and e models)
  • Colortrac SmartLF Gx+ T56 (m, c and e models)
  • Colortrac SmartLF SC 42



  • Epson GT-S50
  • Epson GT-S55
  • Epson GT-S80
  • Epson GT-S85
  • Epson DS-5500
  • Epson DS-6500
  • Epson DS-7500
  • Epson DS-50000
  • Epson DS-60000
  • Epson DS-70000



  • HP 4300C
  • HP 5200C
  • HP GX85
  • HP 7400
  • HP 7450C
  • HP 7800
  • HP 8250C
  • HP 9000 (Note: This scanner driver supports Auto Paper Sizing in its TWAIN driver, but not in its ISIS driver)
  • HP N9120 (Note: This scanner driver does not support Auto Paper Sizing in its TWAIN or ISIS driver)
  • HP 9250C

Please Note: In our experience HP are very slow to release driver updates for their scanners. So if something doesn't work you're stuck with it (unless we can figure out a workaround)



  • AS3690
  • AS7200
  • DS1225



  • Panasonic KV-S2026CU
  • Panasonic KV-S2046CU
  • Panasonic KV-7065CW
  • Panasonic KV-S3105C
  • Panasonic KV-S3065CW



  • Ricoh IS300E
  • Ricoh IS330DC
  • Ricoh IS450S
  • Ricoh IS200E
  • Ricoh IS760



  • Syscan DocketPORT 464
  • Syscan DocketPORT 465
  • Syscan DocketPORT 485



  • Xerox Documate 3125
  • Xerox Documate 3220
  • Xerox Documate 3640
  • Xerox Documate 4440
  • Xerox Documate 4760
  • Xerox Documate 4790
  • Xerox Documate 4799
  • Xerox Documate 4830



  • Visioneer Patriot 480
  • Visioneer Patriot 680
  • Visioneer Patriot 780



  • HP Multifunction Devices
    • EzeScan PRO & KIOSK - HP MFP and CMFP Models with built in scanner
    • EzeScan SERVER - HP MFP and CMFP Models with built in scanner and supports the HP MFP Digital Sending Software 4.1 and above
  • Infotec Multifunction Devices with built in scanner
  • Konica Minolta Multifunction Devices with built in scanner
  • Lanier Multifunction Devices with built in scanner
  • Lexmark Multifunction Devices
    • EzeScan PRO & KIOSK - Lexmark Multifunction Devices with built in scanner
    • EzeScan SERVER - Lexmark Multifunction Devices with built in scanner and supports the Lexmark Solution Composer software.
  • Ricoh Multifunction Devices
    • EzeScan PRO & KIOSK - Ricoh Multifunction Devices with built in scanner
    • EzeScan SERVER - Ricoh Multifunction Devices with built in scanner and GlobalScan NX Serverless 1.2x and above
  • Sharp Multifunction Devices with built in scanner
  • Toshiba Multifunction Devices with built in scanner
  • Xerox Multifunction Devices
    • EzeScan PRO & KIOSK - Xerox Multifunction Devices with built in scanner
    • EzeScan SERVER - Xerox Multifunction Devices with built in scanner and supports the Network Scanning Template option (NSA)


Important Notes

1. We do not provide ongoing support for scanners that have been made End Of Life (EOL) by the scanner manufacturers. We will not modify our code to fix issues found with EOL scanners. We encourage our customers to upgrade their scanners every 3 years well before they become EOL.

2. We strongly recommend using a scanner with a USB 2.0/3.0  connection (as we do not support scanners that use SCSI connections).

3. It is your responsibility to confirm that your combination of scanner, interface card and TWAIN / ISIS / WIA driver will work with EzeScan. This is due to the fact that some manufacturers do not support WIA or ISIS. Most support TWAIN out of the box. Quite often the scanner drivers supplied on the CD with the scanner are outdated. Scanner manufacturers release new device firmware and drivers on a regular basis to fix driver problems that exist on their product CD's, or to release new driver features. Some older drivers may only work on 32 bit versions of Windows Operating Systems, and some drivers are not certified as Windows 7, 8  or 10 compliant. So we suggest that you make sure that your device firmware and scanner drivers are up to date, and work on your Windows OS before you start using EzeScan.

4. If you are unsure about what type of scanner you have, drop us an email and we'll see if we can help you identify if it is TWAIN / ISIS / WIA compatible. We suggest downloading an evaluation copy of EzeScan to confirm that your scanner will work in a satisfactory manner with EzeScan.

5. We have over 70 scanner models in our test lab and we are constantly updating our test scanners as manufacturers release new models.

6. See also the Minimum PC specs for an EzeScan workstation.

Direct link to FAQ

Please make sure that you correctly setup the DCOM settings for the TRIMMaster, TRIMWorkgroup, TRIMEvent processes as per the instructions on pages 27-41 of the TRIM Context Install Guide.  One possible workaround is to make sure that the TRIM application has already been launched on the EzeScan PC.

Direct link to FAQ

Applies to: EzeScan 4.3.60 and above

If there is a requirement to have EzeScan run a spell check on words outside of the standard dictionary it is possible to add these words into one of them.

You can create a new custom dictionary by using an existing dictionary (e.g. US/UK) and adding words to it by following the steps below:

  1. Admin -> Spelling Dictionaries - Select an dictionary and click export
  2. Select a location and press save
  3. Open the document in notepad (note the syntax)
  4. Open your custom words from your other source and copy them onto the bottom of this document and then save and close the file.
  5. Admin -> Spelling Dictionaries - Select Custom and click Import
  6. Browse to your new file and select it. Click ok on the message to overwrite the dictionary.

To enable from KFI

  1. Admin -> KFI -> Fields Tab -> Edit on your field -> Automation Tab
  2. For the setting Spell check input data using dictionary -> Set to custom
  3. Click OK, apply and OK

When you run the job the value in the field will be checked against the dictionary.


Direct link to FAQ

This is most likely because you have unticked the "Use ADF" option which sets the "Pages To Scan" value to 1 page at a time. Simply tick the "Use ADF" option and make sure that "Pages To Scan" value is set to a value greater than 1.

Direct link to FAQ

First you might like to take a look at the following web site articles:

Here are some useful suggestions:

  • Barcodes could be applied using pre printed labels, or printed on documents at 600 dpi on a laser printer. Printing them on poor quality paper or on a bubble jet would be a definite no no. Any ink bleed between vertical lines in the barcode will cause problems.
  • A barcode printed using a small font will have a problem when scanned because the white space between the black lines becomes harder to see. If the lines look like they  are touching each other in the scanned image, the recognition will most likely fail. Using  a larger font or point size can help to spread the lines out in the barcode. Fine barcodes should be scanned at a minimum of 300 dpi, 400 dpi would be better but the resulting large image size may slow the process down too much. It's best to start with a large fort that works and gradually decrease it's size until it doesn't, and then increase the size back up 1 or 2 sizes from that failure point.
  • What font is best?. No easy answer here. Depends on how much data you want to put in the barcode, and what software tools you have purchased to produce your barcodes. It looks like code 3 of 9 is a reasonable choice, but EAN 8/13 could be better. An important factor is that you should use a barcode that is designed for that industry segment or packaging requirement.
  • If the barcode doesn't work you will need to increase the font size up to 24 or 26 point to get it to work okay.
  • If the barcodes are poor quality then you must specify the barcode type on the Profiling Tab within EzeScan. You must not try to use UNKNOWN type when running the job in production. The UNKNOWN option is normally used to just help identify what type of barcodes are being read. Once this is determined the barcode type should be set to that specific type.
  • If you are using 3 of 9 barcodes did you remember to add the "*" character to the start and end of the value you are putting in the barcode? For example let's say your barcode value is "123456789",  then the value placed in the barcode label is actually "*123456789*". The start and end "*" characters are required by the barcode recognition engine, but they are discarded from the returned value of "123456789". These characters are not normally required when using other barcode types.
Direct link to FAQ

The most likely cause of this problem is that the EzeScan DWORD entry is missing from the HKEY_CURRENT_USERS\Software\Xerox\DocuShare Client\DsOdma\SupportedEditors registry key. Simply use regedit to add a DWORD named "EzeScan" and sets it's value = 1.

Direct link to FAQ

1. The Audit database is only active if you are licensed for the AUDIT module and your job/route has "Update Audit Database' set.

2. As of 4.0.844 It contains 3 tables (Note: the Jobtype_Statistics table is no longer used/written to)

[Completed_Work] with the following columns in it:

  • ID (AutoNumber)
  • Date_Time (DateTime)
  • Module_Type (Text)
  • Job_Type (Text)
  • Other_Destination (Text)
  • Input_Filename (Text)
  • Input_Directory (Text)
  • Output_Filename (Text)
  • Output_Directory (Text)
  • Output_Email_Address (Text)
  • Output_FtpServer_Address (Text)
  • Output_File_Format (Text)
  • Output_File_Size (Number)
  • Number_Of_Pages (Number)
  • Elapsed_Time (Number)
  • Routing_Rulename (Text)
  • Processed_By (Text)
  • KFI_Index_File (Text)
  • KFI_Index_File2 (Text)
  • Key_Strokes (Number)
  • Workstation_Name (Text)
  • Operator Name (Text)
  • Zone_Errors (Number)
  • Scanner_Settings (Text)
  • Enhancement_Settings (Text)

[Current_Work] with the following columns in it:

  • ID (AutoNumber)
  • Job_Type (Text)
  • Module_Type (Text)
  • Job_Type (Text)
  • Workstation_Name (Text)
  • Operator_Name (Text)
  • Date_Time (DateTime)

[Deleted_Work] with the following columns in it:

  • ID (AutoNumber)
  • Job_Type (Text)
  • Module_Type (Text)
  • Job_Type (Text)
  • Workstation_Name (Text)
  • Operator_Name (Text)
  • Date_Time (DateTime)

3. When Ezescan is installed the default Admin-Options form, Audit database settings are set to use a local copy of the Ezescan_Audit MS Access database. 

4. If you want to use a centralised Audit Database with several Ezescan workstations you could simply place the Ezescan_Audit MS Access database file (Ezescan_Audit.mdb) onto a network shared drive, and then configure each of the PC's Admin->Options, Audit tab settings to use that network shared database file.  This is only recommend for low volume usage, with a small number of Ezescan PC's.

5. If there a large number of Ezescan PC's then a better option, would be to create an Audit database on a networked MS SQL Server and then configure the EzeScan Audit Database ODBC connection to use that database rather than the local or network shared EzeScan_Audit.mdb file. FAQ #55 provides information on how to do this.

Direct link to FAQ