Base32 Encoder & Decoder

Convert text, hex bytes, and binary strings to and from Base32 representations supporting RFC 4648, Base32hex, and Crockford alphabets.

At a glance

Base32 Encoder & Decoder is a free web tool that encodes text and hex to Base32 and decodes Base32 strings online. It easily switches between RFC 4648 Standard, Base32hex (RFC 4648 §7), Crockford Base32, and z-base-32 alphabets. Everything runs locally in your browser — nothing is uploaded and no sign-up is needed.

Universal Switcher:
From:
To:

100% Client-Side In-Browser Base32 Processing

Cryptographic seeds, 2FA authenticator secrets, Tor v3 keys, and hex strings are encoded and decoded strictly inside your browser memory. Zero data is sent to external servers.

Pure In-Browser
Ready 0 chars
UTF-8 and Hexadecimal byte-safe
Base32 0 chars
Real-time conversion
Base32 Conversion Telemetry
Input Data Size
0 B
0 characters
Output Data Size
0 B
0 bits
Expansion Ratio
1.60x
8 bits → 5 bits/char
Active Alphabet
RFC 4648
Padded (=)

4 Standard Alphabets

Supports RFC 4648 Standard, RFC 4648 §7 Extended Hex, Crockford Base32, and z-base-32 representations.

2FA & Tor Secret Keys

Decode Base32 seeds into hexadecimal bytes for Google Authenticator, Authy, hardware tokens, and onion v3 addresses.

Lenient Auto-Sanitize

Automatically ignores whitespace, linebreaks, and hyphens while normalizing Crockford ambiguous letters (I/L → 1, O → 0).

100% In-Browser Privacy

All bitwise calculations execute purely in client RAM. Your passwords, secrets, and private keys never touch any server.

How to Encode and Decode Base32

1

Select Conversion Mode & Alphabet

Choose Encode or Decode mode, then pick your target alphabet (RFC 4648 Standard, Base32hex, Crockford, or z-base-32).

2

Configure Padding & Format

Choose whether to include = padding bytes and select your input/output encoding format (UTF-8 Text or Hexadecimal).

3

Inspect, Copy, or Download

View your converted result instantly, check the live byte metrics, and copy the string or download it as a file with one click.

Frequently Asked Questions

What is Base32 encoding?

Base32 is a binary-to-text encoding scheme that represents arbitrary binary data using an alphabet of 32 ASCII characters (each character representing 5 bits). It is case-insensitive and designed to avoid ambiguous characters in human transcription.

Where is Base32 commonly used?

Base32 is the official encoding standard for two-factor authentication (TOTP/HOTP secret keys used by Google Authenticator), Tor v3 .onion hidden service addresses, DNSSEC signatures, and human-readable product registration codes.

What is the difference between RFC 4648 and Crockford's Base32?

RFC 4648 Base32 uses A-Z and digits 2-7. Crockford's Base32 uses digits 0-9 and letters A-Z, but excludes I, L, O, and U to prevent reading confusion with 1, 0, and vulgar words, and allows permissive decoding where I/L are treated as 1 and O as 0.

Is any data sent to external servers?

No. 100% of Base32 encoding and decoding executes locally in your browser memory via client-side JavaScript. Your sensitive tokens and keys are never transmitted over the internet.

Why Use This Base32 Encoder & Decoder?

Multi-Alphabet Radix-32 Support: Easily switch between RFC 4648 Standard, Base32hex (RFC 4648 §7), Crockford Base32, and z-base-32 alphabets.
Bidirectional Encoding & Decoding: Convert plain UTF-8 text and raw hexadecimal bytes to Base32, or decode Base32 back to readable text and hex.
Strict & Unpadded Formatting: Toggle standard RFC = padding bytes on and off for compact URL and token representations.
2FA & Secret Key Compatibility: Decode and inspect two-factor authentication secret keys (Google Authenticator, Authy) and Tor onion v3 addresses.
Lenient Input Sanitization: Automatically strips spaces, hyphens, and whitespace while mapping ambiguous Crockford letters (I/L to 1, O to 0).
100% Client-Side Privacy: All bitwise operations execute entirely inside your web browser. No private keys or strings are transmitted over the network.

How to Use Base32 Encoder & Decoder

1

Select Conversion Mode & Alphabet

Choose Encode or Decode mode, then pick your target alphabet (RFC 4648 Standard, Base32hex, Crockford, or z-base-32).

2

Configure Padding & Format

Choose whether to include = padding bytes and select your input/output encoding format (UTF-8 Text or Hexadecimal).

3

Inspect, Copy, or Download

View your converted result instantly, check the live byte metrics, and copy the string or download it as a file with one click.

Worked example: Base32 Encoder & Decoder

Executed entirely inside your local browser memory using modern Web APIs. The engine verifies input syntax, performs deterministic transformation, and exposes instant copy or download options.

Sample TEXT Data Source
sample_payload.text (Valid format conforming to TEXT specification)
Resulting BASE32 Output Processed
converted_result.base32 (100% client-side)

Technical Specifications & Engine Details

Technical specifications and engine details for Base32 Encoder & Decoder
Specification Details
Supported Formats TEXT, HEX, BASE32 → BASE32, TEXT, HEX
Execution Mode 100% Client-Side In-Browser (client)
Browser Requirements Requires modern web browser with Web Cryptography API (SubtleCrypto).
Performance Constraints Client browser memory limit (typically 1–2 GB RAM); processing speed depends on local device CPU.
Maintained by Pragyan Pahadi

100% Client-Side Privacy Guarantee

Your data remains strictly in your local browser memory. No text, hex bytes, or Base32 strings are ever sent over the internet.

Frequently Asked Questions

What is Base32 encoding?
Base32 is a binary-to-text encoding scheme that represents arbitrary binary data using an alphabet of 32 ASCII characters (each character representing 5 bits). It is case-insensitive and designed to avoid ambiguous characters in human transcription.
Where is Base32 commonly used?
Base32 is the official encoding standard for two-factor authentication (TOTP/HOTP secret keys used by Google Authenticator), Tor v3 .onion hidden service addresses, DNSSEC signatures, and human-readable product registration codes.
What is the difference between RFC 4648 and Crockford's Base32?
RFC 4648 Base32 uses A-Z and digits 2-7. Crockford's Base32 uses digits 0-9 and letters A-Z, but excludes I, L, O, and U to prevent reading confusion with 1, 0, and vulgar words, and allows permissive decoding where I/L are treated as 1 and O as 0.
Is any data sent to external servers?
No. 100% of Base32 encoding and decoding executes locally in your browser memory via client-side JavaScript. Your sensitive tokens and keys are never transmitted over the internet.

Methodology

Rankings and recommendations here are never paid for.

Last updated .