> Source: https://txtfetch.com/compare/per-page-pricing > Plain-text twin — every page on txtfetch.com has one. https://txtfetch.com/text --- # Per-page pricing punishes long documents. Most extraction APIs meter by the page. That's a fair way to price OCR compute. But it means your bill scales with document length, not with how many documents you process. Almost every document-extraction vendor bills per page. That list includes [Unstructured.io](https://txtfetch.com/compare/unstructured), [LlamaParse](https://txtfetch.com/compare/llamaparse), [AWS Textract](https://txtfetch.com/compare/aws-textract), [Azure AI Document Intelligence](https://txtfetch.com/compare/azure-document-intelligence), and [Mindee](https://txtfetch.com/compare/mindee). Per-page pricing is a fair proxy for the OCR and inference cost of a page. But it has a side effect. The price of extracting a document depends on the document's length, not on how much work it is for _you_. To you, it's one file, fetched or uploaded, and handled once. Consider two customers sending 100 documents a month. Customer A sends one-page invoices. Customer B sends 300-page compliance reports. Under per-page billing, Customer B pays 300x more for the same "100 documents a month" workload. Under per-document billing, both customers pay the same amount. The unit of billing matches the unit of work: one document extracted, once. This isn't an argument that per-page pricing is dishonest. It maps cleanly to compute cost. For vendors selling OCR as commodity infrastructure, it's a defensible model. The real argument is different: **the pricing unit should match how you think about your workload.** If you ingest long documents, per-page billing makes your costs unpredictable. Your bill depends on content you don't control. A vendor could send you a 50-page PDF instead of a 5-page one, and your bill jumps 10x. txtfetch bills per document instead. A 300-page PDF and a one-page memo cost the same to extract. From your side, they're both "one thing I needed turned into text." ## The math, worked out Below is a representative per-page rate: the Read/OCR tier that AWS Textract and Azure AI Document Intelligence both charge. This is roughly what "commodity OCR" costs across the market. Try your own document length and monthly volume. [Interactive cost calculator — adjust pages per document and documents per month to compare pricing against a typical per-page OCR vendor] ## Where per-page pricing is the right call Per-page pricing can be the better deal in some cases. If your documents are uniformly short, such as single-page forms, receipts, or IDs, per-page billing may cost less than a flat document quota. The same is true if you need per-feature pricing. Then you pay only for the specific analysis you use, such as tables, key-value pairs, or a single prebuilt model. Per-page pricing is also more transparent for pure infrastructure: you buy compute, not a product tier. See the individual comparisons below for where each vendor's model wins for your workload. ## Read the individual comparisons - [txtfetch vs Unstructured.io](https://txtfetch.com/compare/unstructured): Open-core ETL for RAG pipelines, priced per page. - [txtfetch vs LlamaParse](https://txtfetch.com/compare/llamaparse): Credit-metered parsing, tuned for complex PDFs. - [txtfetch vs AWS Textract](https://txtfetch.com/compare/aws-textract): AWS-native OCR and document analysis, billed per 1,000 pages. - [txtfetch vs Azure AI Document Intelligence](https://txtfetch.com/compare/azure-document-intelligence): Microsoft's prebuilt-model document API, billed per 1,000 pages. - [txtfetch vs Mindee](https://txtfetch.com/compare/mindee): Subscription + credits for structured field extraction. Full plan details, including the durable free tier, are on [the pricing page](https://txtfetch.com/pricing). ## Sources - [Unstructured.io: Pricing](https://unstructured.io/pricing) Accessed 2026-07 - [LlamaIndex: LlamaParse pricing](https://developers.llamaindex.ai/llamaparse/general/pricing/) Accessed 2026-07 - [LlamaParse free-tier credits (secondary source)](https://developers.llamaindex.ai/llamaparse/general/pricing/) Accessed 2026-07 directional - [AWS Textract: Pricing](https://aws.amazon.com/textract/pricing/) Accessed 2026-07 - [Azure AI Document Intelligence: Pricing](https://azure.microsoft.com/en-us/pricing/details/document-intelligence/) Accessed 2026-07 directional - [Microsoft Q&A: Document Intelligence per-page rate consensus](https://learn.microsoft.com/en-us/answers/questions/tagged/azure-ai-document-intelligence) Accessed 2026-07 directional - [Mindee: Pricing](https://www.mindee.com/pricing) Accessed 2026-07 - [Mindee: derived effective per-page rate (not a published figure)](https://www.mindee.com/pricing) Accessed 2026-07 directional ## Check the numbers yourself. The benchmark runs against a committed corpus. You can re-run it. [See the benchmarks →](https://txtfetch.com/benchmarks) [Get an API key →](https://app.txtfetch.com/signup)