Base 64 encoded fonts2021-09-14
I struggle referencing fonts in a CSS file. I struggle with getting fonts setup in general.
Sometimes your referencing the path to where your font is locally, but that doesn't quite match where it would be on your server (for example if your CSS file is being used on multiple projects hosted in different places, or just on different domains).
I'm generally quite lazy about this stuff and just reach for google fonts and do what they tell me to do. This isn't always an option, you'll also dependent on a external ressource that might not be available somewhere (google stuff isnt easily available in China for example).
This is the problem I faced at work. Multiple projects referencing the same CSS files and the fonts got lost somewhere for 2 out of 3 projects.
It turns out you can change your font file into a Data URLs by base 64 encoding it.
That's a lot of words. Let's try to break it down a bit.
Here's what MDN has to say:
Data URLs, URLs prefixed with the data: scheme, allow content creators to embed small files inline in documents.
So that means we're actually embedding the font in the CSS file. We can do that by encoding the file. we can do this by using the
base64 command line tool (on unix systems). Browsers can encode and decode base 64, that's why we're using this format.
base64 -w 0 font.woff2 > font.base64
-w 0 argument is to remove whitespace and linebreaks.
font.base64 file there'll be a massive string of gibberish. We can copy/paste that gibberish into our css file where we define our font:
font-family: 'My Cool Font';
src: url(data:application/font-woff2;base64,<this is where the gibberish lives>) format('woff2');
And that's it!
Zach's deep dive and demos
CSS tricks article
Zell Liew and his thoughts