Verified July 2026

Google Document AI Limits: Page Limit, File Size and Quotas

Google Document AI reads 15 pages online (30 with imageless mode) and up to 1,000 pages per file in batch, with a 40 MB online and 1 GB batch file size. The 15-page online cap is what triggers the page-limit error.

The online endpoint stops at 15 pages, which is the surprise on the first long document. Here is every Document AI limit, read from Google's docs. Last updated July 2026.

  • 15 pages online, 30 imageless
  • Up to 1,000 pages in batch
  • 40 MB online, 1 GB batch
  • Quotas and throughput
Upload a multi-page PDF, no signup

PDF, JPG, PNG, BMP, HEIC, TIFF

Upload a document to extract

Read a document past 15 pages without an online-versus-batch decision.

SOC 2 Type II
256-bit encryption
US data handling
Multi-page in one upload
15
pages, online processing
30
pages with imageless mode
1,000
pages per file in batch
1 GB
max batch file size
// The short answer

What the Google Document AI limits actually are

Google Document AI has two processing modes and the split defines its limits. Online processing, the synchronous ProcessDocument call, accepts a file up to 40 MB and 15 pages, or 30 pages if you enable imageless mode. That 15-page cap is the lowest single-request page ceiling in the cloud OCR group, and it is exactly what raises the PAGE_LIMIT_EXCEEDED error the first time you send a long document. Batch processing, the asynchronous BatchProcessDocuments call, reads a file up to 1 GB and up to 1,000 pages depending on the processor, with as many as 5,000 files in a single request pulled from a Cloud Storage bucket. Quotas such as 5 concurrent batch requests per project and roughly 120 pages per minute of provisioned throughput are adjustable in the Cloud console, while the content limits above are system limits that cannot be changed. Everything here is read from the Google documentation in July 2026, so confirm each figure on the current limits and quotas pages before you design around it.

The limits that matter

  • Online: 15 pages, 40 MB, response inline.
  • Imageless: 30 pages online, from page 1.
  • Batch: up to 1,000 pages, 1 GB, from Cloud Storage.
// The 15-page cap

Why the online endpoint stops at 15 pages

The first long document is where teams meet the limit. You send a 20-page contract to the online ProcessDocument endpoint and get back PAGE_LIMIT_EXCEEDED. That is expected. Online processing is built for an immediate, synchronous response, so it caps at 15 pages, or 30 if you enable imageless mode, which skips returning rendered page images and processes pages contiguously from page 1.

For anything longer you move to batch processing. You put the file in a Cloud Storage bucket, call BatchProcessDocuments, and Google reads up to 1,000 pages per file, writing the results back to Storage. A single batch request handles up to 5,000 files, and you can run 5 concurrent batch requests per project. Batch is where Document AI actually scales; the online endpoint is for short, interactive requests.

The 15-page cap itself is not the cost. The cost is the plumbing it forces once your documents cross it: a Cloud Storage bucket, an async batch call, polling the long-running operation, and reading results back out of Storage. For a team already on Google Cloud that is routine. For everyone else it is real integration work to read a document that a product would take as one upload.

Past 15 pages, three options

  1. 1. Enable imageless mode to reach 30 pages online.
  2. 2. Split the file into 15-page chunks, merge results.
  3. 3. Send it to batch: 1 GB, up to 1,000 pages per file.

Page and file-size caps are system limits and cannot be raised. Throughput and concurrency quotas are adjustable in the Cloud console. Verified from Google docs, July 2026.

// Online vs batch

Google Document AI limits, online vs batch

The same limits split by mode, because which one you use decides your page ceiling and your architecture.

Limit Online (sync) Batch (async)
Max file size 40 MB 1 GB per file (from Cloud Storage)
Max pages 15 (30 with imageless mode) 100 to 1,000, varies by processor
Max files per request 1 5,000
Result Returned in the response Written to Cloud Storage, poll the job
Input source Bytes or Cloud Storage Cloud Storage only
Best for Short docs, immediate response Long docs, high volume

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

// Quotas and throughput

The Document AI quotas that gate volume

Concurrency and throughput are adjustable quotas. The page and file-size caps above are fixed system limits.

Quota Value
Concurrent batch requests 5 per project (US, EU, regional).
Provisioned throughput (base) About 120 pages per minute.
Provisioned throughput (Pro base) About 30 pages per minute.
Image resolution 40 megapixels per page.
Imageless mode Raises online cap to 30 pages, contiguous from page 1.
System vs quota limits File size and page caps are fixed; throughput quotas adjustable.

