FAQs

Any questions not answered here are welcome at webfontshowcase@myfonts.com or help@myfonts.com.

 

Q: Why do I need to choose between a desktop font and a webfont? What’s the difference?

A: ‘Desktop’ fonts are what we call the TrueType, OpenType and PostScript fonts that you've been using on your computer for years. These are installed locally in your system's Fonts folder, and you use them in your word processor, design programs, etc. 
“Webfonts” are the same fonts encoded in different ways, which web developers can use to design a website using the fonts of their choice. Browsers (e.g. Internet Explorer, Firefox, Safari) know how to download these fonts and use them to display web pages in the designer's desired choice of fonts.
At purchase time, you can decide whether you need one or the other, or both types of license. For example, if you will only be using a font on web sites, and don't need to use it in Word or Photoshop at all, you only need a webfont license.

Q: Why can’t I see the fonts I specified in my CSS?

A: To troubleshoot your CSS (Cascading Style Sheets, more info at Wikipedia) you can enable a testing mode to debug any issues you have or assess your webserver's configuration. It will enable a debug page that will output the status of your webfont kit, testing all of your fonts. Enable testing mode and go to your homepage as normal, and the testing magic will take care of the rest. To enable "troubleshooting mode", copy-pasted code snippet from above change:
var myfont_webfont_test = true;
Testing is a global setting, it will test all of your fonts. When you are done testing, you'll just have to set the regular javascript back in place.
var myfonts_webfont_test = false;
If you continue having difficulty, feel free to write us at help@myfonts.com send us the web page URL for review.

Q: Why does my text look terrible?

A: It could be one of many reasons. Did you check the webfont previews to make sure it would render well in older browsers? Thin, highly stylized or grungy fonts won’t display very well in small sizes, and this can be checked before purchase in our Webfont previews. For other guidelines on optimal type design for the web, there's lots in our Webfonts know-how section or our further reading resources.

Q: What difference does it make if I have live text as opposed to making my text out of graphic files?

A: You can make your entire website out of a single bitmap graphic if you wish, but it would be very difficult to submit it to search engines, scale it for different browsers and devices, allow the user to print it, make easy updates or changes… the list goes on. Websites made from a single graphic file do exist, but they are rare and are an extreme example to prove our point. Normally, people compromise by having some elements within their design as live text, and some — often menu bars, buttons, and headers — as fixed size graphic files, if they want to do something interesting with typography. Using webfonts means you can keep those parts of your design that would have been converted into graphics as live text.
Using real text is preferable because it has huge advantages for accessibility. Sight-impaired visitors will be able to have more of your site read by screen-reader technology; search engines will be able to index more of your page, and interpret the relative importance of text by HTML tags such as <h1>.

Q: Do I now need to buy a webfont license because I used a font I bought from you to make a logo for a website/graphic page headers/navigation buttons?

A: No, as long as they’re not live text. That original license permits you to use the font on your computer within any application that supports font selection, including the graphic packages you use to make menu bars or header elements.
There’s also no reason to stop making graphical elements this way if you really want to. We outline why one might want to use webfonts in this article, but it’s by no means obligatory that every website now features live text everywhere.

Q: Why can’t I use a font I have already purchased from you in my website design?

A: There are two reasons: one, the license you agreed to on purchase only licensed the font for your own personal use (or that of employees at your company, etc.). Webfonts involve hosting the fonts on a public server where they must be accessed by anyone viewing your website, which requires a new license; and two, formatting fonts for the web and screen is a complicated business, given the wide variety of ways that web browsers and operating systems interpret the data built into your font file. Our webfont packages automate much of that compatibility work, as well as protecting the font files themselves from illegal distribution.

Q: Can I convert a desktop license into a webfont license?

A: For older purchases, no; but if you purchase a desktop license by mistake, we can switch them for you.

Q: How does licensing work for specifying fonts in a client’s website? Do they need to make the purchase?

A: That depends on your working relationship with your client. With webfont licenses, the name on the license must be the owner of the domain name, effectively meaning that you can’t share your license between multiple clients, in the way you might have been used to in print projects.

Q: How will I know when I need to upgrade to more pageviews?

A: The style sheet included in our webfont kits includes a pageview counter. Pay As You Go license customers will receive a notification from us when they are close to exceeding their pageview limit.

Q: Can I customize my download package?

A: Yes, absolutely. There are many tweaks and adjustments you can make to suit your requirements. See the Webfont Kit Builder tab on your order download pages in your Order History.

Q: Why should I have to customize? Everything I need is in the package, right?

A: This is usually true, and you can download the "basic kit" from your order download page. Some reasons to build a custom kit include: limiting the selection of fonts in the kit (e.g. if you bought fonts for multiple projects in a single order); choosing between Javascript or CSS-only implementation; tweaking included characters / languages / advanced features.