handyman
Hazuu Tools

Base32 Encode File

Convert any file to Base32 format — upload, encode, and copy instantly.

Upload File
upload_file

Drop a file here or click to browse

Output Base32
Encoded data will appear here...
info

About Base32 Encode File

Base32 Encode File converts any file — image, PDF, binary, config, or certificate — into a Base32-encoded string using the RFC 4648 alphabet (A–Z and 2–7). Unlike text-oriented Base32 encoders, this tool reads the raw binary bytes of the file directly, so it handles every file type accurately, including those with null bytes and non-printable characters that would corrupt a plain text pass-through.

The most common reason to choose Base32 over Base64 for file encoding is case insensitivity. Base32 output uses only letters and the digits 2–7, which means it survives round-trips through case-folding systems such as DNS zone files, legacy file systems, and OTP authenticators. If you are embedding a small file into a DNS TXT record, a TOTP seed, or a case-insensitive configuration field, Base32 is the encoding you need — not Base64.

Every byte of your file is processed locally in your browser using the native FileReader API and a pure-JavaScript Base32 encoder. Nothing is transmitted to a server, stored in any database, or logged. There are no file size caps beyond your device's available memory, no account required, and no charge. You can encode private keys, personal documents, and internal assets without any data leaving your machine.

star

Key Features

check_circle

True binary file support

Reads raw bytes via FileReader readAsArrayBuffer, so any file type — PNG, PDF, ZIP, certificate — encodes correctly without text-encoding corruption.

check_circle

RFC 4648-compliant output

Produces standard Base32 with the A–Z / 2–7 alphabet and correct = padding to the nearest 8-character boundary, compatible with all RFC 4648-compliant decoders.

check_circle

Case-insensitive encoding

Base32 output contains no lowercase letters or symbols beyond digits 2–7, making it safe for DNS records, OTP seeds, case-folding file systems, and QR code payloads.

check_circle

Drag-and-drop upload

Drop a file directly onto the upload zone or click to browse. File name and size are shown before encoding so you can confirm you selected the right file.

check_circle

Fully client-side and private

No server upload, no logging, no account. Your files stay on your machine throughout the entire encoding process.

check_circle

One-click copy

Copy the entire Base32 output string to the clipboard with a single button — ready to paste into a config file, DNS record, or script.

help

How to Use

01

Upload File

Drag and drop a file onto the upload zone or click to browse and select one.

02

Encode

Click "Encode" to convert the file contents to Base32 format.

03

Copy Result

Use the copy button to grab your Base32-encoded output.

code_blocks

Example

A plain text file containing "Hello" (5 bytes) encodes to its RFC 4648 Base32 representation with padding to the nearest 8-character boundary.

File contents (hello.txt)
Hello
Base32 output
JBSWY3DP
lightbulb

Common Use Cases

  • arrow_circle_right

    Embedding files in DNS TXT records

    DNS is case-insensitive and many resolvers normalise labels to lowercase. Base32's all-uppercase alphabet survives this round-trip intact, making it the standard choice for DKIM keys, DNSSEC records, and custom TXT payloads that carry binary data.

  • arrow_circle_right

    Generating TOTP / HOTP seeds from key files

    Time-based one-time password libraries (Google Authenticator, Authy) expect secrets as Base32 strings. Encode a raw key file here to get the seed string you need to configure an OTP authenticator.

  • arrow_circle_right

    Encoding binary assets for case-insensitive config fields

    Some legacy configuration systems and environment-variable loaders fold keys to lowercase. Base32-encoding a certificate, private key, or binary blob before inserting it prevents case-mangling that would corrupt a Base64 value.

  • arrow_circle_right

    Embedding small files in QR codes

    QR code scanners decode alphanumeric mode more compactly than byte mode. Because Base32 uses only uppercase letters and a subset of digits, it triggers the more space-efficient alphanumeric encoding, fitting more data into the same QR symbol size.

  • arrow_circle_right

    Cross-platform file identity and checksums

    Some content-addressable storage systems (e.g., IPFS CIDv1 in Base32) encode file hashes in Base32 to produce identifiers that work safely in URLs, file names, and directory paths across Windows, macOS, and Linux.

quiz

Frequently Asked Questions

What is Base32 Encode File? expand_more
Base32 Encode File is a free online tool that converts any file into a Base32-encoded string. Unlike Base64, Base32 output uses only uppercase letters and digits 2-7, making it case-insensitive and safe for use in file systems, DNS records, and OTP authenticators.
What file types are supported? expand_more
All file types are supported including images, documents, text files, audio, video, certificates, and any binary format. The tool reads the raw bytes of the file via the FileReader API and encodes them directly without any text-encoding conversion step.
Is my file secure? expand_more
Yes. All file processing happens entirely in your browser. Your files are never uploaded to any server, sent over the network, or logged in any way, so sensitive files such as private keys and personal documents remain on your machine.
How does this differ from the Base32 Encode (text) tool? expand_more
The Base32 Encode text tool accepts a typed or pasted string and encodes it as UTF-8 text. This tool accepts an uploaded file and reads its raw binary bytes, which is the correct approach for images, PDFs, certificates, and any non-text file. Using a text encoder on a binary file would corrupt the output because text encoding cannot faithfully represent arbitrary byte sequences.
How does Base32 file encoding differ from Base64 file encoding? expand_more
Base32 produces output about 60% larger than the original file (versus about 33% for Base64) but uses only 32 characters — uppercase A–Z and digits 2–7 — instead of 64. This makes Base32 case-insensitive, which is important for DNS records, OTP seeds, and case-folding file systems. Choose Base64 when storage efficiency matters; choose Base32 when case safety or OTP compatibility matters.
Why does the output end with equals signs? expand_more
Base32 encodes 5 bits per character and groups output into 8-character blocks (40 bits). When the file size is not a multiple of 5 bytes, the output is padded with = characters to reach the next 8-character boundary. This RFC 4648-compliant padding tells a decoder exactly how many padding bits to discard when reversing the encoding.
Is there a file size limit? expand_more
There is no hard limit imposed by the tool. Because encoding runs locally in your browser, the practical limit is your device's available memory. Very large files (hundreds of megabytes) may cause your browser to slow down during encoding.
Can I decode the Base32 output back to the original file? expand_more
Yes. Use the companion Base32 Decode tool on this site. Paste the Base32 string, decode it, and save the resulting bytes as a file to recover the original binary content.