Playing with Google Font API and WordPress

With new webdesign trends, standard fonts such as Arial, Times and Verdana aren’t enough to give our blog/website the loon&feel we want.

That’s why today we’ll discover the magic of Google Font API.

The Google Font API lets you include in your pages high-quality web fonts provided by the Google Font Directory.

This means you can use custom fonts in your design, and they are hosted and served by Google.

That’s nothing new, since services like Typekit are already on the wild for quite a while, and scripts like cufòn already enhance the beauty of most premium templates.

But unlike cufòn, texts rendered with the Google Font API are selectable, and there isn’t any copyright issue, and unlike Typekit, Google Font API is free.

So let me show you the simplest example…

Let’s take the CSS of this blog post titles:

and change the first line to

and then just add somewhere between <head> and </head> (normally in the header.php file located in your theme directory)

and… see the difference:

Nice, elegant and without any important downside, if you can bare with a small number of fonts (but don’t forget we are talking about Google, so expect the number to grow fast) and the lack of iPhone/iPad compatibility (hey… shouldn’t CSS heroes design a i/whatever specific layout anyway?)

  • That’s a great way to standardize the use of fonts online.

    Some sites look funny for me in Linux since Times New Roman is a proprietary format, so font defaults to something else (and usually doesn’t show up right, so it gets cut off or bleeds over to a new row in some instances when using manually set width).

    However, if people are able to link to the font on Google code, they ensure that it will show up regardless if you have that font installed or not, and if enough websites link directly to the Google code fonts, they will be cached in the browser.

    There were some suspicions on the Kirupa forums who argued that because of the amount of time it takes to design one font, people will be reluctant to release it for free; unlike Wikipedia articles which take relatively little effort to write and publish.

    However, as you said, it’s Google, and if the users won’t contribute enough (which I still feel they will), Google will find a way to increase their repertoire of fonts.

  • I think I may have found a hack to stop the aliasing (jagged edges) on Windows machines. It only works in WebKit though, so I don’t know how useful it is.

    Check it out here:

  • uint

    I love google! especially the upcoming “App Store”!.Just take a look here:

    and here:

    Goodbye Mochi:-)

  • Thanks Man,

    This is awesome. I’m definitely going to have to look at using this feature in my blog posts ;)

  • Pingback: Using Google Font API - Tony Lea()

  • Pingback: defensive netball zone()

  • Lorenzo

    it’s also can be used on flash?

  • Google just launched a nice preview function for the Font API that makes it even easier to use the API.

    See more here:

  • Naushad

    Thanks a lot for sharing this..its the Best Solution for My Websites and My Clients Websites..

  • What I don’t understand is the direction. They will be for free or paid as on TypeKit. We can see on Google Fonts Webpage that they are partners with TypeKit.

  • Tom

    If you are WordPress user you can use Ultimate Google Fonts plugin for WordPress with beqautiful CSS text effect tips

  • wow…great.thanks for your sharing,buddy :D