Why Scanned PDFs Get So Large: DPI Math, Color Overhead, OCR Layers, and What Phone Scanner Apps Are Doing to Your File

When a scanned PDF is huge, the problem is almost never the number of words on the page. It is the number of pixels. A born-digital PDF made from typed text can hold dozens of pages in a few hundred kilobytes because the text is stored as characters, vectors, and references. A scanned PDF stores each page as one or more raster images, and those images are what make the file swell.

That distinction explains why a two-page form scanned from a phone can be larger than a 30-page contract exported from Word. The form is really two photos wrapped in a PDF container. The contract is still text. Once you understand that scanned PDFs are image-heavy objects, the rest of the file-size behavior becomes much easier to predict.

The three biggest drivers are scan resolution, color mode, and the app or scanner profile used when the PDF was created. OCR can help or hurt depending on how it is applied, but OCR is almost never the primary reason a scan explodes in size. The pixel count is the starting point.

• Typed PDFs are compact because they store text as text.
• Scanned PDFs are large because each page is stored as image data.
• Resolution and color mode matter more than page count in many scan workflows.

A standard U.S. letter page is 8.5 by 11 inches. At 72 DPI, that page becomes 612 by 792 pixels. At 150 DPI, it becomes 1275 by 1650. At 200 DPI, it becomes 1700 by 2200. At 300 DPI, it becomes 2550 by 3300. At 600 DPI, it becomes 5100 by 6600. The jump in pixels is the important part, because file size follows pixel count far more closely than people expect.

Doubling DPI does not double the amount of image data. It roughly quadruples it because you are increasing both width and height. A 300 DPI page contains 8.4 million pixels. A 600 DPI page contains 33.7 million pixels. That is four times the raw pixel count before compression format, grayscale choice, OCR, or app-specific enhancement has done anything at all.

This is why 600 DPI is wildly oversized for ordinary forms, letters, and receipts. It is useful for archival work, tiny print, or image extraction, but it is overkill for most upload and email workflows. For ordinary legible document delivery, 150 to 200 DPI is often the best compromise between sharpness and weight.

• DPI grows file size geometrically because both dimensions increase together.
• 300 DPI has about four times the raw pixel data of 150 DPI.
• 600 DPI is usually unnecessary for standard upload and email workflows.

The table below is an illustrative benchmark, not a vendor-published guarantee. It models the same one-page letter-size document scanned with ordinary office content and saved as a reasonably compressed PDF page. Exact numbers vary by app, device, JPEG quality, PDF wrapper, and whether the scanner chooses monochrome, grayscale, or color enhancement automatically. The point is to show the relative weight changes, not to claim that every device will output the same exact megabyte number.

The pattern is what matters. Grayscale scales more gently as DPI rises. Color adds much more data because it stores multiple channels instead of one luminance-style channel. In practice, a color scan of a simple black-and-white document is usually wasted file size unless the page contains highlights, stamps, photos, colored handwriting, or shaded fields that genuinely need to survive.

• The table is a benchmark-style scenario, not a promise of exact output from every scanner app.
• Color at 300 or 600 DPI is where one-page scans start becoming absurdly heavy.
• For ordinary text documents, grayscale 150 to 200 DPI is usually the right answer.

Color usually costs far more than people expect because each pixel carries more information. A grayscale page mainly stores brightness values. A color page stores multiple channels, typically red, green, and blue. Even before compression, that means color starts with about three times as much raw image information as a grayscale equivalent.

Compression can narrow or widen that gap depending on the document. A page with large white margins and a few black text lines compresses efficiently in either mode, but grayscale still wins. A page with colored highlights, stamps, shaded boxes, photos, or signatures forces the encoder to keep more variation, which makes color scans grow quickly. That is why a form with blue handwriting or red approval stamps can still justify color, while a plain black-and-white tax document usually does not.

The important operational rule is simple: if the content is functionally black and white, scan it in grayscale. Do not scan in color out of habit. The extra channels almost always cost more than the value they add.

