1. Code
  2. Designing

Quick Tip: How to Work with @Font-face

Scroll to top
Read Time: 2 min

Due to the fact that @font-face can be a bit overly complicated, it hasn't caught on quite as much as it should. Once you start reading about licensing, different font formats, browser consistencies, it can potentially become more trouble than it's worth.

But - in five minutes, I'll try to simplify the process of working with custom fonts as much as I possibly can. Services like Font Squirrel help to make the task a cinch!

Final CSS

Notice how we're referencing both an .eot and .ttf font? This is because, of course, Internet Explorer only uses its own format, that has yet to truly catch on. As such, we must first import that .eot file, and then move on to the different formats for Firefox, Safari, etc. It's essential that you load the .eot version first.

Next, we search for the font on the user's computer by using the "local" attribute. If it's unfound, only then do we pass a url that will load the font.

Why Doesn't IE Try to Load the TTF Fonts?

This was definitely a concern. If Explorer can't work with the truetype format, we don't want to waste time trying to download the font. Luckily, because of all those local attributes, and the commas, IE won't understand any of it. As such, it will simply skip the line all together, thus, only utilizing the .eot version.

Did you find this post useful?
Want a weekly email summary?
Subscribe below and we’ll send you a weekly email summary of all new Code tutorials. Never miss out on learning about the next big thing.
Looking for something to help kick start your next project?
Envato Market has a range of items for sale to help get you started.