CSS selectors

CSS selectors tell the browser where to apply the web fonts you're using, as well as the weight and style of the font to use for the text.

The Web Projects page lists the CSS font-family name, numerical weight, and font style for each font in the project. Once you’ve included the embed code in your document, use these font-family names in the CSS to apply the fonts to the text. For example:

If a user’s browser doesn’t support web fonts or they don't load for any reason, the fallback fonts in the CSS stack will be used instead.

The font stack should contain at least one fallback font that is uniformly available across platforms (like Georgia or Arial), followed by a generic font-family name (like serif or sans-serif). If the browser can’t find the first font, then it will try the second font, and so on.

You can specify font-weights other than "normal" and "bold" by using numeric font-weight values in the CSS. The numeric values most frequently correspond to these weights:

• 100 = thin
• 200 = extra-light
• 300 = light
• 400 = normal, book
• 500 = medium
• 600 = demi-bold
• 700 = bold
• 800 = heavy
• 900 = black

You can find the numeric values for all of the fonts in your project on the Web Projects page.

For example, use this CSS to apply the 100 weight of a font to the h1 element:

Internet Explorer 8 loads a maximum of four weights per family, and using two closely-related weights (e.g., 400 and 500) may result in only one weight loading correctly. Adobe Fonts serves variation-specific font-family names to those versions of the browser to manage both of these bugs.

The variation-specific name should be added at the beginning of a font-family stack as needed, before the main family name:

The names consist of the normal font-family name, followed by a dash, followed by a font variation description (or FVD). For example, the variation-specific name for proxima-nova that contains the normal 600 weight font is proxima-nova-n6.

The variation-specific name will be undefined in browsers that don't have these issues, so they will use the full family name that comes second in the stack.

Most users won't need to use these additional font-family names. You'll only need to add them if you see problems with fonts displaying correctly in Internet Explorer 8 specifically.