Subscribe

UiPath Document Understanding

UiPath Document Understanding

OCR Engines

An OCR Engine is used in the Digitization component, to identify text in a file, when native content is not available.

📘

Note:

The images that need to be processed should have a resolution range of:

  • min: 50 x 50 MP
  • max: 9000 x 9000 MP

Here is a selection of OCR Engines that you can choose from, according to your needs, throughout the Document Understanding Framework.

OCR EngineActivity PackDebug Logs Format in Logs FolderReports Confidence
UiPath Document OCRUiPath.OCR.Activities${date:format=yyyy-MM-dd}_Vision_UiPathOCRActivitiesHost.json
OmniPage OCRUiPath.OmniPage.Activities${date:format=yyyy-MM-dd}_Vision_VisionOmniPageHost.json
Google Cloud Vision OCRUiPath.UIAutomation.Activities${date:format=yyyy-MM-dd}_VisionHost.json if DetectionMode is set to TextDetection (default)
if DetectionMode is set to DocumentTextDetection
Microsoft Azure Computer Vision OCRUiPath.UIAutomation.Activities${date:format=yyyy-MM-dd}_VisionHost.json if UseReadAPI is not selected (default)
if UseReadAPI is selected
Microsoft OCRUiPath.UIAutomation.Activities${date:format=yyyy-MM-dd}_VisionHost.json
Tesseract OCRUiPath.UIAutomation.Activities${date:format=yyyy-MM-dd}_VisionHost.json
Abbyy Document OCRUiPath.AbbyyEmbedded.Activities${date:format=yyyy-MM-dd}_AbbyyEmbeddedHost.json

📘

Note:

When debugging errors, you can always visit the logs folder and check the relevant OCR log files. Read more about logging here.

🚧

Warning:

Abbyy OCR and Abbyy Cloud OCR are not available in Document Understanding wizards.

Updated about a year ago


OCR Engines


Suggested Edits are limited on API Reference Pages

You can only suggest edits to Markdown body content, but not to the API spec.