MyFonts

What Is MyFonts?

MyFonts is a large web-font marketplace and font-hosting service owned by Monotype, one of the world's major type companies. It serves two related audiences: designers and businesses who want to buy and license fonts from an enormous catalog spanning independent foundries and well-known type houses, and website owners who want to embed web fonts on their pages through MyFonts' hosting and delivery. In short, MyFonts is both a store for typefaces and a way to serve licensed fonts on the web.

Its scale is its defining characteristic. MyFonts has long been described as one of the largest collections of fonts available for licensing, aggregating the libraries of many independent foundries in a single storefront. That breadth is the main reason a designer visits MyFonts: rather than tracking down a foundry's own site, they can search a vast catalog, preview families with custom text, and license desktop, web, and other font formats in one place. For web use specifically, MyFonts provides a web-font hosting mechanism, the page references a MyFonts-hosted script or stylesheet, and MyFonts serves the licensed font files.

MyFonts is a hosted commercial service, not a browser extension or a free open-source library. Using a MyFonts web font on a site involves a licensed web-font project and an embed, either a small JavaScript tracker and CSS, or a self-hosted kit you download, governed by the terms of the web-font license. This commercial, license-based model is a key contrast with free services like Google Fonts or Bunny Fonts, where the typefaces are open-source.

It helps to frame who MyFonts is for. The service targets professional designers, brand teams, and businesses that need specific, often premium or distinctive typefaces, the kind not available in free libraries, and that are prepared to license them properly. Because it is owned by Monotype and aggregates many foundries, MyFonts is a go-to destination when a project's typography calls for a particular commercial family rather than a generic open-source alternative. That positioning, a broad marketplace for licensed type plus the means to serve it on the web, explains both why designers buy there and why its web-font embeds appear on brand-conscious sites.

How MyFonts Works

MyFonts operates first as a marketplace. Designers browse or search the catalog, preview typefaces by typing custom sample text and adjusting size, and then purchase licenses. Licensing is format- and usage-specific: a desktop license covers using the font in design software, while a web-font license covers embedding the font on a website, typically priced by metrics such as page views or sold as a defined allowance. This licensing structure is central to the commercial model and distinguishes MyFonts from free font CDNs.

For web use, MyFonts provides web-font hosting. After acquiring a web-font license, the site owner sets up a web project and embeds the fonts. Historically this has involved a small JavaScript snippet plus a CSS file that defines the @font-face rules and points to MyFonts-hosted font files; the script also handles font-loading behavior and license tracking. Alternatively, a license may allow a self-hosted kit, where the owner downloads the font files and the CSS and serves them from their own domain, subject to the license terms.

When a page loads a MyFonts-hosted web font, the browser requests the MyFonts script and CSS, reads the @font-face declarations, and downloads the font files from MyFonts' delivery infrastructure. The fonts then render in the chosen font-family. Because the embed references MyFonts' domains, the network requests point at MyFonts hosts rather than the site's own server, which is what makes the hosted form detectable.

It is worth situating MyFonts within Monotype's broader ecosystem. Monotype operates several type properties and web-font technologies, and MyFonts is the large, foundry-aggregating marketplace among them. The lineage matters for detection because the web-font delivery and tracking scripts associated with MyFonts and Monotype's font services share recognizable domains and naming patterns, historically including hosts and scripts tied to the Fonts.com and MyFonts infrastructure. For a site owner, the practical point is that adopting a MyFonts web font means depending on Monotype's hosting and abiding by a commercial license, rather than pulling a free family from an open CDN.

Two technical realities shape how MyFonts appears on a page. First, the hosted embed typically loads a tracking and loader script plus a CSS file from MyFonts/Monotype domains, so those requests are visible in the Network tab. Second, the @font-face rules carry src URLs pointing at MyFonts-hosted font files. This pairing, a MyFonts script or CSS request plus @font-face sources on MyFonts hosts, is the clearest external fingerprint of the service.

How to Tell if a Website Uses MyFonts

MyFonts leaves recognizable fingerprints when its hosted web fonts are used. Because StackOptic analyzes a URL from the server side, it inspects the same signals you can check manually with View Source, DevTools, or a detection extension.

MyFonts script and CSS domains. The strongest signal is a request to MyFonts' hosting domains, for example a loader/tracker script or a font CSS served from MyFonts hosts (historically hello.myfonts.net for the tracking script and MyFonts/Monotype CDN hosts for font files). A reference to a myfonts.net host is a near-certain indicator of a MyFonts web font.

