How to use the font license review checklist
People buy a font and then get stuck on whether they may serve it as a web font or ship it inside an app. This checklist lays out the eight clauses that cause trouble most often, asks whether each one is part of your use and what your own license text says about it, and then shows you only the items still left to check.
There are three answers per item: the text allows it, the text limits or forbids it, or you could not find it. The last two are counted as items that still require checking. Where a cap is written as a number, such as pageviews or domains, entering both your figure and the cap compares them, with the cap itself counted as inside. Written as of October 2026.
The page does not rule on what is allowed. Font licenses differ by foundry, reseller and purchased tier, and judging scope is a legal judgment, so building in per-font license data or declaring a use "permitted" would lead whoever believed it into breaching the terms. The output sorts your own entries; the license text (EULA) and the rights holder still have to be checked, and a contested case belongs with a lawyer.
Frequently Asked Questions
No. Judging license scope is a legal judgment, and the same font can be allowed or not depending on the license tier. This page only sorts the values you read out of your own text against the uses you need and lists what is still open.
No. Terms differ by foundry, and the same font can carry different conditions depending on the reseller and the date of purchase, so building in per-font license data would produce wrong answers. Read the EULA file from wherever you bought it.
They are not. A license may also cover the term, transfer and subcontracting, cloud hosting or variable font instances. These eight are the ones that cause trouble most often, and they do not replace reading the whole text.