#1 India's Top IT Training Institute

×

About Uncodemy

Know more about who we are and what we stand for.

About Us

About Us

Discover our mission to equip individuals with essential IT skills and industry expertise.

Read More →
UnCodeMy Gallery

UnCodeMy Gallery

Explore highlights from our IT training sessions and success stories.

Read More →
×

Free Resources

Learn, practice and plan your career — bilkul free.

Tutorials

Tutorials

Step-by-step written tutorials to learn any technology at your own pace.

Read More →
Free Counselling

Free Counselling

Book a free video counselling session and pick the right course for you.

Read More →
Online Compiler

Online Compiler

Write, run and test your code online — no setup required.

Read More →
🔤 FREE · RFC 4648

Base32 Encoder & Decoder: Convert Text and Base32 Both Ways

Encode or decode Base32 with the standard or hex alphabet, padded or not.

  • 🔁 Encode and decode
  • 🔠 Standard or Base32hex
  • ⏱️ TOTP-friendly

How to use the Base32 Encoder Decoder

  1. 1. Enter the inputType text to encode, or paste Base32 to decode.
  2. 2. Pick the optionsChoose the alphabet and whether to add = padding.
  3. 3. Copy the resultUse the output in your app, config or authenticator.

How Base32 works

Base32 splits data into 5-bit groups and maps each group to one of 32 characters. The standard alphabet (RFC 4648) is A–Z and 2–7; it leaves out 0, 1 and 8 because they are easily confused with O, I and B. Every 5 bytes become exactly 8 characters, and = padding fills the last block.

Worked example: "hello" is 5 bytes (68 65 6c 6c 6f in hex). Those 40 bits split into eight 5-bit groups, giving NBSWY3DP, with no padding needed because 5 bytes fill one block exactly. Decoding NBSWY3DP returns hello.

Where you meet Base32

  • Two-factor authentication: TOTP secret keys shown under QR codes are Base32, usually without padding.
  • Case-insensitive systems: file names, DNS labels and URLs where Base64's mix of upper, lower and symbols causes trouble.
  • Base32hex (0–9, A–V) keeps sort order, which some databases and DNSSEC records use.

Base32 is about 60% longer than the original data, while Base64 is about 33% longer, so use Base32 only when its limited character set is needed. It is an encoding, not encryption: anyone can decode it. When decoded bytes are not readable text, such as a TOTP secret, the tool shows them as hex. Decoding ignores spaces, dashes and padding, and is case-insensitive. For the more common encoding, see the Base64 encoder; to inspect bytes, use the hex dump viewer.

Frequently asked questions

Why did my TOTP secret decode to strange characters?

TOTP secrets are random bytes, not text. The tool shows them in hex, which is the correct result.

Do I need padding?

Standards include it, but many apps, including authenticator apps, omit it. Both forms decode here.

Is the Base32 Encoder Decoder free?

Yes, the Base32 Encoder Decoder is free. The first time you see your first result, you are asked for your name and WhatsApp number once. After that, this and every other Uncodemy tool opens straight away without the form.

More free tools

See all free tools