Read a QR code that is already on your screen, without picking up your phone to photograph your own monitor. Drop in a screenshot, a photo or a whole folder of images and each code is decoded in your browser. It goes further than showing you the raw string: Wi-Fi codes come back as a network name, security type and password you can copy; contact cards come back as name, phone and email; location codes as coordinates. Codes shown light-on-dark decode fine, and large photos are retried at a smaller size, which often succeeds where the full-resolution original fails. Links are only made clickable when the scheme is safe — a QR code is untrusted input from a stranger's sticker, and a javascript: payload will never be handed to you as something to click. Your images are never uploaded.
| Code contains | You get |
|---|---|
| Website link | Host, path and a clickable link |
| Wi-Fi credentials | Network name, security type, password |
| Contact card | Name, organisation, phone, email |
| Location | Latitude and longitude, with a map link |
| Email or phone | Address or number, ready to copy |
| Calendar event | Title, location and times |
| Two-factor setup | Issuer and account — never the secret |
| Anything else | The raw text, copyable |
No. Each image is decoded in your browser and never transmitted. That matters here more than it looks — QR codes routinely carry Wi-Fi passwords, contact details and two-factor setup secrets.
Usually the code is too small, too blurred, cropped, or at too steep an angle. Try a tighter crop around the code, or a sharper image. The tool already retries with inverted colours and at a reduced size, which covers the two most common causes.
Yes, and it separates out the network name, security type and password rather than dumping the raw string. Passwords containing semicolons or colons survive intact, which naive decoders truncate because those characters are the format's own separators.
Reading one here is safe — nothing is followed automatically, and links are only made clickable for schemes that cannot execute code, so javascript: and data: payloads are shown as text. That is exactly the point: check where a code leads here before letting your phone open it.
No. For an otpauth code it shows the issuer and account but deliberately never prints the shared secret, since that secret is the entire credential and printing it on screen invites shoulder-surfing.
Yes. Drop in multiple files or a whole folder and every image is decoded, with the result shown per file.
Each image is drawn to a canvas and its raw pixels handed to jsQR, which locates the three finder patterns, corrects perspective and reads the Reed-Solomon-protected payload — the same error correction that lets a physical QR code survive being scuffed or partly covered. Decoding is attempted with both normal and inverted polarity, because light-on-dark codes are common in dark-mode screenshots and a reader that only tries one reports a perfectly good code as unreadable. Very large photographs are retried at a reduced size: scanning is proportional to pixel count, and a downscaled copy frequently decodes when the full-resolution original does not, since resampling smooths the sensor noise that breaks the module grid. The decoded string is then parsed against the conventions layered on top of QR — Wi-Fi credentials, vCard and MECARD contacts, geo points, mailto, tel, SMS, calendar events and otpauth. Those formats escape their own separators with backslashes, so the parser splits on unescaped delimiters only and treats just the first colon as the key separator; a naive split truncates any Wi-Fi password containing a semicolon or colon, which is a silent and very annoying failure. Links are only made clickable for schemes that cannot execute code: a QR code is untrusted input from a stranger's sticker or an email, and javascript: and data: payloads are a known phishing vector, so those are shown as plain text and never linked. A two-factor setup code shows its issuer and account but deliberately never prints the shared secret. Images are read in the page and never uploaded.