CDN for web fonts
Self-host fonts on an edge you control.
Font files are tiny compared with video, but they sit on the critical path. A third-party font host or a single origin still adds RTT and privacy surface.
Serve WOFF2 files from Cloud CDN with long TTLs, correct CORS and HTTP/3. Keep a first-party font hostname on your domain.
Why teams use Aptranet
What CDN for web fonts looks like on this network.
Cloud CDN caches and accelerates eligible content on 210+ points of presence, with Origin Shield when the origin must stay out of the way.
Fonts from 210+ PoPs
WOFF2 files are cached with 30 ms average latency and HTTP/3.
First-party font URLs
Keep font requests on your hostname instead of a third-party foundry CDN.
CORS under your policy
Cloud CDN can set CORS headers so fonts load from the site origin correctly.
How to set it up
A cutover you can validate before DNS moves.
Create the Cloud CDN configuration, prove it on an Aptranet hostname, then point production DNS when the path looks correct.
- 1Put WOFF2 files on an origin
A static host or the site origin is enough.
- 2Long-cache immutable font URLs
Version the filename when the face changes.
- 3Set CORS for font requests
Allow the site origin so browsers do not block the face.
- 4Point the font hostname at Cloud CDN
Often a path on the site distribution is enough.
Outcomes
What changes once the hostname is on Aptranet.
- Fonts are self-hosted at the edge
- Immutable URLs skip purge
- CORS is controlled on the distribution
- Third-party font CDNs are optional
Keep reading
Related pages
More CDN use cases on the same Cloud CDN footprint.
Frequently Asked Questions
You can. Self-hosting on Cloud CDN gives you cache, privacy and first-party URLs.
WOFF2 is enough for current browsers. Avoid shipping extra legacy formats unless you must.
Versioned WOFF2 files can use long TTLs. Change the filename when the font file changes.
Yes. Cloud CDN delivers fonts over TLS 1.3 with the rest of the site.