Scanbot SDK
Commercial on-device SDK for mobile scanning, barcodes and data capture.
Operated by Apryse
Opens the vendor's own site.
Jobs covered
Open a task to see exactly what the vendor documentation supports.
OCR
Browse all ocr toolsrunning optical character recognition with the Scanbot SDK, where the vendor's documentation for the OCR module of the Data Capture Modules, version 10.0.0 on Android, iOS, web, Linux and Windows Server, says the OCR engine turns written text into machine-readable data from still images and a live camera stream and is the backbone of the Data Capture Modules; the results are recognised text as plain text, bounding boxes of recognised paragraphs, lines and words, and text and confidence values for each box; Android exposes OcrEngineManager with the Scanbot OCR engine and an optional Tesseract engine enabled through EngineMode.TESSERACT and the optional io.scanbot:sdk-ocr-tesseract dependency, with Tesseract language data supplied as .traineddata files plus osd.traineddata and no language files bundled in the SDK; iOS offers a legacy Tesseract-based engine for non-Latin languages such as Arabic, Japanese, Chinese, Russian, Greek and Korean and a machine-learning engine that is faster and more accurate but supports only Latin-script languages and needs no language training data, with an optional OCR data bundle containing English and German examples; the web module returns the same text, bounding-box and confidence results for images and live camera frames; the built-in PDF generator can be combined with the OCR module to create searchable PDF files from a Document object or from image files using PdfConfiguration defaults; the pages give no accuracy figures or supported-language counts beyond naming the engines and their language families, and no hosted OCR is claimed, with the vendor's own documentation stating that the SDK works completely offline and contains no networking code
Where your files are processed
Your own instance
This runs on a server you operate rather than on your own device: Windows Server, Linux. Documents do not reach a server the vendor runs, and they do not stay in your browser either. That is a property of the library itself: what an application built with it does with your file depends on that application, not on this.
It is an SDK, so the scanning and recognition run inside the application that embeds it, on the device or on a server depending on the edition. The vendor announced Linux Barcode and Document Scanner SDKs in January 2026 alongside the mobile and web editions, so a customer-controlled server deployment is a documented option rather than a hypothetical.
That is not the same as a ready-made hosted app, and it is not a statement that every result stays on an end user’s device: the current vendor material describes configurable routing to server workflows, so the destinations follow from the configuration.
What it does
A developer kit that app makers embed to add document scanning, barcode scanning and structured data extraction to their own iOS, Android or web apps. The document scanner handles automatic capture, cropping, perspective correction, filters, quality scoring and JPG, PDF or TIFF export, while the data capture modules add OCR, machine-readable travel documents, VIN, credit card, cheque and German medical-certificate extraction.
Processing runs in the integrator's own app, browser, Windows Server or Linux deployment, with the vendor documenting that the SDK works completely offline and contains no networking code, and it is licensed per app or web domain for a fixed annual fee.
Best for
Product teams building scanning or data capture into their own mobile or web app who need a licensed, offline, on-device component rather than an end-user app.
Worth knowing
No published price list - the site routes to sales, and cost depends on the number of apps or domains and which feature set you license. It is a component, not an application: no viewer, editor or redaction module of its own, and PDF editing and signing are pointed at the wider Apryse SDK family.
Deployment is not one thing here: mobile, web, Linux and Windows Server editions have their own capabilities and their own licensing, and the per-app or per-domain fees describe the licences they were quoted for rather than extending to a server edition. Not every scanning module is OCR, so the module in use determines whether OCR applies at all.
Details, and where each comes from
Vendor statements, our own reading of their pages, and the things nobody has established yet, each answered separately. Where we have not confirmed something it says so rather than guessing, and a row nobody has established is greyed out.
- Versions covered
- Android · iOS · Web · Windows · Linux
- Website
- scanbot.io
- Requires an account
- Not applicable
- Free tier
- No
- Watermark on trial output
- Not verified
- Maximum file size
- Not verified
- Batch processing
- Not verified
- Data residency
- Not verified
- Open source
- No
- Self-hostable
- Yes
- Licence
- commercial, annual per-app or per-domain licence
- Redaction
- No redaction feature
- Programmatic access
- Embeddable library
- Last availability check
- Responded in 703 ms 21 October 2026
Checked automatically by our own runner, not reported by the vendor. 100% of our last 30 checks got a response.
What the redaction verdict rests on
From the vendor's own documentation, read 22 September 2026. Not tested by us.
What that does not establish
The vendor’s own site was read on 22 September 2026 and contains no mention of redaction, sanitisation, blackout or whiteout. Absence from a vendor’s own material is not proof that a feature does not exist - it may be undocumented, or on a page the reading did not reach - but for a NEGATIVE claim it is the strongest evidence available, and it is weaker than a positive quote.
Recorded as such rather than presented as certainty.
What the vendor says
Claims are labelled rather than repeated as fact. Where we have checked something ourselves, it says so and shows when. Checked means we read the vendor's own page and it says what we recorded - not that we tested the behaviour, unless the note says we did.
-
“The Scanbot SDK works completely offline. It does not even contain any networking code.”
Checked by us - the source says this Read 22 September 2026
Confirmed verbatim, and the vendor then does something no other claim in this campaign has: it tells the reader how to check. "This can easily be verified by routing all networking traffic coming from the app through a proxy." That is a testable claim, stated with its own test, and it is the strongest local-processing assertion in the index after PAC's.
Our locality instrument drives browsers rather than Android applications, so the suggested verification is not one we can currently run - but the claim is the kind that could be settled by observation rather than by reading, and the vendor says so first.
Standing: Re-read and matched byte for byte
Check it yourself: the source, the SHA-256, and how we checked
- From
- the text a browser renders
- SHA-256
- 54f4c089ec4ea0d30e8eefb1e52ce552377411d57e76856ee845b14e0de77761
How we checked
Re-verified verbatim on 2026-09-22: https://docs.scanbot.io/document-scanner-sdk/android/introduction/ re-rendered in headless Chrome with scripts/render-page.mjs and the claim's wording found in the rendered text. Originally verified on 2026-09-21. sourceHash is the SHA-256 of the re-rendered text, held as rv-docs-scanbot-io-document-scanner-sdk-android-introduction-4703d932.txt.
-
“The Scanbot SDK comes at a simple, predictable annual license fee.”
Checked by us - the source says this Read 22 September 2026
Confirmed verbatim: the FAQ opens with the sentence exactly. "Simple and predictable" is the vendor's framing, and the page then explains the mechanics behind it, which is more useful: the fee is set by two factors - the number of mobile apps or web domains integrating the SDK, and the feature set chosen from Document Scanning, Barcode Scanning or Data Extraction - there are deliberately no tiers, and the licence is all-inclusive with unlimited scans, users and device installations and no increase with usage.
So the claim's word "predictable" rests on a stated pricing model rather than on an assertion, which is unusual and worth recording. No price figure appears on the page, and none was sought.
Standing: Re-read and matched byte for byte
Check it yourself: the source, the SHA-256, and how we checked
- From
- the text a browser renders
- SHA-256
- 9e5b4ee3a2b18a12f1f65328c1303370ad03ae9b880956a74ddb9f02a1f79f67
How we checked
Re-verified verbatim on 2026-09-22: https://docs.scanbot.io/faq/pricing-and-licensing-model/ re-rendered in headless Chrome with scripts/render-page.mjs and the claim's wording found in the rendered text. Originally verified on 2026-09-21. sourceHash is the SHA-256 of the re-rendered text, held as rv-docs-scanbot-io-faq-pricing-and-licensing-model-1b56aa74.txt.
Each claim is quoted from the vendor's own pages. This section describes what we have and have not checked - it is not a judgement about anyone.
Sponsorship is distribution, not an endorsement or a promise of search rankings, AI citations, traffic, or sales. This listing is a free entry, compiled from published sources.