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.

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

OCR Engine

Activity Pack

Debug Logs Format in Logs Folder

Reports Confidence

UiPath Document OCR

UiPath.OCR.Activities

${date:format=yyyy-MM-dd}_Vision_UiPathOCRActivitiesHost.json

ImageImage

OmniPage OCR

UiPath.OmniPage.Activities

${date:format=yyyy-MM-dd}_Vision_VisionOmniPageHost.json

ImageImage

Google Cloud Vision OCR

UiPath.UIAutomation.Activities

${date:format=yyyy-MM-dd}_VisionHost.json

no_rightno_right if DetectionMode is set to TextDetection (default)
ImageImage if DetectionMode is set to DocumentTextDetection

Microsoft Azure Computer Vision OCR

UiPath.UIAutomation.Activities

${date:format=yyyy-MM-dd}_VisionHost.json

no_rightno_right if UseReadAPI is not selected (default)
ImageImage if UseReadAPI is selected

Microsoft OCR

UiPath.UIAutomation.Activities

${date:format=yyyy-MM-dd}_VisionHost.json

no_rightno_right

Tesseract OCR

UiPath.UIAutomation.Activities

${date:format=yyyy-MM-dd}_VisionHost.json

ImageImage

Abbyy Document OCR

UiPath.AbbyyEmbedded.Activities

${date:format=yyyy-MM-dd}_AbbyyEmbeddedHost.json

ImageImage

📘

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 month 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.