# Base32 & Base64URL codec — no upload

> Encode or decode Base32 and Base64URL in your browser. Nothing is uploaded — the data stays in the tab.

Encode and decode Base32 and URL-safe Base64 (Base64URL) — the variants used in TOTP secrets and tokens. It all happens in the browser, with nothing uploaded.

Base32 and Base64URL are the encodings you hit around auth and tokens — a 2FA secret to decode, a URL-safe token to inspect. Having both codecs handy avoids reaching for a script.

For standard Base64, use the Base64 tool; to turn a decoded secret into a working 2FA code, the security TOTP tool.

## How to

1. **Paste input.** Paste text or an encoded string.
2. **Pick a codec.** Choose Base32 or Base64URL, encode or decode.
3. **Copy.** Copy the result.

## FAQ

### How is Base64URL different from Base64?

Base64URL replaces + and / with - and _ (and often drops padding) so the output is safe in URLs and filenames. The tool handles both.

### What uses Base32?

TOTP/2FA secrets are commonly Base32-encoded, as are some file and key formats, because it avoids case-sensitivity and ambiguous characters.

### Is my data uploaded?

No. Encoding and decoding run locally in the tab.


## Related tools

- [Base64](https://www.safepaper.app/dev/base64)
- [TOTP generator](https://www.safepaper.app/security/totp)
- [Hex / ASCII / binary](https://www.safepaper.app/dev/hex-ascii)
- [URL encode](https://www.safepaper.app/dev/url-encoder)

---

Canonical HTML: https://www.safepaper.app/dev/base32
Markdown: https://www.safepaper.app/dev/base32.md

There is no upload endpoint — your files are processed in this browser tab. Open your network tab and check.