Read the code on your own screen
Scan a QR Code From a Screenshot
When a QR code is already on your phone or computer screen, you can inspect a saved screenshot on that same device. You do not need a second screen or a camera. The useful sequence is capture, crop externally if necessary, select the local image, and review the decoded text.
This reader accepts one still JPEG or PNG and returns one recognized QR payload. It does not scan PDFs, use a camera, accept a remote image URL, expose an API, or fetch or automatically open a decoded destination. Start with a clear image file rather than a link to an image.
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.
Capture the complete code on the device showing it
First make the full code visible, including its outer border, and dismiss any notification covering it. On Windows, press Windows + Shift + S and make a rectangular capture around the code with some clear space on every side. Save the capture as a local PNG or JPEG file; a clipboard-only snip is not yet the file you need for this workflow. If the code is displayed as an image, saving its original file may preserve more detail than taking another screenshot of a scaled preview.
On an iPhone with Face ID, briefly press the side and volume-up buttons together; on a Home-button model, use its documented Home and side or top button combination. On many Android phones, press power and volume down together; the manufacturer may provide a different method. Save the still capture, then select that image from the reader’s file chooser on the same device. There is no need to send it through messaging or email first. Before capturing a security setup screen, consider whether saving the reusable enrollment secret in your photo library is appropriate at all.
Crop externally and isolate one complete symbol
Open the screenshot in your device’s image editor and crop away browser chrome, conversation text, and unrelated artwork. Cropping is performed outside this reader. Preserve every corner of the symbol and its surrounding quiet zone, the blank area separating it from other content. Standard QR guidance calls for a clear margin four modules wide, where a module is one small square of the code. Do not crop exactly against the outermost dark squares or place a selection border through them. Save the crop as a separate still JPEG or PNG.
If the screenshot contains two or more codes, create a crop containing only the one you want to inspect. The reader returns one recognized result, not a comprehensive inventory, so a successful scan of a crowded flyer might identify a different code from the intended one. Label your local crops by purpose without putting secret values in their filenames. Remove nearby private information by framing the crop, not by drawing across the code. For a tilted photograph embedded in a screenshot, prefer a straight, original source image when you can obtain it.
Check bytes, dimensions, and the downscale together
Inspect the saved file’s properties before selecting it. The reader accepts at most 10 MiB, a maximum of 8000 pixels on either side, and no more than 16 million pixels overall. Width multiplied by height gives the pixel count. A 6000 by 3000 image exceeds the total at 18 million pixels even though neither side exceeds 8000. An 8001 by 100 image exceeds the side limit despite its small total. All limits apply before decoding, so compressing a file below the byte limit does not solve excessive dimensions.
After validation, an accepted bitmap with a longest side above 2000 pixels is downscaled to that longest-side limit. Smaller images are not enlarged. This matters when a small code sits inside a large screenshot: reducing a 6000-pixel-wide image to 2000 pixels makes a 150-pixel-wide code only about 50 pixels wide. An external crop around the code before selection avoids shrinking all that surrounding screen area. Keep sufficient border and source detail, rather than aiming for a particular file size alone. A tiny file can still contain an unreadably small or blurred QR symbol.
Keep the useful pixels
Inspect your cropped screenshot
Select one complete QR code in a still JPEG or PNG and review the decoded text locally.
Select the image and inspect the result as text
Select the saved JPEG or PNG in the reader and check that its preview contains the intended complete code. Let the attempt finish before deciding what to change. A failed attempt means the reader did not recognize a supported QR payload from that image; it does not establish that the encoded address is invalid. If the image is rejected, check its actual format, dimensions, and size rather than repeatedly selecting the same file. Renaming another format with a PNG or JPG extension is not a conversion, and detected animation is rejected.
When a result is available, explicitly reveal it and inspect the entire value. A web address stays plain text: there is no automatic link, destination fetch, or opening action. Compare its true hostname and path with what you expected from the source. A familiar logo beside the code is not destination verification. Other results may be plain data or an authenticator enrollment rather than a website. Copy only through an explicit action, and only when you know where the value belongs. The reader does not approve a login, recover an account, or connect an external service.
Improve the source instead of enlarging damaged pixels
PNG is a good choice for a fresh screenshot because it preserves sharp square boundaries without JPEG’s lossy compression. An existing clear JPEG can still work; converting it to PNG cannot undo compression already present. Avoid repeated messaging-app transfers, thumbnail downloads, and resaves that make edges softer. If the original page can render the code larger and sharply, capture that improved rendering. Merely magnifying a low-resolution screenshot adds pixels without recovering the original small-square pattern. Source quality, not the apparent display size in a photo viewer, is the useful distinction.
Look for clipped corners, a missing quiet zone, overlays, washed-out contrast, or a decorative logo covering too much of the symbol. Start again from an unobstructed original where possible. Do not paint guessed squares into place or rely on sharpening filters to reconstruct missing data. There is no universal minimum pixel width that guarantees every QR code will read: denser codes contain more modules and need adequate detail across them. After one sensible crop and a better-source attempt, ask for a fresh image or a nonsecret text reference instead of endlessly exporting the same damaged screenshot.
Treat enrollment screenshots and clipboard copies as sensitive
An accepted otpauth://totp result contains reusable enrollment material, not a current login number. The reader does not generate one-time passwords or test whether an account accepts the key. When setup-key copying is available, manually match the algorithm, digit count, and period in your intended trusted tool. Missing settings are identified as defaults of SHA1, six digits, and 30 seconds. The separate 2FA tool supports 30- or 60-second periods only; do not convert another valid period to fit it. HOTP and migration exports are unsupported here. Never transfer an enrollment key or URI through any page URL, query string, or fragment.
Keep the reader visible until you have reviewed and copied what you need. Becoming hidden or receiving pagehide clears the current inspection, and page restoration does not bring the result back. Copy while visible before switching tabs, then perform any manual entry yourself. Local decoding does not delete the screenshot, clear the operating-system clipboard, remove clipboard history, or promise secure memory erasure. Photo backups may also retain the source capture. Browser extensions, device compromise, and a compromised parent page that replaces the interface remain outside the guarantee. Use a trusted environment for secrets and clean up saved captures separately.
Questions about QR Codes From Screenshots
Can I scan a screenshot on the same phone that displays it?
Yes. Save a still JPEG or PNG, crop it externally if needed, and choose that local file in the reader. No second device or camera is required. Keep one complete QR code and its clear border in the selected image.
Why does a large screenshot fail even when the code looks sharp?
It may exceed the byte, side-length, or total-pixel limit. An accepted large image is also downscaled to a 2000-pixel longest side, which can make a small code too tiny. Crop around the intact code externally before selecting it again.
Why did the result disappear when I changed tabs?
The reader clears its state when the page becomes hidden and on pagehide. Review and copy while it remains visible, then switch tabs for any manual entry. Returning requires a new inspection; clearing does not remove earlier clipboard copies or saved screenshots.
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.
Stay on the same device
Read the code already on your screen
Prepare the image first, keep the reader visible while copying, and manage sensitive captures separately.