Inspect enrollment data deliberately

Decode an Authenticator QR Code Without Opening It

An authenticator QR image can contain a reusable setup secret. Decoding it is credential inspection, not an account check, a login approval, or a way to recover a key that is missing from the image.

Use the public authenticator demo first. For authorized private material, prepare a local crop and read it with the QR code reader. Keep the image and decoded result off shared screens and out of routine work documents.

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.

Decide whether the image is enrollment material

Start with the context in which the image was provided. A profile QR may simply identify a public page. A login or device-pairing QR may represent a session challenge. An authenticator enrollment QR commonly packages a secret and configuration as an otpauth URI. These purposes are not interchangeable, even when the pictures have the same square outline. Reading the pixels does not approve a session, establish account ownership, or confirm that an enrollment remains current. If the screenshot has lost its original context, a familiar account label inside the decoded data is not enough to restore that trust.

Use only an image you are authorized to inspect. If you need to demonstrate the process to a colleague, choose the published demo rather than a real enrollment screenshot. Its shared example data is not suitable protection for an account. Avoid forwarding an uncertain image to a group chat for identification: the QR may itself be the credential, even while the secret is not visible as letters. You can describe a nonsecret observation such as an unsupported format without attaching the image, the account label, the complete payload, or any setup key it contains.

Prepare one complete code in a local image

The input is one local JPEG or PNG, not a pasted URI, camera stream, PDF, or remote image address. The file must be at most 10 MiB, at most 8,000 pixels on either side, and at most 16 million pixels in area; detected animation is rejected. Crop in a local editor before selecting it here. Preserve the whole symbol and a clear border on all four sides. Remove unrelated account details from the crop where possible without cutting into the code. A page containing several enrollment images should be reduced to the single intended symbol externally.

The reader validates image headers, decodes the bitmap, and downscales only when needed to fit a 2,000-pixel longest side. A small code buried in a large capture can lose useful detail during that reduction, so work from the original image rather than a tiny preview. Cropping cannot repair a blurred or incomplete source. One successful read returns one recognized payload, not a complete list of enrollments or confirmation that the picture contains only one. If another symbol appears in the crop, isolate your target more carefully instead of treating the first result as a multi-account import.

Inspect the key and settings without assuming an identity

A standard otpauth://totp URI can carry a secret, issuer, account label and calculation settings. This reader deliberately displays only the raw setup key and the algorithm, digit count and period; issuer and account labels are not shown, nor is the complete enrollment URI. The key starts masked until you reveal it. Establish identity from the trusted original setup context. Even a label in the source image would report only what its creator encoded, not prove who issued the QR or whether a service still accepts that enrollment.

Check whether each calculation setting was explicit or defaulted. Missing algorithm, digits, and period are interpreted as SHA1, six digits, and 30 seconds, and marked as defaults. That marking preserves a useful distinction: the parser supplied a conventional value rather than discovering an explicit instruction in the image. Consider a fictional training enrollment whose label is Demo Practice and whose period is absent. Reading 30 seconds alongside a default marker does not mean that an account was contacted to confirm it. If trusted enrollment instructions disagree with the decoded package, stop and resolve the source discrepancy before using a secret elsewhere.

Practice without private credentials

Inspect the public authenticator example

Check which settings are explicit and which are marked defaults. Public demonstration secrets must never protect real accounts.

Separate a valid payload from a compatible handoff

Validation checks URI syntax, a canonical Base32 secret, and the relevant parameter rules. Duplicate known parameters are rejected rather than resolved by guesswork. An explicit period must be positive. The supported algorithm choices for handoff are SHA1, SHA256, or SHA512, with six or eight digits. Do not edit an unfamiliar value until it passes validation: that produces a different package without establishing what the original enrollment required. Base32 is an encoding with structural requirements, not a password hint. A plausible-looking sequence of letters is not permission to reconstruct missing characters or change the underlying credential.

Compatibility is a second question. The separate 2FA authenticator offers only 30-second and 60-second periods. A valid TOTP enrollment with a 45-second period can be inspected here, but it must not be described as compatible with that generator or silently converted to either available option. A copied raw key does not carry its algorithm, digits, or period with it. Treat the decoded settings as a set that must remain intact during any authorized manual use. If the destination cannot represent the exact configuration, stop the handoff rather than changing the enrollment to fit the destination.

Recognize formats that this reader does not unpack

Counter-based otpauth://hotp material is recognized as unsupported. It is not a time-based enrollment waiting for you to choose a period. Likewise, an otpauth-migration package is recognized without decoding its migration contents or presenting a recovered account inventory. Copy setup key is limited to valid, accepted TOTP payloads, not offered as a conversion route for those unsupported formats. Use the originating trusted authenticator workflow when a package requires its own import process. Changing the scheme name, extracting a guessed substring, or relabeling a transfer image does not establish a valid standalone TOTP enrollment.

A syntactically decoded result may instead be an ordinary web address, application-specific data, or a login challenge. URLs stay text, never automatic links; the reader neither fetches their destination nor tests a session. It also does not recognize every branded symbol as a standard QR or recover secrets from proprietary images. Once text has been extracted, repeated cropping will not turn an unsupported payload type into supported enrollment data. Read the category as the outcome of inspection and return to the authorized source workflow when it calls for something other than this single-image TOTP parser.

Copy deliberately and end the inspection session

This reader generates no current OTP. If manual use in the separate 2FA authenticator is appropriate and every setting is supported, copy the accepted setup key before switching tabs, then enter it and match the settings yourself. There is no automatic secret transfer or account connection. Hiding the page and pagehide, pageshow, or freeze events clear the working image and result. Returning does not resume the inspection. Clear also ends it explicitly. Do not rely on the old result remaining available while you open another tab to check a setting.

The selected image and decoded data are processed locally in the sandbox, not sent to the parent page; only bounded layout-height messages leave it. They are not added to page URLs, logs, analytics, exports, or history. There is no PDF report, downloadable project, or saved enrollment collection. Those controls do not erase a copied clipboard value or guarantee removal of every browser-memory copy. Extensions, capture software, and a compromised parent that replaces the interface remain outside that guarantee. Finish with Clear, handle the clipboard under your device policy, and never describe local parsing as proof that a service will accept the enrollment.

Questions about Decode Authenticator QR Codes

Is an authenticator QR the same as a temporary login code?

No. A TOTP enrollment QR can contain the reusable setup secret and configuration. This reader inspects that material but generates no current OTP, approves no session, and cannot confirm acceptance by an account provider.

Can I use a valid 45-second enrollment in the separate generator?

Not with that period. The separate generator supports only 30 or 60 seconds. The reader can inspect a valid unsupported period without changing it; rounding to an available period would change the configuration rather than make it compatible.

Can the reader extract accounts from an authenticator transfer QR?

No. An otpauth-migration package and HOTP material are recognized as unsupported. They are not unpacked, converted, or turned into a multi-account inventory. Setup-key copying is restricted to valid, accepted TOTP data.

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.

Keep the configuration intact

Read first, choose a compatible next step

Inspect one authorized image. Copy only deliberately, preserve every required setting, and clear the working session when finished.