Start with font health
OTS checks the font structure before any preview loads. A warning means the sanitized copy differs from the uploaded source and deserves review.
Private font analysis
Upload one font to inspect its names, licensing fields, language coverage, OpenType features, variable axes and technical health. You get a practical report without creating an account.
The original file is analyzed in an isolated worker and removed as soon as the report is ready.
Private inspection report
Download the current size, OpenType features and variable-axis settings. Use the CSS with an installed font or your own @font-face rule; the font file is not included.
The most useful identity, coverage, rights and health signals for this font face.
Edit the text below. Only the sanitized font copy is loaded into your browser.
Coverage is measured against exact CLDR 48.2 exemplar characters. Layout readiness also checks shaping support for complex scripts.
Block totals are technical coverage indicators, not proof that a font fully supports a language.
Paste the exact text you plan to use and find every character missing from this font face.
Compare the font’s normal rendering with explicit OpenType overrides. Leave a feature on Default to preserve the font and browser behavior, choose On to force it, or Off to suppress it in the selected preview. Required shaping features stay active.
Move an axis slider or choose a named instance to change the preview below. Reset axes becomes available after a value changes; hidden axes are marked.
These values come from the font itself. Empty or inaccurate metadata does not establish legal rights.
Treat these fields as clues, not legal advice. Confirm the license with the font author or distributor before publishing, embedding or redistributing the font.
Review metrics, rendering capabilities and layout scripts, then open any sanitized font table for bounded, table-specific technical facts.
Search by tag, purpose or decoded value. Open a table to see its directory integrity fields and the facts this inspector can safely decode without exposing font bytes.
Read your results
Use the report to catch practical compatibility problems early, then verify licensing and real-world rendering before release.
OTS checks the font structure before any preview loads. A warning means the sanitized copy differs from the uploaded source and deserves review.
A large glyph count is not enough. Review core characters, auxiliary marks and shaping readiness for every language your project needs.
Paste names, UI labels and translations into the local tester. This catches missing punctuation, symbols and less common letters.
Embedding bits and name-table license text are useful evidence, but only the actual license and rights holder can authorize use.
No public page or database record is created. The original is deleted after analysis; the sanitized preview files and in-memory report expire automatically after about 15 minutes, and Delete now removes them sooner.
No security tool can make that absolute promise. The preview is generated only after OpenType Sanitizer accepts the font, and processing runs in an isolated worker with strict size and time limits.
It means the font maps every core exemplar character in the pinned CLDR 48.2 profile. Complex-script languages also need a successful shaping probe. Quality, style and all possible vocabulary still require visual testing.
No. It reports embedded permission bits and license text stored in the font, but those fields may be missing or wrong. Verify the original license and your grant of rights.
The sanitizer can reject malformed data or normalize unsafe or invalid structures. The report flags meaningful changes to glyphs, coverage, layout, variations or outlines so you can investigate.