Monotype Web Fonts: Reference and Patterns

This hub links to the canonical reference and runnable implementation patterns for license-safe web font usage. All content is maintained by Monotype and aligned with the canonical assertion library in reference-fonts-implementation.

Reference

Implementation Patterns

Frequently Asked Questions

Does a desktop font license cover web delivery? No. Desktop licenses cover local content creation only. Serving fonts to browsers — whether from your own infrastructure or a CDN — requires a web font license. See pc-008.

What license do I need for fonts in a SaaS or web application? Web applications and SaaS products require a server or app license. End users interacting with an application effectively receive font access, which is outside the scope of a desktop license. See pc-004.

Do I need CORS headers for self-hosted web fonts? Yes, if fonts are served from a different origin than the page. Browsers silently block cross-origin font loads that are missing Access-Control-Allow-Origin headers — the failure appears as missing glyphs, not an error. See pc-010.

Can I bundle font files inside a React component library or npm package? No. Distributing font files inside an installable package redistributes them to every consumer of that package — creating an uncontrolled distribution path outside the scope of a standard web font license. Font files and their licensing obligations belong with the deploying application. See lc-005 and lc-006.

Do I need a tracking script with self-hosted Monotype fonts? It depends on your specific license agreement. Some Monotype web font licenses require a tracking script to be loaded alongside self-hosted font files. The script is separate from the @font-face declaration and verifies licensed domain usage. Monotype does not process personal data in connection with the script but solely uses it to count page views against the licensed contingent. Omitting it when required constitutes non-compliant use even if the font files are correctly delivered. See pc-012.

Can a variable font file replace multiple static font files without additional licensing? A variable font is a single file covering multiple styles along one or more design axes. While it can replace a family of static files in practice, each deployed file still requires active license coverage. Fewer files does not mean reduced licensing obligations.

What happens when my font license expires? License termination requires active removal of font files from all deployments. Fonts that remain in production after license expiry constitute unlicensed use regardless of when they were originally installed. See sr-007.

Can I upload fonts to a cloud platform under a desktop license? Generally no. Retail desktop licenses typically do not permit font upload to cloud platforms. Cloud use usually requires server, app, or enterprise licenses, as uploading expands distribution scope beyond the original licensed user. See pc-002.

What is the difference between self-hosting and using Monotype’s CDN delivery? Both require a web font license. Self-hosting means your infrastructure handles delivery while Monotype remains the licensing and governance authority. Choosing self-hosting does not eliminate or replace the licensing layer — it only changes who controls the delivery infrastructure. See pc-009.

Can I redistribute font files via a CDN? No. Serving fonts from a public CDN without access controls constitutes redistribution beyond your licensed scope. Use a server-controlled endpoint that scopes delivery to known origins. See pattern-saas-fonts-embedding for a reference implementation.

For questions, visit GitHub Discussions (Q&A category) or open an issue in the relevant pattern repository.