Adobe Fonts
Premium font service included with Adobe Creative Cloud subscriptions. Offers 20,000+ fonts from world-class foundries.
Websites Using Adobe Fonts
What Is Adobe Fonts (Typekit)?
Adobe Fonts is Adobe's subscription web-font service, included at no extra charge with every Adobe Creative Cloud plan. It gives subscribers access to a large library of professional, foundry-quality typefaces for both web embedding and desktop use in applications like Photoshop, Illustrator, and InDesign. It was previously called Typekit, and Adobe rebranded it to Adobe Fonts in 2018 - but the underlying delivery infrastructure still uses Typekit domains, which is exactly why it remains easy to detect (more on that below).
The core value proposition differs from a free service like Google Fonts. Adobe Fonts is aimed at designers and brand teams who already pay for Creative Cloud and want premium typefaces - including fonts from major commercial foundries - without negotiating per-font web licenses or worrying about pageview caps. One subscription covers desktop fonts for design software and web fonts for live websites, with the typography staying consistent from the mockup in Illustrator to the deployed page.
A real, source-grounded clarification: because Typekit was folded into Adobe Fonts, you will still see use.typekit.net and p.typekit.net in the network traffic of sites that use the service today. Adobe kept the Typekit serving domains for compatibility. So "Typekit" and "Adobe Fonts" are, in practice, the same service at the detection layer. We avoid quoting an exact library size here because Adobe's catalog changes as foundry agreements come and go; the dependable signal is the Typekit-domain request, not a memorized count.
There is one more reason Adobe Fonts occupies a distinct niche from free font services: it is a licensing product as much as a delivery product. When a designer activates a foundry typeface through Adobe Fonts, the Creative Cloud subscription is what grants the right to use that font commercially, both in design software and on the live web. With a free, open-licensed family, the license travels with the font file; with Adobe Fonts, the license is tied to an active account and to Adobe's serving infrastructure. This is the underlying reason you generally cannot lift an Adobe Fonts typeface off a site and self-host it the way you can with an open-source family, and it is why detecting Adobe Fonts on a competitor's site tells you something about their budget and workflow, not just their typography.
How Adobe Fonts Works
Adobe Fonts is built around the concept of a web project (historically a "kit"). A subscriber assembles the typefaces they want in the Adobe Fonts web interface, and Adobe generates an embed code tied to that project.
1. The embed code. A site includes a small stylesheet (and sometimes a script) from the Typekit serving network. The classic forms look like:
<link rel="stylesheet" href="https://use.typekit.net/abc1def.css">
or, using the asynchronous JavaScript loader:
<script src="https://use.typekit.net/abc1def.js"></script>
<script>try{Typekit.load({ async: true });}catch(e){}</script>
2. Font delivery. The stylesheet contains @font-face declarations whose font files are served from Adobe's CDN. The CSS is generated per-project, so it only includes the families and weights the designer selected.
3. Loading classes. The Typekit/Adobe Fonts loader adds state classes to the <html> element so CSS can react to font loading: wf-loading while fonts download, then wf-active once they are ready (or wf-inactive on failure). This Web Font Loader behavior is a strong fingerprint.
4. Desktop activation. Separately, the Creative Cloud desktop app activates the same fonts locally for use in design tools. That part is invisible to a website visitor but is central to the product's appeal.
Because the service is account-based, the embed code is the integration point - there is no public font catalog URL to copy a single font from the way Google Fonts allows.
To trace the full request flow on a live page: the browser parses the HTML, finds the use.typekit.net reference, and fetches the project stylesheet (and the loader script, if the JavaScript method is used). The loader adds wf-loading to <html>, requests the actual font files from Adobe's CDN, and - once they arrive - swaps the class to wf-active. Somewhere in this sequence a request to p.typekit.net typically fires. Each of these steps leaves a distinct, observable trace, which is what makes the service so reliable to fingerprint even when the rest of the page is heavily scripted or server-rendered.
How to Tell if a Website Uses Adobe Fonts
Adobe Fonts is highly detectable thanks to its dedicated serving domains and its distinctive loader classes.
Signal 1 - Typekit CSS/JS links. The most direct evidence is a <link> or <script> to use.typekit.net (or the older use.typekit.com):
<link rel="stylesheet" href="https://use.typekit.net/abc1def.css">
The short alphanumeric ID is the project/kit identifier.
Signal 2 - The p.typekit.net beacon. Adobe Fonts often fires requests to p.typekit.net for usage/analytics purposes. Seeing this domain in the Network tab is a reliable confirmation.
Signal 3 - Loader state classes. Inspect the <html> element. If you find class="wf-loading" momentarily, or wf-active / wf-inactive and family-specific classes like wf-proximanova-n4-active, the Web Font Loader (used by Typekit/Adobe Fonts) is running.
Signal 4 - Typekit.config or Typekit.load. In the page's inline scripts you may find references to a Typekit global, a Typekit.config object (which contains the kit ID and family list), or a Typekit.load(...) call.
Signal 5 - @font-face from Adobe's CDN. The generated CSS references font files on Adobe's font CDN; the request origins differ from Google's gstatic and are tied to the Typekit/Adobe infrastructure.
How to check, tool by tool:
- View Source: search the HTML for
typekit. Theuse.typekit.netlink or aTypekitscript reference usually appears in the<head>. - DevTools - Network: type
typekitinto the filter and reload. You should see the.css/.jsfromuse.typekit.net, the font files, and often ap.typekit.netrequest. - DevTools - Elements: watch the
<html>element's class attribute during load forwf-loading-wf-active. These classes are characteristic of the Adobe Fonts / Web Font Loader flow. - Wappalyzer: identifies Adobe Fonts (Typekit) automatically from the
use.typekit.netand related patterns.
For a structured, no-browser check, StackOptic fetches the URL and looks for the use.typekit.net / p.typekit.net signatures and the loader classes. To do it by hand, follow how to find what fonts and colors a website uses.
Key Features
- Premium foundry typefaces spanning text, display, and script faces.
- One subscription, web + desktop: the same fonts work in design tools and on live sites.
- No pageview caps or per-traffic fees in the Creative Cloud model.
- Per-project subsetting: the generated CSS includes only the families and weights you select.
- Asynchronous loader with
wf-loading/wf-activestate classes for fine-grained CSS control. - Tight Creative Cloud integration: fonts activated on the web appear instantly in app font menus.
- Adobe CDN delivery for fast, optimized font serving.
Pros and Cons
Pros
- Access to high-end commercial typefaces that are not free elsewhere.
- Seamless consistency between design comps (Illustrator/Photoshop) and the shipped website.
- Predictable cost: bundled into an existing Creative Cloud subscription with no traffic-based pricing.
- Mature loader with explicit loading states for avoiding flashes of unstyled text.
Cons
- Subscription required. Unlike Google Fonts, there is no free tier; access ends if the subscription lapses.
- Third-party dependency and privacy considerations. Fonts and beacons load from Adobe's servers (
use.typekit.net,p.typekit.net), which means visitor requests reach Adobe - a consideration under privacy regimes like GDPR, similar in spirit to the Google Fonts debate. - Less portable. Because licensing is tied to the subscription, you generally cannot freely self-host these fonts the way you can with open-source families.
- Extra connections to the Typekit network add some loading overhead.
Adobe Fonts vs Alternatives
| Service | Cost model | Hosting | Library focus | Self-host? | Best for |
|---|---|---|---|---|---|
| Adobe Fonts (Typekit) | Creative Cloud sub | Adobe CDN (use.typekit.net) | Premium foundry fonts | Generally no | CC design/brand teams |
| Google Fonts | Free | Google CDN or self-host | Open-source families | Yes | Most sites, fast setup |
| Self-hosted (licensed) | Per-font license | Your server | Whatever you license | Yes | Full control, strict privacy |
| System font stack | Free | Local (OS) | OS-installed fonts | N/A | Maximum performance |
The clearest tradeoff is Adobe Fonts versus Google Fonts: Adobe wins on premium foundry selection and Creative Cloud integration; Google wins on cost and self-hosting freedom. Teams already paying for Creative Cloud frequently default to Adobe Fonts simply because it is included and matches their print workflow.
Use Cases
- Brand and agency websites that must match a specific commercial typeface used in print collateral.
- Design-led teams on Creative Cloud who want one font source across desktop apps and the web.
- Editorial and publishing sites needing refined text faces with extensive weights and italics.
- Campaign microsites where distinctive display type is part of the creative.
- Portfolios by designers who already license the fonts through their subscription.
If you are auditing a competitor's premium typography, recognizing the use.typekit.net fingerprint quickly tells you they are on Adobe Fonts; our how to find out what technology a website uses guide covers fitting that into a full stack profile.
Performance and privacy notes
Two operational considerations come up repeatedly with Adobe Fonts. On performance, the service adds at least one third-party origin to the critical path (use.typekit.net), plus the font files themselves and the p.typekit.net request. The asynchronous loader helps avoid blocking render, and the wf-loading/wf-active classes let you control the flash of unstyled text, but the extra DNS lookup and TLS handshake are real costs - the same kind of overhead that pushes some teams toward self-hosting on other services. On privacy, because fonts and beacons load from Adobe-controlled domains, visitor requests (including IP addresses) reach Adobe. This is the same category of concern that produced the well-publicized Google Fonts GDPR debate, and it is worth flagging for any site operating under strict EU privacy requirements. Unlike open-source families, the self-hosting escape hatch is generally not available here because of the licensing model, so consent management is often the practical mitigation rather than first-party hosting. As always, confirm the specifics with qualified legal counsel rather than treating this as legal advice.
Frequently Asked Questions
Is Adobe Fonts the same as Typekit?
Effectively, yes. Typekit was Adobe's font service; Adobe rebranded it to Adobe Fonts in 2018. The serving infrastructure still uses Typekit domains (use.typekit.net, p.typekit.net), which is why detection tools still surface the "Typekit" name.
Is Adobe Fonts free?
No. Adobe Fonts is included with a paid Adobe Creative Cloud subscription rather than offered as a standalone free service. If the subscription ends, the web project fonts stop being served. This is the main contrast with the free Google Fonts catalog.
How do I detect Adobe Fonts on a site?
Look for a use.typekit.net stylesheet or script in the HTML, watch for wf-loading/wf-active classes on the <html> element, and check the Network tab for use.typekit.net and p.typekit.net requests. Wappalyzer and StackOptic flag it automatically.
Can I self-host Adobe Fonts for GDPR reasons?
Generally no - because the licensing is tied to the subscription and Adobe's serving network, self-hosting is not the intended (or permitted) model the way it is for open-source Google Fonts. Sites with strict first-party privacy requirements often choose self-hosted open-source or fully licensed fonts instead. Confirm licensing specifics with Adobe and your legal team.
What are the wf-active and wf-loading classes?
They are loading-state classes added to the <html> element by the Web Font Loader used by Typekit/Adobe Fonts. wf-loading is present while fonts download; wf-active appears once they are ready, letting CSS style text differently during and after font load to control flashes of unstyled text.
Why do I still see typekit.net if Adobe rebranded the service?
Adobe kept the original Typekit serving domains after the 2018 rebrand so that existing embed codes would keep working without forcing every site to update. As a result, use.typekit.net and p.typekit.net remain the canonical detection signals for Adobe Fonts to this day, which is also why many tools still report the service under its old "Typekit" name.
Want to see whether a website runs on Adobe Fonts, Google Fonts, or self-hosted type? Profile any URL with StackOptic.
Alternatives to Adobe Fonts
Compare Adobe Fonts
Analyze a Website
Check if any website uses Adobe Fonts and discover its full technology stack.
Analyze Now