WOFF

WOFF
Name	WOFF
Extension	.woff, .woff2
Type	Web font container
Owner	World Wide Web Consortium (W3C), originally Mozilla Corporation
Released	2010 (WOFF), 2014 (WOFF2)
Latest release	WOFF 2.0

WOFF

WOFF is a web font file format developed to deliver font resources to web clients efficiently, interoperably, and with metadata support. It was created to bridge established font technologies such as OpenType and TrueType with web standards from organizations including the World Wide Web Consortium, while addressing implementation concerns raised by browser vendors like Mozilla Corporation and companies such as Google, Microsoft, and Apple. WOFF and its successor WOFF2 have become integral to modern web typography workflows used by content management systems like WordPress and infrastructure providers such as Cloudflare and Akamai.

Overview

WOFF packages native font files—principally OpenType and TrueType—into a container that adds compression and metadata for web use. The format was formalized through standardization efforts within the World Wide Web Consortium's Web Fonts Working Group with contributions from implementers at Mozilla Corporation, Google, Microsoft, Apple, and independent authors. WOFF2 introduced improved compression using the Brotli algorithm developed by Google and collaborators. Major browser engines—Gecko, Blink, and WebKit—implemented support to enable typographic features across browsers like Firefox, Chrome, Edge, and Safari.

WOFF is designed to preserve font hinting and glyph tables from source formats like TrueType and OpenType while enabling additional fields for licensing metadata used by foundries such as Monotype Imaging and Adobe Inc.. Web authors reference WOFF fonts via the @font-face rule defined in the CSS Fonts Module specification, enabling site-specific typography in projects ranging from Wikipedia to commercial properties hosted on GitHub Pages.

History and development

The initial WOFF proposal originated at Mozilla Corporation as an interim solution to serve fonts on the web without changing existing font formats. Early discussions involved browser vendors and type foundries including Monotype Imaging and Font Bureau, and drew on compression technologies from projects like zlib and Brotli. In 2010, the WOFF 1.0 format was published as a working draft that codified metadata containers and PNG-like compression derived from zlib.

Standardization moved to the World Wide Web Consortium where the format was refined alongside parallel efforts such as the CSS Fonts Module and the SVG Fonts and WOFF2 initiatives. WOFF2 work began with contributions from Google engineers and researchers experienced with Brotli and fontTools; WOFF2 was published following interoperability testing across projects like Firefox, Chromium, WebKit, Opera Software, and various open-source font tooling suites including FontForge and fonttools.

Adoption accelerated as content platforms and CDNs including Akamai, Cloudflare, and Fastly added support, and as browser vendors rolled out compatibility across desktop and mobile products such as Android and iOS devices. Licensing dialogues with organizations including International Typeface Corporation and independent designers influenced best practices for embedding license metadata within WOFF containers.

Technical specifications

The WOFF container encapsulates a font file table directory, header, and metadata block. WOFF 1.0 applied zlib compression to font table data while preserving original checksum and table structure of OpenType/TrueType sources. WOFF2 replaces zlib with the Brotli-based transform and a specialized per-table lossless compression method that achieves higher sizesavings for glyph-rich fonts used in UI and publishing projects.

WOFF supports embedding an XML metadata block and a private "font-flavor" signature used by font distributors such as Adobe Inc. and Monotype Imaging to assert provenance. The format maintains compatibility with font tables like GSUB, GPOS, CFF, and glyf so that typographic features employed by applications such as InDesign, Illustrator, and Sketch (software) are preserved when rendered by browsers. Tools in the font ecosystem—fonttools, ttf2woff, woff2_compress—implement conversion pipelines and validate checksums against WOFF headers.

Browser and platform support

WOFF and WOFF2 support was incorporated into major browser engines: Gecko (used by Firefox), Blink (used by Chrome and Microsoft Edge), and WebKit (used by Safari). Legacy browsers such as older versions of Internet Explorer required fallbacks to EOT or system fonts from vendors like Microsoft Corporation. Mobile platforms including Android (operating system) and iOS added native support as their respective browser shells updated engine versions. Progressive enhancement strategies often detect WOFF2 support via feature tests implemented in libraries like Modernizr and delivery networks such as Akamai or Cloudflare may serve format-specific assets to clients identified by User-Agent strings.

Usage and implementation

Web developers include WOFF fonts with the CSS @font-face rule, specifying format hints and Unicode-range subsets to optimize delivery for multilingual sites like BBC or The New York Times. Build tools and asset pipelines—Webpack, Parcel, Gulp, and Grunt—commonly integrate plugins to convert source OTF/TTF fonts into WOFF/WOFF2 and produce subsetted artifacts for projects hosted on GitHub Pages or deployed via Netlify. Font subsetting services and libraries like Glyphhanger, pyftsubset (part of fonttools), and commercial offerings from Monotype Imaging reduce file size by removing unused glyphs, kerning pairs, and OpenType tables.

CDNs and HTTP servers use content negotiation and cache-control headers to deliver compressed WOFF files efficiently; optimizations such as HTTP/2 multiplexing and TLS termination on platforms like Amazon Web Services and Google Cloud Platform further reduce latency. Accessibility and internationalization concerns involve Unicode coverage and integration with input methods provided by operating systems such as Windows and macOS.

Security and licensing considerations

WOFF files can carry licensing metadata but do not enforce usage restrictions; enforcement is a legal matter involving foundries like Monotype Imaging, Linotype, and Font Bureau as well as designers represented by entities such as Fontspring and MyFonts. Embedding font files on public sites can expose intellectual property to unauthorized downloads; mitigations include subsetting, using EULA terms, and employing delivery services with access controls.

From a security perspective, font parsing has historically been a vector for vulnerabilities exploited in projects handled by vendors including Microsoft Corporation and Apple Inc.. Browser vendors and security communities such as CERT and CVE coordinators monitor and patch font-rendering flaws in engines like Gecko, Blink, and WebKit. Best practices recommend serving WOFF/WOFF2 files over secure transport (TLS) and keeping toolchains like fonttools and server software up to date to reduce exposure to parsing bugs and supply-chain risks.

Category:File formats