DocSupra Document photo rejected
Your document photo was rejected. Here is why, and how to fix the file.
DocSupraCompliance Studio
Fix this file now
Drop the document here: it opens in the Compliance Studio, which asks where it is going. Nothing is uploaded.
Your browser reads the file on this device: DocSupra never uploads it. You see the finished file before you pay; paying is only for the download. Terms · Privacy
What it means. A human opened your file, could not read a field they needed, and stopped. It is a statement about the image, not about your paperwork, and it costs weeks.
It is the most frustrating rejection to receive, because the document in your hand is perfectly readable. The problem is not your document — it is what survived the trip from paper to screen.
The four causes, in the order they happen
1. Shadow across the page
The most common by far. You leaned over the page and blocked the light. The text is still there, just dark, and rebuilding the tone across the page normally recovers it completely.
2. Glare over a data field
Flash or a ceiling light reflecting off the paper puts a white patch exactly where the number is. Unlike a shadow, a blown-out area holds no detail at all — it cannot be recovered and the page has to be rephotographed without flash.
3. Photographed at an angle
Shooting from the side makes the far edge of the page smaller and blurrier than the near edge. On a form with fine print, half the page ends up below readable resolution even though the photo looks fine.
4. Over-compressed
Someone squeezed the file to fit a size cap by dropping the JPEG quality. That eats fine detail first, which is precisely the punctuation and the digits. A 3 becomes an 8 and a decimal point disappears.
Before you resubmit
- Open the file at 100% and read the smallest print on it. If you cannot, neither can the reviewer.
- Check every field the form actually asks about — a date, a number, a signature, a seal.
- Confirm the whole page is in the frame, including the edges. Cropped corners get rejected too.
- Check it is still within the size cap after correcting it.
Never retype, redraw or "clean up" what a field says. Correcting the lighting on a photograph is image processing. Changing what the document states is falsification, with consequences far worse than a rejection. Software should only ever change the file — never the content.
Make the page readable before you resubmit
Runs in your browser. Your document is never uploaded. See the finished result before you pay.
Open DocSupraThey refused your document at the counter. You can fix it tonight.
The short answer. When a document is refused in person it is almost never the document — it is the copy. Faint print, a shadow across the page, a photograph taken at an angle, or text that has gone grey are the usual reasons. All four are repairable from the photo you already have, in a browser, in about twenty seconds.
You took the day off, queued, and were told to come back with a legible copy. Nobody explained what legible means. It means a reviewer can read every field without effort — and that is a property of the image, not of the paper.
The 5 reasons, in plain words
- Faint or grey print. Guide text on official forms is printed in light grey on purpose. A bad copy turns it into nothing, and a reviewer sees a form with missing fields.
- A shadow across the page. Your own hand or head blocking the light. The reviewer sees a document that is half dark.
- Photographed at an angle. The page becomes a trapezoid, the lines stop being straight, and text near the far edge stretches.
- Glare from a flash or window. A bright patch that erases whatever was under it — often a stamp, a signature or a number.
- Too low resolution. Below the 300 DPI most offices expect, small print stops resolving and a number becomes a guess.
Which of them can software fix?
None of these require a scanner. Flattening the perspective, evening out the light, recovering faint print and exporting at the resolution the office expects are all done on the photograph you already took — and the document never leaves your device while it happens.
They will not accept the photo of your licence. It is the glare on the plastic.
The short answer. A driver’s licence is laminated, and laminate reflects. That bright patch sitting across your number or your face is what the reviewer cannot read. The second cause is the angle: an ID photographed from above becomes a trapezoid and the automatic reader fails on the geometry before a person ever sees it. Both are fixable from the picture you already took.
You sent it three times and it came back three times. Nobody tells you it is the reflection — they tell you it is not legible, which sounds like it is your fault.
The 5 reasons, in plain words
- Glare on the laminate. The most common cause by a distance. A flash or a ceiling light bounces off the plastic and erases whatever is under it, usually the licence number or the face.
- Photographed at an angle. Held above the card, the rectangle becomes a trapezoid. Readers reject the shape before a human sees it.
- Too dark. Your own shadow over the card — common precisely because you lean over it to take the picture.
- Corners cut off. Portals want all four corners visible. A photo that clips one is refused even when everything else is perfect.
- Too large, or HEIC. Many portals cap at 5 MB and refuse HEIC, which is what every recent iPhone shoots by default.
Which of them can software fix?
An ID is exactly the document where uploading it is the worst idea. Removing glare, flattening the perspective and evening out the light all run on your own device here, so the one thing you least want sitting on someone else’s server never gets there.
Your document upload keeps failing. Here is why.
Upload forms are famously bad at saying what went wrong. "Something went wrong, please try again" covers six completely different problems, and trying again fixes exactly none of them. Here they are in the order they actually occur.
The short answer. In order of how often they happen: the format is not accepted (HEIC is the usual culprit), the file is over the size limit, the dimensions are outside the allowed range, the session timed out while the file uploaded, the filename contains characters the system rejects, or the page itself is failing and the file is fine.
1. The format is not accepted
An iPhone saves photos as HEIC by default, and most receiving systems cannot open it. The upload often fails with no message at all, because the file never gets far enough to produce one. Converting to JPEG or PDF solves it. To stop it recurring: Settings → Camera → Formats → Most Compatible.
How to tell it is this
The failure is instant, and the same file fails on every attempt. If a different photo taken with a different app uploads fine, it is the format.
2. The file is over the size limit
The second most common, and the one people diagnose last, because the limit is usually written somewhere you did not read. The failure usually arrives after a long wait, at the very end of the progress bar.
3. The dimensions are outside the allowed range
Photo uploads in particular often have a minimum and a maximum pixel size, and a square requirement. A file can be well under the size limit and still be refused for being 1400 pixels wide where 1200 is the ceiling.
4. The session timed out
A large file on a slow connection can outlast the login session. The upload appears to complete and then bounces you to a sign-in page, or fails with a generic error. A smaller file uploads faster and simply avoids the problem.
How to tell it is this
It fails at the end, not the start, and the same file sometimes works on a faster connection.
5. The filename
Accented characters, emoji, hashes, ampersands and very long names still break older systems. Rename to plain letters, numbers, hyphens and underscores before assuming the file is at fault.
6. The portal is broken and your file is fine
It happens more than anyone admits, particularly near a filing deadline. If a small, plainly named JPEG also fails, the problem is not your document. Try a different browser once, then wait rather than re-uploading twenty times — repeated failed attempts occasionally trip rate limits and lock you out.
The five-minute triage
- Check the file extension. If it is .heic, convert it.
- Check the file size against the stated limit.
- Check the pixel dimensions if it is a photo upload.
- Rename to plain characters.
- If a tiny test file also fails, it is not you.
Why a screenshot of your document gets rejected
A screenshot records what your screen is showing, at the resolution your screen is showing it. That sounds obvious until you work out what it means for a full page of text: the file is not slightly under the requirement, it is a third of it.
The short answer. A full-page screenshot on a typical laptop captures the page at roughly 90 to 120 DPI, because that is all the screen was displaying. Filing systems commonly ask for 300. No processing can recover the difference — the detail was never captured.
The arithmetic
Suppose you open a Letter page in a viewer and it fills the height of a 1080-pixel-tall screen. The page is 11 inches tall, so you have captured 1080 ÷ 11 ≈ 98 pixels per inch. A 4K display roughly doubles that to about 196 — still short of 300, and only if the page really does fill the screen.
| Screen | Page filling the height | Captured DPI |
|---|---|---|
| 1080p laptop | 1080 px over 11 in | ≈ 98 DPI |
| 1440p monitor | 1440 px over 11 in | ≈ 131 DPI |
| 4K monitor | 2160 px over 11 in | ≈ 196 DPI |
| Phone screenshot | usually a partial page | lower still |
Why it looks fine to you
Because you are looking at it on the same screen that produced it, at the same size. It is only when the file is opened at full size, or printed, that the missing detail shows — and the person who opens it that way is the reviewer.
The other three reasons a screenshot gets flagged
- Interface furniture. Scroll bars, tabs, a browser address bar and a clock all end up in the file. It reads as a picture of a screen, not as a document.
- It is visibly a partial view. A screenshot usually shows what fitted on the screen, so the bottom of the page is missing — and an incomplete document is refused on its own.
- PNG size. Screenshots are usually PNG, which is lossless and large for a page of text, so the file can be both low-resolution and over the size limit at the same time.
What to send instead
- If the document exists as a file, send that file. Do not photograph or screenshot a PDF you already have — export or download it.
- If it only exists on paper, photograph it with the page filling the frame, then straighten it and even out the lighting.
- If it only exists inside a web portal, look for a download or "print to PDF" option before resorting to a capture.
Print to PDF is the underused answer. It re-renders the page as a document at full page size, rather than recording what the screen happened to show.
Related
Doing this for clients, not for yourself? DocSupra for teams adds the batch queue, one combined PDF per matter and a dated compliance report — still with nothing uploaded.
What it costs
See the finished file first — sharp on screen, 100% with the lens, no card and no account.
Prices are in USD and exclude any tax that applies in your country; Stripe calculates it and shows it before you pay.
See the full comparison →