Chinese Simplified (简体中文)

System Requirements

ABBYY FineReader Engine 12 Requirements

Hardware

  • PC with x86-compatible processor (1 GHz or higher)
  • Memory:
    • for processing one-page documents — minimum 400 MB RAM, recommended 1 GB RAM
    • for processing multi-page documents — minimum 1 GB RAM, recommended 1,5 GB RAM
    • for parallel processing — 450 + (number of cores) × 350 MB RAM
    • for parallel processing of documents in Arabic or CJK languages — 750 + (number of cores) × 850 MB RAM
  • Hard disk space:
    • for library installation:
      • 1600 MB for core functionality
      • additional 400 MB for the OfficeConverters module
    • for program operation:
      • 100 MB for running the program
      • additional 15Mb for every page when processing a multi-page document
  • 100% TWAIN-compatible scanner, digital camera, or fax modem — for scanning or image import only
  • Video card and monitor (minimum resolution 1024×768 — for pattern training, dictionary editing, scanning with a GUI displayed, Visual Components)
  • Keyboard, mouse or other input device

Operating system

  • Windows Server 2022
  • Windows Server 2019
  • Windows Server 2016
  • Windows 11
  • Windows 10
  • Windows Server 2012 R2 with the April 2014 update rollup (KB2919355)
  • Windows 8.1 with the April 2014 update rollup (KB2919355)
  • Windows Server 2012

ABBYY FineReader Engine has been tested on the following cloud computing platforms:

  • Microsoft Azure:
    • Azure App Services
    • Azure Cloud Services
    • Azure Service Fabric
    • Azure Virtual Machines
  • Amazon EC2

ABBYY FineReader Engine has been tested in the following virtual environments:

  • Microsoft Hyper-V Server 2012
  • Microsoft Hyper-V Server 2012 R2
  • Microsoft Hyper-V Server 2016
  • Oracle VM VirtualBox 6.1.32
  • Parallels Desktop for Mac 16.1.3
  • VMware ESXi 6.7
  • VMware Workstation Player 16.2.3
  • VMware Workstation Pro 16.2.2

ABBYY FineReader Engine can also be run in a Docker container on supported platforms.

Other software components

ABBYY FineReader Engine installer uses Windows Installer XML Toolset (WiX), that requires .NET Framework for its operation:

  • For Developer installation:
    • .NET Framework 4.6.1 and above is required
  • For Runtime installation:
    • automatic installation - .NET Framework 4.6.1 and above is required
    • manual installation with the OfficeConverters module - .NET Framework 4.5 and above is required
    • manual installation without the OfficeConverters module - .NET Framework is not required

The following versions of .NET Framework are supported:

  • 4.8, 4.7, 4.6, 4.5, 4.0, 3.5

The following components should be installed:

  • Microsoft® Internet Explorer 8.0 or higher
  • .NET Framework 4.5 — required for opening digital documents

For correct operation of the font detection mechanism the fonts needed for the languages you use should be installed; for the list of recommended font families see FontNamesFiltersEnum.

For ABBYY FineReader Engine Visual Components only:

  • Microsoft Windows Common Controls must have version 6.0 or later
  • If you use Microsoft Visual Studio 2010 and .NET Framework 4.0 for development of your application, you may need to install COM Interop assemblies for Visual Components manually. Refer to Using Visual Components in Different Versions of Visual Studio for details.

Working with the .NET Core wrapper

ABBYY FineReader Engine .NET Core wrapper supports working with the following versions of .NET Core:

  • 3.1

Working with the Java wrapper

ABBYY FineReader Engine Java wrapper has been tested on the following Java Development Kits:

  • for 32-bit operating systems:
    • Oracle Java SE Development Kit 8u331 x86
  • for 64-bit operating systems:
    • Open JDK 17.0.2 x64
    • Open JDK 18.0.1 x64
    • Oracle Java SE Development Kit 8u331 x64
    • Oracle Java SE Development Kit 11.0.15 (LTS) x64
    • Oracle Java SE Development Kit 17.0.3 x64
    • Oracle Java SE Development Kit 18.0.1 x64

Permissions

Full control permissions for the following folders are required:

  • %TEMP% folder
  • folder %ProgramData%\ABBYY\SDK\12\FineReader Engine
  • folder %ProgramData%\ABBYY\SDK\12\Licenses (required for license server, optional for workstations)

All users running your application should have read&execute and write permissions to:

  • %ProgramData%\ABBYY folder.

The following registry branches should be accessible from the workstation:

  • "HKEY_CURRENT_USER\Software\ABBYY\SDK\12\FineReader Engine" — full control
  • "HKEY_CURRENT_USER\Software\ABBYY\SDK\12" — full control for installation only
  • "HKEY_LOCAL_MACHINE\Software\ABBYY\SDK\12" — full control for installation only

ABBYY SDK 12 Licensing Service Requirements

  • PC with x86-compatible processor (1 GHz or higher)
  • Operating system:
    • Windows Server 2022
    • Windows Server 2019
    • Windows Server 2016
    • Windows 11
    • Windows 10
    • Windows Server 2012 R2 with the April 2014 update rollup (KB2919355)
    • Windows 8.1 with the April 2014 update rollup (KB2919355)
    • Windows Server 2012

ABBYY SDK 12 Licensing Service has been tested in the following virtual environments:

    • Microsoft Hyper-V Server 2012
    • Microsoft Hyper-V Server 2012 R2
    • Microsoft Hyper-V Server 2016
    • Oracle VM VirtualBox 6.1.32
    • Parallels Desktop for Mac 16.1.3
    • VMware ESXi 6.7
    • VMware Workstation Player 16.2.3
    • VMware Workstation Pro 16.2.2
  • 25 MB of free hard disk space
  • Full control access to a folder with licensing information (%ProgramData%\ABBYY\SDK\12\Licenses folder by default)
  • For activation/deactivation of the License:
    • allowed connections to *.abbyy.com
    • port: 80 (except Online License), 443 (HTTPS)
    • protocol: http
    • GoDaddy Trusted Root Certification Authority (for Online License only)

24.03.2023 8:51:52

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 Privacy Notice.