AWS Textract Pricing 2026: Cost Per 1,000 Pages Explained

Last updated July 2026.

AWS Textract pricing is pay-as-you-go by the page, and the rate depends on which API you call. In the US West (Oregon) region the published rates run about $1.50 per 1,000 pages for Detect Document Text (plain OCR), about $15 per 1,000 pages for Tables, about $50 per 1,000 pages for Forms, about $70 per 1,000 pages for Forms, Tables, and Queries together, about $10 per 1,000 pages for Analyze Expense, and about $25 per 1,000 pages for Analyze ID. There is no monthly subscription and no seat license. New AWS accounts get a three month free tier that covers 1,000 pages a month of plain OCR and only 100 pages a month of the Analyze Document features. This guide breaks down the 2026 rates per API, the volume discounts, the free tier limits, and the costs the headline per-page number leaves out.

AWS Textract pricing per 1,000 pages (2026)

Textract does not have one price. It has a price per feature, and the gap between the cheapest and the most expensive feature is roughly 45x. Here are the published US West (Oregon) rates, with the discounted rate that kicks in after the first million pages in a month.

Two things about this table matter more than the numbers themselves. First, rates vary by AWS region, so confirm yours on the current AWS Textract pricing page before you build a budget on them. Second, the features stack. If you call Analyze Document asking for Forms and Tables on the same page, you are billed the combined rate for that page, not the cheaper OCR rate.

How is AWS Textract priced?

Textract bills per page processed, per feature requested, with no minimum commitment and no monthly platform fee. You are charged when a page passes through an API, and the rate is set by which API you called and which features you asked for in that call. Volume discounts apply automatically once you cross one million pages in a calendar month for most features.

A page is a page whether it is a clean digital PDF or a crooked phone photo of a receipt. Textract does not charge more for hard documents and it does not charge less for easy ones. What changes the bill is how many features you ask for. Teams that discover Textract is expensive are almost always calling Analyze Document with Forms turned on for every page, including the pages that only needed plain text.

Is there a free tier for AWS Textract?

Yes, but it is time limited and small. New AWS accounts get three months of free usage: 1,000 pages a month of Detect Document Text, 100 pages a month of the Analyze Document features (Forms, Tables, Queries, Signatures, Layout), 100 pages a month of Analyze Expense and Analyze ID, and 2,000 pages a month of Analyze Lending. After three months the free tier ends completely and every page bills at the standard rate.

One hundred free pages a month of Forms extraction is enough to run a proof of concept on a handful of documents. It is not enough to test whether Textract handles the twenty layouts your vendors actually send. Plan to spend real money during evaluation, or test on a platform that does not meter your pilot.

How much does AWS Textract cost at volume?

Run the arithmetic on your own document mix rather than on the headline OCR rate, because the headline rate is the one you will almost never pay. Three worked examples at 50,000 pages a month:

• Plain text only: 50,000 pages of Detect Document Text at $1.50 per 1,000 is $75 a month. Cheap, and you get unstructured text you still have to parse.
• Invoices through Analyze Expense: 50,000 pages at $10 per 1,000 is $500 a month, and you get named fields like vendor, date, and total.
• Mixed forms through Analyze Document: 50,000 pages at $70 per 1,000 for Forms, Tables, and Queries is $3,500 a month.

The million-page threshold is where the discount lands, and most US mid-market teams never reach it. If you process 50,000 or 200,000 pages a month, you pay the first-tier rate on every page. Budget accordingly, and do not assume the volume discount will rescue a spreadsheet that only works at scale.

Why do Forms and Tables cost so much more than plain OCR?

Because they are different jobs. Detect Document Text recognizes characters and tells you where they sit on the page. Forms extraction has to work out that the characters "Invoice Date" are a label, that "03/14/2026" is the value that belongs to it, and that the two are related even though they sit forty pixels apart in a two column layout. Table extraction has to rebuild a grid that exists only visually. That inference is the expensive part, and it is the part you would otherwise write yourself.

This is worth understanding before you optimize your bill. The common cost mistake is routing every page through the most expensive call. The fix is classification: work out what each page is first, then send plain pages to cheap OCR and only send structured pages to Forms and Tables. Textract will not do that routing for you. You build it.

What does the AWS Textract per-page price not include?

The per-page rate buys you a JSON response. It does not buy you a working process. Costs that show up after the invoice does:

