The @font-faceCSSat-rule specifies a custom font with which to display text; the font can be loaded from either a remote server or a locally-installed font on the user's own computer.
Allows low-level control over OpenType or TrueType font variations, by specifying the four-letter axis names of the features to vary, along with their variation values.
Defines a multiplier for glyph outlines and metrics associated with this font. This makes it easier to harmonize the designs of various fonts when rendered at the same font size.
It's common to use both url() and local() together, so that the user's installed copy of the font is used if available, falling back to downloading a copy of the font if it's not found on the user's device.
If the local() function is provided, specifying a font name to look for on the user's device, and if the user agent finds a match, that local font is used. Otherwise, the font resource specified using the url() function is downloaded and used.
Browsers attempt to load resources in their list declaration order, so usually local() should be written before url(). Both functions are optional, so a rule block containing only one or more local() without url() is possible.
If more specific fonts with format() or tech() values are desired, these should be listed before versions that don't have these values, as the less specific variant would otherwise be tried and used first.
By allowing authors to provide their own fonts, @font-face makes it possible to design content without being limited to the so-called "web-safe" fonts (that is, the fonts that are so common that they're considered to be universally available). The ability to specify the name of a locally-installed font to look for and use makes it possible to customize the font beyond the basics while making it possible to do so without relying on an internet connection.
Note:
Fallback strategies for loading fonts on older browsers are described in the src descriptor page.
The @font-face at-rule may be used not only at the top level of a CSS, but also inside any CSS conditional-group at-rule.
Web fonts are subject to the same domain restriction (font files must be on the same domain as the page using them), unless HTTP access controls are used to relax this restriction.
@font-face cannot be declared within a CSS selector. For example, the following will not work:
css
.className{@font-face{font-family:"MyHelvetica";src:local("Helvetica Neue Bold"),local("HelveticaNeue-Bold"),url("MgOpenModernaBold.ttf");font-weight: bold;}}
This example specifies a downloadable font to use, applying it to the entire body of the document:
html
<body>
This is Bitstream Vera Serif Bold.
</body>
css
@font-face{font-family:"Bitstream Vera Serif Bold";src:url("https://mdn.github.io/shared-assets/fonts/VeraSeBd.ttf");}body{font-family:"Bitstream Vera Serif Bold", serif;}
In this example, the user's local copy of "Helvetica Neue Bold" is used; if the user does not have that font installed (both the full font name and the Postscript name are tried), then the downloadable font named "MgOpenModernaBold.ttf" is used instead:
css
@font-face{font-family:"MyHelvetica";src:local("Helvetica Neue Bold"),local("HelveticaNeue-Bold"),url("MgOpenModernaBold.ttf");font-weight: bold;}
Tip: you can click/tap on a cell for more information.
Full support
Full support
Partial support
Partial support
No support
No support
Non-standard. Check cross-browser support before using.
Deprecated. Not for use in new websites.
See implementation notes.
Requires a vendor prefix or different name for use.
Has more compatibility info.
The compatibility table on this page is generated from structured data. If you'd like to contribute to the data, please check out https://github.com/mdn/browser-compat-data and send us a pull request.