Add your BDF file
Drop one or more .bdf files onto the converter above, or browse for them. They load into browser memory only — nothing is uploaded, so there is no size-based pricing and no server queue.
BDF to WOFF2
Converting a .bdf font to .woff2 repackages the same glyphs and metrics for a different delivery target. Free, private, and validated — the file never leaves your browser.
Private for supported formats — processed in your browser
Runs on your deviceConvert supported files
Drop BDF files here
Batch files can each use a different output. Nothing uploads for local conversions.
Working inputs include camera RAW, browser-local audio/video, PDF, CBZ/CBR comics, office documents, ebooks, markup, 3D models, structured text, images, and archives.About converting Glyph Bitmap Distribution Format to WOFF2 web font
Converting a .bdf font to .woff2 repackages the same glyphs and metrics for a different delivery target. A .bdf file is a bitmap font written as plain text. Each glyph is stored as a small grid of hexadecimal rows describing which pixels are lit, together with its bounding box, advance width, and character encoding — no curves, no hinting, just the exact pixels the font was designed to produce at one specific size.
WOFF2 (.woff2) is the current web-font format: a font's sfnt tables preprocessed and squeezed with Brotli compression so pages download less type data. It is purely a transport wrapper — decompressing a .woff2 reconstructs a working TrueType or OpenType font. For this route the practical draw is the smallest deliverable font format, cutting load time and bandwidth and lossless — full fidelity of the wrapped font is preserved — balanced against operating systems will not install it, so designers juggle separate web and desktop copies of the same font, which is worth knowing before you commit a large batch.
Why convert BDF to WOFF2?
The practical trigger for this conversion is usually a mismatch: with .bdf, single-size by design; enlarging a BDF font produces visible stair-stepping rather than smooth glyphs. Switching to .woff2 buys you the smallest deliverable font format, cutting load time and bandwidth, which is why it is the better fit for serving fonts on production websites as the default @font-face source. Because the conversion runs locally, trying it costs nothing but a few seconds of compute on your own machine.
BDF vs WOFF2 at a glance
| Aspect | Glyph Bitmap Distribution Format (.bdf) | WOFF2 web font (.woff2) |
|---|---|---|
| Format type | Lossless — every pixel or sample is preserved exactly | Container — quality depends on the codecs and settings inside |
| How it stores data | the whole file is ASCII text: STARTFONT, FONTBOUNDINGBOX, and a STARTCHAR/ENDCHAR block per glyph, which makes it readable and diffable | brotli compression over the whole font, preceded by a glyf and loca transformation that re-encodes outline data for better compressibility |
| Strongest at | bringing a terminal or retro-computing bitmap font into a browser or design tool that only loads outline fonts | serving fonts on production websites as the default @font-face source |
| Weak spot | single-size by design; enlarging a BDF font produces visible stair-stepping rather than smooth glyphs | operating systems will not install it, so designers juggle separate web and desktop copies of the same font |
| Metadata | the family name, pixel size, and FONT_ASCENT/FONT_DESCENT values are carried into the converted font's name and vertical-metric tables, and each glyph keeps its DWIDTH advance and encoding. XLFD property fields that have no sfnt equivalent are dropped | all metadata of the wrapped font survives untouched, and the container can additionally carry an optional extended-metadata XML block from the vendor |
Pick WOFF2 as the output
Select .woff2 in the output menu next to each file. The menu only offers targets this engine can genuinely produce, so if WOFF2 is selectable, the route is real and validated.
Convert on your device
Press Convert. The font tables are parsed and rewritten locally with fonteditor-core; glyph outlines, hinting, and kerning survive the trip.
Verify and download
Each result is signature-checked before the download unlocks, so a failed encode can never masquerade as a valid WOFF2 file. Outputs keep the original filename with the .woff2 extension.
BDF to WOFF2 questions, answered
Will converting BDF to WOFF2 lose quality?
Since bdf is lossless-oriented and woff2 is container-oriented, the conversion preserves the source content exactly as stored; no additional compression pass is applied beyond what .woff2 itself requires.
Is it private to convert BDF files here?
Yes — the .bdf file is processed inside your browser tab and never uploaded. The font tables are parsed and rewritten locally with fonteditor-core; glyph outlines, hinting, and kerning survive the trip. Close the tab and the file is gone from memory.
Where will the WOFF2 file work?
Chrome, Firefox, Safari, and Edge have all supported .woff2 for years — coverage is effectively universal outside long-dead browsers like Internet Explorer, which never adopted it. Because no operating system accepts it for installation, workflows convert to TTF or OTF whenever a font must leave the browser.
Will the WOFF2 file be bigger or smaller than my BDF?
It depends on the content: brotli compression over the whole font, preceded by a glyf and loca transformation that re-encodes outline data for better compressibility. Convert one representative file first and compare before batch-processing a large set.
What happens to the metadata in my BDF file?
In .bdf, the family name, pixel size, and FONT_ASCENT/FONT_DESCENT values are carried into the converted font's name and vertical-metric tables, and each glyph keeps its DWIDTH advance and encoding. XLFD property fields that have no sfnt equivalent are dropped. Re-encoding through the browser pipeline does not carry embedded metadata into the output, which doubles as a privacy scrub — check the exported file if you specifically need tags preserved.