Host Yourself - Web Fonts
If you like control, you can host Font Awesome yourself, and you can choose to use Web Fonts + CSS described below or SVG + JS to get icons into your projects.
We’ll cover the basics of getting set up with Web Fonts and how you can use specific Font Awesome icon styles.
Set-Up with Web Fonts
Inside the Font Awesome Download or package, you’ll find the files you need. The /css
folder contains the core styling and utilities for all of Font Awesome’s families (Classic, Sharp, and Brands) as well as style options (Solid, Regular, Light, Duotone, and Thin). The /webfonts
folder contains all of the typeface files that the CSS files depend on.
Which Files and Folders | What’s in there |
---|---|
/webfonts | Icons as Web Fonts to be used with CSS |
/css | CSS files for using Web Fonts |
Add Font Awesome Files to Your Project
Copy both the /webfonts
and the /css
folders into your project’s static assets directory (or wherever you prefer to keep front-end assets or vendor stuff). Be sure to include the core styling file - /css/fontawesome.css
- as well as the CSS files for any individual styles you want to use, and you can remove any .css
and web font files you don’t plan on using.
Copy webfonts and CSS assets into one of your project directories
Here’s a handy table that shows which files go with which styles:
Icon Style | Availability | Web Font Filename | CSS Filename |
---|---|---|---|
Brands | Free | fa-brands-400.* | brands.css |
Solid | Free | fa-solid-900.* | solid.css |
Regular | Pro only | fa-regular-400.* | regular.css |
Light | Pro only | fa-light-300.* | light.css |
Thin | Pro only | fa-thin-100.* | thin.css |
Duotone Solid | Pro only | fa-duotone-900.* | duotone.css |
Duotone Regular | Pro only | fa-duotone-regular-400.* | duotone-regular.css |
Duotone Light | Pro only | fa-duotone-light-300.* | duotone-light.css |
Duotone Thin | Pro only | fa-duotone-thin-100.* | duotone-thin.css |
Sharp Solid | Pro only | fa-sharp-solid-900.* | sharp-solid.css |
Sharp Regular | Pro only | fa-sharp-regular-400.* | sharp-regular.css |
Sharp Light | Pro only | fa-sharp-light-300.* | sharp-light.css |
Sharp Thin | Pro only | fa-sharp-thin-100.* | sharp-thin.css |
Sharp Duotone Solid | Pro only | fa-sharp-duotone-solid-900.* | sharp-duotone-solid.css |
Sharp Duotone Regular | Pro only | fa-sharp-duotone-regular-400.* | sharp-duotone-regular.css |
Sharp Duotone Light | Pro only | fa-sharp-duotone-light-300.* | sharp-duotone-light.css |
Sharp Duotone Thin | Pro only | fa-sharp-duotone-thin-100.* | sharp-duotone-thin.css |
Reference Font Awesome in Your Project
Link the core fontawesome.css
file along with the CSS files for whichever styles you want to use into the <head>
of each template or page that you plan to add icons to. Make sure the paths correctly point to where you placed the files!
Here’s an example html page with the file links in the <head>
and a couple of icons in the content.
Just this once, we recommend letting things go to your head.
Yuss! You’re Ready to Add Icons
Like Anakin said, it’s woooorking! All of our icons are now ready to do your project’s bidding. Learn how to add them to your project and then use their power to bring order and style to your UI!
Alternate Install: Using all.css
In the /css
folder, you may have noticed a file named all.css
. This file contains the core styling and utilities PLUS all of the icons in all the Classic styles in Font Awesome. (The Sharp family is not included in the all.css
file - you’ll need to add the Sharp .css
files separately.)
It’s a handy file if you’ll be using all the icon styles or testing out different styles as you develop your project. But if you’re using just a couple of styles, we don’t recommend it for production sites since loading all of the icons and files isn’t great for performance.
If you’d like to use the all.css
, just copy the /webfonts
folder and the /css/all.css
file into your project’s assets directory where other images and CSS are stored. You’ll want to keep them in the same directory.
Then, add a link to the /your-path-to-fontawesome/css/all.css
file into the <head>
of each template or page where you want to use Font Awesome.
Hosting Your Own Downloaded Kit
If you’d rather do the heavy lifting, you can download any Pro Kit and host it yourself! To download your Kit, make sure it’s a Pro with the version in Settings is set to “Latest 6.x” or at least 6.4. Then from the Set Up tab in your Kit, you’ll see the options for downloading.
Custom Icons in Downloaded Kits
If you have custom icons in your Kit, they will be included in your Kit download. You’ll find these additional files included in the download zip:
Path to the files | What the files do |
---|---|
/css/custom-icons.css | Handles the display of custom icons with Web Fonts |
/js/custom-icons.js /js/custom-icons.min.js | Handles the display of custom icons with SVG+JS |
/sprites/custom-icons.svg | All your custom icons in one SVG sprite |
/svgs/custom-icons/ | Folder containing all your custom icons as SVGs |
/webfonts/custom-icons.woff /webfonts/custom-icons.ttf | Custom icon font in WOFF2 and TTF formats |
/scss/custom-icons.scss and /less/custom-icons.less | Sass (SCSS) and Less Preprocessor partials that handle the display of custom icons with Web Fonts |
These files will work the same as the Font Awesome files and assets. And if you are using all.js
or all.css
, your custom icons will be included in those, though for performance reasons, we recommend adding just the files you are using in your project.
Here’s an example project using Sharp Solid and custom icons from a downloaded Kit:
Using Kit custom icons is easy peasy.
Older Version Compatibility
If your project is using an older version of Font Awesome, we’ve got you covered with backward compatibility. That means you won’t have to update any icon names in your project - we’ll translate any older version icon names, style syntax, and CSS pseudo-element icon references automatically. Here’s how to enable that support for the previous version you need to support:
Version 5 Compatibility
If you’re hosting yourself and using only certain styles, add the css/v5-font-face.css
to the files linked in your html head
. (The all.css
file includes these utilities by default so you won’t need to do anything.)
Here’s an example:
Version 4 Compatibility
If your project contains Font Awesome 4 icon references, add the css/v4-font-face.css
to the files linked in your html head
. Our CSS will then translate any Font Awesome 4 icon names and CSS pseudo-elements references to Version 6 automatically.
If you’re using all.css
, you’ll need to add the v4-shims.js
file, which will map V4 icon names to icons in the latest version of Font Awesome, like this:
If you need more help upgrading an existing project to a newer version of Font Awesome, check out our upgrading guides.