What Is Typekit?

Typekit is the original brand name for what is now Adobe Fonts - a subscription web-font service that delivers professional typefaces to websites and design applications. Adobe acquired Typekit in 2011 and rebranded the service to Adobe Fonts in 2018. The name lives on for a very practical reason: the delivery infrastructure still runs on Typekit domains, so when you inspect a modern site that uses Adobe Fonts, you will see requests to use.typekit.net and p.typekit.net. Detection tools and developers therefore continue to encounter and report "Typekit" today, even though the product is officially called Adobe Fonts.

If you are reading this to identify a technology on a website, the key takeaway is: Typekit signals and Adobe Fonts signals are the same thing. A use.typekit.net stylesheet is evidence of Adobe's subscription font service, regardless of which name a particular tool uses to label it. This profile focuses on the legacy brand and, in particular, on the loader behavior and beacon requests that make Typekit so recognizable in the wild.

A grounded note on accuracy: we do not quote a fixed font count or precise historical adoption figure here, because the catalog and usage shift over time and Adobe controls the canonical numbers. The reliable, verifiable facts are the serving domains (use.typekit.net, use.typekit.com, p.typekit.net), the Web Font Loader state classes (wf-loading, wf-active, wf-inactive), and the Typekit JavaScript global - all of which are observable directly in any browser.

Why does this legacy name deserve its own profile rather than a footnote under Adobe Fonts? Because in technology-profiling terms, the signals a tool reports are what you actually work with, and an enormous number of sites - particularly those built between roughly 2011 and 2018, plus newer sites whose templates were copied from that era - still carry the Typekit footprint verbatim. A detection tool that says "Typekit" is not wrong and is not out of date; it is reporting the real domains the browser contacted. Treating Typekit as a first-class detection target, with its own characteristic loader behavior, helps you read those signals correctly instead of dismissing them as a stale label.

How Typekit Works

Typekit (Adobe Fonts) is a hosted, account-based service. A subscriber builds a kit (now called a web project) by choosing fonts in Adobe's interface, and Adobe issues an embed snippet keyed to a short kit ID.

1. Embedding the kit. Two integration styles are common. The CSS form:

<link rel="stylesheet" href="https://use.typekit.net/xyz1abc.css">

And the JavaScript loader form, which is the historically classic Typekit pattern:

<script src="https://use.typekit.net/xyz1abc.js"></script>
<script>try{Typekit.load({ async: true });}catch(e){}</script>

2. The Typekit global and config. The loader exposes a Typekit object. Older embeds reference Typekit.config (containing the kit ID and the list of font families/variations), and call Typekit.load(...) to kick off font loading.

3. Web Font Loader state classes. While fonts download, the loader adds wf-loading to the <html> element; when they finish it swaps in wf-active (or wf-inactive on failure). It also adds per-family classes (for example wf-proximanova-n4-active). This staged class system lets CSS hide or restyle text to avoid a flash of unstyled or invisible text.

4. Beacons to p.typekit.net. The service commonly issues requests to p.typekit.net, historically associated with kit usage/performance reporting. That domain is a dependable fingerprint distinct from the font files themselves.

The font files are served from Adobe's CDN, subsetted to the families and weights the kit includes. Because everything is tied to a subscription and a kit ID, there is no public way to self-host these specific fonts.

A useful mental model is that Typekit/Adobe Fonts moves through three observable states during a page load. Loading: the kit CSS/JS has been requested and <html> carries wf-loading; text may be hidden or shown in a fallback depending on the site's CSS. Active: the font files have arrived, wf-loading is replaced by wf-active (and per-family wf-<family>-n4-active classes appear), and the real typefaces render. Inactive: if loading fails or times out, wf-inactive is applied and the page falls back to system fonts. Watching these transitions in the Elements panel is often faster than digging through the Network tab, and it confirms not just that Typekit is present but whether it actually succeeded in activating its fonts - a common source of "the font looks wrong" bug reports.

