Help & Support


What is a CDN?

Content Delivery Networks (CDN) are used all over the Internet. In short they are Internet servers that deliver all sorts of stuff to browsers and mobile devices faster and with more reliability than just using your own server. If you want to geek out read what Wikipedia says about them.


Why should I use a CDN?

CDNs can help with basic page and asset loading performance, which provides a more responsive and quick experience for your users. Two things are important when we talk about basic performance: the number of requests and the size of the response. There are basically three ways the CDN improve those biggest pain-points in content delivery.

  1. By having a faster server (latency, concurrency)
  2. By making sure it’s always available (scaling/distributing load)
  3. By moving the server physically closer to the browser

How do I use Font Awesome via CDN on my site?

You'll need to do just a few things in order to get started using Font Awesome via CDN on your project:

  1. Create an Embed Code

    Get a unique embed code that's made just for you.

  2. Add that Embed Code to Your Project

    Once you have a code, place it in your project's HTML files. You'll want to add this within the <head> of each template or page that you want to use Font Awesome on.

  3. Drop any of the 600+ icons in

    Find and place the right icon for the job in your markup. Check out the Font Awesome icons and examples to learn how.

Here's an abbreviated example of a page that's using Font Awesome CDN

<!doctype html>
<html>
  <head>
    ...
    <!-- your embed code -->
    <script src="https://use.fontawesome.com/your-embed-code.js"></script> <!-- TODO: Place your Font Awesome embed code  -->
    ...
  </head>
  <body>
    ...
    <!-- reference any icon you'd like -->
    <i class="fa fa-flag"></i>
    ...
  </body>
</html>
Want to use Font Awesome without Font Awesome CDN?

What do you mean by Auto Accessibility?

Icons are symbols that can convey a ton of information and really help people comprehend directions, signs, and interfaces. Its important that we create and use them so that they can reach the largest amount of people possible. That means making sure our icons play well with technology that helps people navigate and use apps and sites.

According to this article, there are a potentially surprising number of folks with sight and hearing impairments: Blindness, low vision, and visual impairment represent 8.4% of the total world population and disabling hearing loss represents 5.3% of the total world population.

We've built-in ways to help technology that supports impairments, like screen readers, either ignore or better understand the Font Awesome icons you're using. In short, we try to help with the following cases:

  1. Using Icons are Decorative Elements

    If you're using an icon to add some extra decoration or branding, it does not need to be announced to users as they are navigating your site or app aurally. Additionally, if you're using an icon to visually re-emphasize or add styling to content already present in your HTML, it does not need to be repeated to an assistive technology-using user.

  2. Using Icons for Semantic or Interactive Purposes

    If you're using an icon to convey meaning, ensure that this meaning is also conveyed to users who may be interacting with your UI using different methods or tools by providing text-based alternatives. This goes for content you're abbreviating via icons (e.g. shopping cart status, number of unread messages, etc.) as well as interactive controls (e.g. buttons, form elements, toggles, etc.).

If enabled as a feature in your embed code, Font Awesome CDN will try to identify the scenarios above in your UI as well as provide the modern and proper syntax assistive technologies recognize. For icons that have semantic or interactive meaning, this means you'll need to provide a proper text alternative to be used. Here's how:

For icons that are decorative

Font Awesome CDN's auto accessibility feature will make sure it is ignored by assistive technology. There's nothing extra you need to on top of how you would usually reference an icon.

Here's what your markup should be.

<button type="submit">
  <i class="fa fa-envelope"></i> Email Us!
</button>

And Font Awesome CDN changes that to the following.

<button type="submit">
  <i class="fa fa-envelope" aria-hidden=”true”></i> Email Us!
</button>

For icons that have semantic or interative meaning

Font Awesome CDN's auto accessibility feature will try to apply a fallback alternative for the icon based on any any alternatives and configuration you set on the icon.

Here's what your markup should be.

<button type="submit">
  <i class="fa fa-arrow-right" title="Submit My Tax Return"></i>
</button>

And Font Awesome CDN changes that to the following.

<button type="submit">
  <i class="fa fa-arrow-right" title="Submit My Tax Return"></i>
  <span class="sr-only">Submit My Tax Return</span>
</button>
More on Font Awesome & Accessibility

What are aynchronously loading icons?

