Designers who began using web fonts a decade or so ago will remember Typekit. It let websites use professional typefaces without the old restrictions of web-safe fonts. The service was later folded into Adobe’s wider offering and renamed, and today it is known as Adobe Fonts. If you are wondering what that means for you, or you simply want to understand how Adobe Fonts and similar services work, this guide covers the essentials.
In this article
Why web fonts mattered in the first place
In the early days of the web, designers could only rely on a small set of fonts installed on nearly every computer. Anything else risked falling back to a default if the visitor did not have it. The result was a lot of websites that looked alike.
Hosted services such as Adobe Fonts solved this by hosting fonts online and delivering them to the browser when a page loads. Designers could finally use a wide range of typefaces with confidence, and visitors saw the intended design on any device. Typography matters more than it first seems. The shape of letters sets the tone of a page long before anyone reads a word, and a font that suits the content makes text easier to scan. Licensing was handled by the service, so nobody had to negotiate separately with each type foundry.
What Adobe Fonts is today
Adobe Fonts is a library of typefaces available to subscribers of Adobe’s Creative Cloud plans. You browse the collection, filter by style, and activate the fonts you like. Activated fonts then appear in your desktop applications, and you can also use them on websites through a snippet of code.
The key idea is licensing. Instead of buying each font one by one, you pay for the subscription and gain access to a large collection. As long as the subscription stays active, you can use the fonts as the service’s terms allow. If you stop paying, the fonts stop working in your apps, so it pays to know that before building a brand around them.
You can read a short history of the company behind it in the Wikipedia article on Adobe Inc. if you want the background on how Typekit ended up inside a larger product line.
How Adobe Fonts differs from a regular font download
When you buy a font file from a foundry, you own a licence to a file. You install it, send it to a printer if the licence allows, and keep using it for as long as you like. A subscription library works differently. You are borrowing access to the fonts and the service keeps track of which ones you have switched on.
For a freelance designer, Adobe Fonts is convenient. You can try a typeface in a layout, swap it for another, and not worry about the cost of each experiment. For a client who needs the final files, it can be awkward. If you hand over a document that depends on a subscription font, they may need their own access to open it properly.
That is why many teams that rely on Adobe Fonts agree early on which fonts go into a project and who holds the licence. A few minutes of planning saves a lot of awkward emails later, and it is worth repeating when you start a new job for a new client.
Using Adobe Fonts on a website
For the web, the process is usually straightforward. You create a web project in the service, add the fonts you want, and receive a line of code to place in your site. The browser then fetches the fonts from Adobe’s servers when pages load. If you change your mind, you edit the project and the site picks up the new choice without you uploading any font files.
There are some trade-offs. Fonts add weight to a page, and loading them from another server adds a small delay. With Adobe Fonts, as with any web font, choose only the weights you really need, because every extra style is more data. A page that uses one regular and one bold style will usually feel quicker than one that loads six.
Privacy is another point to think about. Any third-party resource means your visitors’ browsers connect to another company’s server. Some site owners prefer to host fonts themselves for this reason, where the licence allows it. Check the terms of whichever service you choose.
A good fallback font also matters. If the custom font is slow to load, the browser shows a stand-in until it arrives. Pick a fallback with similar proportions so the page does not jump around.
Is Adobe Fonts worth using?
If you already pay for Creative Cloud, Adobe Fonts is a useful extra that costs nothing more. It works well for designers who move between print and web work and want reliable licensing. If you only need one or two typefaces, you may not need Adobe Fonts at all, and for a small site there are free open-source alternatives that may be enough. The best test is simple: list the typefaces your projects really use over a year, then decide whether a subscription library or a couple of free choices fits better.
For anyone who builds layouts, a related question is how design files are shared and reused. Our guide to design community files shows how designers pass templates around, and fonts are often the first thing that breaks when a shared file lands on another machine.
Whatever you choose, the sensible habit with Adobe Fonts is to read the licence, check what happens if the subscription ends, and keep a record of which fonts each project uses. Understanding how Adobe Fonts works means you can enjoy a huge library of typefaces without surprises later.
