About FontScanner

FontScanner finds the fonts on a website, inside a PDF, or in a screenshot — and puts them in a clear report, including commercial typefaces that may need a review. You can also schedule recurring website scans, run a free homepage check, use the Chrome extension, call the developer API, or deploy the whole product on-prem.

Why FontScanner exists

Most teams cannot name the fonts a live site actually loads. Themes, CDNs, screenshots, and linked PDFs add typefaces that never made it into the brand guide.

We crawl a site the way a browser does, read a PDF you upload, or match visible type in an image. Recurring website scans can run on a daily, weekly, or monthly schedule — in our cloud or on-prem. The same engine powers a free homepage checker, a Chrome extension, a CI API, and an on-prem install for teams that need scans to stay inside their network. The report lists every font we found and flags known commercial families so you can decide what to do next.

Enterprise

On-prem when it needs to stay inside your network

We can install FontScanner on your infrastructure.

Talk to us. FontScanner runs on your network — website and PDF scans stay with you.

See how an on-prem install works →

How it works

From a URL, a file, a screenshot, or the tab you have open — to a report or JSON.

1

Choose how you scan

Full site, scheduled crawl, PDF, image, free homepage check, Chrome extension, or API. No DNS changes.

2

We find the fonts

Pages, CSS, JavaScript, CDN links, linked PDFs, embedded PDF fonts, or visible type in a photo.

3

You get a report — or JSON

A list of fonts, commercial flags, and where they appeared. Export as PDF or receive a webhook.

What we detect

FontScanner finds fonts on live sites, inside documents, and in images.

Google Fonts & Bunny Fonts

Fonts loaded via CDN links, link tags, and @import rules.

Adobe Fonts / Typekit

Commercial fonts loaded through Adobe's Typekit JavaScript and CSS endpoints.

Self-hosted fonts

WOFF, WOFF2, TTF, and OTF files served from your domain via @font-face rules.

CSS stacks & system fonts

font-family declarations in stylesheets, inline HTML, and computed page styles.

Uploaded & linked PDFs

Embedded fonts in PDFs you upload, plus PDFs linked from pages during a site crawl.

Screenshots & images

Visible type in a photo, logo, or mockup — matched against the catalog and flagged when a commercial license is likely.

What the report covers

The same sections you see on a completed scan.

Commercial fonts

Paid typefaces loaded or distributed from the site, with vendor and pages.

PDFs

Embedded fonts in a file you uploaded, or in PDFs linked from the site.

Page by page

Which page loaded which font, and from which CSS or JS file.

License management

You can also keep an inventory of licenses you own. When you scan, those records are matched to the commercial fonts in the report.

Your license list

Store font name, vendor, type, covered domains, seats, dates, and a proof-of-purchase file.

Matched to scan results

Commercial fonts found on a site or in a PDF are checked against your inventory on the same report.

How license matching works →

Who it is for

Anyone who needs a straight answer: which fonts are on this site, in this file, or in this screenshot?

Agencies & studios

Check a client site, a deliverable PDF, or a mockup screenshot before launch.

Brands & stores

See what actually loads on marketing pages and in sales PDFs — or run a 10-second homepage check.

Developers

Catch fonts added by a theme, a widget, or a CDN change — locally in Chrome, automatically from CI on the Enterprise plan, or from an on-prem API inside your network.

IT & security

Keep crawl data on your PostgreSQL or SQL Server. On-prem is for teams that cannot send site content to a SaaS crawler.

Scan your first site free

One scan credit on signup — or start with a free homepage check. No credit card.

Get Started Free