Mobile OCR Engine

  • ABBYY Mobile OCR Engine will reach End of Sales as of 12/31/2018.
    • ABBYY will no longer offer new developer licenses of Mobile OCR Engine.
    • Existing customers will still have the possibility to purchase additional runtime licenses.
    • ABBYY will still provide technical support for customers, which have a valid Software Maintenance and Upgrade Agreement (SMUA).
  • ABBYY Mobile OCR Engine will reach End of Life as of 12/31/2019.
    • No runtime licenses
    • No technical support.
  • If you are looking for a mobile capture solution similar to Mobile OCR Engine, we recommend you to try ABBYY’s Real-Time Recognition SDK which provides advanced technology and usability for your mobile capture needs.
  • Development for Mobile Platforms
    Desktop and server OCR have been established for quite some time. ABBYY Mobile OCR Engine, allows developers to integrate text recognition on mobile devices. The SDK has been designed especially for the mobile platform and enables the development for a large spectrum of applications.

  • Mobile applications that have ABBYY OCR inside are able to transform digital images of
    • documents
    • notes
    • newspaper clippings
    • business cards
    • timetables
    • menus and other text taken with a built-in camera
  • Mobile Developers can “pimp” their existing mobile apps and use the OCRed data within their own applications. This way OCR
    • reduces manual text/data input by the user
    • generates a new usability of the app
    • opens a new way of dealing with information
    • ultimately the application delivers more value for users, therefore developers can charge more for it ;o)
  • ABBYY first premiered the small code-sized version (V1.0) of its toolkit in 1999 when the technology was integrated into the C-Pen, a small hand-held pen scanner. OCR implementation in the C-Pen required less than 2 MB of disk space and was combined with the ABBYY Lingvo Russian-English dictionary.

Processing Overview

Binarisation is always executed before the character recognition

  • Original
  • Binary - Black/White Result

Requirements & Recommendations

  • To enable the OCR SDK to deliver usable results, the device should have an auto focus lens with more than 3 mega pixel
    (as usual: more = better)
  • These devices normally have CPUs with more than 500 MHz.
    (as usual: faster = better)
  • Memory:
    Exact memory requirements vary depending on the operating system and specific recognition tasks (e.g. multilingual recognition requires more memory).
    • OCR of Latin and Cyrillic characters: 8 MB ROM, 10 MB RAM;
    • Chinese and Japanese OCR: 14 MB ROM, 22 MB RAM;
    • Korean OCR: 18 MB ROM, 28 MB RAM.

Technical Specifications

Different versions of Mobile OCR Engine

Mobile OCR technology is already available for several years and the importance for light OCR technology is increasing with the growing market of smart phones.

FineReader Engine for the most operating systems is already available for 2 technology cycles :

Mobile OCR Engine for Mobile Technology Cycle CPU Types supported
Android V3, V4 ARM
iOS V3, V4 ARM
MacOS1) V4 x86
Windows2) V2, V3, V4 x86
MSDK for Propriety OS3) on request ARM, x86, porting on request
Discontinued Operating Systems
Symbian V2, V3, V4 ARM
Windows Mobile V2, V3, V4 ARM
Linux4) V2, V3, V4 ARM, x86
Bada not developed any more ARM

For current availability of Mobile OCR SDK for a specific OS please check further information under the particular OS in table above.

Further Information

1) , 2) , 3) , 4) Contact ABBYY to discuss your project
This website uses cookies which enable you to see pages or use other functions of our websites. You can turn off such cookies in your browser’s settings. If you continue to use these pages, you consent to the use of cookies.