PFB to BIN Converter

Wrap PFB fonts in MacBinary containers online — free

Drop files here. 1 GB maximum file size or Sign Up
to
Facebook Amazon Microsoft Tesla Nestle Walmart L'Oreal

Container Wrapping

Repackage your PFB font inside a MacBinary container without altering glyph data — the font itself stays identical inside the BIN wrapper.

Legacy Mac Support

BIN format preserves the resource-fork structure that classic Macintosh publishing systems expect for PostScript font installation.

Fast Processing

Container wrapping is lightweight — your PFB to BIN conversion completes in seconds, even for complex font files.

How to convert PFB to BIN

1

Select files from Computer, Google Drive, Dropbox, URL or by dragging it on the page.

2

Choose bin or any other format you need as a result (more than 200 formats supported)

3

Let the file convert and you can download your bin file right afterwards

About formats

PFB (Printer Font Binary) is the compact binary representation of Adobe's PostScript Type 1 font format, introduced alongside PFA in 1984. Where PFA stores the entire font program as hex-encoded ASCII text, PFB wraps the same data in a lightweight binary container that uses segment headers to mark regions as ASCII or binary. The encrypted glyph outline section (eexec) is stored as raw bytes rather than hex characters, cutting the file size roughly in half compared to PFA. Each segment begins with a marker byte and a 32-bit length field, making the format simple to parse while still significantly more compact. PFB became the dominant Type 1 distribution format on Windows and DOS platforms, used in combination with PFM (Printer Font Metrics) or AFM files that supply the character width and kerning data needed for text layout. One advantage is storage and transfer efficiency — the binary encoding means a typical text font occupies 30-50 KB rather than the 60-100 KB its PFA equivalent would require. The segmented structure also allows PostScript interpreters to stream font data efficiently, processing ASCII and binary portions with their respective handlers. Adobe Type Manager (ATM) on Windows relied on PFB files to render smooth Type 1 text on screen, a capability that transformed desktop publishing on the PC platform. While OpenType fonts have largely replaced Type 1 for new work, PFB files persist in established print workflows, archival font libraries, and systems that depend on PostScript output.
Developer: Adobe Systems
Initial release: 1984
BIN refers to MacBinary-encoded font files, a transfer format that preserves classic Macintosh file system features when moving data across platforms. Classic Mac OS stored fonts using the resource fork — a secondary data stream invisible to non-Mac systems — which meant that simply copying a Mac font to a Windows PC or Unix server would strip the actual font data entirely. MacBinary solves this by combining both the data fork and resource fork into a single flat file with a 128-byte header containing the original HFS metadata. In the font context, BIN files typically wrap TrueType suitcase fonts, PostScript Type 1 LWFN outline files, or bitmap NFNT font resources. The format was first specified in 1985 by Dennis Brothers and collaborators from the early Mac community, with MacBinary II following around 1987 and MacBinary III arriving in 1996 to support longer filenames. A key advantage is lossless preservation: every byte of the original Mac font file survives intact through email, FTP, or cross-platform file sharing, including creator and type codes that identify the font format. The single-file packaging is another practical strength — rather than dealing with separate data and resource streams, users and automated systems handle one portable container. Although modern macOS has moved away from resource forks and Mac fonts now typically ship as OTF, TTF, or DFONT files, BIN remains important for accessing archived font collections from the classic Mac era.
Developer: Dennis Brothers
Initial release: 1985

Frequently Asked Questions

Why convert PFB to BIN?

BIN (MacBinary) packages PFB font data with the resource fork structure that classic Mac systems require — essential for legacy publishing workflows.

How to open BIN?

BIN files are recognized by classic Mac OS, Stuffit Expander, The Unarchiver on macOS, and font management tools that handle resource-fork data.

Is MacBinary still used today?

MacBinary is mainly needed for archival and legacy system support. Modern macOS moved away from resource forks, but older workflows still depend on BIN.

Does conversion change the font data?

No — BIN is a container format. Your PFB glyph outlines and metrics are preserved exactly; only the file wrapper changes.

Can I do this conversion in bulk?

Yes, Convertio supports batch uploads. Package multiple PFB fonts into BIN format in a single conversion session.