# AWS Textract vs DocsAPI: Honest 2026 Comparison

> AWS Textract pricing per 1,000 pages for every API, its real limits (6 languages, 1-page sync PDFs), and when Textract or DocsAPI fits better. Checked 2026.

**In short:** Pick AWS Textract if you already run on AWS and read English or Western European forms, receipts or US IDs; plain OCR costs $1.50 per 1,000 pages. Pick a document API like DocsAPI when you need multi-page statement tables joined and fields returned in one call.

**Canonical URL:** https://docsapi.co/resources/blogs/aws-textract-vs-docsapi
**Author:** Nupura Ughade — Content Marketing Lead, DocsAPI
**Author LinkedIn:** https://www.linkedin.com/in/nupura-ughade/
**Published:** 2026-06-17T00:00:00.000Z
**Updated:** October 12, 2026
**Primary topic:** aws textract
**Site:** https://docsapi.co (DocsAPI — Document AI & OCR API for SMB Lending)

---

AWS Textract is cheap for plain text ($1.50 per 1,000 pages) and gets expensive once you turn on forms ($50 per 1,000). It reads six languages, handles handwriting only in English, and needs an asynchronous job for any PDF over one page.

## Should you use AWS Textract or DocsAPI?

Use Textract if your stack is on AWS and your documents are English or Western European forms, receipts or US IDs. Use DocsAPI if you need document classification and named fields in one call, and bank statement or invoice tables joined across pages. Disclosure: DocsAPI is our product, so test both on your own documents.

| Dimension | AWS Textract | DocsAPI |
| --- | --- | --- |
| What it is | AWS managed service with separate APIs for text, forms, tables, queries, expenses, IDs and mortgage documents | Standalone document API: classification, field extraction and validation |
| Plain OCR price | $1.50 per 1,000 pages (first million a month) | Per page, from $0.02, tables and classification included |
| Tables | $15 per 1,000 pages, returned page by page | Included; tables that run across pages are joined into one |
| Forms (key-value pairs) | $50 per 1,000 pages | Included for supported document types |
| Languages | English, French, German, Italian, Portuguese, Spanish | Major commercial languages; test yours |
| Multi-page PDFs | Asynchronous job (synchronous calls take 1 page) | Whole document per request |
| ID documents | AnalyzeID: US passports and US driver's licenses only | ID documents supported; test your countries |
| Free tier | 3 months: 1,000 text pages and 100 forms or tables pages a month | Free 30-day trial for qualified lenders, after a demo |
| Best fit | AWS-native teams, forms, receipts, US IDs, mortgage packages | Lending and fintech documents, multi-page statements and invoices |

## How much does AWS Textract cost per 1,000 pages?

Textract charges per page, with a lower rate after the first million pages a month. Plain text detection costs $1.50 per 1,000 pages ($0.0015 a page), tables $15, forms $50, queries $15, layout $4, receipts and invoices $10, and US IDs $25. The prices below are AWS's own list prices for US West (Oregon), taken from AWS's price list on September 28, 2026.

