Rohman
Quick answer: Google Drive's free OCR rejects files over 2 MB and reads only the first ten pages of a PDF, with no warning either way. For anything longer or more sensitive, OCR PDF runs recognition in your browser — no upload, no page cap, no account.
Someone on Google's own support forum put it better than I could: "Google Drive thinks my 150 page PDF OCR file only has 55 pages."
No error. No warning banner. No note at the bottom of the document saying the rest was skipped. You right-click, choose Open with Google Docs, get a document back, and it looks like it worked. The tail of your file is simply gone, and you find out when you go looking for something on page 80.
Google Drive's free OCR is genuinely useful and costs nothing, which is why so many people reach for it. It also has two hard limits that Google documents thinly, and both of them fail silently.
Key takeaways:
- The limits: 2 MB per file, and only the first ten pages of a PDF get converted. Both are documented behavior; neither produces a warning.
- The privacy frame: Drive already ran text extraction on your file to build its search index before you ever clicked "Open with Google Docs." The upload was the decision; the OCR step is bookkeeping.
- The accuracy picture: on clean printed pages, the gap between Google's free pipeline and a browser-based engine is small. Handwriting is where cloud engines genuinely pull ahead.
- The alternative: OxygenPDF's OCR PDF runs locally in the browser — no size cap, no page cap, no upload, no account.
The Two Limits
2 MB per file. Google's help page for the feature states it plainly: "The file should be 2 MB or smaller." A ten-page color scan at 300 DPI runs 5 to 15 MB, so the limit rules out most real scans before you start. There is no paid tier that lifts it inside Drive and no official workaround — Google's answer is to make the file smaller.
The first ten pages of a PDF. The current help page no longer spells this one out, but earlier versions of the same page did — "for PDF files, we only look at the first 10 pages when searching for text to extract" — and silent truncation is still what users report. The 150-page file that came back as 55 pages is one thread; an 80-page cutoff and partial imports with no explanation are others. The exact cutoff varies in these reports, but the failure mode is the same: everything past it is dropped, quietly, with no marker in the output. This is the limit that costs people real work, because a truncated document looks exactly like a complete one until you audit it.
Neither limit is a bug. Both are documented or long-observed behaviour. What is missing is any signal at the moment it happens, and a 55-page result from a 150-page input is the kind of failure you carry forward for weeks before noticing.
The workarounds are what you would expect and about as pleasant. Compress the PDF until it slips under 2 MB, accepting whatever that does to the image quality your OCR then has to read. Or split the file into chunks, run each one by hand, and paste the resulting Google Docs back together. There is no batch mode. Every file needs its own right-click.
How to Check Whether Your Conversion Was Truncated
If you have already run a document through Drive and you are not sure it survived whole, three checks take under a minute. Compare the page count: open the PDF's properties and look at the page total, then scroll the Google Doc to the end and see where it stops. Search for a phrase you know appears near the end of the original — a signature block, an appendix heading, the last invoice number. And check the file size before you bother: anything over 2 MB was never going to convert in the first place, whatever the interface let you click.
Drive Already Read It
Here is the part most people have not clocked.
Google Drive runs text extraction on your uploaded PDFs and images regardless of whether you ask for OCR. It does this to build its search index, which is why Drive search can find a word inside a scanned PDF that you cannot select or copy a single character from. You can check this yourself in thirty seconds: upload a scan, wait a minute, and search a word that only appears inside it. The recognition already happened. The Google Doc conversion is a separate, manual step that hands you a copy of what Drive extracted for itself the moment the file landed.
What "Automated Systems" Covers on a Free Account
Google's privacy policy says plainly that it collects the content you create, upload, or receive, and that it uses "automated systems that analyze your content" to provide tailored features. Google does not sell your files and says it does not target ads based on Drive content. Those are real commitments and worth crediting.
The gap that matters is between account types, and it is wider than most people assume.
On a paid Workspace account, Google's contractual language is specific. Its Generative AI privacy commitments state that your data is not reviewed by humans and is not used for generative AI model training outside your domain without permission, and admins can set policy that keeps customer data out of model improvement entirely.
On a free consumer account, you get the general privacy policy. Content may be processed to improve services and develop new products and features. If you use Gemini with a personal account, the Gemini Apps Privacy Hub notes that Google collects your prompts and generated content and may use them to develop machine-learning technologies — and that human reviewers may read some conversations. Where "improving services" ends and "training models" begins is not a line a consumer account gets to draw.
For a scanned recipe, none of this matters. For the documents people actually run OCR on, it might. Google's HIPAA business associate agreement covers paid Workspace accounts, not free consumer Drive, which is a problem for medical records. Attorney-client privileged material sitting on a third party's servers is a conversation you may not want to have. Tax returns, bank statements, passport scans and driver's licences are the exact document classes that end up in an OCR queue, and they are the exact ones where the upload is the risk rather than the processing.
There is a small irony worth noting: Google Cloud's own Sensitive Data Protection service uses OCR to detect sensitive data inside stored documents. The capability to read what you uploaded is not hypothetical. It is a product.
The Free One Is the Weakest of Google's Four
Google sells four different OCR products, and the one in Drive is the oldest and simplest pipeline of the set.
Google Docs OCR is free and built into Drive. Google Lens handles camera and screen capture. Cloud Vision API costs $1.50 per thousand units after a free monthly allowance, and Document AI runs $1.50 to $30 per thousand pages depending on the processor, per Cloud Vision and Document AI pricing as of September 2026. The accuracy numbers people quote for "Google OCR" almost always come from Cloud Vision, not from the free Drive feature — so the reputation is borrowed from a product you are not using.
The free pipeline's weak spots are documented by Google itself on the same help page: lists, tables, columns, footnotes and endnotes are "not likely to be detected." In practice tables collapse into linear text, multi-column layouts merge into one paragraph, headers and footers mix into the body, and page numbers land inline mid-sentence. Handwriting is the worst case — the help page's preparation advice assumes printed text in common fonts like Arial or Times New Roman, and says nothing about handwriting at all.
Developers hitting Drive OCR through the API have watched it get squeezed too. One report on Google's developer forums, from November 2025: "even when limiting myself to only 1 file, I nearly always encounter a GoogleJsonResponseException" — the error being "User rate limit exceeded for OCR," on an undocumented quota that several posters in the same thread hit at once. Some found that moving from the v2 to the v3 Drive API stopped the errors, which suggests the free path is being deprioritised in favour of the metered ones.
The Accuracy Gap Is Narrower Than the Privacy Gap
The assumption doing the most work in people's tool choices is that cloud OCR is meaningfully more accurate. On clean printed text, it barely is.
Published comparisons between Cloud Vision and Tesseract on clean printed pages generally land within a couple of percentage points of each other — the kind of gap you notice in bulk, not on a single document. Where cloud engines pull genuinely ahead is handwriting and badly degraded scans, which is the difference between usable output and not. If your document is handwritten, a cloud engine or a vision model is the honest answer.
For everything else — printed contracts, invoices, scanned reports, forms — resolution matters far more than which engine reads them. A clean 300 DPI scan reads near-perfectly on a modern open engine; the same page captured at 100 DPI loses visible accuracy no matter whose model you pay for. Fixing your capture is worth more than switching vendors, which is the whole argument of why your phone photos read as garbage.
OCR With No Page Cap and No Upload
OCR PDF runs recognition in your browser. The file is never uploaded, so there is no 2 MB ceiling, no ten-page truncation, no rate limit, and no account.
- Drop in the PDF or image — any size your browser can hold
- Pick the language rather than hoping auto-detect guesses right
- Run recognition across every page, not the first ten
- Download a searchable PDF with the text layer written in, or send it to Word
It ships five on-device engines: Tesseract for fast English work, two PaddleOCR models sized for Asian scripts, and two Florence-2 vision models that run on WebGPU for the best on-device accuracy the tool offers. The language picker covers 20 languages. For the rare document none of them handle — a heavily degraded scan, an uncovered script — three cloud engines are available as an explicit opt-in with your own API token, never the default.
If the sceptical read is "everyone claims privacy," that claim is checkable here in a way a policy page never is. Open DevTools, watch the Network tab, run the OCR. No request carries your file. That is the difference between an architecture and a promise.
One thing worth doing first: check the orientation. Recognition accuracy collapses on sideways pages and Drive does not auto-rotate at all — its own help page requires the document to arrive right side up. Straighten the pages, then recognise. It is the cheapest accuracy gain available, and it works no matter whose engine reads the file.
FAQ
Does Google Drive OCR work on files over 2 MB?
No. Google's help page caps conversion input at 2 MB, and there is no paid tier or setting that lifts it inside Drive. Your options are to compress or split the file first, or use a tool without the ceiling — browser-based OCR has no upload at all, so no size cap either.
Why did Google Docs only convert part of my PDF?
Because conversion stops after the first ten pages, silently. Earlier versions of Google's help page stated this directly, and users still report truncated results — 55 pages back from a 150-page file, in one support thread. Compare the output's page count against the original before trusting it.
Is Google Drive OCR free?
It costs no money, but it is not free of terms. The file uploads to Google's servers, where consumer accounts fall under the general privacy policy rather than Workspace's stricter contractual commitments. For everyday documents that trade is fine; for sensitive ones, the upload is the cost.
Can Google Drive OCR read handwriting?
Not reliably. Google's own preparation guidance assumes printed text in common fonts and never claims handwriting support. Handwritten pages are where paid cloud engines and vision models genuinely earn their keep — or where a local vision model like Florence-2 is the better free option.
Does Google Drive OCR work without uploading the file?
No. The file has to live in Google Drive before you can open it with Google Docs, and Drive runs its own text extraction on upload regardless. If the upload itself is the problem, recognition has to happen locally — which is what browser-based OCR tools do.
Is Google Drive OCR safe for medical or legal documents?
A free consumer account is not covered by Google's HIPAA business associate agreement — that applies to paid Workspace. Privileged or regulated documents are exactly the class where keeping the file on your own machine is the defensible choice, rather than a preference.
If your document is short, clean, and already in Drive, the built-in OCR is fine — that is what it is for. If it is long, large, or sensitive, run the OCR in your browser instead. Every page, no upload, no account.
