OTF to TTF is on hold On hold
This route is not available in Glyph Batch, and the page exists to say so plainly rather than to collect a search visit and then disappoint it. A real OTF to TTF conversion has to redraw every glyph from cubic Bézier curves into quadratic ones. This build does not implement that transform, so it will not offer it.
This conversion is not available
Not implemented and not faked. Converting OpenType/CFF outlines to TrueType requires an approximating curve conversion this build does not have.
An .otf file usually contains a "CFF " table: glyph outlines drawn with cubic Bézier curves, the PostScript curve model. A .ttf file contains a "glyf" table: outlines drawn with quadratic curves. These are different mathematics, not different packaging.
Cubic to quadratic is an approximation. Each cubic segment has to be subdivided into a chain of quadratic segments until the error falls below a chosen tolerance, and the result then has to be rounded onto the integer grid TrueType uses. Every hinting instruction in the source has to be discarded, because CFF hints and TrueType bytecode are unrelated systems. The glyph set has to be rebuilt, "loca" and "maxp" recalculated, and left side bearings re-derived from the new bounding boxes.
Done carelessly, that pipeline produces files that open in a font viewer, load in a browser, and render with subtly melted curves or missing contours that nobody notices until print. Done not at all — which is what many online converters do — it produces the original CFF bytes with a .ttf extension stapled on. Glyph Batch will not ship either outcome.
The curve mathematics, the outline model and the glyf writer needed for this route are already in this codebase and unit-tested. What is missing is the CFF charstring interpreter that reads the source outlines, and the verification corpus needed to prove the result is correct across CJK, variable and colour fonts. Until both exist, this route stays held. It is tracked in BACKLOG.md.
What to do instead
- Keep the .otf and convert the container instead — If your goal is a web font, you do not need TrueType at all. OpenType/CFF compresses to WOFF2 and loads in every browser. That route accepts .otf directly.
- Check what your .otf actually contains — Some files named .otf hold TrueType outlines already. If yours does, no outline conversion is needed and any container route will give you a genuine .ttf.
- Use fontTools if you truly need TrueType outlines — The formats page explains what the desktop toolchain does here and when the conversion is worth its losses.
Related
Inspector
Read everything inside a font file in your browser: family and PostScript names, version, copyright and licence text, OS/2 embedding permissions, variation axes, colour tables and the full table directory.
OpenTTF to WOFF2
Compress TTF or OTF fonts to WOFF2 in your browser using the reference Google encoder. Batch queue, @font-face CSS, preload snippet and ZIP. No upload, no server.
OpenFormats
A precise guide to the four font formats: what a container is, what an outline model is, why OTF to TTF is a real conversion and TTF to WOFF2 is not, and which format to ship.
Open