DPI Explained: What Resolution Do Documents Really Need?
DPI stands for Dots Per Inch. Along with PPI (Pixels Per Inch), it is one of the most widely misunderstood metrics in digital document processing. Users often believe higher DPI is always better, resulting in 20 MB files that jam email inboxes and crash web forms.
The Mathematical Relationship Between DPI and File Size
DPI is a two-dimensional area density measurement. This means file size does not increase linearly with DPI—it increases with the square of the DPI ratio:
For a standard US Letter or A4 document (approx 8.5 × 11 inches):
- 72 DPI: 612 × 792 pixels = ~484,000 pixels (~100 KB)
- 150 DPI: 1,275 × 1,650 pixels = ~2,100,000 pixels (~450 KB) — 4.3x more pixels than 72 DPI
- 300 DPI: 2,550 × 3,300 pixels = ~8,415,000 pixels (~2.8 MB) — 17.3x more pixels than 72 DPI
- 600 DPI: 5,100 × 6,600 pixels = ~33,660,000 pixels (~12 MB+) — 69.5x more pixels than 72 DPI
The Truth About 300 DPI vs 150 DPI
300 DPI was historically defined by commercial printing presses using physical ink halftone screens on high-gloss paper. At arms length, the human eye cannot distinguish individual dots beyond 300 DPI on physical paper.
However, for documents reviewed on computer screens, tablets, or smartphone displays, a resolution of 110 to 150 DPI provides 100% legibility for standard typography while consuming less than 10% of the byte storage. Scanning office memos or tax receipts at 600 DPI creates enormous files without contributing any meaningful legal or visual value.
Recommended DPI by Use Case
| Use Case | Recommended DPI | Why |
|---|---|---|
| Email Attachments & Quick Sharing | 72 – 96 DPI | Keeps entire document under 1 MB limit |
| Government, University & Job Portals | 110 – 150 DPI | Optimal balance between 200 KB cap and OCR readability |
| Passport & Driver's License Scans | 150 – 200 DPI | Preserves microprint and security watermarks |
| Physical Print Reproduction & Archival | 300 DPI | Required for laser and inkjet halftone fidelity |
Inspect, adjust, and downsample document DPI levels with real-time file size computation.
About Pushpendra Sharma
AuthorPushpendra is the creator of DocuShrink and a systems engineer specializing in WebAssembly, browser sandboxing, and client-side document processing architectures. He writes extensively on verifiable privacy, byte-stream optimization, and high-performance document tools that run with zero server dependencies.