TOTP key in Base32
- Input
- JBSWY3DPEHPK3PXP
- Expected output
- Bytes: 48 65 6c 6c 6f 21 de ad be ef
This is the key "Hello!\xde\xad\xbe\xef" encoded in Base32, classic RFC example.
base32 totp 2fa authenticator key
When you scan a 2FA authentication QR code or type a manual key, you are using Base32. The TOTP protocol (RFC 6238) uses Base32 as the interchange format for secret keys because it is case-insensitive, has no ambiguous characters and is easy to type.
This is the key "Hello!\xde\xad\xbe\xef" encoded in Base32, classic RFC example.
Use the result as technical or educational support, keeping the tool limits explicit in the workflow.
If the other side says RFC 4648 without qualifying, it means the A-Z2-7 alphabet with padding. Use base32hex when the alphabetical order of the encoded text has to follow the numeric order of the data, which is the case for NSEC3 in DNSSEC. Use Crockford when the code will be read and typed by people and you want to catch errors on the spot with the check symbol. Use z-base-32 when the value will be spoken aloud. Picking the wrong one corrupts nothing, but the other side will not be able to decode it.
Yes, to verify the Base32 format of a backup key. Never enter active 2FA keys into unknown websites. In this case, decoding is performed entirely in your browser, no data is sent to any server.
No. It helps explain the scenario and use the tool more safely, but real decisions should consider official sources, full context and qualified guidance when needed.
ABCDEFGHIJKLMNOPQRSTUVWXYZ234567Everything is computed in your browser, including the loaded file and any pasted secret. Nothing is sent to a server.