The Google Fonts service has been immensely popular with web designers ever since it first launched in May of 2010. And for good reason. There are no accounts to sign up for and no monthly fees like there are with other web font services. Just add a single line of code to your website and you have at your disposal a huge selection of free fonts that display beautifully on screen.
But all of this begs the question: why is Google in the fonts game? What do they have to gain by hosting fonts for millions of websites for free? Is Google in this for the long haul or will Google Fonts eventually end up in the dreaded Google Graveyard?
Google Fonts 2010-??
Will Google Fonts end up in the Google Graveyard?
What’s in it for Google?
It can’t be cheap to serve fonts on this kind of scale. To date there have been over 2.6 trillion pageviews using Google Fonts. Sure, the fonts are oftentimes cached in the user’s browser but that is still a lot of requests and a lot of data being transferred. A trillion is a big number, even for a company like Google.
Font views counter
2.6 trillion pageviews and counting.
I’ve heard people compare Google Fonts to other Google products such as YouTube and Google Maps—the cost of serving fonts is nothing compared to the cost of serving large image and video files to hundreds of millions of people. However, there is a huge difference here. Both YouTube and Google Maps are monetized through advertising. I really can’t fathom any way Google could use that type of monetization strategy with Google Fonts.
And it’s not just the server costs. Google must surely devote engineers to maintaining this project. Every resource they devote to Google Fonts takes away from other potentially more profitable areas of their business.
Why Did Google Start Google Fonts?
I’ve heard several reasons as to why Google started their fonts service in the first place. Google thinks differently than other companies so sometimes it’s hard to really know what their true intentions are. But here are the most compelling explanations I’ve come across.
Reason # 1: Using Text Instead of Images Improves Search
Back when I first started doing web design professionally in 2001, it was common to use image files instead of HTML text on websites. Headers, navigation and buttons were almost always graphics created in Photoshop. This slowly became less common as the years went by but really started to die out once web fonts came on to the scene around 2009-2010 (although Apple still uses quite a bit of images for text on their site).
An example of Apple using images instead of text
An example of Apple using images instead of text.
The use of images in place of text is obviously bad for many reasons. Requiring a designer to open up Photoshop in order to tweak the copy on your site isn’t an ideal workflow. But for Google this is especially bad because they can’t index content if it’s inside an image.
Search is the bread and butter of Google. Improving search will significantly improve their core product. And the better their product is, the more people will search on Google and click on their AdWords ads. This seems like a pretty clear way for Google to increase their revenue.
However, the web was already heading in this “don’t use images for text” direction and although I’m sure Google Fonts played a role in speeding up that process, I feel like this goal has already been achieved.
Even if Google Fonts went away today, I still couldn’t imagine web designers switching back to using images in place of text as it’s now considered a terrible practice in modern web design. CSS3 can now accomplish text effects that used to require Photoshop and with high-density retina displays becoming common, the ability for text to scale is more important than ever.
So therefore I can’t really see this reason as a driving factor for Google continuing the service going forward. Images are no longer commonly used in place of text and that won’t change with or without Google Fonts.
Reason #2: The Caching of Google Fonts Improves Other Google Products
Google uses Google Fonts in many of their own products. Their redesigned product pages have been using Open Sans and more recently Roboto. If a user visits another site that uses Open Sans and then visits a Google site that uses Open Sans, the font files will already be cached on their system so the site will load more quickly, resulting in a better user experience.
The key here is that if sites are using the Google Fonts API, it will eliminate repeated downloads of the same font files. If a user visited 10 different sites that were self-hosting Open Sans, the font files would be downloaded 10 different times. However, if the 10 sites were using the Google Fonts API to embed Open Sans, then it would only need to be downloaded once. As more sites use Google Fonts, this cross-site caching will significantly reduce download times, not just on Google products, but on all sites.
Reason #3: Google Just Wants Your Data
On a typography forum I frequent, there seems to be the common sentiment that Google Fonts was created with nefarious purposes in mind. And given Google’s somewhat sketchy history of adhering to their “don’t be evil” policy, it’s hard to blame them. Google is a company built around collecting data. Their goal is to organize all of the world’s information. And that includes information from you. Having millions of websites using their fonts gives them access to untold amounts of data.
Don't be evil
Was Google Fonts created with nefarious purposes in mind? Probably not.
If that kind of data was that valuable to Google, then I have a hard time understanding why Google Reader was shut down. Surely data about what blogs people read is more valuable than data about which open-source fonts websites use.
But again, this is Google so who knows. If collecting data is a driving factor, then I wouldn’t even be able to begin to fathom why.
Update: Aral Balkan pointed me to an interesting article about the privacy concerns with Google Fonts being automatically embedded on the backend of the latest versions of WordPress.
Reason #4: What’s Good for the Web is Good for Google
This is the explanation that I find the most compelling and at the same time, the hardest to fully grasp. The reasoning goes that what is good for the web in general, is good for Google. Having access to nice web fonts is good for the web so that will eventually translate into increased revenue for Google.