Verified July 2026

Azure Document Intelligence Limits: File Size, Page and Rate Limits

Azure Document Intelligence reads up to 500 MB and 2,000 pages in one call on the paid S0 tier, with a 15 analyze-per-second rate limit. The free F0 tier caps files at 4 MB and returns only the first 2 pages.

The free-tier two-page cap is the surprise that makes evaluators think the model failed. Here is every Azure limit, read from Microsoft's docs. Last updated July 2026.

  • 500 MB, 2,000 pages on S0
  • Free F0 returns first 2 pages
  • 15 analyze TPS, adjustable
  • Formats and page counting
Upload a multi-page PDF, no signup

PDF, JPG, PNG, BMP, HEIC, TIFF

Upload a document to extract

Read a long document without picking a tier or a page range.

SOC 2 Type II
256-bit encryption
US data handling
Multi-page in one upload
500 MB
max document size, S0
2,000
pages in one analyze call
2 pages
all the free F0 tier returns
15 / sec
analyze rate limit, S0
// The short answer

What the Azure Document Intelligence limits actually are

Azure AI Document Intelligence, the service Microsoft used to call Form Recognizer, has two sets of limits that depend entirely on your pricing tier. On the paid Standard (S0) tier a single analyze call accepts a document up to 500 MB and 2,000 pages, and neither figure can be raised. That is the highest single-request page count in the cloud OCR group, so a 500-page PDF goes through in one call with no asynchronous job. The rate limit is 15 analyze transactions per second by default, plus 50 get-operations per second for polling results, and both are adjustable for free through an Azure support request. The free F0 tier is where teams get caught: it caps files at 4 MB, holds every per-second limit at 1, and returns results for only the first 2 pages of any request. Everything here is read from the Microsoft documentation in July 2026, and because Microsoft updates its quotas, confirm each figure on the current service-limits page before you build around it.

The limits that matter

  • S0: 500 MB, 2,000 pages, one call.
  • F0 free: 4 MB, first 2 pages only.
  • Rate: 15 analyze / sec, adjustable.
// The free-tier trap

Why the free tier only reads two pages

The most common Azure Document Intelligence support question is not about the 500 MB ceiling. It is a developer testing on the free F0 tier who sends a ten-page invoice and gets fields back for pages one and two, then nothing. The model looks broken. It is not. F0 returns analyze results for only the first two pages of any request, by design, so you can test features without processing real documents at no cost.

The fix is to move to the Standard S0 tier, where the same call reads up to 2,000 pages. There is no code change and no different endpoint, only the resource tier. Because F0 and S0 share the REST API, a proof of concept built on F0 will suddenly read the whole document the moment you point it at an S0 resource. If pages three and beyond come back empty, check your tier first.

The second free-tier limit is the 4 MB file cap versus 500 MB on S0, and every per-second transaction limit fixed at 1. F0 is a feature sandbox, not a low-volume production tier. If you need to process even a handful of real multi-page files, you are on S0 from the start.

Free F0 vs paid S0

  • Pages returned: F0 first 2, S0 up to 2,000.
  • File size: F0 4 MB, S0 500 MB.
  • Rate limits: F0 all 1/sec, S0 15 to 50/sec.
  • Same REST API, so no code change to move up.

Max document size and max pages are set limits and cannot be raised. Analyze and get TPS can be increased free via a support ticket. Verified from Microsoft docs, July 2026.

// Free vs Standard

Azure Document Intelligence limits, F0 vs S0

The same limits split by tier, because which tier you are on decides your page ceiling, file size and rate.

Limit Free (F0) Standard (S0)
Max document size 4 MB 500 MB
Max pages per analyze call First 2 pages returned 2,000 pages
Analyze transactions / second 1 15 (default, adjustable)
Get operations / second 1 50 (default, adjustable)
Model-management ops / second 1 5 (default)
List operations / second 1 10 (default)
Max OCR JSON response 500 MB 500 MB

See how these ceilings compare with AWS and Google on the OCR API limits comparison, and what Azure costs per 1,000 pages on the Azure Document Intelligence pricing breakdown.

// Formats and counting

Formats, page counting and training limits

These rules apply on every tier and decide what Azure will read and how it counts a page toward your ceiling.

Constraint Rule
Accepted formats (all models) PDF, JPEG/JPG, PNG, BMP, TIFF, HEIF.
Office formats (Read and Layout only) DOCX, PPTX, XLS. Not supported by prebuilt or custom models.
PDF and TIFF page counting Each page or image counts as one page, no character cap.
Word and HTML page counting Counted in blocks of 3,000 characters per page.
Excel and PowerPoint Each worksheet or slide counts as one page.
Custom classifier training Up to 25,000 pages and 1,000 document classes.
Custom neural training 10 free hours per month, then billed by the hour.

