ABBYY Mobile OCR Engine 4.0

System Requirements

Operating Systems

The Mobile OCR Engine SDK is a cross-platform technology and supports the following operating systems:

ABBYY offers professional services to port the software to other platforms and to customize the software for special tasks.

Memory requirements

ABBYY Mobile OCR Engine is a compact code OCR solution and requires minimal memory resources.

  European languages Korean Chinese & Japanese
Library (RAM), MB From 5 to 7* From 5 to 7* From 5 to 7*
Patterns (RAM or ROM)*, MB 1.64 From 1.37 to 5.23 11.5
Keywords (RAM or ROM)*, MB 1.56 0.113 0.869
Dictionaries (RAM or ROM)*, MB 14.4 N\A N\A

* Exact memory requirements vary depending on the operating system and specific recognition tasks (e.g., multilingual recognition requires more memory).

The library itself is almost always placed in RAM (some platforms allow direct operation from the storage memory).

Patterns, keywords, and dictionaries are to be placed in ROM though some (rare) platforms may require loading them to RAM. European patterns should always be included, while other patterns — depend on the required languages. Dictionaries are optional components and could be excluded, but in this case recognition quality will be decreased. Keywords are necessary only for business card recognition.

Full-text Recognition Languages

Business Card Recognition Languages

Barcode Recognition

Supported barcode formats include 1d and 2d:

1D (linear)

Code 39

Interleaved 2 of 5


Code 128




Industrial 2 of 5

IATA 2 of 5

Matrix 2 of 5

Code 93











Knowledge Base

All topics


All recent products have built-in update system.
To update product: Select the Help › Check for update menu item.

All Updates

ABBYY Mobile OCR Engine
ABBYY Mobile Imaging SDK
ABBYY Real-Time Recognition SDK
Usage of Cookies. In order to optimize the website functionality and improve your online experience ABBYY uses cookies. You agree to the usage of cookies when you continue using this site. Further details can be found in our Cookie Policy.