Base64 to WOFF2 Converter
Paste Base64 and get the font file back. WOFF2 files begin with the four bytes wOF2, WOFF with wOFF — the tool reads that signature, so you find out immediately whether the string is really WOFF2, an older WOFF, or a raw TrueType file with the wrong label.
- WOFF2 starts with
wOF2; WOFF starts withwOFF - Both are compressed containers — the decoded file is not a plain font table dump
data:font/woff2;base64,prefixes are stripped automatically- Inlining a full font in CSS blocks rendering and defeats caching
- Check the font licence before embedding it anywhere
Processed as you paste — no button to press (Ctrl+Enter converts now / Esc clears)
Drop a file here, or — Ctrl+V a screenshot works too
Any file type · 100 MB maximum
Paste, drag and drop, or Ctrl+V a screenshot
Where Base64 WOFF2 appears
- CSS
@font-faceblocks — the classicsrc: url(data:font/woff2;base64,...)pattern, usually produced by a build tool or copied from a font CDN - Single-file HTML — an offline demo or a design mockup that must render identically with no external requests
- Email templates — where external font files are blocked, so some senders inline them (rarely a good idea, see below)
- App bundles and config files — a mobile build that ships one font as a JSON string field
The four signatures worth knowing
The first four bytes tell you what you have, and they are easy to confuse:
wOF2— WOFF2, Brotli-compressed, the format you actually want on the webwOFF— WOFF 1, zlib-compressed, the older formatOTTO— OpenType with CFF outlines (often a.otf)00 01 00 00ortrue— raw TrueType
A string labelled "woff2" that starts with 00 01 00 00 is a plain TTF: it will still work in a browser, but it is several times larger than the same font recompressed to WOFF2.
Why inlining a font is usually wrong
A font file is the largest thing most sites inline. A single Latin subset is 15–30 KB; a full family can be hundreds. Base64 adds another 33 percent, the CSS that carries it cannot finish downloading until the whole string has arrived, and because the data lives inside the stylesheet it is re-sent with every cache miss on that stylesheet instead of being cached as its own file.
The exceptions are narrow: a tiny icon font under a few KB, or a genuinely single-file artifact that must work offline. Everything else is better as a separate .woff2 with font-display: swap and a long cache header.
Licensing is the part people skip
Most commercial fonts are licensed per use, and embedding the file in CSS is a distribution. Open-licensed fonts (OFL, Apache) permit it with attribution rules; paid desktop licences often do not cover web embedding at all. If the Base64 came from a template or a purchased theme, the licence travels with the font file, not with the CSS you found it in.
To encode a font you own, use file to Base64. To identify an unknown Base64 blob, the general decoder reads the header for you.
Frequently asked questions
The decoded file will not load as a font — why?
Check the signature first. A .woff2 extension on a file that starts with 00 01 00 00 is a TTF, and some servers refuse to serve it under the wrong MIME type. Rename it to .ttf, or recompress it to WOFF2.
Can I convert WOFF2 back to TTF here?
No — this page restores the bytes exactly as they were encoded. WOFF2 is a Brotli-compressed wrapper, so converting it to TTF needs a font tool such as woff2_decompress or fonttools.
Does Base64 change the font quality?
No. Encoding is lossless and reversible; the bytes are identical. Only the size changes, upward by about a third.