免费转换 UFO 文件
专业的 UFO 文件转换工具
将您的文件拖放到这里
或点击浏览文件
支持的格式
以高质量在所有主要文件格式之间转换
桌面字体
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.
如何转换文件
上传您的文件,选择输出格式,立即下载转换后的文件。我们的转换器支持批量转换并保持高质量。
常见问题
什么是 UFO 字体文件,为什么它在现代字体设计中被广泛使用?
UFO 文件是一个基于文件夹的人类可读源格式,存储字形、元数据、字距调整、组件和设计层。
它充当可编辑的主文件,从中生成最终字体,如 OTF 或 TTF。
其开放性和清晰性使其成为协作和脚本工作流程中的标准。
为什么 UFO 结构是目录而不是单文件格式?
将字形、元数据和库数据分开,避免了单一、模糊的容器。
这种结构使版本控制、差异比较和合并变得更加精确。
它还简化了设计师和开发人员的自动化工具。
为什么 UFO 将字形存储为单独的 XML 文件而不是二进制数据?
XML 既可被人类读取,也可被软件读取,便于调试和检查。
二进制格式隐藏结构,复杂化跨平台工具。
XML 模型支持字体开发每个阶段的透明度。
为什么 RoboFont、Glyphs(通过转换器)和 FontLab 等主要工具支持 UFO?
UFO 提供了一种中立的开放标准,避免了供应商锁定。
设计师可以在不丢失数据或重新格式化项目的情况下切换工具。
它的兼容性促进了编辑器和脚本的强大生态系统。
为什么新兴的字体构建系统依赖于UFO作为起点?
像fontmake、ufo2ft和AFDKO这样的工具可以以编程方式使用UFO数据。
轮廓和元数据的清晰分离使得自动生成变得可靠。
这支持CI管道、批量构建和可重现的字体。
为什么UFO将字距调整、组、特征和字形数据分开?
复杂的排版规则需要模块化存储以确保清晰性和可维护性。
特征代码必须独立于轮廓几何。
这种模块化设计增强了编辑和协作的效果。
为什么UFO保持严格的版本规范,如UFO2和UFO3?
每个版本定义了轮廓、组件和元数据的结构方式。
清晰的规范确保工具一致地解释数据。
这种稳定性对于长期、大规模的字体项目至关重要。
为什么UFO非常适合在基于Python的工作流程中进行脚本和自动化?
UFO数据通过defcon和fontParts等库可以干净地映射到Python结构。
设计师可以自动化重复性任务,如间距、插值和清理。
这减少了人工劳动,加快了复杂项目的进度。
为什么一些设计师更喜欢UFO而不是二进制的.glyphs源文件?
UFO是完全开放的,不依赖于任何专有编辑器。
它为长期归档和互操作性提供了更强的保障。
它的结构使得团队导向的工作流程更具韧性。
为什么UFO存储组件和引用而不是扁平化轮廓?
基于组件的设计确保了重复形状(如重音符或衬线)之间的一致性。
它使得更新能够自动传播到字形集。
扁平化轮廓仅保留用于最终构建,而不是源文件。
为什么可变字体项目在开发过程中经常使用UFO主文件?
每个UFO文件代表一个独特的主文件,用于插值轴。
UFO保持主文件之间的轮廓和点结构同步。
这种对齐对于生成高质量的可变字体至关重要。
为什么UFO非常适合排版教学和学术研究?
它的透明性帮助学生理解字体构建的内部逻辑。
研究人员可以直接分析字形几何、特征代码和字距调整算法。
该格式鼓励对代码驱动的字体设计进行实验。
为什么高级工具将元数据和设计笔记嵌入UFO库中?
该库允许自定义数据,如风格决策、构建参数或编辑器设置。
这支持复杂的工作流程,其中多个工具通过共享元数据进行协调。
它将所有项目相关的信息保持在一个结构化的源中。
为什么UFO被优先用于字体项目的长期保存?
它的纯文本、开放标准架构避免了专有锁定。
未来的工具可以解析或转换UFO文件,而无需逆向工程。
这确保字体在创建几十年后仍然可编辑。
为什么设计师应该避免将UFO文件作为最终字体分发?
UFO是一个工作源格式,而不是可安装的字体。
它缺乏OTF或TTF所需的编译指令、优化轮廓和最终特征结构。
分发需要通过适当的字体构建管道导出和验证。