Font Finder

Detect fonts used on any website - Google Fonts, @font-face declarations, and font-family stacks. Enter a URL to see font samples.

Enter Website URL

About the Font Finder

The Font Finder detects all fonts used on any public website by fetching its HTML and stylesheets server-side to bypass browser CORS restrictions. It identifies Google Fonts API links, @font-face declarations and CSS font-family stacks, then renders a live preview of each font so you can see exactly how it looks. It's the fastest way to identify a typeface you spotted on a site you admire.

Common use cases

Frequently Asked Questions

How does Font Finder detect fonts on a website?

Font Finder fetches the target page's HTML server-side to bypass CORS restrictions, then parses the markup and linked stylesheets looking for three types of font references: Google Fonts API URLs (e.g., fonts.googleapis.com), @font-face declarations that specify a custom typeface and source file, and inline font-family CSS rules on body and heading elements. Each detected family is then loaded into the preview panel so you can inspect its weight, style, and rendering at a glance.

Can Font Finder detect fonts on pages that require login?

No - Font Finder can only fetch publicly accessible pages. Password-protected pages, pages behind a CDN that blocks server-side requests, or single-page applications that load fonts dynamically via JavaScript after the initial HTML response may not have all fonts detected. For SPAs or JavaScript-rendered pages, the most reliable method is to open the page in Chrome DevTools, go to the Network tab, filter by "Font", and inspect the loaded font files directly.

Does fetching a URL through this tool expose my query to the target site?

When you enter a URL, our server makes an HTTP GET request to that address on your behalf - this means the target site's server logs may record a request from our server's IP address, not yours. The URL you enter is used only to retrieve fonts and is not stored or shared. No authentication cookies, session data, or browser fingerprints from your own browser are forwarded to the target site, so your personal identity is not revealed in the process.

What are the limitations of browser-based font detection?

Font Finder cannot detect fonts that are loaded lazily via JavaScript after page load (e.g., fonts injected by a tag manager or a design system at runtime). It also cannot identify fonts embedded directly inside SVG elements or bitmap images - for image-based text, a tool like WhatTheFont or a reverse image search for fonts is more appropriate. Additionally, self-hosted fonts served from a CDN with restrictive CORS headers may not be loadable into the preview panel even when their names are successfully detected.

How does this compare to WhatFont or similar browser extensions?

Browser extensions like WhatFont identify the font of a specific element you click on in a live rendered page, giving you per-element precision including font weight, size, and line height. Font Finder takes a different approach: it analyses the entire page's source to give you an overview of all fonts used across the site without needing to install an extension. It's ideal for auditing a site you can't visit interactively or for quickly identifying fonts on a competitor's site from any device without any installation.