Troubleshoot pixels, margins, and file limits
QR Code Not Reading? Check the Image First
When a QR image will not read, first identify what failed: file acceptance, locating the symbol, decoding its data, or interpreting an unsupported payload. Each outcome needs a different next step.
Use the public demo in the QR code reader as a starting check, then compare your original image. Change one image feature at a time and keep private QR contents out of troubleshooting screenshots.
Before leaving the reader: copy the result you need while the panel is visible. Changing tabs or apps clears its image and decoded data. Clear does not erase your device clipboard.
Check whether the file was accepted at all
A rejected file is not evidence that the QR pattern is damaged. This reader accepts one local JPEG or PNG, no larger than 10 MiB, with neither side exceeding 8,000 pixels and a total area no greater than 16 million pixels. These are separate checks. A 5,000 by 4,000 image has 20 million pixels and is too large even if its compressed file occupies only a few megabytes. Detected animation is rejected. Check the actual format and dimensions in your local image editor; changing a filename extension does not turn a different file format into PNG.
There is no PDF import, camera mode, or remote-image fetch. If the source is a document or a web preview, prepare an appropriate saved JPEG or PNG locally before selecting it. Avoid repeatedly exporting at very low quality just to reduce bytes, because smaller compressed size can come at the expense of readable edges. Cropping out irrelevant material may address both dimensions and file size while retaining useful detail. If the public demo works but your file is rejected before decoding, resolve that acceptance problem before investigating the QR contents or any account named beside it.
Isolate the intended standard QR symbol
Inspect the original at a readable size and locate the exact code you intended to read. A collage, account-settings page, or marketing sheet may include several symbols. This reader returns one recognized payload, not an exhaustive multi-code inventory. Crop externally to leave one complete target and its margin, then select that saved crop. If the first result describes something unexpected, check the selected region before assuming the code itself changed. A successful read of a nearby symbol does not prove that your intended symbol was also located, decoded, or even present in the processed image.
Confirm that you have a standard QR rather than a one-dimensional barcode, a proprietary social badge, or another two-dimensional symbol. Similar-looking square graphics do not necessarily share an encoding. This reader does not promise support for Micro QR, rectangular variants, or proprietary Snapcodes. Extra resizing cannot supply a decoder for an unsupported format. For a supported-looking symbol, retain the whole square, including the three large corner finder patterns. If an interface overlay covers a corner, obtain a clean capture instead of painting a replacement pattern or cropping away the obstruction and hoping the rest will be sufficient.
Restore breathing room without cutting the border
A crop should remove the surrounding page, not the symbol boundary. Standard QR needs an empty quiet zone four modules wide on every side; a module is one of its small squares. Nearby text, a decorative frame, or a crop touching the outer modules can make the boundary harder to locate. Work from the original and keep the full clear margin where available. If your source already omitted the margin, a local editor can add blank space outside an otherwise complete symbol, but that does not replace any modules already cut away from its edge.
Use a simple, even background around the code rather than leaving nearby text or graphic elements in the crop. Check all four edges rather than judging only the two most visible sides. A screenshot can look comfortably framed while a notification or caption touches the bottom edge. Do not add a border over the symbol or round off the corners to make the crop look tidy. The goal is to present the existing geometry clearly, not redesign it. Retry once with the corrected margin, and record only the nonsecret change you made if you are comparing attempts.
Change one observable thing
Retry a clean crop from the original
Keep the complete symbol and clear margin. Use the public demo when checking the workflow without exposing private data.
Keep useful resolution through the downscale step
The reader decodes the native bitmap after checking its header, then downscales images whose longest side exceeds 2,000 pixels. It does not upscale small images. That makes the share of the picture occupied by the code important. Suppose a 6,000-pixel-wide screenshot contains a 240-pixel-wide QR. Processing the entire screenshot reduces that symbol to roughly 80 pixels across. Cropping the original around the code before selection can avoid that unnecessary reduction. This is why uploading a larger overall screenshot is not automatically better: most of its pixels may describe unrelated page content rather than the symbol.
Judge detail inside the code, not merely the pixel dimensions reported for the file. Dense symbols contain more modules, so each square gets fewer pixels when the displayed size stays fixed. Enlarging a tiny thumbnail makes larger blocks or smoother blur, not newly captured detail. Prefer an original image download or a fresh capture with the symbol clearly rendered at a useful size. Avoid a chain of screenshots of screenshots. If you can no longer distinguish neighboring squares in the original, a better source is a more promising next step than another enlargement of the same limited sample.
Remove capture problems instead of inventing detail
A photograph can introduce glare, motion blur, perspective distortion, or a screen interference pattern that was absent from the original QR. Where possible, obtain the original digital image. Otherwise prepare a clearer saved photo outside this tool: keep the camera square to a flat symbol, bring it into focus, use even light, and avoid reflections. The reader itself has no camera capture or perspective-correction controls. Rotation alone is not the same problem as strong perspective skew; a tilted rectangle with compressed modules on one side may need a better capture rather than simply being turned upright.
Look for ringing around edges from repeated JPEG compression, low contrast between modules and background, transparency over busy artwork, or an opaque logo hiding part of the code. Prefer a clean, high-contrast original when it exists; do not assume filters or aggressive sharpening reconstruct lost information. QR error correction can sometimes tolerate damage, but its existence is not a guarantee that this particular obstruction is recoverable. Avoid relying on a percentage of visibly covered area as a repair allowance. If the source has missing or merged modules, stop editing when changes become guesses and request a fresh image through an appropriate trusted channel.
Interpret the retry result and stop at the right boundary
After each controlled change, read the outcome carefully. A no-result or bounded decoding timeout says that this attempt did not yield a readable payload, not that an account is invalid. A decoded HOTP or otpauth-migration result is different: the image was read, but that authenticator format is recognized as unsupported. More sharpening cannot change that category. A URL or plain-text result is also a completed image read, not an instruction to follow it. Results begin masked, and URLs remain text without automatic opening. The reader never checks service identity, visits a destination, or tests account acceptance.
Finish with deliberate handling of the working data. The image and result clear when hidden and on pagehide, pageshow, and freeze; copy any needed value explicitly before changing tabs. Processing stays local, and only bounded height messages go to the parent, not the image or payload. There is no PDF, project, export, or saved reading history. Clearing does not erase the system clipboard or guarantee secure removal from browser memory, extensions, or a compromised interface supplied by the parent. Use public demos for support examples and share a nonsecret description of the geometry problem instead of private enrollment material.
Questions about Fix an Unreadable QR Image
Why can a small file still exceed the reader limits?
Compressed bytes and decoded dimensions measure different things. A JPEG or PNG must meet all limits: at most 10 MiB, at most 8,000 pixels per side, and at most 16 million pixels overall. Crop or prepare an appropriate local image first.
Will enlarging a blurry screenshot make the QR readable?
Enlargement cannot restore missing detail. Start with the original, crop the intended symbol with its clear margin, and avoid losing resolution when a large surrounding screenshot is downscaled. Request a sharper source when the modules have merged.
Does a failure mean the link or authenticator account is invalid?
No. Image acceptance, pixel decoding, payload support, and account acceptance are different questions. The reader handles one image locally; it never opens destinations or tests accounts. An unsupported decoded format is not fixed by changing the image geometry.
Continue with another QR-reading guide
Read an image in the QR Code Reader & 2FA QR Decoder or explore the related topics below. Find other practical utilities in all free tools.
A focused next attempt
Check the image before the contents
Confirm format and limits, isolate one standard QR, and preserve sharp modules. Stop when a better source or a different trusted workflow is needed.