Intent to Prototype: Incremental font transfer
95 views
Skip to first unread message
Chromestatus
Apr 28, 2026, 7:39:09 PM (2 days ago)
Apr 28
to blin...@chromium.org, wmed...@chromium.org, wmed...@google.com
Contact emails
wmed...@google.com
, wmed...@chromium.org
Explainer
https://garretrieger.github.io/ift-demo
Specification
https://www.w3.org/TR/IFT
Summary
Incremental font transfer enables the browser to download only the specific portions of a web font needed to render the text on a page. This reduces bandwidth usage and improves page load times for sites using large fonts. This allows developers to optimize web performance without needing to generate and manage font subsets. Blink component
Blink>WebFonts
Web Feature ID
Missing feature Motivation
Web fonts for languages with large character sets—such as Chinese, Japanese, and Korean (CJK)—often exceed several megabytes in size. Downloading these massive files significantly delays text rendering, consumes excessive bandwidth, and degrades the user experience.
The current alternative to incremental font transfer is unicode-range based subsetting. From our demo, incremental font transfer sees typical savings of 50% or more compared to the subsetting approach. fonts.google.com
serves a significant amount of web fonts and will be ready to support the best font delivery option Initial public proposal
https://www.w3.org/TR/IFT/
Goals for experimentation
None Requires code in //chrome?
False Tracking bug
https://g-issues.chromium.org/issues/498722796
Estimated milestones
No milestones specified
Link to entry on the Chrome Platform Status
https://chromestatus.com/feature/5135917565214720?gate=4886470612615168
Reply all
Reply to author
Forward
Search
Clear search
Close search
Google apps
Main menu
