Font Awesome


The official way to use Font Awesome Free or Pro icons on your site, brought to you by the Font Awesome team.

New Plugin, Replacing an Old Plugin

This is a new, completely re-written plugin, tested with the latest WordPress and Font Awesome versions. It replaces the older plugin formerly occupying this space in the WordPress plugins directory, which was no longer being maintained. Many thanks to Rachel Baker and the team behind the former plugin for getting the original plugin started and allowing us to carry it forward.


Our official plugin lets you use Font Awesome the way you want:

  • Use Pro or Free icons.
  • Leverage the latest release or a specific version of our icons.
  • Choose the tech, either SVG or Web Font.
  • Take your pick of loading your icons from our classic Font Awesome CDN, or use Font Awesome kits – the easiest and most robust way to use our icons on the web.
  • And, if you haven’t had the chance to update your project in a long while, you can turn on automatic compatibility for Font Awesome Version 4.

But that’s not all… our official plugin can troubleshoot and help you resolve when multiple versions of Font Awesome are loading on your site from other plugins/themes and causing display or technical issues.


Install and enable the plugin
(See the Installation tab for details)

Add icons to your pages and posts
Once you’ve set up your plugin, you add icons to your pages and posts by using their names in shortcodes or HTML.

When you use shortcodes, you add the name of the icon and a prefix, where the prefix is the style of icon you want to use. Note that you don’t need to include the fa- part of the name. And if you don’t include any prefix, the style will default to Solid.

The shortcode for an icon looks like this:

[icon name="stroopwafel"]

[icon name="stroopwafel" prefix="fal"]

Or you can use basic HTML with standard Font Awesome syntax:

<i class="fas fa-stroopwafel"></i>

Using Pro Icons and Features
To enable Pro icons with the CDN, you will need to add your domain to the list allowed domains on your Font Awesome CDN Settings page. To configure a kit, get your API Token from your Font Awesome account page.

Troubleshooting with the Plugin
Font Awesome icons are popular, so lots of themes and plugins also load Font Awesome, and sometimes their version can conflict with yours. So we created a way to help you find and prevent those conflicting versions from affecting your icons: The Conflict Detection Scanner.

If the plugin seems to be set up correctly and your icons still aren’t loading and you’re not sure why, head over to the Troubleshoot tab, which has two parts:

  • Detect Conflicts with Other Versions of Font Awesome – which lets you start the conflict detection scanner to find versions of Font Awesome loading on your site.
  • Versions of Font Awesome Active on Your Site – which lists any other versions of Font Awesome being used on your site and lets you prevent conflicting versions from loading.

Get more information about using the scanner for troubleshooting on the WordPress page on Font Awesome.


The plugin is set to serve Font Awesome Free icons as a Web Font via the Font Awesome CDN by default. You can change the CDN settings right in the plugin. In the simplest case, no additional configuration is required.

Note: The plugin is not compatible on WordPress multisite at this time.

You can get more information about all the available settings and troubleshooting on the WordPress page on Font Awesome.

Upgrading from the Old Versions

If you used the old plugin or are still using Version 3 of Font Awesome, we’ve tried to smooth the upgrade path for you by keeping [icon] shortcode compatibility for Font Awesome 3 names used with the old plugin. But we plan to remove version 3 naming support from this plugin soon so don’t wait too long to update your code!

See Also

The README on GitHub which has details for WordPress site owners and developers.

The API docs for developers.


From the Plugins Directory in WordPress Admin

From the “Add Plugins” page in WordPress admin:

  1. Search the plugins directory by author: fontawesome

  2. Click “Install” on this plugin in the search results

  3. Click “Activate”

Installing a Zip Archive

  1. Click Download on this plugin’s directory entry to get the .zip file

  2. On the “Add Plugins” page in WordPress admin, click “Upload Plugin” and choose that .zip file

Access Font Awesome Plugin Settings

Once you activate the Font Awesome plugin, you will see a top-level menu item for Font Awesome in your WordPress admin area, or you can click “Settings” on the plugin’s entry on the Plugins page.


You can get more information about using the plugin, details for available settings, and answers to frequently asked questions on the WordPress page on Font Awesome.


I purchased FontAwesome PRO, but it would not work with my theme. I contacted tech support several times for assistance. At first they tried to help, but when their solutions didn't solve the problem, they quit responding. Furthermore, they refused to refund the $99 I had paid for PRO saying, "We don't give refunds for downloadable commercial software." Well, you have to download it to try it. And if it doesn't work, and their tech support can't provide a solution, it stands to reason that a refund is in order. I finally challenged the charge with my credit card company and got the refund, but it took a lot of time and effort on my part. I'm a website designer and have never had this type of issue with a plugin developer. Needless to say, I won't be buying the PRO version of FontAwesome for any future projects.
I operate multiple (double digits) sites and have tried a host of Font Awesome plugins - none of them works as effectively as this one, the official one. Very simple but it just does what it’s designed to do - many thanks ...
I have 2 sites that are almost identical running on the same server environment. On one site I'm able to enable the plugin and on the other I get this error: "The Font Awesome plugin caught a fatal error: Font Awesome could not be activated." It's maddening.
Font didnt work within the plugin it was linked to and then when I asked them about it, was told I wont help you unless you pay, read the instructions or ask the forum. Thats like me going into a shop and being told I will only answer your question if you give me money, but read the the tag info or ask another customer.
40 (az összes) vélemény olvasása

Közreműködők és fejlesztők

“Font Awesome” egy nyílt forráskódú szoftver. A bővítményhez a következő személyek járultak hozzá:


“Font Awesome” 11 nyelvre lett lefordítva. Köszönet a fordítóknak az áldozatos munkájukért!

