T11 to BIN Converter

Transform CID Type 2 fonts into MacBinary format online for free

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

Legacy Compatibility

Convert your T11 CID Type 2 font into MacBinary format to ensure it works with classic Mac OS environments and older publishing software.

Browser-Based Tool

Run the entire T11 to BIN conversion from any web browser — no desktop applications or plugins to install on your machine.

Private and Secure

Your font files are handled confidentially — uploads are purged after processing and converted BIN outputs are deleted within 24 hours.

How to convert T11 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

T11 (Type 11) is a PostScript font type defined by Adobe Systems as part of the CID-keyed font architecture, combining CID glyph addressing with TrueType outline data wrapped in a Type 42 PostScript shell. In Adobe's font type numbering, Types 9, 10, and 11 are CID-keyed counterparts to Types 1, 3, and 42 respectively — so Type 11 is essentially a CID-keyed Type 42, designed for TrueType fonts that contain very large glyph sets, particularly CJK (Chinese, Japanese, Korean) character collections. The format allows PostScript interpreters with TrueType rasterizer support to render CJK TrueType fonts while using CID numeric indexing instead of glyph names, which is critical for character sets numbering in the tens of thousands. Glyph outlines remain in native TrueType quadratic spline format, preserving the original hinting instructions, while the CID layer provides efficient glyph access and subsetting through CMap resources. One advantage is direct TrueType rendering quality — unlike converting TrueType outlines to PostScript cubics, Type 11 passes the original outlines to the rasterizer intact, preserving hand-tuned grid-fitting instructions. The CID indexing provides another benefit by supporting multiple encoding schemes (Unicode, national standards) mapped to the same glyph collection without data duplication. Type 11 fonts appear primarily in professional CJK print production and PDF document workflows where large TrueType-based character sets must be embedded in PostScript-derived output.
Developer: Adobe Systems
Initial release: 1993
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 T11 to BIN?

MacBinary wraps font data with resource and data forks in a single file — required for transferring fonts to classic Mac OS systems or legacy publishing tools.

How do I open a BIN file?

On macOS, BIN files can be opened with StuffIt Expander or The Unarchiver. Classic Mac utilities and font managers also handle MacBinary natively.

Is the font data preserved during conversion?

Yes — MacBinary is a container format that encapsulates the original font data intact, preserving all glyphs, metrics, and CID mappings from your T11 file.

Who still needs MacBinary fonts?

Legacy publishing environments, classic Mac OS systems, and certain archival workflows still depend on MacBinary encoding for font distribution and storage.

Is T11 to BIN conversion free?

Yes, Convertio handles this conversion entirely for free in your browser — no software downloads or signups required.