Unable to Read ID
Understanding and fixing this common KYC rejection
⚠️ What This Error Means
Unable to Read ID means the OCR engine extracted zero usable fields from your document. No name, no ID number, no date of birth, nothing. This is different from a blurry or low quality flag, where the system still pulls out a few fields correctly. Here it found no readable text at all.
That distinction matters because it changes where the problem probably lives. A partial failure is almost always a local image issue, a shadow across one line, a bit of glare on a corner. A total failure like this one is usually a bigger break somewhere upstream of image quality. Verification systems route documents through a pipeline built around expected document types and layouts, and when nothing at all comes back, it is often because that pipeline never recognized what it was looking at in the first place.
In practice that means one of a handful of things happened. You uploaded the wrong document type entirely, a selfie or a screenshot instead of an ID. Your document is a real ID but a type or country the platform's system was never built to read. The physical document is damaged badly enough that no characters are distinguishable, not just soft around the edges. Or the layout is one the system has genuinely never seen before, an unusual national ID design, a very old format, or a document that does not match any template it checks against. Extreme blur or terrible lighting can also cause a total failure, but that is the least likely explanation if the photo looks reasonably clear to your own eyes.
✅ How to Fix It
- Open the file yourself first. Before you touch the camera again, actually look at what you uploaded. Confirm it is a full, in-focus photo of your government ID and not a selfie, a screenshot, or the wrong file grabbed from your gallery. This single check rules out a large share of total failures immediately.
- Check that your document type is actually supported. Look at the platform's accepted ID list. If your country or document type is not on it, no amount of retaking the photo fixes this, since the system was never built to parse that layout.
- Get every line of text sharp and evenly lit. Use a bright, even light source and avoid any single shadow crossing the printed fields. Hold the camera steady or rest it on something solid so nothing is soft or doubled.
- Flatten the document and capture all four edges. Place it on a dark, non-reflective, flat surface. A curled corner or a bent card distorts the text just enough to break character recognition, and a missing edge can make the layout look wrong to the system.
- Inspect the physical card or paper for damage. Deep scratches, water staining, faded ink, or lamination that has gone cloudy can erase text permanently. If the card itself is degraded, no photo technique fixes that.
- Upload a fresh photo file, not a screenshot or converted scan. Take a new picture directly with your camera app and upload that JPEG or PNG. Screenshots, PDF exports, and heavily compressed re-saves strip detail that OCR engines depend on.
Total Failure vs Partial Failure
Unable to Read ID sits at the severe end of a spectrum of document quality errors. The other errors below still let the system extract some fields, which is a meaningfully different, usually easier problem to fix. Here is how they compare.
| Situation | What It Means | Likely Fix |
|---|---|---|
| Unable to Read ID | Total failure. Zero fields extracted, no name, number, or dates found anywhere on the document. | Confirm it is the right document type and country, check for physical damage, then retake with even lighting. |
| Document Blurry | Partial failure. Some fields read correctly, others are garbled or dropped where focus is soft. | Hold the camera steady, tap to focus on the text, retake in better light. |
| Low Resolution | Partial failure. Text is technically visible but too small or compressed for reliable character recognition. | Use your camera's native resolution, avoid re-compressed uploads, get closer to the subject. |
| Document Cropped | Partial failure. Fields inside the visible frame read fine, fields near the missing edge do not exist to the system. | Back up the camera and capture all four corners and edges in one frame. |
Let Us Help You Fix This
Try our free AI analysis first, or let our experts fix it for you.
Frequently Asked Questions
Why can the system not read my ID at all when other errors at least detect something?
Other errors like blur or glare still let the OCR engine detect text regions and pull out a few fields, even if some are wrong. Unable to Read ID means the engine never found any text to begin with, which points to a bigger problem than image quality, like the wrong document type or a layout it does not recognize.
Does this mean my document type is not supported?
It is one of the most common causes. Many verification systems only support a fixed list of document types per country, and an ID format outside that list, an old design, or a rare document category can return zero extracted fields even when the photo itself is perfectly clear.
Could I have accidentally uploaded the wrong file?
Yes, and it happens more often than people expect. A selfie uploaded to the document slot, a screenshot of a PDF viewer, or a photo of your phone case instead of your ID will all produce a total read failure, since there is no document text in the frame for the system to find.
What should I check first before trying again?
Open the file yourself first and confirm it actually shows your full ID clearly, since that single check rules out half the total failure causes. After that, confirm the document type is on the platform's supported list before you spend time retaking the photo.
Can a damaged or very old ID cause this error?
Yes. Heavy scratching, water damage, faded ink, or worn lamination can degrade the printed text enough that no character recognition is possible, which is different from a blurry photo of an otherwise intact document and usually cannot be fixed by retaking the picture.