@font-face source URLs. When you inspect the font CSS, the @font-face rules contain src: url(...) declarations pointing at MyFonts-hosted files. Font-file requests to MyFonts/Monotype CDN hosts in the Network tab confirm the service even if the embed is added dynamically.

The tracking/loader script. MyFonts hosted projects often include a small script (the "MyFonts Webfonts" loader/counter). Spotting that script reference in the page source is a strong secondary signal that the site embeds MyFonts web fonts under a license.

A distinctive licensed font-family. If the applied font-family is a recognizable commercial typeface not found in free libraries, that, combined with a MyFonts request, reinforces the conclusion.

Method	What to do	What MyFonts reveals
View Source	Open the page, right-click, "View Page Source"	A MyFonts loader/tracking script and a <link> to MyFonts-hosted font CSS
Browser DevTools (Network)	Open DevTools, reload, filter by "myfonts"	Requests to myfonts.net hosts for the script, CSS, and WOFF2 files
Browser DevTools (Elements)	Inspect the font CSS / computed styles	@font-face rules with src URLs on MyFonts/Monotype hosts and the applied font-family
Wappalyzer	Run the extension on the live page	May flag "MyFonts" (or Monotype) under fonts when its domain is present
BuiltWith	Look up the domain	Font-service detection alongside the broader stack

A quick command-line check is curl -s https://example.com | grep -i "myfonts". If that returns the loader script or a MyFonts-hosted CSS link, the site is using a MyFonts web font in its hosted form. To identify exactly which typeface is in use, our guide on how to find what fonts and colors a website uses explains how to read @font-face rules and computed styles, and the broader methodology is in how to find out what technology a website uses.

It is worth noting an important caveat. Like other font services, MyFonts is only externally visible when the site uses the hosted embed. If a license permits and the owner has downloaded a self-hosted kit and serves the files from their own domain, the page will show @font-face rules pointing at the site's own URLs, with no MyFonts request, so the origin of the font is not directly visible. When the hosted embed is used, however, the signals are clear: the loader script, the MyFonts-hosted CSS, and the CDN font requests all point at MyFonts/Monotype infrastructure, and because the embed genuinely loads from those domains, the fingerprint is hard to disguise without self-hosting. The presence of a distinctive commercial typeface is a helpful corroborating clue, since free CDNs do not carry such families. Server-side analysis helps by reading the raw HTML and catching the embed references even when scripts would add them after the page loads, and combining multiple signals yields a confident verdict.

Key Features

• Vast font marketplace. One of the largest catalogs of licensable fonts, aggregating many independent foundries in a single storefront.
• Commercial and premium typefaces. Access to distinctive, professionally crafted families not found in free libraries.
• Format-specific licensing. Separate desktop, web, app, and other licenses to match how the font will be used.
• Web-font hosting. A hosted embed (loader script plus CSS) that serves licensed fonts on websites.
• Self-hosted kits. The option, where the license allows, to download and serve fonts from your own domain.
• Custom previews. Type your own sample text and adjust size to preview a family before licensing.
• Monotype backing. Ownership by a major type company, with a large foundry network and established infrastructure.

Pros and Cons

Pros

• Enormous selection, including premium and distinctive typefaces unavailable in free libraries.
• A single storefront aggregates many foundries, simplifying discovery and licensing.
• Clear, format-specific licensing for desktop, web, and other uses.
• Backed by Monotype, with established hosting and a long track record.

Cons

• Commercial licensing means real costs, unlike free open-source font services.
• Web-font licenses are often metered (for example by page views), which requires attention as traffic grows.
• The hosted embed adds a third-party script and font requests, with potential page-speed impact.
• More complex to adopt than simply linking a free font CDN, given the licensing step.

MyFonts vs Alternatives

MyFonts competes with both commercial font services and free web-font libraries. The table below clarifies where it fits.

Service	Model	Catalog type	Best for
MyFonts	Marketplace plus hosting (commercial)	Vast, many foundries, premium	Buying and serving specific licensed typefaces
Adobe Fonts	Subscription (with Creative Cloud)	Large curated commercial library	Designers in the Adobe ecosystem wanting included fonts
Google Fonts	Free hosted CDN	Open-source families	Sites wanting free, convenient web fonts
Bunny Fonts	Free hosted CDN (privacy-first)	Open-source families	Privacy-conscious teams replacing Google Fonts
Self-hosted (any source)	Files on your own domain	Whatever you license/download	Maximum control over delivery and performance