If your documents routinely run past 15 pages and you would rather not build the batch job, a Google Document AI alternative that reads a long PDF in one upload skips the online-versus-batch decision entirely.

// Frequently asked

Google Document AI limits FAQ

What is the Google Document AI page limit?
For online (synchronous) processing the page limit is 15 pages per request, or 30 pages if you enable imageless mode. For batch (asynchronous) processing the limit is set per file and varies by processor, from 100 up to 1,000 pages. So the practical answer is 15 pages online and up to 1,000 pages in batch. The 15-page online cap is exactly what triggers the PAGE_LIMIT_EXCEEDED error when you send a longer document to the synchronous endpoint.
Why does Google Document AI say page limit exceeded?
You sent more than 15 pages to the online (synchronous) processor. Online ProcessDocument accepts 15 pages by default. To fix it you have three options: enable imageless mode to raise the online cap to 30 pages, split the file into 15-page chunks, or switch to batch processing, which reads up to 1,000 pages per file from Cloud Storage. Most teams move to batch once documents routinely run past 15 pages.
What is the Google Document AI file size limit?
Online processing accepts a file up to 40 MB. Batch processing accepts up to 1 GB per file, read from a Cloud Storage bucket, with up to 5,000 files in a single batch request. So a large scanned PDF has to go through batch, not the online endpoint. Images are also capped at 40 megapixels per page. Files over these sizes have to be split or downsampled before Document AI will accept them.
How many pages can Google Document AI process in batch?
In batch mode the maximum pages per file depends on the processor, from 100 pages up to 1,000. Enterprise Document OCR reads up to 1,000 pages per file, while some prebuilt parsers cap lower, so check the limit for your specific processor. A single batch request can include up to 5,000 files, and you can run 5 concurrent batch requests per project. Batch reads files from a Cloud Storage bucket and writes results back to one.
What is imageless mode in Google Document AI?
Imageless mode is an option on ProcessRequest that raises the online page limit from 15 to 30 pages. It works only when you process pages contiguously starting from page 1, and it skips returning the rendered page images, which is what lets it handle more pages in a synchronous call. It is a quick way to double the online ceiling without moving to batch, but 30 pages is still the cap, so longer documents still need batch.
Does Google Document AI have a rate limit?
Yes. Document AI enforces quotas you can view and adjust in the Google Cloud console, including 5 concurrent batch requests per project and provisioned throughput of about 120 pages per minute for base processor versions and 30 pages per minute for Pro base versions. These quotas are adjustable, unlike the content limits such as the 15-page online cap and the 1 GB batch file size, which are system limits that cannot be changed.
Online vs batch processing in Document AI, which do I use?
Use online (synchronous) processing for short documents of 15 pages or fewer when you want an immediate response. Use batch (asynchronous) processing for anything longer, for high volume, or for files up to 1 GB, since it reads up to 1,000 pages per file from Cloud Storage and handles 5,000 files per request. The tradeoff is that batch is asynchronous: you submit the job, then poll or wait for the operation to finish, rather than getting the result inline.
How do I process a document longer than 15 pages?
You have three paths. Turn on imageless mode to reach 30 pages online. Split the document into 15-page chunks and process each online, then merge the results by page number. Or send the whole file to batch processing, which takes up to 1,000 pages per file. Batch is the usual choice for documents that routinely exceed 15 pages, because splitting and stitching adds code and can break tables that span a page boundary.
What file formats does Google Document AI support?
Document AI reads PDF, TIFF and GIF, plus common image types such as JPEG, PNG, BMP and WEBP for online processing, with results depending on the processor. PDF and TIFF are the formats used for multi-page documents. The 40-megapixel-per-page image resolution limit applies across formats. For a Word or Excel file you convert to PDF first, since Document AI processes document images and PDFs rather than native Office files.
Is Google Document AI cheaper than the page limits suggest?
The limits and the price are separate questions. Enterprise Document OCR is about $1.50 per 1,000 pages, but the prebuilt Invoice, Expense and Utility parsers bill in 10-page blocks at roughly $0.10 per block, so a 1-page invoice consumes a full block. The 15-page online cap does not change the rate, but the block billing on prebuilt parsers can make short documents cost more than the page count implies. See the pricing breakdown for the per-processor rates.

Read past 15 pages without the batch job

Google's online cap means a Cloud Storage bucket, a batch call and polling the moment a document runs long. DocuOCR takes the whole PDF in one upload, reads every page, and returns clean fields. Drop in your longest document and compare.