What is Base32 encoding and how does it work?

Base32 is a binary-to-text encoding scheme that uses 32 characters (A-Z and 2-7) to represent binary data. It converts 5 bytes of input into 8 characters of output. Base32 is case-insensitive and avoids visually similar characters like 0/O and 1/I/L, making it ideal for manual entry.

How do I encode text to Base32 online?

Paste your text into the input field, select "Encode" mode, and the Base32 encoded result appears instantly. You can copy the output for use in TOTP authenticator apps, file systems, or any application requiring case-insensitive encoding.

How do I decode Base32 to text?

Paste your Base32 encoded string into the input field, select "Decode" mode, and view the original text instantly. The decoder handles both standard Base32 and Base32 Hex variants, with or without padding characters.

When should I use Base32 instead of Base64?

Use Base32 when you need: case-insensitive encoding (file systems, URLs), human-readable output that's easy to type manually, TOTP/HOTP authentication secrets, or when avoiding confusing characters matters. Base64 is more compact but case-sensitive.

Why does Base32 use letters A-Z and numbers 2-7?

The Base32 alphabet (A-Z, 2-7) deliberately excludes visually similar characters: 0 looks like O, 1 looks like I and L, 8 looks like B. This reduces transcription errors when users manually type Base32 strings, which is common with TOTP codes.

What is the size overhead of Base32 encoding?

Base32 increases data size by approximately 60% (8 output characters for every 5 input bytes), compared to 33% for Base64. This larger overhead is the trade-off for case-insensitivity and human-readability. A 10-byte input becomes 16 Base32 characters.

Is Base32 case-sensitive?

No, Base32 is case-insensitive by design. Both "JBSWY3DPEHPK3PXP" and "jbswy3dpehpk3pxp" decode to the same value. This makes Base32 ideal for systems where case might be changed (email, file systems) or for manual entry.

What is Base32 Hex and when should I use it?

Base32 Hex (Extended Hex) uses 0-9 and A-V instead of A-Z and 2-7. Its key advantage is preserving the lexicographic sort order of the original data. Use Base32 Hex when you need encoded strings to sort in the same order as the original binary data.

Why are there equal signs (=) at the end of Base32?

The = characters are padding to make the output length a multiple of 8 characters. Padding ensures consistent decoding but can often be omitted in practice. Many systems accept Base32 without padding, especially for TOTP secrets.

Is Base32 encryption or secure?

No! Base32 is encoding, NOT encryption. Anyone can decode Base32 data without any key. Never use Base32 to protect sensitive information. It's designed for data representation, not security. Use proper encryption like AES for sensitive data.

Where is Base32 commonly used?

Base32 is used in: TOTP/HOTP authenticator apps (Google Authenticator, Authy), file systems requiring case-insensitive names, Onion addresses in Tor network, DNSSEC, Geohash encoding, and anywhere human-readable, typeable encoding is needed.

How do I use Base32 for two-factor authentication (2FA)?

TOTP authenticator apps use Base32-encoded secrets. When setting up 2FA, the service provides a Base32 secret (or QR code containing it). The authenticator app decodes this secret and uses it with the current time to generate 6-digit codes every 30 seconds.

Can Base32 encode binary files and images?

Yes, Base32 can encode any binary data including files and images. However, due to the 60% size overhead, Base64 is usually preferred for binary data. Base32 is better suited for short strings that need to be typed or displayed.

How do I convert between Base32 and Base64?

First decode the source encoding to get the original binary data, then encode it in the target format. For example: decode Base64 → get bytes → encode as Base32. This tool handles the conversion automatically when you switch modes.

Is my data secure when using this Base32 encoder?

Yes! All encoding and decoding happens 100% in your browser using JavaScript. Your data never leaves your device or gets sent to any server. This makes it safe for encoding TOTP secrets and other sensitive configuration data.

What is Base32 encoding and how does it work?

Base32 is a binary-to-text encoding scheme that uses 32 characters (A-Z and 2-7) to represent binary data. It converts 5 bytes of input into 8 characters of output. Base32 is case-insensitive and avoids visually similar characters like 0/O and 1/I/L, making it ideal for manual entry.

How do I encode text to Base32 online?

Paste your text into the input field, select "Encode" mode, and the Base32 encoded result appears instantly. You can copy the output for use in TOTP authenticator apps, file systems, or any application requiring case-insensitive encoding.

How do I decode Base32 to text?

