@mcrumley's answer is correct, but for those of you who can't figure it out and/or are afraid of the command-line, I have an alternate method.
I just Googled your question, and found http://base64converter.com/ which can convert/decode (and encode) any base64 file back to its original format. I'd used it to encode and decode base64 images in this past, but this was my first attempt with a font. As a test I plugged in the embedded base64 font info I found in a random webpage's css file. You don't want the entire entry, leave off the css info or the conversion will fail.
(For example) delete this info preceding the base64:
@font-face{font-family:"Example";src:url(data:application/x-font-woff;base64,
Delete this from the end:
;font-weight:400;font-style:normal}
You'll be left with the base64 encoded data, paste that in the "Input" field, select "Decode" for the output and press the button. It will create a file called download.bin
: click it to download it. Then change the file extension from bin
to woff
(your font file-type might be different, but it will say in the css). I was able to open the .woff file and the conversion worked perfectly; not only were all the outlines saved, but so were the glyph names, the opentype features, kerning, and everything.
Of course, like any method used to rip webfonts, the number of glyphs outputted will likely be limited to those used on the page in question.
If woff
files aren't what you need, there are plenty of online tools to convert woff
to the format of your choice. Or if you need an offline tool, check out this question I asked and the answers I received:
Modify Python Script to Batch Convert all "WOFF" Files in Directory