BinHex Encoder and Decoder

Encode files to BinHex format, commonly used on classic Macintosh systems, or decode BinHex files to extract the original data and resource forks. This tool supports legacy Mac file encoding.

BinHex Encoder/Decoder

Encode text to BinHex format or decode BinHex back to text

Mode

Text to Encode

BinHex Result

About BinHex

BinHex (Binary-to-Hexadecimal) is a file encoding format originally developed for the Macintosh. It converts binary data to ASCII text using hexadecimal representation, making it safe for email transmission and text-based storage.

BinHex 4.0 includes run-length encoding (RLE) for compression and a CRC checksum for error detection. While largely obsolete today, it was essential for Mac file transfers in the pre-Internet era.

How the BinHex Encoder/Decoder Works

Upload a file or paste binary data to encode to BinHex format, or input BinHex-encoded text to decode. The tool handles the complete conversion process.

BinHex converts binary data to ASCII text using a 64-character alphabet. It includes a CRC checksum for error detection. Originally designed for Mac file transfers.

The encoder adds Mac-specific metadata (resource fork, data fork). The decoder extracts the binary data and validates the CRC. Modern use is primarily for legacy file handling.

When You'd Actually Use This

Opening vintage Mac files

Old Mac archives use BinHex (.hqx). Decode to access the contents. Essential for Mac software preservation and retro computing.

Email attachment conversion

Legacy email systems used BinHex for attachments. Decode old email archives. Extract attachments from historical communications.

Software archaeology

Studying classic Mac software? BinHex was the distribution format. Decode to analyze vintage applications and games.

Data recovery from old media

Recovering data from old Mac disks? Files may be BinHex encoded. Decode to access the original data. Preserve digital history.

Understanding encoding history

BinHex shows early solutions to binary-in-text problem. Educational value for understanding encoding evolution. Compare with modern methods.

Processing Usenet archives

Old Usenet posts used BinHex for Mac files. Decode archived posts. Access historical file distributions.

What to Know Before Using

BinHex is largely obsolete.Modern systems use Base64 or direct binary. BinHex was for 1980s-1990s Mac transfers. Mainly needed for legacy file handling.

Includes CRC error checking.BinHex files contain a CRC-16 checksum. Decoder validates integrity. Detects transmission errors automatically.

Mac file structure is unique.Classic Mac files had two forks: data and resource. BinHex encoded both. Modern systems only have data forks.

File extension is .hqx.BinHex files typically end in .hqx. Sometimes .bin.hqx. The extension helps identify the encoding format.

Pro tip: When decoding vintage Mac files, you may need additional tools to handle the resource fork. Modern extractors often discard resource forks as they're not usable on non-Mac systems.

Common Questions

What is BinHex?

Binary-to-Hexadecimal encoding for Macintosh. Created in 1980s for file transfers. Converts binary to ASCII for safe transmission over text-only channels.

Why was BinHex created?

Early networks couldn't handle binary reliably. BinHex made files text-safe. Mac-specific solution before Base64 became standard.

Is BinHex still used?

Rarely. Replaced by Base64, ZIP, and direct binary transfer. Only needed for vintage Mac files and historical archives.

What's the file extension?

.hqx is standard for BinHex files. Sometimes seen as .bin.hqx. The extension indicates the file needs BinHex decoding.

How does CRC checking work?

CRC-16 checksum is calculated on the data. Stored in the BinHex file. Decoder recalculates and compares. Mismatch indicates corruption.

Can I decode on modern Mac?

Yes, but modern macOS doesn't include native BinHex support. Use third-party tools like The Unarchiver or online decoders.

What about resource forks?

BinHex encoded both data and resource forks. Modern systems ignore resource forks. Data fork contains the main file content.

Other Free Tools

Search tools