Contact Us​​ | Status Blog
Help Center
Main Troubleshooting › Troubleshooting Guide for web ...

Troubleshooting Guide for web fonts

Publishing your kit:

Your kit must be published after adding new fonts, updating the domains in your kit or any other changes you've made since the kit was last published. A kit would also need to be republished to access new features, such as updated browser support. Publishing your kit is a good first step in resolving font loading problems. To do so, simply launch the Kit Editor and click the "publish" button; the updates will be available within a few minutes.

What are you having trouble with?

Fonts aren't working in any browser
Back to top ↑

Problem Solution
Domain is not listed on kit Add the domain name to your kit.
Embed code is missing from site. Add the embed code to the <head> of your site.
Typekit font name hasn't been added to the CSS. This can be done by:
  • adding CSS selectors to your kit
  • using the provided font-family names in your own CSS

Both options are described in the Working with CSS selectors page.

Ghostery is blocking Typekit Go to Options > Blocking Options > Trackers > Widgets and uncheck "Typekit by Adobe".

Fonts aren't working in mobile browsers
Back to top ↑

Problem Solution
The browser isn't supported. Browser and OS support
Mobile Settings may have been disabled in your kit. Mobile browsers are supported by default, but can be turned off in the kit. Launch your Kit Editor and make sure font serving to mobile browsers is enabled under Kit Settings > Mobile Settings.
The correct font weight or style isn't specified in the CSS. If a font weight or style isn't available, many mobile browsers will not display the font and use the fallback instead. Make sure that the weight and style you want to apply are included in your kit and that they are specified correctly in the CSS.

Firefox isn’t showing the fonts but other browsers are
Back to top ↑

Problem Solution
Referrer turned off in hidden preference.

The browser sends a referrer by default, but some add-ons change this preference.

  1. open a new browser tab and type about:config in the address bar.
  2. enter network.http.sendRefererHeader in the search field.
  3. The value should be set to 2, not 0 or 1. To change it, double click on the preference row.
Downloadable fonts turned off in hidden preference.

Another hidden preference disables downloadable fonts.

  1. open a new browser tab and type about:config in the address bar.
  2. enter gfx.downloadable_fonts.enabled in the search field.
  3. The value should be set to true. To change it, double click on the preference row.
Browser preference to override user fonts is turned off. There is a preference that determines whether custom fonts may override the user's browser settings. Under Preferences > Content > Fonts & Colors > Advanced, the "Allow pages to choose their own fonts" box must be checked.
Web Developer extension has disabled the referrer. In the Web Developer toolbar, open the Disable menu and make sure that the Disable Referrers option is unchecked.

Internet Explorer isn’t showing the fonts but other browsers are
Back to top ↑

Problem Solution
Browser preference to disable downloaded fonts is turned on. [IE6-8] There is a security setting that can disable all downloadable fonts. Under Tools > Internet Options > Security > Custom level > Downloads, look for “Font Download”. Font downloads should be enabled with the default security level. If security has been set to "high", fonts may not load.
Browser preference to override user fonts is turned on. [IE7] There is a preference that determines whether custom fonts may override the user's browser settings. Under Tools > Internet Options > Accessibility, make sure that “Ignore font styles specified on websites” is not checked.
The site is using the ie7-js library. Typekit is incompatible with default files from the ie7-js project because they break the font-family definitions. Our recommendation is to remove ie7-js from your site if it's causing issues. If you need to use ie7-js, try adding this line to the beginning of the "for" loop that starts on line 171:

if(styleSheets[i].cssText.indexOf('src:url(/k/') >= 0) return;

You are using IE Tester. @font-face functionality is unreliable in this program, so Typekit fonts may not render when they would work in a real browser installation.

Fonts aren't displaying or look “doubled” in Safari & Mobile Safari
Back to top ↑

Problem Solution
The font weight or style in the CSS isn't available in the kit. If the specified font weight or style isn't included in your kit, these browsers may try to create it. Make sure that the weight and style you want to apply are included in your kit and that they are specified correctly in the CSS.

Still need help? Email Us.

​​​​
support@typekit.com
http://assets04.desk.com/
false
desk
Loading
seconds ago
a minute ago
minutes ago
an hour ago
hours ago
a day ago
days ago
about
false
Invalid characters found
/customer/en/portal/articles/autocomplete