File ↔ Base32

Encode file bytes or decode text to a downloadable file.



FAQ

Where is data processed?

In your browser. Inputs are not uploaded.

What is supported?

Only the listed modes and finite examples are covered; this is not an all-input proof.

Other Languages

References

How we make sure

We check this tool with the automated test suites linked below. Example checks are shown in their original language.

Verification method
Check the RFC4648 foo vector, binary-byte round trips and invalid alphabet rejection. Decoder regressions cover retained Hex/Base64 source selectors and uploaded encoded text.
Comparison reference
RFC 4648 section 10 fixed foo → MZXW6=== vector; same @scure/base 2.0.0 inverse for binary cases.
Verification scope
Only the listed modes and finite examples are covered; this is not an all-input proof.
Test source and cases (select a file to read it)
  • completion-tools.test.js
    • file-base32: RFC4648 vectors and binary file bytes
    • File decoders treat input as encoded text regardless of the source byte selector

These checks cover the listed examples and boundaries, not every possible input. Round trips and checks using the same library are not independent verification.