Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.

To check whether a website’s fonts are properly licensed, identify the exact font files and how the site delivers them, then compare that implementation with the terms for those specific fonts. A desktop license does not necessarily permit web use, and a screenshot or automated scan cannot establish that contractual rights exist. This is a practical compliance screen, not a universal legal test; the rights depend on the applicable license and service terms.

What a website font compliance check can—and cannot—tell you

A useful check answers two separate questions: what font is the site actually serving, and do the relevant terms permit that particular use? The font’s name alone is not enough. You need to know its source, the files or service involved, and whether it is self-hosted or delivered by a provider.

A visual review can help identify typography, but it cannot reliably identify the underlying font file or prove that the site has a license. A technical inspection can reveal loaded font families and network requests; it still cannot determine the contract rights associated with them. Treat the result as a way to find what needs to be checked, not as a legal clearance certificate.

  • Font identity: Record the family name and, where possible, the specific files or styles being loaded.
  • Delivery source: Determine whether the font comes from a hosted provider or from files served by the site itself.
  • Permission: Locate the license or service terms for that font and deployment method.
  • Coverage: Check whether the relevant site, client, account, domain, and ongoing conditions are covered.

Do not infer web rights from a font appearing in a desktop application, a design-tool menu, or a general “commercial use” description. The actual license controls.

Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.

How to check a website’s fonts

  1. Inspect the live implementation. Open the site in a browser and use its developer tools to inspect rendered text and network activity. Look for font-family declarations and font requests, commonly identifiable by file extensions such as WOFF or WOFF2, or by requests to a font-hosting service. Also inspect the site’s stylesheets and asset configuration if you manage the site. This is a practical inspection method, not a prescribed legal audit procedure.
  2. Build an inventory. For each font in use, record the displayed family, styles or weights, file names or provider, and the pages or components that load it. Note whether it is served by the provider or hosted on your own infrastructure. A family name may not uniquely identify the foundry or the exact license, so follow the file or service back to its source.
  3. Find the terms for that exact font. Identify the foundry, authorized reseller, or font service and locate the applicable license or account terms. Confirm that the terms cover website display or web embedding, not only desktop installation or print work. Fort Foundry’s desktop license is one concrete example: it excludes website use and directs users to a separate web license.
  4. Compare the terms with deployment. Check which website or project is covered, who holds the license, whether the font is provider-hosted or self-hosted, and whether any domain, subscription, or other conditions apply. Do not assume another font’s license or a general industry practice answers these questions.
  5. Keep records. Retain the applicable license or service terms, purchase or subscription records, the font and source inventory, and a note of how the production site delivers the font. The sources reviewed do not establish a universal evidence-retention period, so keep records in line with your organization’s needs and applicable obligations.
  6. Resolve uncertainty with the rights holder. If the terms do not clearly cover the live setup, ask the foundry or an authorized reseller for clarification. For a disputed or consequential question, consult a qualified legal professional.

Check the license against the way the font is served

Provider-hosted web fonts

When a font service hosts the files, verify that the account and service terms permit the website to use them. Check who is responsible for the account, whether the site or client is covered, and whether use depends on an active subscription or other conditions. Those requirements vary by provider and service.

Self-hosted font files

When the site serves font files from its own infrastructure, verify that the license expressly permits that web use and covers the relevant project. A desktop license should not be treated as permission to upload and serve the font. Fort Foundry’s desktop terms illustrate why: they exclude website use and point to a separate web license.

Adobe’s web-font guidance distinguishes local hosting from use through its hosted service: Adobe says self-hosting requires a license from the font’s foundry or an authorized reseller. Do not assume that access to a font through one service automatically grants the right to download and host it yourself.

Client and agency websites

If you build or maintain a client’s site, confirm which account or license covers the client’s production deployment. Adobe’s FAQ says client websites must load Adobe Fonts through their own Creative Cloud subscription to ensure uninterrupted licensing or hosting. Check the current terms for the actual account and project rather than assuming an agency’s access covers every client indefinitely.

Free tools Windows power users keep installed

One-click scans. No signup required.

Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.

Adobe Fonts: use the account embed code for website display

For Adobe Fonts, follow Adobe’s service-specific instructions rather than copying font files into your site. Adobe’s support guidance states: “To display fonts on your website, you must use the embed code provided in your account to ensure proper licensing.” Use the embed code provided in the account for the relevant project.

