Paste a URL to see which fonts are used in CSS by default—sources, selectors, and open-source alternatives. Expand the results for theme bundles and icon fonts.
Check which fonts a website uses by analyzing linked CSS, @font-face rules, and font provider URLs.
A website font checker helps you discover which typefaces a site references in its stylesheets—Google Fonts, Adobe Fonts (Typekit), self-hosted WOFF2 files, or system font stacks. FontLeech crawls public HTML and linked CSS, then organizes families, evidence, and usage hints so designers and developers can audit typography without guessing from screenshots.
Google Fonts typically loads from fonts.googleapis.com and fonts.gstatic.com. Adobe Fonts often uses Typekit hosts such as use.typekit.net. Self-hosted fonts appear in @font-face rules with same-origin src URLs. FontLeech labels each family using these patterns—not assumptions from the family name alone.
Login walls, bot protection, heavy client-side rendering, CSS-in-JS, lazy-loaded stylesheets, and CORS limits can all reduce coverage. When that happens, results may be partial or empty even though the site looks styled in your browser. For local inspection, use browser DevTools or a page-specific extension alongside this tool.
Building your own stack? Try the Web Font Generator, Font Comparison, or Typography Scale Calculator.
FontLeech shows fonts in use first—families referenced in font-family on crawled CSS selectors. WordPress themes often ship a google-font.css cache with many @font-face rules; those appear under theme bundle / preloaded unless they are actually used. Icon/plugin fonts (WooCommerce, dashicons) and generic system stacks are listed separately. Deferred stylesheets (Flying Press data-href, Bunny CDN) are included in the crawl.
Not always. FontLeech analyzes HTML and CSS it can fetch from a public URL. That reveals declared font-family names, @font-face rules, and links to Google Fonts, Adobe Fonts, or self-hosted files. It does not execute the site’s JavaScript or replicate DevTools computed styles.
The family name appears in CSS, but no matching @font-face resource was found in the stylesheets we crawled. The site may load fonts dynamically, use CSS-in-JS, or block stylesheet access.
No. Alternatives are suggestions from the Google Fonts catalog with licensing links. They are similar open-source options—not guaranteed visual matches.
We fetch HTML and CSS for analysis. We do not package or redistribute font binaries from third-party sites. Previews use Google Fonts only when an alternative or catalog match is available.
