Subset a font in your browser

A Japanese webfont is 3–8 MB because it carries thousands of glyphs your pages never show. Paste your site’s text, keep those characters, ship 90% less font.

Loading the tool…

How it works

  1. Drop the .ttf or .otf.
  2. Paste the text of your site (or add ranges with the buttons) — those characters survive.
  3. Download the WOFF2, paste the @font-face, done.

Why nothing is uploaded

Every operation on this page is done by code running inside your browser tab, using the same engine that renders web pages. The file is read from disk into your tab’s memory, transformed there, and written back out as a download. It is never sent anywhere — not to us, not to a third party.

Verify it yourself

  1. Open your browser’s developer tools (F12) and select the Network tab.
  2. Load your file and run the tool.
  3. The only requests you will see fetch the tool’s own code — and, for a few heavy tools, their open-source engine from a public CDN — plus one small page-view ping to loreatec.jp (page address and title, nothing more). None of them carry your file.

Proof it stays local →

Frequently asked questions

What happens if a page later needs a missing glyph?

The browser falls back to the next font in your stack for that character — visible as a style mismatch, not as a broken page. If your content changes often, re-subset with the new text, or keep whole ranges (kana + the jōyō set) instead of exact characters.

Is subsetting allowed by font licences?

Open licences (OFL, Apache) explicitly permit it. Many commercial webfont licences do not, or count pageviews. The tool transforms bytes you already have; checking the licence is your side of the deal, and it is stated here rather than hidden.

Why is the WOFF2 so much smaller than the TTF?

Twice over: first the subset drops unused glyphs, then WOFF2 compresses what is left with Brotli. Serve the WOFF2; keep the TTF for desktop testing.