How to Tell if a Website Uses Typekit

Typekit's fingerprints are unusually clean - the dedicated domains and loader classes make it one of the more unambiguous detections in front-end auditing.

Signal 1 - use.typekit.net (or use.typekit.com) CSS/JS. A <link> to a use.typekit.net/<id>.css stylesheet, or a <script> loading use.typekit.net/<id>.js, is the primary tell.

Signal 2 - wf-loading / wf-active on <html>. Inspecting the root element and seeing these Web Font Loader classes (especially the brief wf-loading state during page load) strongly indicates Typekit/Adobe Fonts.

Signal 3 - p.typekit.net beacon. A request to p.typekit.net in the Network tab confirms the Typekit serving network is active.

Signal 4 - The Typekit JavaScript global. In DevTools Console, references to a Typekit object, or Typekit.config / Typekit.load in inline scripts, are direct evidence.

Signal 5 - Per-family wf-* classes. Classes like wf-<familyname>-n4-active on <html> reveal both that Typekit is in use and which families/weights it activated.

How to check, tool by tool:

View Source: search the raw HTML for typekit. The kit <link> or <script> typically sits in the <head>.
DevTools - Network: filter by typekit and reload; expect the kit .css/.js, the font files, and a p.typekit.net request.
DevTools - Elements: observe the <html> element's class attribute during load - the wf-loading to wf-active transition is the giveaway.
DevTools - Console: type Typekit and press Enter; if a configuration object returns, the kit is present.
Wappalyzer: reports Typekit / Adobe Fonts automatically from these patterns.

For automated, server-side detection from just a URL, StackOptic inspects the page for use.typekit.net references, the wf-* loader classes, and p.typekit.net beacons. To walk it manually, our how to find what fonts and colors a website uses guide is the place to start.

Key Features

Subscription-based premium fonts delivered through Adobe's CDN.
Kit/web-project model: fonts are bundled per project under a short kit ID.
Asynchronous Web Font Loader with wf-loading / wf-active / wf-inactive states.
Typekit JavaScript API (Typekit.config, Typekit.load) for controlled loading.
Per-family activation classes for granular CSS styling during load.
Backward-compatible domains: still served from use.typekit.net after the Adobe Fonts rebrand.
Web + desktop parity via the broader Adobe Fonts / Creative Cloud subscription.

Pros and Cons

Pros

Access to professional, foundry-grade typefaces under a single subscription.
Mature loading behavior that minimizes flashes of unstyled or invisible text.
Clean, predictable detection footprint (useful for auditing and migration planning).
Consistent typography across Adobe design tools and the live site.

Cons

Legacy branding confusion. Documentation and tools split between "Typekit" and "Adobe Fonts" for the same service.
Subscription dependency. No free tier; fonts stop serving if the Creative Cloud subscription ends.
Third-party requests and privacy. Loading from use.typekit.net and beaconing to p.typekit.net means visitor requests reach Adobe's network - a consideration under GDPR-style regimes, comparable to the Google Fonts privacy discussion.
Limited self-hosting. The licensing model does not allow freely hosting these fonts on your own origin.

Typekit vs Alternatives

Option	Branding	Cost	Hosting / domains	Self-host?	Notes
Typekit (Adobe Fonts)	Legacy name for Adobe Fonts	Creative Cloud sub	`use.typekit.net`, `p.typekit.net`	Generally no	Same service, old label
Adobe Fonts	Current name	Creative Cloud sub	`use.typekit.net`	Generally no	Identical infrastructure
Google Fonts	Google	Free	`fonts.googleapis.com` / `gstatic.com` or self-host	Yes	Open-source, free
Self-hosted fonts	First-party	Per license	Your own server	Yes	Best for strict privacy

In short, "Typekit vs Adobe Fonts" is not a real competition - they are the same product across a rebrand. The meaningful comparison is against Adobe Fonts documentation (current naming) and against free, self-hostable services. If you are choosing fresh today, you would evaluate it as Adobe Fonts; if you are auditing an existing or older site, you will likely see it reported as Typekit.