The Office-format gap catches teams too: you can OCR a DOCX or XLS with Read and Layout, but a prebuilt or custom model needs a PDF. An Azure Document Intelligence alternative that takes mixed file types and long PDFs in one upload removes the tier and format math.

// Frequently asked

Azure Document Intelligence limits FAQ

What is the Azure Document Intelligence file size limit?
On the paid Standard (S0) tier the maximum document size is 500 MB. On the free F0 tier the maximum is 4 MB. These are set limits that cannot be raised through a support request, so a file over 500 MB has to be split before you send it. The 500 MB ceiling is the highest single-file size in the cloud OCR group, ahead of Google Document AI at 40 MB online and level with AWS Textract async at 500 MB.
How many pages can Azure Document Intelligence process?
On the Standard (S0) tier a single analyze call accepts up to 2,000 pages. That is the highest single-request page count you can send without an asynchronous job, higher than Google Document AI online at 15 pages. The catch is the free F0 tier: it returns results for only the first 2 pages of any request, so if you test on F0 you will think the model stopped reading after page two.
What is the Azure Document Intelligence free tier limit?
The free F0 tier caps documents at 4 MB and, more importantly, returns analyze results for only the first 2 pages of each request. Every transactions-per-second limit on F0 is fixed at 1 and cannot be raised. F0 exists to test features, not to process real multi-page documents. If pages three and beyond come back empty, you are on F0, not hitting a model failure, and you move to S0 to read the whole file.
Does Azure Document Intelligence have a rate limit?
Yes. On S0 the default limits are 15 analyze transactions per second, 50 get-operations per second, 5 model-management operations per second and 10 list operations per second. The analyze and get limits are adjustable through an Azure support request at no cost. On F0 all four limits are fixed at 1 per second. If you get HTTP 429 responses, you are over one of these per-second limits and should add exponential backoff.
What is the maximum file size for Azure Form Recognizer?
Azure Form Recognizer is the former name of Azure AI Document Intelligence, so the limits are the same: 500 MB per document on the paid S0 tier and 4 MB on the free F0 tier. Microsoft renamed the service but kept the quotas and the same REST API. Any older guide that says Form Recognizer still describes the current Document Intelligence limits.
What file formats does Azure Document Intelligence support?
All models read PDF, JPEG, PNG, BMP, TIFF and HEIF. Microsoft Office formats, DOCX, PPTX and XLS, are supported only by the Read and Layout models, not by the prebuilt or custom models. So you can OCR a Word or Excel file, but you cannot run it through the prebuilt invoice or a custom extraction model without converting it to PDF first. Each Excel worksheet and each PowerPoint slide counts as one page.
How does Azure count pages for Word and HTML files?
For PDF and TIFF, each page or image counts as one page. For Word and HTML files that the Read and Layout models support, Azure counts pages in blocks of 3,000 characters. A 7,000-character document is billed as three pages: two full 3,000-character pages and one partial page. Excel worksheets and PowerPoint slides each count as one page. This matters for both your page ceiling and your bill.
Can Azure Document Intelligence handle a 500-page PDF in one call?
Yes, on the S0 tier. A single analyze request accepts up to 2,000 pages and 500 MB, so a 500-page PDF fits in one call with no asynchronous job, no polling and no storage bucket. This is the main practical advantage over AWS Textract, whose synchronous call reads one page and forces an S3-based async job for anything longer. With Azure you send the file and wait for the operation to finish.
What is the max training size for a custom Azure model?
For a custom neural or generative model the training dataset can be up to 1 GB, and training up to 50,000 pages. A custom template model allows 50 MB and 500 pages. A custom classifier accepts up to 25,000 pages and 1,000 document classes. Custom neural training gives 10 free hours a month, then bills by the hour. Training itself is free up to that allowance; you pay when a trained model analyzes documents.
How do I avoid HTTP 429 errors with Azure Document Intelligence?
A 429 means you crossed a per-second transaction limit, usually the 15 analyze calls per second on S0 or the polling get-operations limit. Add exponential backoff on the get call, honor the retry-after header Azure returns, and ramp your workload up gradually instead of spiking. If your steady-state volume genuinely needs more than 15 analyze transactions per second, open a free support request to raise the limit.

Read the whole document, no tier math

Azure's free tier reads two pages and its Office support skips the prebuilt models. DocuOCR takes a mixed batch or a long PDF in one upload, reads every page, and returns clean fields. Drop in your longest document and compare.