“Font Awesome” fordítása a saját nyelvünkre.

Érdekeltek vagyunk a fejlesztésben?

Browse the code, check out the SVN repository, or subscribe to the development log by RSS.

Változási napló


  • FIX: plugin now handles kits with version “5.x” or “6.x”

  • FEATURE: shortcode supports attributes: style, role, title, aria-hidden,
    aria-label, aria-labelledby


  • Metadata about available Font Awesome releases is now stored as a normal option
    in the WordPress database, instead of as a transient. Thus, it does not expire
    and does not disappear if the transient cache is purged.

    This is in part to avoid the scenario where a request to the Font Awesome API
    server may be required to refresh metadata in response to a front end page load
    when that transient expires.

    Some site owners had occassionally experienced problems where a sudden burst of
    requests to the API server from many WordPress sites caused this plugin to fail
    when making a request with an error like ‘An unexpected response was received
    from the Font Awesome API server.’ This change means that it is significantly
    less likely that such a scenario will occur.
    (Additionally, changes have been made on the API server, also making it
    significantly less likely that this over-load failure will occur again.)

  • Developers: the refresh_releases() API method has been deprecated to discourage
    unnecessary blocking network requests to the API server.


  • optimize normal page loads by loading much less metadata from the database (GitHub #96)
  • move the Font Awesome settings link from the main admin nav menu back down under Settings, where it used to be
  • update the version of the conflict detection script to one that also detects conflicting kits
  • minor maintenance changes to keep JavaScript dependencies up to date
  • fix a bug involving the pseudo-elements setting when moving back and forth between using a kit and using CDN (GitHub #82)


  • developer-oriented update to support building themes that use this code as a composer package


  • another minor update with additional error logging


  • minor update with additional error logging


SECURITY: fixes a vulnerability in how API tokens were being stored, when configured to use a kit. All users of 4.0.0-rc15 or 4.0.0-rc16 should update immediately. Find more details and instructions for updating your API Token on the Font Awesome blog.

  • a minor bug in how network errors are handled


  • Fixes to the upgrade process


MAJOR UPDATE, some breaking changes for developers. Improves conflict detection, adds support for kits and internationalization.

  • Includes auto-upgrade logic so that most users can upgrade with no impact, except those that have “registered client” themes or plugins. Users who had previously enabled the “remove unregistered clients” option should verify that the auto-upgrade worked successfully – check that your icons are appearing correctly. If not, run the Conflict Scanner from the Troubleshoot tab.
  • New conflict detection and resolution: The new conflict detection scanner can be enabled to more precisely discover conflicting versions of Font Awesome and provides more granular conflict resolution.
  • Expanded error handling with detailed reports in the web console for more advanced diagnostics.
  • Adds support for Kits.
  • Adds comprehensive internationalization in both PHP and JavaScript.
  • New design of the admin UI.
  • Developers: Significant changes to the way the settings are handled internally: Font Awesome will always load in the way the WordPress admin chooses. Registered themes or plugins may register preferences (which are displayed to the admin), but the site admin will determine the configuration.
  • Developers: Registered client plugins and themes need to be updated before they will work as expected.
  • Developers: The PHP API contains significant changes. See the GitHub README for an overview and the PHP API docs for details. This release is intended as a final API-changing release before stabilizing the API at 4.0.0. Once 4.0.0 is released, it will follow semantic versioning best practices.


  • Improve diagnostic output for unhandled errors.


  • Bug fix: Fix loading of admin page assets when removal of unregistered clients is enabled. This bug has been
    hiding under a rock for a while. rc11 turned over the rock, and this bug scurried out.


  • Bug fix: enqueue Font Awesome assets in admin and login areas, not just in the front end


  • Attempt to fix a problem where the admin settings is sometimes being confused by unexpected output from the WordPress
    server. This condition has been reported when certain other plugins are active, and (possibly) when PHP output
    buffering works differently than this plugin expects.


  • Enhance Font Awesome version 4 compatibility: add shimming of the version 4 font-family to enable version 4
    icons defined as pseudo-elements to be rendered via the version of Font Awesome 5 loaded by this plugin.

  • Add warnings to the admin UI to indicate that using svg and pseudo-elements may result in slow performance,
    and that svg with pseudo-elements and version 4 compatibility is not supported at all.


  • Remove dependence on third party libraries, eliminating a class of potential conflicts with other plugins.

  • Breaking changes to the API used by theme and plugin developers (no breaking changes for WordPress site owners).
    See commit log


  • Fix detection and removal of unregistered clients by changing the internal resource name this plugin uses to enqueue its resource.
    Change it to something unlikely to be used by other themes or plugins.


  • Fix error when updating options on admin page: handle null releaseProviderStatus in cases where the release provider
    does not have to make a network request to update release metadata.


  • Remove tilde character from JavaScript filenames to avoid violating some URL security rules


  • Cache releases data in the WordPress database to reduce the number of server-side network requests.

  • Ensure that releases data are always loaded fresh from when loading the admin
    settings page so site owners can see when new versions are available.

  • Add more specific error message on admin dashboard in the event that the WordPress server is not able to
    reach in order to get an initial set of available releases data.


  • Add missing v3 shim file


  • Fix handling of v3 deprecation warnings in admin settings page


  • Add admin settings page
  • Lots of back end code changes to support theme and plugin developers
    • Package plugin as a composer dependency
    • API Changes
    • Comprehensive API documentation for developers
  • Cache load specification unless client requirements change
  • Handle changing configurations as new plugins or themes are activated, de-activated or updated
  • Lock working load specifications and only rebuild when new requirements are conflict-free
  • Load Font Awesome release version metadata from the releases API


  • Last stable version of the old plugin