handyman
Hazuu Tools

Base32 Encode

Encode text to Base32 format — paste, encode, and copy instantly.

Input Text
Output Base32
Encoded Base32 will appear here...
info

About Base32 Encode

Base32 Encode converts plain text into Base32 format — a binary-to-text encoding scheme that uses a 32-character alphabet of uppercase letters A through Z and digits 2 through 7. Each group of five bits from your input maps to one Base32 character, and the output is padded with equals signs so its length is a multiple of eight. The result looks like JBSWY3DP and contains no lowercase letters, no special characters, and no whitespace.

The encoding is designed for environments that cannot reliably preserve letter case or that reject symbols like + and /. TOTP-based two-factor authentication secrets (Google Authenticator, Authy, and compatible apps) are distributed as Base32 strings precisely because they survive copy-paste between upper- and lower-case systems. DNS labels, case-insensitive file systems, and some data formats share the same constraint. Use this tool whenever you need to prepare a binary value or secret key for those contexts — not when you simply need to shorten or obfuscate a URL (URL encoding is the right choice for that).

Every conversion runs entirely in your browser. The tool uses the native TextEncoder API to convert your text to UTF-8 bytes and then applies the RFC 4648 Base32 alphabet in pure JavaScript. Nothing is uploaded, logged, or transmitted to any server, so secrets and private keys stay on your machine. The tool is free, requires no account, and has no usage limits.

star

Key Features

check_circle

RFC 4648 alphabet

Uses the standard A-Z plus 2-7 alphabet with correct equals-sign padding, producing output that is compatible with TOTP libraries, DNS tooling, and other RFC 4648 consumers.

check_circle

Case-insensitive output

Every character in the output is uppercase and drawn from a 32-symbol set, so the encoded string survives round-trips through systems that fold or mangle letter case.

check_circle

UTF-8 aware encoding

Text is first converted to UTF-8 bytes via the native TextEncoder API before encoding, so accented characters, non-Latin scripts, and emoji are handled correctly.

check_circle

100% client-side, no upload

All computation happens in your browser. Secrets, API keys, and seed phrases never leave your device, making the tool safe for sensitive inputs.

check_circle

Instant one-click copy

A single copy button grabs the full encoded string so you can paste it straight into an authenticator app, config file, or DNS record.

check_circle

No account or rate limit

Encode as many strings as you need, as often as you need, at no cost and without signing up.

help

How to Use

01

Enter Text

Type or paste the text you want to encode into the input pane.

02

Encode

Click "Encode" to convert your text to Base32 format.

03

Copy Result

Use the copy button to grab your Base32-encoded output.

code_blocks

Example

Each group of five input bits maps to one character from the A-Z/2-7 alphabet. The string "Hello" encodes to eight Base32 characters with no padding required.

Plain text input
Hello
Base32 output
JBSWY3DP
lightbulb

Common Use Cases

  • arrow_circle_right

    Generating TOTP authenticator secrets

    Two-factor authentication apps like Google Authenticator and Authy expect the shared secret in Base32 format. Encode your raw secret key here to produce the string you enter into or QR-encode for the authenticator app.

  • arrow_circle_right

    Encoding values for case-insensitive systems

    Some file systems, DNS labels, and legacy databases fold all text to one case. Base32 output contains only uppercase letters and the digits 2-7, so it survives intact where Base64 would be corrupted by case-folding.

  • arrow_circle_right

    Preparing seed phrases and recovery codes

    Hardware wallets and backup tools sometimes require secrets in Base32 form. Encoding them here keeps the conversion local — nothing is sent over the network.

  • arrow_circle_right

    Building and testing encoding pipelines

    Developers verifying a Base32 implementation can paste a known string here, compare the output to a reference value, and quickly catch alphabet or padding bugs in their own code.

  • arrow_circle_right

    Creating compact identifiers from binary data

    Base32-encoded identifiers can be embedded in hostnames, subdomain labels, or file names where Base64 characters like + and / are forbidden and lowercase is unreliable.

quiz

Frequently Asked Questions

What is Base32 Encode? expand_more
Base32 Encode is a free online tool that converts plain text into Base32 format. Base32 uses a 32-character alphabet (A-Z and 2-7) to represent binary data, producing case-insensitive output that is safe for use in file names, DNS records, and authentication tokens.
What is the difference between Base32 and Base64? expand_more
Base32 uses 32 characters (A-Z, 2-7) while Base64 uses 64 characters (A-Z, a-z, 0-9, +, /). Base32 output is about 20% larger than Base64 but is entirely uppercase and symbol-free, making it the right choice for case-insensitive environments like DNS labels, authenticator secrets, and certain file systems. Choose Base64 when storage size matters more than case safety.
How is Base32 Encode different from URL Encode? expand_more
Base32 Encode converts arbitrary binary data into an alphanumeric string using a 32-character alphabet — the output is typically used for secrets, tokens, and identifiers, not web URLs. URL Encode (percent-encoding) escapes individual characters in a URL so browsers can parse the address correctly. They solve different problems: use Base32 when you need a case-insensitive binary-safe string; use URL Encode when you need to safely include special characters in a web address.
Why does the output end with equals signs? expand_more
Base32 works on groups of five bits. When the total number of input bits is not a multiple of five, the encoder pads the bit stream with zeros and adds equals signs (=) at the end of the output to signal how many bits of padding were added. This is defined by RFC 4648 and allows decoders to reconstruct the original data exactly.
Is my data secure? expand_more
Yes. All encoding happens entirely in your browser using JavaScript. No data is sent to any server, ensuring your text remains completely private and secure.
Does it support Unicode? expand_more
Yes. The tool uses the native TextEncoder API to convert your input to UTF-8 bytes first, so it correctly handles text in any language including accented letters, CJK characters, and emoji before encoding to Base32.
Is Base32 encryption? expand_more
No. Base32 is an encoding scheme, not encryption. It converts bytes into a printable string using a fixed alphabet. Anyone who has the encoded string can reverse it to the original input with a Base32 decoder. Do not use Base32 to protect confidential data — use proper encryption for that.
What alphabet does this tool use? expand_more
The tool uses the standard RFC 4648 Base32 alphabet: A through Z (26 letters) and the digits 2 through 7, giving 32 symbols total. This is the alphabet used by TOTP authenticators, many DNS libraries, and most Base32 implementations. It is different from Base32hex, which uses 0-9 and A-V.