Paste your Base32 encoded string into the input field, select "Decode" mode, and view the original text instantly. The decoder handles both standard Base32 and Base32 Hex variants, with or without padding characters.

When should I use Base32 instead of Base64?

Use Base32 when you need: case-insensitive encoding (file systems, URLs), human-readable output that's easy to type manually, TOTP/HOTP authentication secrets, or when avoiding confusing characters matters. Base64 is more compact but case-sensitive.

Why does Base32 use letters A-Z and numbers 2-7?

The Base32 alphabet (A-Z, 2-7) deliberately excludes visually similar characters: 0 looks like O, 1 looks like I and L, 8 looks like B. This reduces transcription errors when users manually type Base32 strings, which is common with TOTP codes.

What is the size overhead of Base32 encoding?

Base32 increases data size by approximately 60% (8 output characters for every 5 input bytes), compared to 33% for Base64. This larger overhead is the trade-off for case-insensitivity and human-readability. A 10-byte input becomes 16 Base32 characters.

Is Base32 case-sensitive?

No, Base32 is case-insensitive by design. Both "JBSWY3DPEHPK3PXP" and "jbswy3dpehpk3pxp" decode to the same value. This makes Base32 ideal for systems where case might be changed (email, file systems) or for manual entry.

What is Base32 Hex and when should I use it?

Base32 Hex (Extended Hex) uses 0-9 and A-V instead of A-Z and 2-7. Its key advantage is preserving the lexicographic sort order of the original data. Use Base32 Hex when you need encoded strings to sort in the same order as the original binary data.

Why are there equal signs (=) at the end of Base32?

The = characters are padding to make the output length a multiple of 8 characters. Padding ensures consistent decoding but can often be omitted in practice. Many systems accept Base32 without padding, especially for TOTP secrets.

Is Base32 encryption or secure?

No! Base32 is encoding, NOT encryption. Anyone can decode Base32 data without any key. Never use Base32 to protect sensitive information. It's designed for data representation, not security. Use proper encryption like AES for sensitive data.

Where is Base32 commonly used?

Base32 is used in: TOTP/HOTP authenticator apps (Google Authenticator, Authy), file systems requiring case-insensitive names, Onion addresses in Tor network, DNSSEC, Geohash encoding, and anywhere human-readable, typeable encoding is needed.

How do I use Base32 for two-factor authentication (2FA)?

TOTP authenticator apps use Base32-encoded secrets. When setting up 2FA, the service provides a Base32 secret (or QR code containing it). The authenticator app decodes this secret and uses it with the current time to generate 6-digit codes every 30 seconds.

Can Base32 encode binary files and images?

Yes, Base32 can encode any binary data including files and images. However, due to the 60% size overhead, Base64 is usually preferred for binary data. Base32 is better suited for short strings that need to be typed or displayed.

How do I convert between Base32 and Base64?

First decode the source encoding to get the original binary data, then encode it in the target format. For example: decode Base64 → get bytes → encode as Base32. This tool handles the conversion automatically when you switch modes.

Is my data secure when using this Base32 encoder?

Yes! All encoding and decoding happens 100% in your browser using JavaScript. Your data never leaves your device or gets sent to any server. This makes it safe for encoding TOTP secrets and other sensitive configuration data.

Base32 Encoder/Decoder

simple

Encode and decode Base32 data for TOTP authenticator apps, case-insensitive systems, and human-readable encoding. Supports standard Base32 and Base32 Hex variants.

Encoders & Decodersbase32encoderdecodertotp

100% Private - Runs Locally

How to Use

1Enter text or Base32 string
2Select encode or decode
3View result instantly
4Copy the output

Examples

Encode Simple Text

Input

Hello, World!

Output

JBSWY3DPEBLW64TMMQQQ====

Encode Short Text

Input

test

Output

ORSXG5A=

Decode Base32

Input

JBSWY3DPEHPK3PXP

Output

Hello!

Frequently Asked Questions

Related Tools

View all

Base64 Encoder/Decoder

Encode and decode Base64 data instantly. Convert text, files, and images to Base64 format for embedding in HTML, CSS, JSON, and APIs. Supports URL-safe Base64 and handles Unicode characters.

Hex to Text Converter

Convert between hexadecimal and text bidirectionally. Decode hex strings to readable text or encode text to hex format. Supports multiple separators, 0x prefix, and UTF-8 Unicode characters.