Adobe says its library includes web and desktop use while a Creative Cloud subscription is active, and its web guidance describes Adobe as hosting the web fonts. The subscription condition matters: check that the actual account remains active and that the project is covered under the applicable terms. For a self-hosted implementation, Adobe says to obtain a license from the foundry or an authorized reseller. Adobe’s FAQ also describes the client-site account requirement above. These points are specific to Adobe’s service and should not be generalized to other providers.

What to document for a defensible internal review

A compact record makes it easier to revisit a site after a redesign, account change, or font migration. For each font, keep:

  • Family name, style or weight, and file name or provider, as identified from the live implementation.
  • The source of the font and whether the site uses provider hosting or self-hosting.
  • A copy or record of the relevant license, purchase, or service terms, including the date checked.
  • The account, project, site, or domain that the terms cover, where the terms specify one.
  • Any subscription or other continuing condition stated by the rights holder.
  • A brief record of the production implementation, including embed code or asset location where useful.
  • Any written clarification from the foundry or authorized reseller if the terms were ambiguous.

This documentation helps show what you checked and how the site was configured. It does not itself create rights that the license does not grant.

What’s actually slowing this PC down?

Pick the symptom - the matching free tool is one click away.

Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.

Use screenshots to document appearance, not to certify rights

A screenshot can preserve how a page looked during a review or help a team compare typography before and after a change. It cannot tell you whether the font file is licensed, which account covers it, or whether the relevant terms permit the implementation. Pair a screenshot with the font inventory and license records rather than treating the image as proof of compliance.

For a quick visual record, you can capture a page with ScreenshotNeo, a website screenshot API and MCP server from Yorker Media. For example, this cURL request returns a screenshot of the site; see the ScreenshotNeo API documentation for request options.

curl -G "https://api.screenshotneo.com/v1/shot" -d access_key=YOUR_API_KEY --data-urlencode url=https://example.com -o font-review.webp

Or skip the browser setup

One GET request captures the page. ScreenshotNeo removes cookie and consent banners, newsletter popups, and chat widgets before capture; each cleanup step can be turned off. Bot checks, blank pages, failed loads, timeouts, and cache hits are not billed, and response headers report the page verdict and billing status. Its MCP server lets AI agents use tools including take_screenshot, get_page_info, and capture_pdf. The Free plan includes 1,000 screenshots a month with no card; paid plans start at $5 for 3,000 shots. A screenshot remains visual documentation—not evidence of font licensing. Learn about ScreenshotNeo.

Sign up free for 1,000 screenshots a month, with no card required.

Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Support on Ko-Fi

Common problems and how to resolve them

The font name is visible, but the source is unclear

A CSS family name or rendered appearance may not identify the foundry or exact file. Inspect network requests and site assets, then trace the file or service to its source. If you still cannot establish the source, do not assume the font is covered; replace it with a known, properly licensed option or obtain clarification before relying on it.

A desktop license is the only record you can find

That record may not grant the right to serve the font on a website. Check the license language for web embedding or website use and locate any separate web license. Fort Foundry’s terms are an example of a desktop license that excludes website use. If the relevant terms remain unclear, contact the foundry or reseller.

A hosted font is being copied to the site

Do not assume the hosted-service permission also allows self-hosting. Confirm that the license explicitly covers local hosting. Adobe’s guidance says self-hosting requires a license from the foundry or an authorized reseller.

An agency subscription is being used for a client site

Verify that the actual service terms cover that client’s site and that required account conditions are met. Adobe’s FAQ describes client websites loading fonts through their own Creative Cloud subscription. Ask the provider or rights holder if the account arrangement is uncertain.

Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.

A scanner reports no obvious font issue

That is not proof that a license exists. A scanner or screenshot can help with technical discovery or visual review, but it cannot establish the contractual rights attached to the font. Confirm the license and deployment with the rights holder.

Questions to ask before approving a font

  • Have we identified the actual font files or hosted service used in production?
  • Do the terms for this exact font permit website display and the delivery method we use?
  • Is the relevant website, client, account, or project within the license’s scope?
  • Are there active-subscription, domain, or other ongoing conditions we must maintain?
  • Can we produce the applicable terms and show that the live implementation matches them?

If you cannot answer one of these questions from the terms and deployment records, treat it as unresolved and seek clarification rather than treating a visual or technical check as legal approval.

Frequently Asked Questions

Can I use a font on my website if I bought a desktop license?

Not necessarily. Check whether the license explicitly grants web use; some desktop licenses exclude it and require a separate web license.

Does a screenshot prove that a website’s font is licensed?

No. It can document appearance, but it does not establish the font’s source, license, account coverage, or permitted use.

Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.

Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.