logo
GeekFormat

Base32 Encoder/Decoder

Input 0 characters · Output 0 characters

Uses RFC 4648 Base32 alphabet(A-Z、2-7), when decodingignores whitespaceandhandles case automatically.

Plain text, encoded in UTF-8 and converted to Base32

0 chars

Free online Base32 encoder and decoder compliant with RFC 4648. Perfect for handling TOTP/2FA secrets, case-insensitive data, and DNS labels.

Related

Hex Converter

Secure String Comparison

SHA-512 Hash

SHA-256 Hash

URL Parser

HTTP Headers Checker

Use Cases

  • Generate or decode Base32 secret keys for setting up TOTP-based Two-Factor Authentication (2FA).
  • Convert binary data into case-insensitive text strings for systems that don't support mixed case.
  • Encode data for use in DNS labels or file systems where special characters and case sensitivity are restricted.
  • Debug and verify Base32 encoded strings in legacy systems or specific network protocols.

Features

  • RFC 4648 Compliant: Strictly follows the standard Base32 alphabet (A-Z, 2-7), ensuring compatibility with all major systems.
  • TOTP & 2FA Ready: The ideal tool for encoding and decoding secret keys for Google Authenticator, Authy, and other 2FA apps.
  • Case-Insensitive & Safe: Uses a character set that avoids visual confusion (no 0, O, I, l), perfect for manual transcription and DNS labels.
  • Instant Local Conversion: Encode or decode Base32 strings instantly in your browser. No data is ever uploaded to our servers.

How to Use

  1. 1.Select Encode (Text to Base32) or Decode (Base32 to Text) mode.
  2. 2.Enter your plain text or Base32 string into the input box.
  3. 3.The tool instantly converts the data following RFC 4648 standards.
  4. 4.One-click copy the result for your authenticator app, config file, or code.

FAQ

What's the difference between Base32 and Base64?

Base32 uses a limited character set (A-Z and 2-7) making it case-insensitive and safe for filenames, URLs, and human transcription. Base64 is more compact but includes lowercase letters, numbers, and symbols (+, /) that can cause issues in case-sensitive or restricted environments.

Why is Base32 used for TOTP and 2FA secrets?

Base32 is the standard (RFC 4648) for Time-based One-Time Password (TOTP) secrets because it is case-insensitive and avoids visually similar characters (like 0 and O, or 1 and l). This makes it much easier for users to manually enter secret keys into authenticator apps without errors.

Does this tool support Base32 Hex?

This tool focuses on the standard RFC 4648 Base32 alphabet. If you need Base32 Hex (which uses 0-9 and A-V), please check our other encoding tools or let us know in the feedback!

Is it safe to decode my private 2FA secrets here?

Yes. GeekFormat's Base32 tool operates entirely on the client-side (in your browser). Your secret keys and data are processed locally and are never transmitted to or stored on any external server.