What characters are valid in a Base32 string?

RFC 4648 Base32 uses the 32 characters A–Z (uppercase) and 2–7. The string may also include = padding characters at the end. Lowercase letters are accepted and automatically normalized to uppercase.

How is the octal output formatted?

Each decoded byte is represented as a 3-digit octal number (e.g., byte value 65 becomes 101). The tool shows both space-separated (101 154 165) and continuous (101154165) formats.

What does Base32 actually encode?

Base32 encodes arbitrary binary data using only 32 printable ASCII characters. It is commonly used for TOTP secrets, DNS labels, IPFS content addresses, and other systems that need case-insensitive, human-readable binary encoding.

Why might my conversion produce no output?

If the input contains characters outside A–Z and 2–7 (excluding padding =), or if the string length is not a valid Base32 multiple, the tool will show an error. Remove any spaces or invalid characters and try again.

Is the conversion done locally in my browser?

Yes. All decoding and conversion happens entirely in your browser using JavaScript. Nothing is sent to any server.

Base32 to Octal Converter

Name: Base32 to Octal Converter
Availability: InStock
Author: Nham Vu

Paste a Base32 string and instantly convert it to its octal (base-8) representation.

Base32 Input

Characters A–Z and 2–7 (RFC 4648). Spaces and lowercase are normalized automatically.

Octal Output

Spaced (per byte)

Result appears here…

Continuous string

Result appears here…

Copied!

Summary

Paste a Base32 string and instantly convert it to its octal (base-8) representation.

How it works

Accepts any valid RFC 4648 Base32 string (characters A–Z and 2–7, with optional padding).
Decodes the Base32 input to its underlying raw byte sequence.
Converts each byte value (0–255) to a zero-padded 3-digit octal number (000–377).
Displays both spaced and continuous formats for maximum compatibility.

Use cases

Inspect the raw bytes of a Base32 encoded secret or token.
Debug TOTP secret keys and verify their byte-level content.
Explore number base conversions for educational purposes.
Verify Base32 encoding in protocols like DNS and IPFS.
Convert encoded data for use in octal-based file permissions or scripts.
Cross-check Base32 payloads in security audits.

Frequently Asked Questions

Last updated: 2026-07-01 · Reviewed by Nham Vu