When a web page loads, there are often many requests for files needed to render the interface and content. This can create a line of assets and information waiting to be understood and then presented by the browser. Some of the requests, such as initial or very important content and basic layout styling, may be needed right away. Others, such as icons, typefaces, and images, may not be as critical to load for users first. To help speed up the loading of pages, its wise to delegate the latter to loading after the critical set.

If enabled as a feature in your embed code, Font Awesome CDN will move the loading of Font Awesome's icons and supporting styling from the critical request order and load them on a parallel track when the browser is available to.


How does icon stats reporting work?

Heads Up!

This feature is still being developed and the information here as well as how well the feature works both are still moving targets for the Font Awesome team.

Your embed code can report information back too! Icon stats reporting let you see exactly what icons you're using. If enabled as a feature in your embed code, Font Awesome CDN, with a bit of your help, will keep track of icons you're using for specific domains you specify.

Here's how to set it up and get stats on your icons:

  1. Enable icon stats reporting for an embed code (JS-based codes are required for this)
  2. Specify which domains we should track icons on. We don't want to slow down the performance of your production site without your explicit request. Good candidates are local dev environments, and staging or preview servers. We've prepopulated our favorites for you to start with.
  3. Let our tracking follow you around that domain. Navigate to one or many of the domains you provided and browse around all of the different pages, states, and views of your project. Our tracking will pick up any Font Awesome icons used on pages and report them back to your embed code's stats.

You may reset your stats at any point - this will result in all previous information about your icon use being deleted. We find this handy when you want to do a clean sweep through sites or projects you've redesigned.

Note: Icon stats reporting only monitors your UI's front end assets and focuses on icons. We do not track any other descriptive types of information, nor do we mine for any personal or private data outside of the terms of our Privacy Policy.


What does it mean to upgrade an embed code?

A Font Awesome CDN embed code can be easily upgraded into a Fort Awesome kit, where you can use Font Awesome icons while mixing in your own custom icons or icons from many other sets. Fort Awesome makes it easy to manage these curated sets of icons and using them in your projects is as easy as using Font Awesome. Fort Awesome can also manage your project's typefaces and comes with awesome features you love about Font Awesome CDN, including asynchronous icons, and auto-accessibility.

When you upgrade, there are a few things to note:

  1. Your upgraded Font Awesome CDN code will continue to work. Any sites or apps using that code will continue to display Font Awesome icons.
  2. The Fort Awesome kit you've created from an embed code will not be made live until you complete a couple of steps in Fort Awesome


My icons aren't rendering correctly

We're not able to provide direct one-on-one support to all of our customers all of the time, but if you're having trouble, here are some places to start.

  1. Make sure you've set things up properly

    Double-check and follow the steps above to make sure the basics are covered.

  2. Make sure you're not using another version or copy of Font Awesome

    If you're using another copy of Font Awesome, via download or Fort Awesome, in your site or app, this can cause conflicts. Make sure the CDN Embed code is the only way you're using Font Awesome.

  3. Double-check your icon markup

    Make sure that you've followed Font Awesome's conventions and examples properly.

  4. Double-check your CSS

    Make sure that any CSS you are writing does not conflict or supersede the supporting CSS that Font Awesome is served with.

  5. Ask the community

    Font Awesome has a huge following and community. You can look at the open issues Check out the existing questions tagged as Font Awesome over on Stack Overflow. Other folks might have had the same question you've had. Can't find the answer to your question on Stack Overflow? Ask a new question.

  6. Still perplexed?

    If you still can't resolve things or thing its a bug on our end? You can report a new bug or issue.


Font Awesome isn't loading on my pages

Again, We're not able to provide direct one-on-one support to all of our customers all of the time, but if you're having trouble, here are some places to start.

  1. Make sure you've set things up properly

    Double-check and follow the steps above to make sure the basics are covered.

  2. Triple-check that you've referenced your embed code

    Seriously, make sure you that are referencing your embed code within your HTML's <head>

  3. Ask the community

    Font Awesome has a huge following and community. You can look at the open issues Check out the existing questions tagged as Font Awesome over on Stack Overflow. Other folks might have had the same question you've had. Can't find the answer to your question on Stack Overflow? Ask a new question.

  4. Still have a boggle?

    If you still can't resolve things or thing its a bug on our end? You can report a new bug or issue.



Questions & Feedback

Font Awesome CDN is still really new. We're still squashing a few bugs and polishing things. If you notice something that seems off or is causing trouble, let us know by reporting a bug. Got a question, specific idea, or need something? Feel free to get in touch with the Font Awesome Team.

Contact us!