Today, we’re announcing official support for more web browsers on both iOS and Android devices. To get these latest browser support updates, simply republish your kits.

Chrome for iOS

In February, we added support for Chrome for Android. Now, we’re also adding official support for the recently released Chrome for iOS.

Firefox for Android

In June, Mozilla released a major overhaul of Firefox for Android. The Android version is now keeping pace with the latest desktop version and has a speedy native interface. We’ve added Firefox for Android to our list of officially supported Android browsers.

Opera Mobile for Android

We’ve also added official support for Opera Mobile for Android. Unlike its little brother, Opera Mini, the Opera Mobile browser has support for @font-face and the WOFF file format, just like the full desktop version.

As a reminder, you can enable or disable sending fonts to Android, iPad, or iPhone in your Kit Editor (under Kit Settings > Mobile Settings). Disabling a platform will disable support for all browsers on that platform. If you have mobile support turned on (which is the default), you need only republish your kits to get the latest updates.

The new Firefox 4 is out of beta and looking sharp. New interface improvements accompany improved tools for private browsing, accessing frequently visited pages, and more. Plus, major performance upgrades make it noticeably speedier. As of this writing, it’s been downloaded over ten million times.

Typekit has supported Firefox 4 throughout the beta period, so newer kits will work on the full release automatically. Older kits (those published before August 2010) need to republish to get the latest browser support.

As always, Typekit continues to keep a close eye on new browsers and devices to keep your fonts looking beautiful, everywhere.

As noted previously, iOS 4.2 adds support for TrueType fonts, an improvement over previous versions of iOS which only supported SVG fonts. TrueType fonts are superior to SVG fonts in both performance and rendering quality.

We tested TrueType fonts across our system and have been pleased with the results; in particular, the fonts load noticeably faster. Today, we have updated our system to serve TrueType fonts to all iOS (iPhone/iPad/iPod) devices. To update your sites to the latest font versions, just republish your kits.

As always, if you have any questions, please drop a line to and we’ll be happy to help.

As mentioned previously, Apple iOS 4.2 brings with it some significant improvements in web fonts: Mobile Safari no longer crashes when multiple weights of a web font are loaded. And iOS 4.2 adds support for TrueType fonts (where previous versions only supported SVG fonts).

As a result, we are updating our support for mobile devices. Starting today, support for iOS devices is no longer experimental; fonts for the iPad and iPhone will be enabled in new kits by default. (Note that this change does not affect settings in your existing kits — only in newly created kits.) You can still disable them if you choose, however; just pop into the Kit Editor and change the settings under Kit Settings > Mobile Settings. Remember to republish your kit after making changes.

We’ve also added an option to disable sending web fonts to Android 2.2 devices in your Kit Settings. As with iOS 4.2, support is enabled by default, but you can disable it if you choose.

At the same time, we are dropping support for versions of iOS prior to 4.2. This means that users of these devices will see the fallback fonts for your site, and be spared a browser crash. We recommend that you use Font Events to take full control over the fallback scenario, ensuring a good experience for users of older devices and browsers.

Additionally, we are currently testing support for TrueType fonts on iOS 4.2. Look for further updates as we make the switch from sending SVG fonts to sending TrueType fonts to these devices.

Update: We are now serving TrueType fonts to iOS 4.2 devices.

As always, if you have questions, we’re here to help; drop a line to at any time.

Update: The latest on Typekit’s support for iOS devices can be found here Also, we are now serving TrueType fonts to iOS 4.2 devices.

With yesterday’s release of iOS 4.2, a frustrating Mobile Safari bug has been resolved: previously, Mobile Safari would crash if more than one weight or style of a font was loaded. This bug has been repaired in iOS 4.2, so that users of the iPhone, iPod, or iPad who update their device will no longer experience crashing.

This is great news, and as a result we are updating our support for iOS. Currently, support for iOS is disabled by default; starting in two weeks (on December 6th), support for iOS devices will be enabled by default. You will still have the option of disabling it if you choose, but every new kit created will have iOS turned on. (Note that this change does not affect settings in your existing kits — only in newly created kits.)

Additionally, we have decided to drop support for older versions of iOS. Also starting on December 6th, we will no longer send fonts to versions of iOS prior to 4.2. Dropping support for a browser is not something we take lightly; but we believe the crashing bug is so offensive as to make supporting these browsers untenable. No one should ever experience a browser crash because of a web font; and we are taking this step to make sure that they never will.

What does this mean for you? It means that older versions of iOS will see your sites with the fallback fonts rather than Typekit fonts. We recommend that you use Font Events to take full control over the fallback scenario, so that your site looks just as effective with those fonts as it does when the Typekit fonts are enabled. Doing so will also ensure a good experience for users who visit from older browsers, as well as for those who have disabled web fonts. This is a smart, progressive enhancement practice, no matter which devices are supported now or in the future.

iOS 4.2 is also the first version of Mobile Safari to support native web fonts (in TrueType format) instead of SVG. This is also exciting news, as TrueType fonts are superior to SVG fonts in two very important ways: the files sizes are dramatically smaller (an especially important factor on mobile devices), and the rendering quality is much higher. We are currently updating our testing suite to evaluate how well TrueType fonts perform in Mobile Safari; once we’ve confirmed that they do in fact work effectively, we will begin sending TrueType fonts to iOS devices. Look for more updates on this change in the near future.

As always, if you have any questions about what these changes mean for your site, or if you need help working with Font Events, please drop a line to

We’ve added support for Android 2.2+ devices. We’re quite excited about this addition for two reasons: First, it expands the number of platforms that support rich typography; second, Android 2.2 supports OpenType font files. OpenType files support hinting and other advanced features, and represent an improvement over the SVG fonts currently in use by the iPhone and iPad. We’re happy to see more devices support OpenType and hope that trend continues.

We know the mobile space changes rapidly, and we’ll continue to keep up with these changes so that you don’t have to. To add support for Android to your site today, simply republish your kit.

Update: The latest news on Typekit’s support for iOS devices can be found here.

We’re happy to report that the latest version of iPhone OS, now called iOS, includes a fix for the webfont related crashing of Mobile Safari that we observed in previous versions. As we reported earlier, Mobile Safari on iPhone OS 3.1+ will crash when rendering multiple weights and styles of SVG webfonts. This has been fixed in iOS4 (8A293), making webfonts far more usable. Now, Typekit supports the devices that can run iOS4 — iPhone 4, iPhone 3GS, and iPhone 3G.

This more stable performance is a great step forward for webfonts on the iPhone, but some of the other quirks we found in our testing of earlier versions remain: Mobile Safari still does not synthesize undefined weights and styles from the normal weight of an SVG font, and the text selection behavior of SVG-styled text still feels non-native. For these reasons, we’ll continue to offer iPhone support as an experimental, opt-in feature for now. Likewise, since Apple has yet to release iOS4 for the iPad, support for that device will remain an experimental feature in Typekit as well.

If you’d like to enable Typekit’s iPhone support, just sign in to your account and select the kit you’d like to configure. Then launch the Kit Editor, select Kit Settings, and click on Experimental Features.