• Engineering time. Textract is an API. Someone has to stand up the AWS account, configure IAM roles, write the upload path, handle the asynchronous job flow for multi-page PDFs, map Textract's blocks and relationships into your field names, and keep it running.
• Classification. Textract will read whatever page you hand it. Deciding which document type that page is, so you know which fields to expect and which API to call, is your code.
• Human review. Textract returns a confidence score per field. Deciding what to do with a 71% confident total, building the screen where a person corrects it, and tracking who changed what is all yours to build. Amazon A2I exists for this and bills separately.
• Surrounding AWS services. S3 storage for the documents, Lambda or containers for the orchestration, data transfer, and CloudWatch logs all appear on the same bill under different line items.
• Validation and export. Checking that line items sum to the invoice total, that a date is a real date, and that the result lands in your ERP is application code.

None of this is a criticism of Textract. It is a well built, accurate, extremely scalable API and it is priced like one. It is simply not a product, and comparing its per-page rate to the price of a finished product compares two different things.

AWS Textract vs a ready-to-use extraction product on cost

Here is the honest version of the comparison. If all you need is text off a page and you already have engineers inside AWS, Textract at $1.50 per 1,000 pages is very hard to beat on raw cost, and you should probably use it. Nothing in this article changes that.

The picture changes when you need structured fields. Analyze Document with Forms, Tables, and Queries costs about $70 per 1,000 pages, and it still hands back JSON that your team has to classify, validate, review, and export. DocuOCR's published plans work out to roughly $14 to $20 per 1,000 pages depending on volume, and that price includes the classification step, the extraction, the validation rules, the human review screen, the dashboard, and the export, with no AWS account, no IAM policy, and no pipeline to maintain.

Pick on fit, not on the sticker. A team of engineers processing ten million pages of plain text should use Textract. An accounting or operations team that needs validated fields out of 30,000 mixed pages a month, this quarter, will spend less in total on a product that already includes the parts Textract leaves for you to write.

How do you estimate your AWS Textract bill?

Take a real month of documents, not a guess. Count the pages, not the files, because a 12 page loan package is 12 billable pages. Sort the pages by what you actually need from each one: text only, tables, form fields, or invoice fields. Multiply each bucket by its rate from the table above. Then add roughly 10 to 20 percent for the S3, Lambda, and data transfer line items that sit around the API, and add the fully loaded cost of the engineer who will build and own the pipeline. That last number is usually larger than the Textract line, and it recurs every year.

If most of your volume is invoices, price the Analyze Expense path specifically rather than assuming Forms, because the difference between $10 and $50 per 1,000 pages compounds fast. If you are doing this to get invoice line items into a spreadsheet at the end, be honest about whether a raw API is the shortest path to that spreadsheet.

Does AWS Textract charge for pages it reads badly?

Yes. Textract bills for pages it processes, and the confidence score it returns does not change the rate. A page it reads at 62% confidence costs exactly the same as a page it reads at 99% confidence. That matters because low-confidence pages are the expensive ones twice over: you pay Textract for the read, and then you pay a person to check it.

This is the cost line that never appears in a pricing comparison and always appears in a real budget. If 8% of your pages need a human to look at them, and a person handles 60 pages an hour, then 50,000 pages a month buys you roughly 67 hours of review labor. At $25 an hour that is about $1,675 a month, which dwarfs the $500 Analyze Expense bill sitting next to it. Any tool that reduces review volume, or that includes the review screen instead of making you build one, is competing on that number and not on the per-page rate.

The short answer on AWS Textract pricing

Textract is priced per page and per feature: about $1.50 per 1,000 pages for plain OCR, about $15 for Tables, about $50 for Forms, about $70 for Forms with Tables and Queries, about $10 for invoices through Analyze Expense, and about $25 for identity documents. Volume discounts start above one million pages a month. The free tier lasts three months and covers 100 pages a month of the features most people want to test. It is an excellent API and a genuinely cheap way to read text at scale, as long as you have budgeted for the pipeline, the classification, and the human review that surround it.

For the full cross-vendor picture, see our OCR API pricing comparison, which puts these rates side by side with Azure and Google. For the single-vendor breakdowns, read our Azure Document Intelligence pricing guide and our Google Document AI pricing guide. If you would rather skip the pipeline entirely, DocuOCR is a ready-to-use Amazon Textract alternative that returns validated fields instead of JSON blocks.