Drop the culprit
or press Cmd+V / Ctrl+V anywhere
Or try a broken sample
Baked in, not borrowed
Most SVG editors reference fonts by URL — url("https://…"). That URL silently fails inside <img> tags, email clients, and sandboxed iframes. SVGOMG-Font encodes the actual WOFF2 data as base64 directly in the file, so fonts travel with the SVG, always.
<img src="diagram.svg">
Works in <img> tags
Inline SVGs can load external fonts. But the moment you drop an SVG into an <img> tag, a CSS background, or an email, external requests are blocked by the browser sandbox. Embedded fonts sidestep the sandbox entirely — the font data is already in the file.
Zero uploads. Zero server.
Your SVG never leaves your machine. Parsing, font lookup, base64 encoding — everything runs locally in your browser. Fonts are fetched from the open Fontsource CDN and cached for instant re-use. No accounts, no quotas, no waiting.
Often smaller. Always smarter.
Converting text to outlined paths is the designer's quick fix — but each glyph becomes hundreds of bytes of bezier data. A compressed WOFF2 subset covering the same characters is routinely smaller. And unlike paths, embedded-font SVGs keep real <text> nodes: screen readers, search engines, translation tools, and language models can all read and act on your content.