Is my secret key sent to your servers?

No. All encoding and decoding operates 100% inside your local browser's memory using JavaScript bitwise operations. No data is transmitted.

Updated: August 2026 • Verified v1.2

Base32 Encoder & Decoder (RFC 4648)

Developer ToolsHigh Usage

Local Browser Execution: Your input is processed locally in your browser and is not sent to UTL servers.

RFC 4648 5-bit Quantization: 8-bit octet stream ➔ 5-bit chunks mapped to [A-Z2-7]

Was this calculation helpful?

Understanding Your Results

Converts binary byte streams and UTF-8 strings into 5-bit RFC 4648 Base32 characters (`A-Z`, `2-7`) and vice-versa with optional trailing padding (`=`).

Practical Guidance & Next Steps

Base32 is chosen over Base64 for 2FA authenticator secret keys because it is case-insensitive and omits visually confusing characters like 0, 1, 8, and 9.

What is this?

A cryptographic data formatting utility that encodes and decodes standard RFC 4648 Base32 strings.

How does it work?

1. Select 'Encode Text to Base32' or 'Decode Base32 to Text'. 2. Enter or paste string. 3. View instant converted output and copy in 1 click.

Why use it?

Safely inspects and generates 2FA authentication secret keys without sending sensitive keys over the network.

Technical Scope & Calculation Limitations

Implements standard RFC 4648 Base32 encoding specifications.

Frequently Asked Questions

Base32 uses only uppercase letters A-Z and digits 2-7. It excludes digits 0 and 1 and 8 and 9 to avoid visual confusion with letters O, I, B, and g, making it easy for humans to type manually.

Windows Desktop & Widget Options