| Textract API or feature | Per 1,000 pages, first 1M a month | Per 1,000 pages, above 1M | Per page, first tier |
| --- | --- | --- | --- |
| DetectDocumentText (plain OCR, printed and handwritten) | $1.50 | $0.60 | $0.0015 |
| AnalyzeDocument: Layout | $4 | $3 | $0.004 |
| AnalyzeDocument: Signatures | $3.50 | $1.40 | $0.0035 |
| AnalyzeDocument: Tables | $15 | $10 | $0.015 |
| AnalyzeDocument: Queries | $15 | $10 | $0.015 |
| AnalyzeDocument: Queries and Tables | $20 | $15 | $0.02 |
| AnalyzeDocument: Custom Queries (trained adapter) | $25 | $15 | $0.025 |
| AnalyzeDocument: Forms | $50 | $40 | $0.05 |
| AnalyzeDocument: Forms and Queries | $55 | $45 | $0.055 |
| AnalyzeDocument: Forms, Queries and Tables | $70 | $55 | $0.07 |
| AnalyzeExpense (invoices and receipts) | $10 | $8 | $0.01 |
| AnalyzeID (US passports and driver's licenses) | $25 (first 100,000 pages) | $10 (above 100,000) | $0.025 |
| AnalyzeLending (mortgage packages) | $70 | $55 | $0.07 |

The free tier lasts three months for new AWS customers: 1,000 pages a month of text detection, 100 pages a month of forms, tables or layout, 100 of AnalyzeExpense, 100 of AnalyzeID and 2,000 of AnalyzeLending. Prices differ slightly by AWS region, so check the region you will run in.

### What Textract costs at 100,000 pages a month

The same prices as monthly bills, so you can see which feature drives the cost. All of these stay in the first-million price tier.

| What you run on 100,000 pages | Math | Monthly cost |
| --- | --- | --- |
| Plain text only (DetectDocumentText) | 100 x $1.50 | $150 |
| Layout | 100 x $4 | $400 |
| Receipts or invoices (AnalyzeExpense) | 100 x $10 | $1,000 |
| Tables | 100 x $15 | $1,500 |
| Queries and Tables | 100 x $20 | $2,000 |
| US IDs (AnalyzeID) | 100,000 x $0.025 | $2,500 |
| Forms | 100 x $50 | $5,000 |
| Forms and Tables together | 100 x ($50 + $15) | $6,500 |
| Mortgage packages (AnalyzeLending) | 100 x $70 | $7,000 |
| DocsAPI, for comparison (our product) | 100,000 x $0.02 | $2,000 before volume discounts |

If you only need text, Textract is far cheaper than any document API. If you need forms on every page, Textract can cost more than a specialized API. And above a million pages the second tier kicks in: 2 million pages of plain text cost 1,000 x $1.50 + 1,000 x $0.60 = $2,100 a month. For how per-page, per-document and subscription pricing compare across vendors, see our [invoice OCR pricing guide](/resources/blogs/invoice-ocr-pricing-models) and [bank statement OCR pricing guide](/resources/blogs/bank-statement-ocr-pricing).

## Which Textract API do you need?

There are five Textract APIs, not one, and each Amazon Textract API call is billed per page. DetectDocumentText returns text and handwriting. AnalyzeDocument adds forms, tables, layout, signatures and queries. AnalyzeExpense reads invoices and receipts. AnalyzeID reads US passports and driver's licenses. AnalyzeLending classifies and extracts mortgage application documents. You pay for each feature you switch on.

| Textract API | What it returns | Use it for |
| --- | --- | --- |
| DetectDocumentText | Lines and words with positions and confidence | Search, archives, feeding text to your own parser |
| AnalyzeDocument | Key-value pairs (forms), tables, layout blocks, signatures, answers to questions you ask (queries) | Applications, tax forms, contracts, any form with labels |
| AnalyzeExpense | Vendor, totals, dates and line items | Invoices and receipts |
| AnalyzeID | Name, date of birth, expiry and other ID fields | US passports and US driver's licenses only |
| AnalyzeLending | Page classification, splitting and extraction | Mortgage application packages |

Queries let you ask for a field in plain English, such as "What is the account number?", and get the answer back. They are limited to 15 per page on synchronous calls and 30 on asynchronous calls, and they only work on English documents. If invoices are your main job, our [invoice OCR API comparison](/resources/blogs/invoice-ocr-api) maps AnalyzeExpense's field names against Azure, Google and Mindee.

## What are AWS Textract's limits?

The main limits: only six languages (English, French, German, Italian, Portuguese, Spanish), handwriting only in English, no vertical text, and synchronous calls that accept just one page of a PDF or TIFF. Multi-page PDFs must go through the asynchronous AWS Textract API, up to 3,000 pages and 500 MB per file.

| Limit | What AWS documents | What it means for you |
| --- | --- | --- |
| Languages | English, French, German, Italian, Portuguese, Spanish; the detected language is not returned | Chinese, Arabic, Hindi or Japanese documents need another engine |
| Handwriting | English only | Handwritten forms in other languages will not read well |
| Synchronous calls | 10 MB; PDF and TIFF limited to 1 page | A 5-page bank statement needs the async API |
| Asynchronous calls | PDF and TIFF up to 500 MB and 3,000 pages | You start a job, then poll or wait for a notification |
| Smallest text | 15 pixels high (8 point at 150 DPI) | Scan fine print at 300 DPI |
| File types | JPEG, PNG, PDF, TIFF; no XFA PDFs or password-protected PDFs | Convert other formats first |
| AnalyzeID | US passports and US driver's licenses only | Non-US IDs need another service |

## Where AWS Textract is the better choice

- You live on AWS. Documents already sit in S3, access runs through IAM, and billing is on one invoice. Adding an outside vendor has a real cost in security reviews and procurement.
- You only need text. At $1.50 per 1,000 pages (and $0.60 above a million), plain text detection is hard to beat for a managed service.
- Forms with clear labels and boxes. Government forms, applications and tax forms with printed labels suit AnalyzeDocument's key-value extraction.
- US IDs and mortgage packages. AnalyzeID and AnalyzeLending are purpose-built for those two jobs.
- Compliance inheritance. If your compliance program already covers AWS, Textract sits inside it. Check that the region and service are on AWS's list for the rules you follow.

## Where AWS Textract falls short

- Tables that run across pages. Textract returns tables page by page, so a bank statement whose transaction table runs over 12 pages comes back as 12 tables your code must join, including repeated headers and rows split at page breaks. Our PDF parser guide shows this failure in detail, and our bank statement OCR guide covers the checks you need after joining.
- Languages. Six languages is narrow next to Tesseract's 100-plus. If you receive documents from Asia, the Middle East or India, Textract alone will not cover them.
- Forms pricing at volume. Forms cost 33 times more than plain text ($50 against $1.50 per 1,000 pages). Switch forms on only for the pages that need it.
- Async for any multi-page PDF. Because synchronous calls take one page, real-time flows on multi-page files need a job, a wait and a result fetch.
- No document classification in the general API. Outside AnalyzeLending, you tell Textract what to run; deciding whether a file is a pay stub or a bank statement is your code's job.

## Where DocsAPI is the better choice, and where it is not

DocsAPI (our product) classifies each document, extracts named fields as JSON and joins tables across pages, with tables and classification included in the per-page price. That suits lending, fintech and accounts payable teams processing bank statements, pay stubs, invoices and IDs.

- Better for: mixed document packets where you do not know the type in advance, multi-page statement and invoice tables, teams not on AWS, and teams that want one price per page instead of per feature. Qualified lenders get a free 30-day trial after a demo, and DocsAPI is SOC 2 Type II and ISO 27001 certified and HIPAA-eligible with a business associate agreement.
- Not better for: plain text at the lowest possible price (Textract's $0.0015 a page wins), teams that need everything on one AWS bill, and research papers or scientific PDFs, where tools like Docling fit better (see our Docling vs LlamaParse comparison). It is a cloud API, so it cannot run air-gapped.

## AWS Textract vs Tesseract: which should you use?

Use Tesseract when you need free, offline OCR of clean printed text in any of 100-plus languages. Use Textract when you want a managed service that also returns forms, tables, receipts and US ID fields, and your documents are in one of its six languages. Tesseract returns text only, and you run and scale it yourself.

On hard images such as phone photos and faded receipts, Tesseract makes more errors than modern deep-learning engines; in our [PaddleOCR vs Tesseract test](/resources/blogs/paddleocr-vs-tesseract-vs-docsapi) it lost a receipt total. If you like open source but need better accuracy on messy images, PaddleOCR is the engine to compare against Textract, not Tesseract.

## How does Textract compare to Google Document AI and Azure?

AWS OCR pricing matches Google and Azure for plain text: all three clouds charge $1.50 per 1,000 pages, falling to $0.60 at high volume. They differ on structured extraction. Google's Form Parser lists $30 per 1,000 pages and its Layout Parser $10; Azure's prebuilt models (invoice, receipt, layout and others) list $10 per 1,000 pages and custom extraction $30; Textract's Forms feature is $50.

| Service | Plain OCR, per 1,000 pages | Structured extraction, per 1,000 pages | Free tier |
| --- | --- | --- | --- |
| AWS Textract | $1.50, then $0.60 above 1M | Tables $15, Forms $50, Expense $10 | 3 months, 1,000 text pages a month |
| Google Document AI | $1.50, then $0.60 above 5M (Enterprise Document OCR) | Layout Parser $10, Form Parser $30 | See Google's pricing page |
| Azure AI Document Intelligence | $1.50 (Read), then $0.60 at volume | Prebuilt models $10, custom extraction $30 | 500 pages a month (F0 tier) |

The practical rule: pick the one on the cloud you already use unless a feature forces your hand, for example Textract's AnalyzeLending for mortgages, or Azure's and Google's wider language support. Our [ABBYY alternatives guide](/resources/blogs/abbyy-finereader-alternative) compares these clouds with on-premise OCR SDKs.

## How do you move from Textract to another API?

Keep Textract running while you test. The work is mostly mapping response formats, not changing the OCR.

1. Pick 50 to 100 of your hardest documents, especially multi-page statements and non-English files.
2. Run them through Textract and the candidate and score the fields you actually use, not character accuracy.
3. Write a small mapping layer from the new response format to the objects your code expects today.
4. Run both in parallel on live traffic for a few weeks and review every difference.
5. Move one document type at a time.

## What to do next

- On AWS, reading English forms or US IDs: stay on Textract and switch on only the features each page needs.
- Processing multi-page bank statements or mixed lending packets: run the same files through Textract and a DocsAPI trial and compare the joined tables.
- Documents outside Textract's six languages: test Google Document AI, Azure, PaddleOCR or Tesseract instead.
- Not sure yet: our Which OCR should I use tool asks six questions and suggests an engine.

## Sources and how we checked this

- Textract prices: AWS's public price list for Amazon Textract, US West (Oregon), published September 11, 2026 and read on September 28, 2026, matching the Amazon Textract pricing page, which also lists the free tier.
- Textract limits (languages, handwriting, page and size limits, AnalyzeID scope, queries): Set quotas in Amazon Textract.
- Google prices: Document AI pricing. Azure prices: Microsoft's public retail prices API for Azure AI Document Intelligence (East US) and the Document Intelligence pricing page for the free tier.
- DocsAPI facts come from our own published product information. The Tesseract comparison uses our September 2026 side-by-side test.

## Frequently Asked Questions

### How much does AWS Textract cost per page?

Plain text detection costs $0.0015 a page ($1.50 per 1,000) for the first million pages a month and $0.0006 after that. Tables cost $0.015, queries $0.015, forms $0.05, invoices and receipts $0.01, US IDs $0.025 and mortgage packages $0.07 a page, in US West (Oregon).

### Is there a free tier for AWS Textract?

Yes, for three months: 1,000 pages a month of text detection, 100 pages a month of forms, tables or layout, 100 of AnalyzeExpense, 100 of AnalyzeID and 2,000 of AnalyzeLending. After three months every page is billed at the normal rate.

### What languages does AWS Textract support?

English, French, German, Italian, Portuguese and Spanish. Handwriting is only supported in English, vertical text is not supported, and Textract does not tell you which language it detected. For other languages use Google Document AI, Azure, Tesseract or PaddleOCR.

### Can AWS Textract read multi-page PDFs?

Yes, through the asynchronous API, which accepts PDF and TIFF files up to 500 MB and 3,000 pages. Synchronous calls accept only one page of a PDF or TIFF. Tables still come back page by page, so a table that runs across pages has to be joined by your code.

### Is AWS Textract better than Tesseract?

Textract does more: it returns forms, tables, receipt fields and US ID fields, and it scales without servers. Tesseract is free, runs offline and reads over 100 languages against Textract's six. For plain text of clean pages in a supported language, Tesseract is often enough.

### Is AWS Textract better than DocsAPI overall?

Neither wins everywhere. Textract is cheaper for plain text and fits AWS-native teams, forms, US IDs and mortgage packages. DocsAPI, our product, fits lending and fintech documents where you need classification, named fields and tables joined across pages in one call. Test both on your own documents.

### Why does Textract struggle with bank statements?

Because it returns tables page by page. A statement whose transactions run across 5 to 15 pages comes back as separate tables with repeated headers and rows split at page breaks, and your code has to join them and check that running balances still add up. APIs built for statements join the pages for you.

### Is AWS Textract good for invoices?

AnalyzeExpense reads vendor, totals, dates and line items for $10 per 1,000 pages, which is good value for standard invoices and receipts. Matching invoices to purchase orders, checking that line items add up to the total and approving exceptions are left to your own code or AP system.

### Is AWS Textract HIPAA-eligible?

Textract can be used under AWS's business associate agreement when the service and region are on AWS's HIPAA-eligible list, so check that list for your region. DocsAPI is HIPAA-eligible with its own business associate agreement on request.

### What is the best AWS Textract alternative in 2026?

It depends on why you are leaving. For price on structured extraction, compare Azure's $10 prebuilt models and Google's $10 Layout Parser. For other languages, Google, Azure or PaddleOCR. For multi-page statements and lending packets, a document API such as DocsAPI. For offline use, Tesseract or PaddleOCR.


---

**Source URL (cite this):** https://docsapi.co/resources/blogs/aws-textract-vs-docsapi
**Author profile:** https://docsapi.co/author/nupura-ughade
**Published by:** DocsAPI (https://docsapi.co)