Understanding Font Metadata Tables
Font files are not merely collections of vector outlines; they are structured databases containing specialized metadata tables. When a browser or operating system renders a typeface, it reads these binary tables to determine how the font behaves, who created it, and what legal restrictions apply to its use.
The primary repository for naming and licensing information within TrueType (TTF) and OpenType (OTF) specifications is the name table. This table consists of standardized name records that store strings for the font family, style, copyright notices, trademark attributions, designer names, and licensing terms. Because these records can be localized, the table often contains multiple language variants for a single record, such as a ‹language› record designed to display the correct translation based on the user's operating system settings.
When a font file is loaded into the Font License & Info Checker, the tool parses these binary structures directly within the browser. It extracts the raw strings from the name table to populate fields under the Ownership and source records and License declarations headings. If these standard fields are empty, the tool displays fallback strings such as No license text is declared in the standard name field., No license URL is declared in the standard name field., or No ownership or source records were found in the standard name fields.. To keep the interface readable when dealing with verbose legal disclaimers, extremely long metadata values are truncated and marked with the label Long value shortened for display.
The Role of fsType in Document Creation
Beyond creative attribution, font files contain an fsType setting that describes how they can be embedded within documents.
The Font License & Info Checker reads this field and displays the Raw fsType value alongside its corresponding Primary setting. The tool maps the raw bitmask to one of several standardized definitions:
- Installable embedding: The font may be embedded in documents and permanently installed on the destination system for use in other applications.
- Restricted License embedding: The font must not be embedded in any document without explicit permission from the copyright owner.
- Preview & Print embedding: The font may be embedded in documents, but the document must be opened as read-only. The recipient can view and print the file but cannot edit it using the embedded font.
- Editable embedding: The font may be embedded in documents, and the recipient is permitted to edit the document using the embedded font.
If the bitmask contains contradictory instructions, the tool displays Conflicting embedding bits. If the table is missing or corrupt, it shows This font has no readable OS/2 embedding field..
The tool also checks for secondary flags within the bitmask, displaying messages such as No subsetting (which requires the entire font to be embedded rather than just the characters used), Bitmap embedding only (restricting embedding to the font's bitmap glyphs), Reserved or deprecated bits are also set, or No extra flags.
Font Licensing vs. Technical Metadata
A critical distinction must be made between the technical declarations embedded inside a font file and the legal right to use that font. The metadata fields parsed by the Font License & Info Checker serve as file evidence. They show what the font file itself declares, but they do not constitute legal proof of a license or confirm who purchased it.
For example, a font file may contain a License URL pointing to a standard commercial agreement, or its Primary setting might indicate Installable embedding. However, these technical properties do not verify whether your specific organization has paid for the appropriate seats, whether your pageview volume covers webfont usage, or whether your planned use is permitted under your contract. As noted in the tool's interface, These are declarations stored inside this font file. They do not confirm who licensed it or whether a planned use is covered.. Similarly, the fsType setting only describes document embedding; it does not decide webfont, app, commercial, modification, or redistribution rights.
Web-Safe and Local Font Formats
The checker accepts TTF, OTF, WOFF, WOFF2 and TTC files. Each file can be up to 32 MB, and a TTC result shows at most the first 32 fonts in the collection.
How Browser-Based File Parsing Works
When you drop a file into the interface, the tool reads the data locally in your browser and does not upload the file to BroBroGo.
Because the processing happens on your local device, it is subject to browser resource limits. If a file is corrupt, empty, or takes too long to parse, the tool will halt and display specific error messages to help you troubleshoot the file.
Troubleshooting and Error States
When inspecting files, you may encounter validation errors if the file does not conform to standard specifications. The tool uses the following error states to diagnose issues:
- Incorrect File Type: If you attempt to load an unsupported format, the tool displays:
Choose a TTF, OTF, WOFF, WOFF2 or TTC font file.. - Zero-Byte Files: If the file contains no data, it triggers:
This file is empty. Choose a complete font file.. - Size Limits: Files exceeding the maximum threshold trigger:
This font is over the 32 MB limit.. - Corrupt Data: If the binary structure is unreadable, the tool displays:
The file is not a readable supported font. It may be damaged or use another format.. - Browser Read Failures: If local security policies or system errors block access, it shows:
The browser could not read this file. Try another copy.. - Timeouts: If parsing hangs, the tool stops and displays:
Reading took too long and was stopped. Try a smaller or different font file.. - General Failures: For unspecified parsing errors, the interface displays:
The font could not be inspected..
Once a font is successfully parsed, you can use the Copy report button to copy the extracted metadata to your clipboard, or click Clear to reset the interface and inspect a different file.
Frequently Asked Questions
Can this confirm that I am licensed to use the font?
No. A font file can carry copyright, license text, a license URL, and technical embedding flags, but it cannot show who bought it, which account or company is covered, where it came from, or whether your planned use fits the agreement. Match these fields with the download source, receipt, and current terms from the foundry or designer.
What if the font contains no license text?
Missing text means only that this copy of the file does not declare a license in the standard name fields. It does not make the font free or unlicensed. Check the folder it came in, the original download page, your order history, or the font maker directly.
What do the embedding flags mean?
They are the font maker’s technical settings for placing the font inside documents: installable, restricted, preview and print, or editable. Extra bits can forbid subsetting or allow bitmap data only. These settings do not grant webfont, app, commercial, modification, or redistribution rights, and written terms may impose other limits.