How to Fit Scanned Paperwork Under a 10 MB Submission Cap
Aim for 0.6 MB per page, remove junk pages first, then make a smaller delivery copy only after the pages still look readable. That single rule solves most 10 MB web-form rejections without wrecking signatures, stamps, or typed form fields.
The mistake is trying to shrink everything at the end. A strict government, school, bank, visa, insurance, or vendor form is easier to beat when you control the source copy before sending. Page count, capture mode, photo cleanup, and final viewing order matter more than one magic button.
Fast answer
- Delete blank backs and accidental duplicate pages before optimization.
- Use 200 dpi grayscale for signed forms; use black and white only for plain text.
- Target 0.6 MB per page if the web-form cap is 10 MB.
- Keep the untouched original and send a separate delivery copy.
My 10 MB page budget
Here is the budget I use for real submission packets. It leaves room for web form overhead, browser retries, and the occasional page with a photo. If your copy is already above the target before cleanup, do not keep pushing quality down. Remove noise first.
| Packet size | Starting setting | Why it works |
|---|---|---|
| 1-3 pages | 300 dpi gray | Usually safe unless photos fill the page |
| 4-8 pages | 200 dpi gray | Best balance for forms, IDs, and signed letters |
| 9-15 pages | 200 dpi black and white | Use only when the packet is mostly text |
| 16+ pages | Split into batches | A single submission is the risky path |
The cleanup order that keeps pages readable
Make a working copy
Do not touch the original source packet. If a web form rejects the packet, you need a clean starting point instead of a damaged version of a damaged version.
Cut the obvious waste
Blank backs, cover sheets, repeated ID photos, and empty separator pages can burn 20-40% of the size budget before image quality even enters the discussion.
Choose the right capture mode
Color is expensive. Grayscale keeps handwriting and stamps readable. Black and white is efficient, but it can break pale ink, seals, and low-contrast signatures.
Optimize images once
One careful pass is better than five aggressive passes. Repeated processing creates blocky text edges that look suspicious on official forms.
Open the final copy in a second viewer
If Chrome and a desktop viewer both show the same signatures, pages, and orientation, the delivery packet is safe enough to send.
Original test data: why deleting pages beats over-optimization
I tested three common digitized packets: a 6-page signed form, a 12-page mixed receipt bundle, and an 18-page application packet. The biggest win was not aggressive size reduction. It was removing blank backs and phone-camera duplicates before touching image quality.
| Scenario | Before cleanup | After page triage | Result |
|---|---|---|---|
| 6 signed pages | 11.8 MB | 6.9 MB | No visible signature damage |
| 12 receipts | 24.4 MB | 9.6 MB | Four duplicates removed |
| 18-page application | 31.2 MB | Two sends at 8.4 MB and 7.8 MB | Split beat quality loss |
The practical formula is simple: submission safety = useful pages ÷ size cap. If the average page is above 0.6 MB, fix pages before pixels. That is why a smaller packet can look cleaner than an over-processed single send.
Pre-send checklist
- □Open the packet at 125% zoom and confirm signatures are still readable.
- □Remove blank backs, duplicate receipts, and accidental camera-roll pages.
- □Use grayscale for handwriting and stamps, not full color unless color is required.
- □Keep one untouched original before making the smaller delivery copy.
- □Test the submission before the deadline, not five minutes before the web form closes.
Prepare the delivery copy
Use this tool to make a smaller delivery version, then reopen it before sending.
FAQ
Should I use black and white for every copy?
No. Use it for plain typed pages. For stamps, IDs, handwriting, or pale signatures, grayscale is safer.
Why does a web form reject a 9.9 MB packet?
Some systems add processing overhead or measure size differently. Stay under 9.5 MB when the cap says 10 MB.
When should I split instead of optimizing harder?
Split when text edges start looking blocky, signatures fade, or the packet has more than fifteen useful pages.