Commercial font licenses (Adobe, Monotype, MyFonts and most independent foundries) routinely forbid transferring the font file to a third party's server. Uploading a font to a website just to check its license can itself be a breach. So: don't upload the font anywhere to check its license — most licenses forbid exactly that.
This tool reads and interprets the technical permission bits inside the font file. It is information, not binding legal advice — confirm the license text with the font's vendor. The fsType bits do not replace the license agreement; the agreement can be more restrictive.
No bits set. The font may be embedded in any document and may even be permanently installed on the receiving system. The most permissive value — where nearly all open-source fonts (SIL OFL, Apache, Ubuntu) sit.
◀ this fontThe strictest value. The font must not be modified, embedded or exchanged in any way without written permission from the owner. Not in a PDF, not in a webfont, not in an app — nothing leaves your machine with the font inside it.
◀ this fontThe font may be embedded and temporarily loaded on the recipient's system, but the document must stay read-only: it can be viewed and printed, never edited with the embedded font. No permanent install, no webfont.
◀ this fontThe font may be embedded, temporarily loaded, and the document may be opened for reading and editing. Everything Preview & Print allows, plus editable documents. It still does not permit permanent installation on the recipient's machine.
◀ this fontA modifier, not a level — it combines with any of the four above. The font must be embedded whole; you may not strip unused glyphs. This breaks the normal webfont pipeline (fonttools subset, glyphhanger, unicode-range splitting) and makes files much heavier.
◀ this fontAlso a modifier. Only the bitmap images inside the font may be embedded — never the outline data. Since a PDF, a WOFF webfont and an app build all embed outlines, this bit effectively blocks ordinary embedding. Very rare in practice.
◀ this fontDrop a TTF, OTF or WOFF file and this free font embedding license checker reads the OS/2 fsType permission bits and the license text stored inside the font, then answers the question you actually have: can I embed this font on my website, in a PDF, in an app or in an e-book — and can I subset it? Other tools show you “fsType: 8” and stop there. This one tells you what that means for the thing you are about to ship. No sign-up, no watermark, and — crucially for fonts — no upload: everything runs in your browser.
Don't upload a font to a website just to check its license — most licenses forbid exactly that. Commercial font EULAs from Adobe, Monotype, MyFonts and most independent foundries explicitly prohibit transferring the font file to a third party or their servers. A checker that runs server-side asks you to break your license in order to read it. Being serverless is not a feature of this tool; it is the reason it exists.
If you have been searching how to check font license terms without handing the file to a stranger, this is the short version: drop it here, read the six answers, download the report.
Drop one font — or a whole family — into the box. TTF, OTF and WOFF are read directly in the browser.
Read the verdict card for each use: website, read-only PDF, editable document, app or game, e-book, subsetting. Green means the font's bits allow it.
Check the designer, vendor and license URL shown underneath, then download the summary as TXT or the whole family as a CSV table.
Restricted (fsType 2): the font file may not travel with your work at all. You may design with it on your own machine, but you must not place the font inside a PDF, a website, an application or a document you hand to someone else. In practice: convert the text to outlines, export an image, or write to the foundry for permission.
Preview & Print (fsType 4): the font file may travel, but only inside a document the recipient can read and print and cannot edit. A press-ready or read-only PDF is fine. An editable Word file, an editable PDF form, an InDesign package, an EPUB or an @font-face webfont is not.
The gap between them is not “a bit stricter”. It is the difference between you may hand over a print PDF and you may hand over nothing. Getting this backwards is exactly the kind of mistake that ends in a licensing claim, which is why this tool spells it out instead of printing a number.
Drop the font in and the tool answers directly. If the fsType value is 0 (Installable) or bit 3 (Editable) is set, the font's own permission bits allow webfont embedding. If bit 2 (Preview and Print) or bit 1 (Restricted) is set, they do not. The bits are only half the answer though: many commercial foundries sell desktop and webfont rights separately, so the license agreement can still say no even when the bits say yes.
Restricted (fsType 2) means the font file must not travel with your work at all. You may design with it, but you may not put the font inside a PDF, a website, an app or a document you hand to somebody else without written permission from the owner. Preview and Print (fsType 4) means the font file may travel, but only inside a document the recipient can read and print and cannot edit. A press-ready or read-only PDF is fine; an editable Word file, an editable PDF form, an InDesign package or a webfont is not.
No. The font is parsed inside your browser and never leaves your device. This matters more here than in any other tool: commercial font licenses from foundries such as Adobe, Monotype and MyFonts often explicitly forbid transferring the font file to a third-party server, so uploading a font to a website in order to check its license can itself be a breach of that license.
No. fsType is a technical permission flag the font vendor set inside the file. The binding document is the EULA you accepted when you obtained the font, and it is frequently more restrictive than the bits. Treat a green answer here as the technical door being open, and the license text as the one that decides whether you are allowed to walk through it.
WOFF2 uses Brotli compression, and decompressing it in the browser needs an extra 1.27 MB library. We deliberately left it out so the page stays light. TTF, OTF and WOFF are read directly. If you only have a WOFF2, convert it to TTF or check the original desktop file instead.