Introducing Adobe Edge Web Fonts

As part of our efforts to make web fonts more broadly accessible and easy to use, we’re excited to introduce Adobe Edge Web Fonts, a new free web font service.

Edge Web Fonts features hundreds of web fonts, including a sampling of fonts from the Adobe library as well as a large collection of open source fonts. Under the hood, the service is powered by Typekit: it uses the same standards-based method of serving fonts and makes use of the same global font serving network for speed and stability. But it’s completely free and requires no account or kit configuration — making it faster and easier to get started.

Google Web Fonts and Edge Web Fonts

We’ve partnered with Google to make many of the open source fonts originally commissioned by the Google Web Fonts project available through Edge Web Fonts. At the same time, Adobe is contributing two open source fonts of its own — the recent Source Sans Pro and, announced today, Source Code Pro — to both the Adobe Edge Web Fonts and Google Web Fonts services.

In addition, Adobe will be applying its considerable font expertise to improving and optimizing a number of the open source fonts that are available in both Google Web Fonts and Edge Web Fonts. The teams from Typekit, Adobe Type, and Google Web Fonts are working to identify which fonts will benefit the most from our attention, and how we can best approach improving their rendering and performance. Efforts will include hinting some fonts for better rendering at smaller sizes, plus a number of other optimizations. All of these contributions will themselves remain open source.

We’re excited to be part of these efforts, and are glad to be once again partnering with our friends at Google to improve fonts on the web. Read more from Google here.

Available now

Starting today, you can use Edge Web Fonts in both Adobe Muse and Edge Code, a code editor based on the open source Brackets project. Next up, Edge Web Fonts will be available in the soon-to-be-released Edge Reflow, a tool for creating responsive CSS layouts and more. More integrations are upcoming with Adobe’s Edge Tools & Services.

But Edge Web Fonts isn’t limited to Edge tools — you’re free to use it with whichever tools you prefer. You can preview some of the best of the fonts here, where you’ll also find instructions on how to use them in your web projects. We’ve also made a list of all of the fonts in the Edge Web Fonts library available.

More tools for working with Edge Web Fonts are just around the corner. Stay tuned.

