How to Check Font Embedding Rights (fsType Flags Explained)
- The fsType flag embedded in every OpenType font file controls whether and how the font can be legally embedded in web pages, PDFs, and documents.
- Using a font with fsType 2 (Restricted) in a CSS stylesheet or PDF violates the license — even if you own a desktop license.
- You can check any font's fsType value in about 15 seconds using a browser-based viewer.
Table of Contents
You found a font you like. You purchased a license. You converted it to WOFF. You added it to your CSS @font-face declaration. Technically, it works. But is it legal?
The answer depends on a two-byte value called fsType embedded in the font file itself. This flag controls embedding permissions at the font specification level, and it's separate from whatever license text you read on the foundry's website. Getting it wrong is a real licensing violation — one that professional type foundries actively enforce.
Here's what the flag means and how to check it in under a minute.
What the fsType Flag Is and Where It Comes From
fsType (also written as "Embedding Licensing Rights") is a field in the OS/2 table of every OpenType and TrueType font. It was defined by Microsoft as part of the font specification and is present in virtually every modern font file.
The field stores a 16-bit integer where specific bits indicate what kind of embedding is permitted. Font authors set this value when creating the font. Foundries use it to technically enforce licensing restrictions — professional PDF viewers and some web font loaders check this value and may refuse to embed fonts with restrictive flags.
The four categories, by the bit pattern:
- 0 — Installable Embedding
- 2 — Restricted License Embedding
- 4 — Print and Preview Embedding
- 8 — Editable Embedding
What Each fsType Value Means for Web and PDF Use
fsType 0 — Installable Embedding
No restrictions. The font can be embedded in PDFs, web pages via @font-face, apps, ebooks, and any other medium. Recipients of an embedded document can install the font on their system. Most OFL-licensed fonts (including all Google Fonts) have fsType 0.
fsType 2 — Restricted License Embedding
No embedding permitted. This font cannot be legally used in a CSS @font-face rule, embedded in a PDF, or included in an app. If you have a desktop-only license, this is the typical value. A separate web font license (usually sold separately by the foundry) is required for any embedded use. Using a restricted font on a website is a licensing violation.
fsType 4 — Print and Preview Embedding
The font can be embedded in PDFs for viewing and printing. However, the document must be read-only — the embedded font cannot be used in an editable document. The recipient also cannot extract or install the font from the document. For CSS web fonts, this value is generally interpreted as not permitting @font-face use.
fsType 8 — Editable Embedding
The font can be embedded in documents that allow editing (e.g., Word documents or fillable PDFs). More permissive than Print and Preview. For web use, this is a gray area — some interpretations permit it; many foundries require a separate web license regardless.
Sell Custom Apparel — We Handle Printing & Free ShippingHow to Check a Font's fsType Value
Open the WildandFree Font Metadata Viewer and drop your TTF, OTF, or WOFF file onto it. The Embedding Permissions field shows the fsType value along with a plain-English description of what it means.
The check takes about 15 seconds — faster than looking up the font's license page, and more authoritative than trusting the description on a font download site.
If you're auditing a large library of fonts, fonttools on the command line lets you check many at once:
python3 -c "from fontTools.ttLib import TTFont; print(TTFont('yourfont.ttf')['OS/2'].fsType)"
What to Do When fsType and License Text Disagree
Some fonts have an fsType value that conflicts with their stated license. This most commonly happens with OFL-licensed fonts that were compiled before the font spec was widely understood — the file says "Restricted" but the OFL text clearly permits web embedding.
In these cases, the general legal consensus is that the license text governs intent and the fsType value is a technical error. Many type lawyers take the position that a signed OFL license overrides a conflicting fsType bit.
However, for commercial work where the cost of being wrong is high, the safest path is to contact the foundry and ask them to update the flag — it's a one-minute fix in any font editor — or use a font where both the fsType and license clearly align to your use case.
Check Your Font's Embedding Rights Now
Drop a TTF, OTF, or WOFF to instantly see its fsType embedding flag — Installable, Restricted, Print & Preview, or Editable — plus full license text.
Open Font Metadata ViewerFrequently Asked Questions
Can I use any font in CSS if I have a license for it?
Not always. Desktop font licenses typically cover use on your own computer but not web embedding via @font-face. You usually need a separate web font license. The fsType flag often reflects this — a desktop-licensed font typically has fsType 2 (Restricted) which technically prohibits web embedding.
Do Google Fonts have any embedding restrictions?
No. All Google Fonts use OFL or Apache 2.0 licenses and have fsType 0 (Installable). They can be embedded in web pages, PDFs, apps, and documents without restriction.
What does fsType 4 mean for web fonts?
fsType 4 (Print and Preview) was designed for print and PDF contexts. Its applicability to web fonts is debated. Most foundries that use fsType 4 intend it to restrict @font-face embedding. If you need certainty, check the foundry's web licensing terms directly.
