Webfont Generator
Drop in your font files and this tool builds the whole webfont kit: converted WOFF2 and WOFF files, correct @font-face CSS, a demo page and install notes. It reads each font's own name table and weight data instead of guessing from filenames, checks the embedding permission bits, and does every step in your browser, so licensed font files never leave your machine.
1 Add your fonts
Drop font files here, or click to choose them
TTF, OTF, WOFF and WOFF2. A whole family at once is fine. Nothing uploads: the files stay on this device.
2 Review the styles
| Family | Preview | Status |
|---|---|---|
| No fonts yet. Add a family above and its styles will appear here, each rendered in its own file. | ||
Click a row to correct its family name, weight or italic flag. The generator trusts the font files over the filenames; the popover is there for the files that lie.
3 Choose your options
4 Get your kit
The kit holds the converted fonts in a fonts folder, styles.css, a demo page that shows every style, and a README with install and caching notes.
How it works
A webfont kit is three things that have to agree: the font files, the @font-face rules that describe them, and the names and weights your CSS asks for. Generators that guess the second and third from filenames produce the classic failures: bold that is really the regular file synthetic-bolded, italics that lean because the browser slanted an upright face, a family split into four one-weight families. This tool reads the truth from the files themselves: the family and style names from the name table, the weight from the OS/2 weight class, the italic flag from the font's own selection bits, and, for variable fonts, the axis ranges from the fvar table, which the CSS then declares as ranges so any weight in between just works.
Why it runs in your browser
Most webfont generators ask you to upload your fonts to their server. Font files are licensed software, and a foundry license that permits web use rarely permits handing the file to a third party for processing. Here the conversion engines (the same HarfBuzz subsetter and WOFF2 codec this site uses for its Subsetter) run as WebAssembly on your device. View source, watch the network tab: the only requests are this page and its engines. Your fonts are never transmitted, stored or logged.
About the embedding check
Every font carries fsType bits, a small permission flag set by its maker. The styles table reads them and says what it finds: a font marked restricted may not be embedded at all, and one marked preview and print is not cleared for the open web. The tool still builds the kit, because the flag is information, not a verdict on your license; foundries sometimes set conservative bits on fonts their licenses do allow on the web. What the bits never do is grant permission: your license is the document that decides, and if it does not cover webfont use, no generator can fix that. TheFont Embedding Fixer explains the bits in full, and thefont licensing explainer covers what web use requires.