Use Cases

Auditing legacy sites that integrated fonts during the Typekit era and never updated the branding.
Migration planning when moving a site off the subscription model toward self-hosted open-source fonts.
Competitive research: spotting use.typekit.net quickly identifies a site on Adobe's premium font service.
Brand-consistent design for teams that adopted Typekit kits and continue to rely on the same families.
Debugging font-loading issues by reading the wf-* state classes to see whether fonts activated.

When the goal is a complete stack picture, recognizing Typekit is one piece; combine it with the broader workflow in how to find out what technology a website uses.

A step-by-step Typekit detection workflow

Scan the head. View Source and search for typekit. A use.typekit.net/<id>.css link or a Typekit script almost always sits in the <head>.
Watch the network. In DevTools, filter the Network tab by typekit and reload. You are looking for three things: the kit .css or .js, the font files served from Adobe's CDN, and the p.typekit.net beacon.
Inspect the root element. In the Elements panel, watch the <html> element's class attribute during load. The transition from wf-loading to wf-active is the most distinctive Typekit fingerprint, and the per-family wf-<family>-n4-active classes even tell you which typefaces activated.
Query the global. In the Console, type Typekit and press Enter. If a configuration object comes back, the kit is live on the page.
Confirm automatically. Run Wappalyzer or a server-side scan to corroborate the manual findings and capture the kit ID for your notes.

Following this order means you rarely need all five steps - the network filter alone usually settles it - but each layer is an independent confirmation, which matters when a site is heavily scripted and the markup is generated at runtime.

Performance and privacy considerations

Like any hosted font service, Typekit/Adobe Fonts introduces third-party origins (use.typekit.net and p.typekit.net) into the page's request flow, adding DNS, TLS, and connection overhead on top of the font downloads. The asynchronous loader mitigates render-blocking, and the staged wf-* classes give you control over the flash of unstyled text, but the third-party hops are a genuine performance cost. On privacy, those same requests transmit visitor IP addresses to Adobe-controlled servers, which is the same class of concern behind the widely discussed Google Fonts GDPR rulings. Because the subscription licensing model does not permit freely self-hosting these fonts, consent management is usually the practical compliance path for EU-facing sites rather than first-party hosting. Treat this as a flag to investigate, not as legal advice.

Frequently Asked Questions

Is Typekit still a thing in 2026?

The Typekit brand was retired in favor of Adobe Fonts in 2018, but the service still serves from Typekit domains (use.typekit.net), so the name persists in detection tools and developer discussion. When you see "Typekit" today, it means Adobe Fonts.

What is the difference between Typekit and Adobe Fonts?

There is no functional difference - Typekit is the former name and Adobe Fonts is the current one for the same Adobe subscription font service. The rebrand also removed some standalone Typekit plan options and folded everything into Creative Cloud.

How do I know if a site is using Typekit?

Check for a use.typekit.net stylesheet or script, look for wf-loading/wf-active classes on the <html> element, query the Typekit global in the Console, and watch for p.typekit.net requests in the Network tab. Wappalyzer and StackOptic detect it automatically.

Are Typekit fonts free?

No. Typekit/Adobe Fonts is a subscription service tied to Adobe Creative Cloud. There is no free tier, and the fonts stop serving if the subscription lapses. For free, self-hostable typefaces, Google Fonts is the common alternative.

Why do I still see use.typekit.net if the service is called Adobe Fonts?

Adobe kept the Typekit serving domains for backward compatibility so existing embed codes would keep working after the rebrand. That is why the legacy use.typekit.net and p.typekit.net hosts remain the most reliable detection signals for the service.

Need to know whether a site runs Typekit, Adobe Fonts, Google Fonts, or self-hosted type - straight from the URL? Analyze it with StackOptic.

Typekit

Websites Using Typekit