Sponsored by Monotype Imaging and Fonts.com,
the Web Fonts plugin provides an administrative interface for browsing and applying web fonts from a variety of sources. The plugin
includes support for web fonts from the Fonts.com web fonts collection out of the box.
In addition, support for Google Web Fonts has been added
in Version 1.1.0. You can now browse and enable any of the many open web fonts available from Google and then add them to your
stylesheet the same way you do with Fonts.com web fonts. Other web font providers will be added in the future via plugins.
If you run into issues with the plugin, please open a support topic on the WordPress.org
Its easy to get started with the Web Fonts plugin. You can install the plugin by either searching for it
in the WordPress plugin installer or, if you download Web Fonts manually, uploading it to
Activate Web Fonts in the
Plugins admin panel using the activate link. After doing so, you’ll be able to
access the Web Fonts settings interface to manage your stylesheet or browse fonts by supported providers.
The first thing you should do is set up your Fonts.com web fonts account by visiting the Fonts.com submenu
under the Web Fonts top level menu item in your administrative sidebar. If you have a Fonts.com account
already you can enter your information into the provided fields and it will be validated. If you do not have
an account you can quickly and easily create one from inside WordPress.
If you wish to use the Google Web Fonts integration you can do so by adding your API key and then browsing
the fonts available from Google.
- Do I need a Fonts.com web fonts account account to use the plugin?
No, you do not need a Fonts.com account to use the plugin. After installation, you’ll need to set
up your Fonts.com account in order to browse and enable fonts for your site. If you don’t have an
account, you can create one right in the WordPress administrative area.
- How do I enable Google Web Fonts? Where do I get my API key?
To use the Google Web Fonts integration
you’ll need to log in with your Google account and visit The Google API Console.
If you haven’t previously created a project you’ll be prompted to do so at that point.
After creating a project, you can click on “API Access” and then copy and paste the key you find
there into the field in the plugin. Make sure you’ve enabled the Web Fonts Developer API from the
list you’ll see when clicking on the “Services” tab on the left.
- What web font providers will be integrated in the future?
It is unknown which web font providers will be integrated in the future. Some of the providers being considered are:
The timeline for integration of the above depends heavily on usage of this plugin. If it becomes popular, more
web font providers will be integrated at an accelerated rate.
- Do I need to have any programming or theme modification knowledge to use this plugin?
No! The plugin is designed to automate the entire process for you. All you have to do is decide what
fonts you want on your site and what selectors they should be assigned to. After saving your stylesheet, the
plugin takes care of making sure the appropriate code appears in your theme.
This being said, knowledge of CSS selectors is strongly recommended as that is how you will specify
where your enabled fonts show up.
Contributors & Developers
“Web Fonts” is open source software. The following people have contributed to this plugin.Contributors
Translate “Web Fonts” into your language.
Interested in development?
Browse the code, check out the SVN repository, or subscribe to the development log by RSS.
- Fixed bug preventing users from disabling Google Web Fonts
- Fixed Google Web Fonts CSS declaration per
- Added web fonts icon designed and built by R. York Funston (http://www.ryarts.com/)
- Modified readme so text wouldn’t get cut off on the plugin page
- Modified readme to change plugin description
- Changed plugin description in plugin header
- Added support for Google Web Fonts
- Fixed silly syntax error that I didn’t check before uploading 1.0.3
- Fixed a bug where I was using the same PHP 5.3+ only feature I fixed in 1.0.2 again
- Fixed a bug where I was using a PHP 5.3+ only feature on accident
- Renamed a few screenshots so they would actually show up in the correct section
- Initial release version