42 Responses

  1. zandyring says:

    Nice – it’s like a lighter Typekit, with a layer removed for the end-user. And that’s not to imply that Typekit is heavy, because it’s also a great user experience.

  2. Looks great! Well done.

    Small nit: why not use the protocol-relative URL for the script include? Looks like the domain supports SSL already.

    1. Sean McBride says:

      We still do recommend the protocol-relative URL for deployment on the web. However, we discovered during development that local development on “file://” was a significant use case for some of the integrations, and the protocol-relative URL obviously isn’t a good choice in that case. We have more detail on protocols and how to choose based on your situation in the documentation.

    2. Ah, makes sense. Yeah file:// gets cranky on Windows. Understandable.

  3. I think this service is a great thing for the web, though I do hope a better system for previewing the fonts is in the works.

  4. Arti Agarwal says:

    Awesome work ! Love the tie up with Google fonts.
    Can you help me out with how we can integrate the new fonts from Adobe Edge Web Fonts into Adobe Muse ?
    I am a bit puzzled and overwhelmed and will appreciate if you can point me to a tutorial or video or something. Thanks !

    1. Joe Shankar says:


      Muse has natively supported Adobe Edge Web Fonts since the v1 release of Muse in May 2012.

      Video tutorial:!/watch/adobe-inspire-magazine/using-typekit-with-adobe-muse/


  5. Chris Adams says:

    This is awesome! One major drawback for me, however, is the lack of a way to view the font repertoire – I work on a non-profit multilingual website with very wide character set usage and it would be invaluable for me to be able to rank fonts based on Unicode ranges or even just the number of glyphs.

  6. Somesh Kumar says:

    This is an excellent news! Great going!

  7. Yvo Schaap says:

    I made a preview overview of all available Edge fonts for quick browsing:

  8. Fitoschido says:

    Such a nice surprise, Adobe!! 😀

  9. AboutaDirk says:

    Does this mean you’re a step closer to allowing fonts to be used in Adobe applications? It’s still a real pain in the hind to have to download fonts elsewhere, or screenshot text for mockups.

    I’m sure you’ve heard this complaint before though, so feel free to respond with a link to the why’s (or why-not’s, in this case).

    Cheers, great product/service.

  10. Sebhelyesfarkú says:

    No Eastern European characters?

    1. Gregory Veen says:

      Some of the fonts do contain some Eastern European characters. While we do not yet offer a way to browse/search the fonts by which languages they support, you can access characters for all of the languages each font supports by using the “all” subset when loading fonts, instead of the default subset. Check out the Subsets section of the documentation for more details.

  11. Jens says:

    Why is JavaScript necessary for loading these fonts? Always thought the only reason for TypeKit using this approach was for DRM reasons.

    1. Gregory Veen says:

      Actually, Typekit doesn’t load fonts with JavaScript for DRM reasons. Instead, we use JavaScript because of the font loading benefits it makes possible, which ultimately result in a better experience. We’ve written in detail about this here.

  12. arminrosu says:

    So, why should we use Adobe Edge Web Fonts instead of Google’s? Will the Adobe improvements be only available on Edge?

    1. Gregory Veen says:

      The improvements Adobe makes to the fonts that are in both the Google Web Fonts library and the Edge Web Fonts library will be available in both places.

      Reasons you might consider using one of the services instead of the other include 1) access to different fonts (the libraries do no exactly mirror each other), 2) access to different font loading options (for example, the default subset behavior is different in the two services — see the URL Specification in the Edge Web Fonts documentation for details on how it works in Edge Web Fonts), or 3) Edge Web Fonts is integrated in customized ways into some Adobe tools you might want to use (for example, Edge Code, Muse, and, soon, Reflow and others).

      But Edge Web Fonts is not intended to be competitive towards Google Web Fonts. Rather, Adobe and Google share the goal of improving the web by enabling more web font adoption. We hope to push that cause forward, in part, by introducing more/different types of designers/developers to web fonts.

      1. arminrosu says:

        Thanks Gregory 🙂

        Point nr. 1 is most interesting to me (#2 is interesting and #3 is really just about preference).

        Will you have a nice gallery, so I can show it to my designers? Something similar to what Peter Chon (thanks btw!) did, but subsetting characters (& especially testing non-latin characters) would be nice.

  13. metai says:

    Sorry, but: Big whoop, a pile of freefonts. If you’re really trying to improve upon Typekit, start by issuing agency licenses the way does.

  14. Libor says:

    How about STIX fonts? They are free and essential for any kind of “scientific” content on the web. Embedding them by hand and serving from own domain is pain, using TypeKit scripting and CDN would be great help to man kind.

  15. Peter Chon says:

    I’ve made a easy compilation of available fonts here:

    1. dbrugge says:

      Peter, I went to your site and the first thing that struck me is how similar the fonts were to each other…. then the images downloaded.
      Thanks for a valuable service!

  16. andrs says:

    How about unicode support?

    1. Gregory Veen says:

      I suspect that by “unicode support” you mean support for more languages than are covered by Latin1. Let me know if you’re asking about something else, if not, my reply above about Eastern European languages applies here, too. Thanks!

  17. Vernon Adams says:

    Many many people said this would never happen, but it’s happening :p
    the ‘free’ webfont revolution goes on…

  18. Tony Stuck says:

    I’ve also made a little tool to preview the fonts: It’s paginated so it doesn’t kill your browser, you can view each variant/style, and also set custom preview text 🙂

  19. adobe has definitely woken up ….nice

  20. tom says:

    What about open type features? Will these be available on any of these fonts? And if so are they documented any where?

    1. Gregory Veen says:

      While we don’t yet offer a way to browse/search the fonts by OpenType feature support, some of the fonts do have some OpenType features. Be sure to use the “all” subset (instead of the “default”) when loading fonts in order to get access to whatever OpenType features a font contains. Note also that not all browsers support OpenType features yet, but their support is growing. Check out the Subsets section of the documentation for more details on subsets.

  21. hrvojester says:

    Pretty disappointed with the fact that 99% of the fonts do not have Central European characters.

    1. Gregory Veen says:

      We hope to expand coverage in the future. In the meantime: some of the fonts do contain some Central/Eastern European characters. While we do not yet offer a way to browse/search the fonts by which languages they support, you can access all of the languages each font supports by using the “all” subset when loading fonts, instead of the default subset. So, when working with fonts and looking for Central European characters, please make sure to use the “all” subset. Check out the Subsets section of the documentation for more details.

  22. draverobber says:

    In the ‘List of Available Fonts’, two fonts – Double Pica and Geo – have duplicate ‘ n4’ FVDs. It seems in both cases one of those needed to be ‘i4’ instead.

    (sorry, couldn’t quite find the appropriate contact form to report this :))

    1. draverobber says:

      (this is fixed now)

  23. Reblogged this on Laggacy and commented:
    Look what I found on the Typekit Blog. Good news for web developers who don’t use Typekit.

  24. MIHAEL says:

    Is there a Way we can build in missing Estern Europe characters by ourself, or download font, add character and reuplovd it?

    1. Gregory Veen says:

      Adding new characters to a typeface requires both design skill (because the new glyphs must be drawn) and technical skill (because the new glyphs must be added to the typeface’s font files and optimized). If you have these skills, I’d love to chat with you. If so, can you email me at Thanks!

  25. draverobber says:

    Edge Fonts seem not to work in Midori browser (0.3.2 / Ubuntu). Other webfont providers (Google, Font Squirrel) are fine.

    1. Gregory Veen says:

      Thanks for the report! The browser/OS support details for Edge Web Fonts are outlined in the documentation. We don’t support every specific WebKit variant at this point, but that may change in the future.

Comments are closed.

Gregory Veen

Co-founder of Typekit and head of product for Adobe Typekit and Type. @gregveen on Twitter.

Announcing Source Code Pro

Paul D. Hunt · September 24, 2012 · Fonts on Typekit

Coming Soon: Fonts from Monotype Imaging

Bryan Mason · September 24, 2012 · Announcements