If you are comparing commercial, subscription-based hosting, it is useful to place MyFonts next to another major option; see Adobe Fonts, which uses a subscription model rather than per-font licensing. For identifying any font provider's signals on a page, how to find what fonts and colors a website uses is the practical companion, and performance considerations for licensed fonts are covered in how to optimize web fonts for performance.

Use Cases

MyFonts is most at home with brand and design work that calls for a specific, often premium typeface rather than a generic open-source family. A studio designing a brand identity might license a distinctive display face from MyFonts for the client's logo and headlines, then license the matching web font to carry that identity onto the website. A company with established brand guidelines that specify a commercial typeface uses MyFonts to license and embed that exact font on its site, keeping print and web consistent.

It also serves designers who simply want the broadest possible selection when exploring options, MyFonts' aggregation of many foundries makes it a natural starting point for discovery and custom previews. Businesses that need proper, documented licensing for legal or brand-compliance reasons value the clear, format-specific licenses. Teams that prefer to control delivery may license a font and use a self-hosted kit, serving the files from their own domain while remaining within the license terms.

Consider a few concrete scenarios. A consumer brand relaunching its website might license its signature typeface's web font from MyFonts so the new site matches its packaging and advertising exactly. A publisher might license a refined text face for long-form readability that no free library offers. An agency might use MyFonts to evaluate and preview several candidate typefaces with the client's real copy before committing to a license. In each case the common thread is a need for a particular, professionally licensed typeface, and a willingness to pay for it, that free services cannot satisfy.

From a technology-research standpoint, detecting MyFonts on a site is a meaningful signal. It indicates a brand or designer investing in commercial typography and licensing fonts properly, often a marker of a design-conscious organization with real brand standards. For vendors and analysts profiling a site's stack, distinguishing a licensed, marketplace-sourced web font from a free CDN adds useful nuance about how seriously the owner treats design and compliance. Surfacing that signal automatically across many domains, rather than inspecting each site by hand, is exactly what a technology-detection scan is built to deliver.

Frequently Asked Questions

What is the difference between MyFonts and Google Fonts?

MyFonts is a commercial marketplace and hosting service for licensed fonts, including premium and distinctive typefaces from many foundries, whereas Google Fonts is a free library of open-source families. With MyFonts you buy a license (desktop, web, and so on) and embed the font under its terms; with Google Fonts the fonts are free to use. MyFonts is the place to go for a specific commercial typeface, while Google Fonts (or a privacy-first equivalent) suits sites that want free, convenient fonts.

How can I tell if a website uses MyFonts?

Check the page source for a MyFonts loader/tracking script and a stylesheet link to MyFonts-hosted font CSS (historically on myfonts.net hosts such as hello.myfonts.net). In the DevTools Network tab, look for requests to MyFonts/Monotype domains for the script, CSS, and font files. Extensions like Wappalyzer and BuiltWith may flag it. A quick curl -s URL | grep -i myfonts confirms hosted usage; if the site self-hosts the kit, MyFonts will not appear directly.

Are MyFonts web fonts free?

No. MyFonts is a commercial marketplace, so fonts must be licensed, and web-font use requires a web-font license that is often metered by usage such as page views. This is a fundamental difference from free services like Google Fonts or Bunny Fonts, whose typefaces are open-source. The cost buys access to a vast catalog of premium and distinctive typefaces not available for free.

Can MyFonts fonts be self-hosted?

In many cases, yes, depending on the specific license. MyFonts has offered self-hosted web-font kits that let a licensee download the font files and CSS and serve them from their own domain, rather than relying on the hosted embed, provided they stay within the license terms (such as page-view allowances). Self-hosting can improve performance and remove a third-party request, but the license still governs how the font may be used.

Does MyFonts belong to Monotype?

Yes. MyFonts is owned by Monotype, a major global type company. Monotype operates several font properties and web-font technologies, and MyFonts is its large, foundry-aggregating marketplace. This backing is why MyFonts offers such a broad catalog and established hosting, and why its web-font delivery shares infrastructure and naming patterns associated with Monotype's font services.

Want to detect MyFonts and the full stack behind any site in seconds? Try StackOptic at https://stackoptic.com.