Want to manage and host Font Awesome assets yourself? You can download, customize, and use the icons and default styling manually. Both CSS and CSS Preprocessor (Sass and Less) formats are included.
font-awesome
directory into your project.<head>
of your html, reference the location to your font-awesome.min.css.
<link rel="stylesheet" href="path/to/font-awesome/css/font-awesome.min.css">
Use this method to customize Font Awesome using Less or Sass.
font-awesome/
directory into your project.font-awesome/less/variables.less
or font-awesome/scss/_variables.scss
and edit the @fa-font-path
or $fa-font-path
variable to point to your font directory.
@fa-font-path: "../font";
The font path is relative from your compiled CSS directory.
Use the Official Font Awesome Less Ruby Gem to easily get Font Awesome Less into a Rails project. Generously maintained by @supercodepoet.
gem 'font-awesome-less'
$ bundle
$ gem install font-awesome-less
If you use Rails, add this to your e.g. application.less
:
@import "font-awesome-sprockets";
@import "font-awesome";
Use the Official Font Awesome Sass Ruby Gem to easily get Font Awesome Sass into a Rails or Compass project. Generously maintained by @supercodepoet.
gem 'font-awesome-sass'
$ bundle
$ gem install font-awesome-sass
If you use Rails, add this to your e.g. application.scss
:
@import "font-awesome-sprockets";
@import "font-awesome";
In order to provide the best possible experience to old and buggy browsers, Font Awesome uses CSS browser hacks in several places to target special CSS to certain browser versions in order to work around bugs in the browsers themselves. These hacks understandably cause CSS validators to complain that they are invalid. In a couple places, we also use bleeding-edge CSS features that aren't yet fully standardized, but these are used purely for progressive enhancement.
These validation warnings don't matter in practice since the non-hacky portion of our CSS does fully validate and the hacky portions don't interfere with the proper functioning of the non-hacky portion, hence why we deliberately ignore these particular warnings.
Getting started - Validators by Bootstrap Team is licensed under CC BY 3.0
IE8 has some issues with @font-face
when combined with :before
.
Font Awesome uses that combination. If a page is cached, and loaded without the mouse over the window
(i.e. hit the refresh button or load something in an iframe) then the page gets rendered before the font loads.
Hovering over the page (body) will show some of the icons and hovering over the remaining icons will show those as well.
See issue #954 for details.
Getting started - Internet Explorer 8 and @font-face by Bootstrap Team is licensed under CC BY 3.0
If you need IE7 support, you have my condolences. Really. Font Awesome doesn't support IE7, but an older version does. You'll need to check out the 3.2.1 instructions for using IE7. Then go complain to whoever decided your project needs IE7 support.
If you're having trouble with Font Awesome, make sure to check out the troubleshooting wiki page. Generously maintained by @gtagliala.