免费转换 BIN 文件
专业的 BIN 文件转换工具
将您的文件拖放到这里
或点击浏览文件
支持的格式
以高质量在所有主要文件格式之间转换
桌面字体
TrueType Font - universal desktop font format developed by Apple and Microsoft in the 1980s. Uses quadratic Bézier curves for glyph outlines. Excellent screen rendering with hinting technology. Works on all platforms (Windows, Mac, Linux). Supports Unicode with up to 65,536 glyphs. Standard desktop font format with maximum compatibility. Perfect for document embedding, desktop publishing, and cross-platform typography. Universal support in all operating systems and applications. Reliable choice for general-purpose font usage.
OpenType Font - modern font format jointly developed by Adobe and Microsoft (1996) extending TrueType. Uses cubic Bézier curves (PostScript outlines) allowing more complex glyph shapes. Supports advanced typography features (ligatures, alternate glyphs, contextual substitutions). Can contain up to 65,536 glyphs enabling comprehensive language support. Cross-platform compatibility (Windows, Mac, Linux). Industry standard for professional typography and multilingual documents. Perfect for print design, branding, and high-quality typography. Superior to TTF for complex scripts and advanced typographic features.
Mac Data Fork Font - legacy Macintosh font format storing TrueType/PostScript data in data fork. Used in Mac OS 9 and earlier. Phased out with Mac OS X transition to .ttf and .otf. Contains complete font data in single file (unlike resource fork fonts). Limited compatibility with modern systems. Convert to TTF or OTF for current macOS and cross-platform use. Historical format important for accessing old Mac fonts. Mainly encountered when migrating legacy Mac systems.
Compact Font Format - Adobe's space-efficient font outline format used within OpenType fonts. Stores glyph outlines using PostScript-based charstrings. More compact than TrueType outlines. Used in OTF fonts with PostScript outlines. Not standalone font file - embedded in OTF. Professional typography standard. Better compression than TTF outlines. Extract from OTF or work with complete OTF fonts.
CID-Keyed Font - Adobe font format for large character sets (Asian languages with thousands of characters). Character ID based system for efficient large font handling. Used in professional CJK (Chinese, Japanese, Korean) typography. Complex format requiring PostScript RIP support. Legacy format superseded by Unicode OpenType. Convert to modern OTF with Unicode mapping for compatibility. Important for accessing legacy Asian language fonts.
Spline Font Database - FontForge's native font format. Editable font source format storing complete font data including editing information. ASCII or binary format with full font metadata. Used in font design and development. Convert to TTF/OTF for deployable fonts. Perfect for font design workflow. Maintains complete font development history. FontForge is free open-source font editor.
Unified Font Object - open source font source format (XML-based directory structure). Developed by font tool creators for interoperability. Stores complete font design data in human-readable XML. Used by modern font editors (RoboFont, Glyphs, FontForge). Perfect for font development and version control. Industry standard for open font source files. Compile to TTF/OTF for distribution. Excellent for collaborative font design.
网页格式
Web Open Font Format - font format specifically designed for web use (2009). Compressed TrueType/OpenType fonts reducing file size by ~40%. Supported by 99% of browsers (Chrome, Firefox, Safari, Edge). Includes metadata for licensing and font information. Perfect for website typography ensuring consistent rendering across devices. Industry standard for web fonts. Faster page loads than raw TTF/OTF. Essential for modern web design and custom typography. Recommended for broad web compatibility.
WOFF 2.0 - improved web font format (2014) with better compression using Brotli algorithm. 30% smaller than WOFF with faster decompression. Supported by all modern browsers (96%+ global coverage). Maintains WOFF's metadata and licensing features. Superior performance for web typography. Recommended format for modern websites. Falls back to WOFF for older browsers. Essential for optimizing website performance and reducing bandwidth. Default choice for contemporary web development.
Embedded OpenType - proprietary web font format developed by Microsoft for Internet Explorer. Compressed and subset fonts with DRM protection. Only supported by Internet Explorer (legacy browser). Obsolete format replaced by WOFF/WOFF2. Historically important for web fonts (1997-2010s). Still encountered in legacy websites. Not recommended for new projects. Convert to WOFF2/WOFF for modern browsers. Maintained only for backward compatibility with old IE versions.
SVG Font - vector-based font format embedded in SVG files. Defines glyphs as SVG paths allowing colors, gradients, and effects. Deprecated for web use in favor of WOFF. Limited browser support (only Safari supports SVG fonts). Larger file sizes than outline fonts. Mainly historical format. Useful for special effects and colored fonts. Modern alternative: OpenType-SVG. Not recommended for general use. Better options: WOFF2 with icon fonts or OpenType color fonts.
专业格式
PostScript Font Binary - Adobe Type 1 binary format for professional printing (1984). Contains glyph outlines in PostScript language. Excellent print quality with precise curves. Requires corresponding PFM or AFM metrics file. Standard in professional publishing and printing industry. Limited to 256 glyphs (single-byte encoding). Being replaced by OpenType. Still used in legacy publishing workflows. Convert to OTF for modern compatibility while preserving PostScript quality.
PostScript Font ASCII - Adobe Type 1 ASCII variant of PFB format. Human-readable PostScript code defining font outlines. Used for font development and debugging. Less efficient than PFB binary format. Requires PFM or AFM metrics file. Same quality as PFB for printing. Legacy format for professional typography. Convert to OTF for modern systems. Primarily historical significance in desktop publishing evolution.
Printer Font Metrics - Windows metrics file for Type 1 PostScript fonts. Contains font measurements (character widths, kerning pairs, bounding boxes). Required companion to PFB/PFA for proper rendering on Windows. Text file format with font metrics data. Does not contain glyph outlines. Legacy format from Windows 3.1/95 era. Used with PFB for complete Type 1 font installation. Modern OpenType fonts include metrics internally. Convert Type 1 fonts to OTF to consolidate metrics and outlines.
Adobe Font Metrics - Adobe's metrics format for Type 1 PostScript fonts. Contains character widths, kerning pairs, ligatures, and bounding boxes. ASCII text format readable by humans and applications. Companion to PFB/PFA outline files. Used by font design tools and professional publishing software. Essential for proper font spacing and kerning. Legacy format with historical importance in digital typography. Modern fonts embed metrics in OTF format. Convert to OpenType for integrated metrics and outlines.
Binary Font File - generic binary font data format used by various font tools and editors. Contains raw font outline data without specific format wrapper. Used in font development and conversion pipelines. Requires specific tools to process. Not a standard end-user format. Intermediate format in font creation workflow. Convert to TTF or OTF for usable fonts. Primarily relevant in font design and development contexts.
Mac Suitcase Font - legacy Macintosh font container (Mac OS Classic) storing multiple fonts in one file. Contains TrueType or PostScript fonts in resource fork. Used with Font Suitcase format (.suit extension). Obsolete with Mac OS X migration. Poor compatibility with modern systems. Required Font/DA Mover for installation on old Macs. Extract individual fonts and convert to TTF/OTF for modern use. Important for recovering fonts from classic Mac archives and systems.
PostScript Font Program - Adobe PostScript Type 1 font in PostScript language format. Contains font outlines as PostScript code. Used for printer font downloads and font development. Human-readable but inefficient. Legacy format from desktop publishing era. Convert to OTF for modern usage. Historical importance in professional typography. Mainly encountered in old publishing workflows.
PageMaker 3 Font - legacy font format from Aldus PageMaker 3.0 (1980s desktop publishing). Proprietary format specific to early PageMaker versions. Obsolete format with no modern support. Important only for recovering old PageMaker documents. Convert to TTF/OTF if font data recoverable. Historical artifact from desktop publishing evolution. Better alternatives available for all uses.
Type 11 Font - variant of PostScript CID-Keyed font format. Used for complex fonts with large character sets. Legacy format for Asian language fonts. Limited modern support. Convert to Unicode OpenType for compatibility. Historical format in CJK font development. Modern alternatives handle large character sets better with Unicode.
Type 42 Font - PostScript font format wrapping TrueType outlines. Hybrid format combining PostScript wrapper with TrueType data. Used for downloading TrueType fonts to PostScript printers. Primarily printer-internal format. Limited end-user relevance. Convert underlying TrueType to TTF/OTF. Historical bridge between TrueType and PostScript worlds.
如何转换文件
上传您的文件,选择输出格式,立即下载转换后的文件。我们的转换器支持批量转换并保持高质量。
常见问题
什么是 BIN 字体文件,为什么它在经典的 Macintosh 系统上使用?
BIN 字体文件是一个 MacBinary 封装的档案,存储了一个 Macintosh Type 1 或基于资源分叉的字体,位于一个单一的可移植容器内。
Classic Mac OS separated file data into resource and data forks, making fonts difficult to transfer intact.
MacBinary 将两个分叉打包成一个 BIN 文件,以在网络和非 Mac 文件系统中保持字体的完整性。
为什么许多早期的 PostScript 字体在 Mac 上以 .BIN 文件而不是标准字体格式发布?
通过公告板、FTP 服务器和早期互联网协议的分发通常会剥离资源分叉。
MacBinary 保护了在传输过程中易受损坏的 Type 1 字体资源。
如果没有 BIN 打包,字体将无法完整到达并加载失败。
为什么在 macOS 上安装字体之前需要解码 BIN 文件?
现代系统不再原生支持 MacBinary,并且无法解释嵌入的资源分叉。
必须解码 BIN 封装以恢复原始的手提箱或 Type 1 组件。
只有在解码后,字体才会以其可用的 Mac 特定结构出现。
为什么一些 BIN 封装的字体内部包含多个组件?
经典的 Macintosh Type 1 字体需要一个手提箱文件用于屏幕度量,以及一个单独的轮廓文件用于打印。
MacBinary 将这些元素分组,以便它们可以作为一个单元一起移动。
这防止了在传输过程中字体部分的不匹配或孤立。
为什么在提取旧字体 CD 或档案时会出现 BIN 文件?
1990 年代的字体供应商将 Mac 字体打包为 MacBinary 格式,以确保与跨平台媒体的兼容性。
CD-ROM 文件系统如 ISO9660 无法直接存储资源分叉。
BIN 为 Macintosh 用户提供了一个保护性胶囊。
Why do BIN fonts fail when opened on Windows or Linux?
BIN 文件包含 Mac 特定的资源分叉,非 Mac 系统无法解释。
如果不解码,内部字体结构将显示为不透明的二进制块。
转换工具必须提取 Type 1 轮廓以便进一步使用。
为什么在某些字体分发中,BIN 文件比 StuffIt SIT 档案更受欢迎?
MacBinary 提供了严格的分叉元数据保护,同时避免了与压缩相关的兼容性问题。
一些系统阻止了 SIT 文件,但允许普通的 BIN 传输。
BIN 在不同网络中提供了最大的可靠性。
为什么将 BIN 字体转换为现代格式有时会破坏字距?
字距和屏幕度量存储在资源分叉中,而不是在轮廓文件中。
如果转换工具错误处理分叉数据,间距信息可能会丢失。
通常需要额外的步骤来准确重建度量。
为什么 MacBinary 在 BIN 文件内部使用严格的头部结构?
The header preserved file type, creator codes, and fork lengths crucial to Classic Mac OS.
这些属性控制操作系统在安装时如何解释字体。
如果没有头部,字体将无法在系统的字体管理器中注册。
为什么现代 macOS 不再生成或使用 BIN 字体文件?
macOS 放弃了资源分叉字体格式,转而使用 TrueType 和 OpenType。
The Apple File System no longer requires MacBinary for file preservation.
直接字体容器如 .ttf 和 .otf 替代了 BIN 打包的需求。
为什么档案字体集合通常包括 BIN 文件和 Type 1 数据?
保留原始 MacBinary 包确保历史字体发布的真实性。
许多早期许可证和元数据仅存在于资源分叉中。
BIN 文件为字体历史学家和博物馆保持了精确的保存。
为什么即使提取的文件似乎存在,解码 BIN 字体有时仍然是必要的?
一些文件浏览器显示数据分叉,但默默丢弃资源分叉。
可见的文件可能看起来完整,但缺少必要的字体信息。
解码可靠地重建两个分叉,确保正确安装。
为什么打印机和RIP系统依赖于BIN封装的Mac字体?
经典的PostScript工作流程要求严格保留字体套件元数据。
Transferring fonts over AppleTalk or FTP could easily break without MacBinary wrapping.
BIN确保了印刷店和出版公司的可预测输出。
Why can extracting BIN fonts on Windows create unusable files?
Windows does not understand fork-based metadata and interprets the BIN as arbitrary binary data.
没有专用的MacBinary解码器,嵌入的字体结构将丢失。
提取必须使用跨平台的MacBinary工具进行。
为什么BIN被认为是遗留格式,即使它仍然出现在旧档案中?
It solved a problem unique to Classic Mac OS that no longer exists in modern filesystems.
当前的字体标准如OpenType消除了对分叉保留的需求。
BIN仅在恢复历史Macintosh字体集合时仍然相关。