Convert WOFF2 to OTF

It happens constantly. A brand package is assembled by whoever built the website, the website needed web fonts, and the folder that circulates afterwards contains a WOFF2 per weight and nothing else. Six months later somebody has to set a report, a pitch deck or a poster, and the typeface will not install.

Unwrapping the web file is the obvious move and it works. It is also the second-best answer, and knowing why matters more here than on any other font page: the web build was a deliberate reduction, and the reduction is what you are about to inherit.

WOFF2 carries either kind of curve without distinguishing them. Underneath, a font holds quadratic outlines in a glyf table or cubic PostScript outlines in a CFF table, and that choice was made by the type designer years before anyone thought about the web.

The unwrapped file has to be named for what it actually contains, so the converter inspects the tables and insists. A CFF font becomes an OTF; a TrueType one becomes a TTF and the OTF request is refused with the reason. If you asked for OTF and were told the font holds TrueType outlines, nothing is wrong — the answer is simply TTF, and it installs and behaves identically for layout work.

Preparing a font for the web means removing every glyph the site does not set, because that is where the download saving comes from. A file built for an English-language site typically holds basic Latin and a handful of punctuation marks, out of a retail character set that may have run to several hundred glyphs.

You will meet it the first time a name, a place or a price needs a character the site never used — an accented vowel, a dash of the wrong length, a currency symbol. The application shows a blank box or silently substitutes another font for that character, which is worse because it is easy to miss until proof stage.

True small capitals, old-style figures, discretionary ligatures and stylistic alternates are separate glyphs that feature tables point at. A subsetter told to keep the characters found in the page content sees them as unreferenced, discards them, and the feature definitions become dead entries or disappear.

That is exactly the material a layout designer reaches for. The typographic panel in InDesign or Affinity will show what is genuinely present, so open the converted font and check before committing a design to small capitals that the web build removed in 2021. It is a five-second check that saves an argument about why the web and the brochure do not match.

This misconception is worth killing directly. Font outlines are vector curves with no resolution of any kind; the same file sets six-point footnotes and a poster headline from the same description. Nothing about having been served to a browser degrades a letterform.

So a subset web font converted to OTF prints at exactly the quality the original does, for every character it still contains. The reason to want the desktop release is coverage, features and licensing — not fidelity, not sharpness, and not print quality. Anyone told otherwise has been sold a different argument.

Install the OTF the way any font is installed and it appears in every application’s font list after a restart. Layout software treats it as an ordinary OpenType font, with the typographic panels reading whatever feature tables survived.

Two practical points. Applications display the family name from inside the file, and web builds frequently rewrite that name, so the typeface may appear under something unrecognisable in the menu. And a document that uses it needs the font wherever it is opened — packaging a layout for a printer copies the font file into the package, which is a distribution of the font and therefore a licensing act rather than a technical one.

The right fix is almost always to obtain the real font. The name table inside the file usually still carries the designer, the foundry or a manufacturer URL even when the family name has been rewritten, and any font editor or inspector will show them.

With that, the desktop release can be bought or the client’s existing licence located. Foundries sell desktop and web as separate products, so a web team holding files is not evidence that a desktop entitlement exists — and buying one is frequently cheaper than the time spent working around a subset. For open-licensed families the original is usually a free download from the project that publishes it.

If the site used a variable font, the WOFF2 holds one set of outlines plus interpolation data covering a whole weight axis, and the unwrapped OTF keeps all of it. Current versions of the major layout applications expose the axes as sliders; older ones show a single default instance and nothing else.

That is worth checking before assuming a weight is missing. A variable font that appears in the menu as one entry may well contain the light and the black the design calls for, sitting behind an interface the application version does not draw.

Four things, and they are worth stating together because they are all decisions made before the file reached you. Glyphs removed by subsetting are gone. Feature tables stripped alongside them are gone. A family name rewritten by a kit builder stays rewritten. And hinting, if a build step dropped it, is not regenerated.

One more, from this end: the converter changes the container and never the curves. It will not turn PostScript outlines into TrueType ones or the reverse — that redraws every glyph, and a half-correct version produces a font that looks right and spaces wrongly, which is why it is refused rather than approximated.