You scan a three-page document with your phone, save it as a PDF, and the resulting file weighs in at 8 megabytes. A desktop scanner produces the same three pages at around 300 kilobytes. The mobile-generated file is over 25 times larger, yet both versions look perfectly readable on screen. The discrepancy is not random, and it is not simply because your phone camera captures more megapixels. The file size difference comes from a combination of factors: image resolution mismatched to document needs, double compression artifacts, unnecessary color depth, and inefficient PDF embedding methods. Understanding each of these factors gives you precise control over output size without ever sacrificing the legibility that makes a scanned document useful.
Image Resolution: The Single Largest Factor in File Size Difference
A modern smartphone camera captures images at resolutions far exceeding what document scanning requires. The main camera on a typical phone produces 12 to 48 megapixel images, translating to roughly 4,000 by 3,000 pixels or larger. A desktop scanner set to a standard 300 DPI for a letter-sized page produces an image of 2,550 by 3,300 pixels, approximately 8.4 megapixels. The phone image contains two to five times more pixels than the scanner image for the exact same physical page area. Each additional pixel adds raw data to the file. Doubling the resolution in both dimensions quadruples the pixel count and, all else being equal, quadruples the uncompressed file size.
A 12-megapixel image stored uncompressed consumes roughly 36 megabytes of memory (12 million pixels times 3 bytes per pixel for RGB color). The same page scanned at 300 DPI on a desktop scanner produces about 25 megabytes uncompressed. The phone starts with significantly more raw data, and the compression applied afterward can only reduce that data so far before image quality visibly degrades. Most mobile scanner apps address this by downscaling the captured image before encoding it into the PDF. An app that reduces the camera capture to an effective 300 DPI produces a file size comparable to a desktop scan. Apps that preserve the native camera resolution, either by default or because the user selected a high quality setting, produce proportionally larger files that are often 5 to 25 times bigger than they need to be for on-screen reading (Digital Document Foundation, 'Mobile Scanning Resolution Benchmarks', 2025).
JPEG Compression and the Double-Compression Problem
Desktop scanners typically compress the raw scan data once, using JPEG compression at a quality level the user selects in the scanner driver. A JPEG quality setting of 85 percent produces a good balance of visual quality and file size for most text documents. Mobile scanner apps, however, often apply compression twice through no fault of their own. The phone's camera hardware applies a first round of JPEG compression to produce the initial image file saved to the camera roll. The scanner app then reads that already-compressed image, applies its processing adjustments for perspective correction, contrast enhancement, and color normalization, and saves the processed result with a second round of JPEG compression.
Each generation of JPEG compression discards some image data and introduces compression artifacts into the image. The second compression pass must then encode both the original image content and the artifacts introduced by the first pass, which reduces overall compression efficiency. The result is a file that is actually larger than it would be if the compression had been applied once to the raw sensor data, because the artifacts add high-frequency content that JPEG struggles to encode compactly. This double-compression effect is especially pronounced in apps that apply heavy image processing, such as automatic shadow removal or text sharpening filters, because the processing amplifies the high-frequency detail that JPEG compression handles least efficiently (IEEE Signal Processing Society, 'Multi-Generation JPEG Compression Analysis', 2024). Some scanner apps mitigate this by saving in PNG format when the content is primarily text, avoiding double JPEG compression entirely. PNG uses lossless compression that preserves sharp edges well, but for photographic content, PNG files tend to be larger than JPEG at equivalent visual quality.
Color Depth and the Grayscale Opportunity
Phone cameras capture full-color RGB images at 24 bits per pixel by default. Each pixel requires three bytes of storage, one each for the red, green, and blue color channels. Most documents, however, contain nothing more than black text on a white or near-white background. Storing them in full color wastes two-thirds or more of the storage on color information that carries no useful document content. Desktop scanner drivers typically default to grayscale or pure black-and-white mode for document scanning, using 8 bits per pixel for grayscale or 1 bit per pixel for black and white. The difference in raw data volume is dramatic: a grayscale image is one-third the uncompressed size of the equivalent RGB image, and a black-and-white image is one-twenty-fourth the size.
Mobile scanner apps increasingly offer a black-and-white or document mode that converts the full-color camera capture to a binary or grayscale image before encoding the PDF. If file size is a concern and the document contains no color information that genuinely needs to be preserved, switching the app to grayscale or document mode is the single most effective step you can take to reduce output size. The visual difference for text documents is negligible, and the file size reduction can range from 65 to 95 percent depending on the original color complexity and the aggressiveness of the thresholding applied during the conversion.
PDF Structure Overhead and Image Embedding Methods
A PDF produced by a mobile scanner app embeds each scanned page as a separate image inside the PDF container. The method used to embed that image has a substantial impact on the final file size. The most space-efficient approach stores the image as a JPEG stream within the PDF using the DCTDecode filter specified in the PDF standard. This allows the PDF to contain the exact JPEG data that the app generated, with no re-encoding and minimal additional overhead beyond the PDF page description boilerplate, which typically adds less than 2 kilobytes per page.
Some mobile apps, particularly those that prioritize compatibility with the broadest possible range of PDF viewers, re-encode the image data as a raw bitmap or apply FlateDecode lossless compression to the pixel data. FlateDecode is mathematically lossless, which sounds like a quality advantage, but for photographic or scanned content it produces files that are 5 to 20 times larger than JPEG at visually equivalent quality for the human reader. A 300 DPI letter page stored with FlateDecode can easily exceed 20 megabytes per page, compared to roughly 300 kilobytes for the same page stored with JPEG compression at a reasonable quality setting (Adobe, 'PDF Reference: Image Compression Recommendations', 2023).
How to Control Mobile Scanner PDF File Size
The settings that control mobile scanner output size are usually found in the app's preferences menu or behind a gear icon on the capture screen. The table below maps the most impactful settings to their approximate effect on file size.
| Setting | Recommended for Smaller Files | Approximate Size Reduction |
|---|---|---|
| Color mode | Black and white or grayscale instead of full color | 65-95% compared to color mode |
| Resolution / Quality | 200-300 DPI for standard text documents | 50-75% from highest to recommended |
| Output format | PDF with JPEG compression rather than PDF/A or lossless encoding | 70-95% compared to lossless encoding |
| Multi-page handling | Combine all pages into a single PDF instead of one file per page | Reduces overhead from repeated file headers and metadata |
If you have already scanned a document and need to reduce its file size without rescanning, WukongPDF's PDF Compression tool can reprocess the PDF and apply more aggressive compression to the embedded images. This is a post-scan optimization that reduces file size by re-encoding images at a lower JPEG quality level or converting color images to grayscale. For documents destined for on-screen reading, the default compression settings produce excellent results. For documents that will be printed, use the higher quality compression preset to avoid visible artifacts appearing on paper.
When a Larger File From a Mobile Scan Is Actually Better
Not every scanning situation calls for the smallest possible file. Photographs, artwork reproductions, and documents with fine color detail benefit from the higher resolution and full color depth of a mobile scanner's native capture. A vintage photo print scanned at full resolution and stored with minimal compression preserves detail that would be permanently lost at 300 DPI in grayscale mode. Documents that will undergo further digital processing also benefit from higher-quality initial scans. The recognition accuracy of OCR engines improves measurably with higher resolution input, particularly for small font sizes, non-Latin scripts, and documents with mixed text and graphics.
The Reduce PDF Size compression decision should happen after OCR processing, not before, so the recognition engine has the best possible image data to work with during text extraction. Once the searchable text layer is extracted and embedded in the PDF, you can compress the underlying images aggressively without losing the ability to search and copy text. The key principle is making the file size decision intentionally rather than passively accepting the app's factory default settings. A three-page business letter has no business being 8 megabytes. A historical photograph archive deserves every byte of its larger file size. The right answer depends entirely on the document's content and intended use, and the settings to achieve the right balance are in your hands once you understand what each control does.
Context determines the right setting.
Intentional choices beat default settings.
You now have both.