• Color stores multiple channels per pixel, which is why it starts heavier than grayscale.
• The size penalty grows when the page contains highlights, photos, or shaded design elements.
• For text-only paperwork, color is usually wasted weight.

OCR does not usually replace the scanned page image. It typically adds a hidden text layer on top of the page so the PDF becomes searchable and selectable. That means OCR usually increases file size slightly, because the page image is still there and new text or structural metadata is added alongside it. On a normal multi-page office scan, the OCR layer might add only a small amount compared with the image data, but it is still an addition, not a subtraction.

Where OCR helps is indirectly. Once a document is searchable, you may be able to rebuild or re-export it more intelligently, remove image-only duplicates, or avoid rescanning pages just to find information later. Some desktop PDF tools also apply image cleanup, deskewing, background removal, or adaptive compression as part of the OCR workflow. In those cases users think OCR “made the file smaller,” but what actually reduced the weight was the image optimization step bundled with OCR processing.

OCR can become heavy when an app embeds multiple recognition passes, keeps original full-size images, and adds structural data for each page. It can also fail to justify its cost when the source scan is too blurry or too high-noise for good text recognition. In that case you pay for the extra layer without getting much search value back.

• OCR usually adds a text layer; it does not replace the scanned page image.
• The OCR layer is rarely the main reason a scan is large; the image pages still dominate.
• OCR helps most when it is combined with cleanup, deskewing, and better downstream document handling.

Phone scanner apps do more than take a picture and wrap it into PDF. They crop edges, flatten perspective, adjust contrast, choose color or grayscale filters, and decide how aggressively to compress each page. Those choices have a direct effect on file size. The app is acting like a mini document-imaging pipeline, and every pipeline has its own defaults.

Apple Notes keeps the workflow simple: scan, crop, and save into Notes. It is excellent for convenience, but the file-size outcome depends heavily on the capture conditions and the filter choices used during scanning. Adobe Scan leans harder into cleanup and OCR-style document enhancement, often producing polished, readable pages with stronger post-processing. Microsoft Lens historically offered dedicated document handling and save-to-PDF behavior, though Microsoft has now retired the standalone Lens app and points users to OneDrive scanning instead. CamScanner emphasizes automatic crop, enhancement, OCR, and document management features, which can create very clean output but also encourages multi-step processing that may increase weight if high-quality defaults are left untouched.

The right conclusion is not that one app is always smaller. It is that each app makes different tradeoffs between convenience, cleanup, OCR, and export quality. If you scan a black-and-white form in color using an enhancement-heavy app, the PDF can be much larger than necessary before you ever think about compression.

• Scanner apps are making image-processing decisions for you before compression starts.
• Document mode and grayscale-style cleanup usually save more space than plain camera capture.
• Enhancement, OCR, and HD-style export can make files cleaner, but not always lighter.

If a scanned PDF is too large, do not start with random repeated compression passes. First identify whether the scan is color when it could have been grayscale. Second check whether the DPI is obviously excessive for the destination. Third look at whether the app exported an image-heavy PDF with unnecessary pages, shadows, or margins. Only after those questions should you decide whether to rescan or simply compress the existing file.

For most upload and email workflows, the best starting settings are grayscale at 150 or 200 DPI, clean page crops, and OCR only if searchability is genuinely useful. If the file already exists and you cannot rescan, PDF Compressor is the fastest repair path. If the scan still refuses to shrink enough, the source settings were probably too aggressive and a cleaner rescan will beat another round of brute-force compression.

If this document also has to survive an email system, read Compress PDF Under 10MB for Email. If it has to fit inside a portal with a documented upload cap, Compress PDF for Upload Limits is the better companion. When the problem is truly scan-specific, though, the biggest win is nearly always upstream: fewer pixels, less color, cleaner capture.

• Check color mode first, DPI second, app export behavior third.
• For ordinary paperwork, grayscale 150 to 200 DPI is usually the right capture target.
• If the scan was created badly, a clean rescan often beats repeated compression passes.