You've just taken over a website from a previous developer. The design looks great, but you have no idea which fonts are being used or whether they're properly licensed.
This happens constantly. A client switches agencies, a freelancer disappears, or you're maintaining a site someone else built. The fonts work fine, but you need to know: what are they, where did they come from, and are we allowed to use them?
Here's your practical guide to identify fonts on website projects you've inherited and sort out the licensing.
Step 1: Run an Automated Font Scan
Start with an automated tool rather than digging through code manually. Scan your website with FontReport to get an instant breakdown of every font being loaded.
You'll see:
Exact font names and weights
Where fonts are hosted (local server, Google Fonts, Adobe Fonts CDN)
Whether fonts appear commercial or open source
Obvious licensing red flags
This takes about 30 seconds and beats inspecting stylesheets for hours.
Step 2: Check How Fonts Are Being Loaded
Once you know which fonts are on the site, figure out how they're implemented. Understanding whether fonts are licensed for desktop or web use is critical - learn more about the difference between desktop and web font licenses.
Self-Hosted Font Files
If fonts load from the site's own server (usually /fonts/ or /assets/fonts/), track down the source files and license documentation.
Check:
Theme fonts folder
Uploads directory
Custom plugin folders
Root-level assets directory
Look for license files like OFL.txt, LICENSE.txt, or README.md that indicate the font source and permissions.
Google Fonts or CDNs
If fonts load from fonts.googleapis.com, use.typekit.net, or other CDNs, that's usually good news.
Google Fonts are open source and licensed under the SIL Open Font License or Apache License, so you're clear to use them. Adobe Fonts (formerly Typekit) requires an active Creative Cloud subscription, so verify the client has one.
Unknown Sources
Fonts loading from random URLs, discontinued services, or unfamiliar domains are red flags that need immediate attention.
Step 3: Identify Commercial Fonts Without Documentation
If you found self-hosted commercial fonts but no license documentation, identify them and verify licensing.
Use Browser DevTools
Open your browser's inspector (F12 or right-click > Inspect) and check the Network tab while loading the page. Filter by "font" to see all font file requests. Each font file shows:
Font family name in the response headers
File format (WOFF, WOFF2, TTF)
Exact URL where it's served from
Try Font Identification Tools
Browser extensions like WhatFont let you hover over text to see the font name. This identifies the family but won't tell you about licensing.
For difficult fonts, use visual identification tools like WhatTheFont or Font Squirrel's Matcherator. Upload a screenshot and these services suggest matching fonts.
Step 4: Research the Font Foundry
Once you know which fonts you're dealing with, look up the original foundry.
Search for "[font name] license" to find the official foundry page. Common foundries include:
Monotype
(Helvetica, Futura, classics)
Adobe Fonts (formerly Typekit)
MyFonts
(marketplace)
Hoefler&Co, Lineto, Grilli Type, Commercial Type (boutique foundries)
Check the foundry's site for:
Current licensing terms
Whether web licenses are sold separately from desktop
Page view limits or domain restrictions
License transferability to new owners
Step 5: Contact the Previous Developer
If you're stuck, reach out to whoever built the site. They should provide:
Font license purchase confirmations
Account credentials for font services
Original font files with license documentation
Be clear you need this for legal compliance. If they're unresponsive or can't provide proof, assume the fonts aren't properly licensed.
Step 6: Check Client Records
Sometimes font licenses were purchased by the client. Ask them to search their email and invoices for:
Receipts from MyFonts, Adobe, or font retailers
Font service subscription confirmations
Creative Cloud subscriptions that include font access
Adobe Creative Cloud subscriptions include access to Adobe Fonts for web use. Verify which fonts are available at fonts.adobe.com.
What to Do If You Find Unlicensed Fonts
If you discover unlicensed commercial fonts, here's your action plan. Keep in mind that companies have paid thousands for font licensing mistakes, so addressing these issues promptly is important:
Option 1: Purchase the Proper License
Contact the font foundry and purchase a web font license for the site. Expect to pay $40 to $200+ per font family per year, depending on the foundry and traffic.
Purchase the license in the client's name or transfer it to them.
Option 2: Replace with Licensed Alternatives
If the original font is too expensive or unavailable, find a similar font you can license affordably. Check out our guide to free fonts for commercial use to find legitimate alternatives. Browse Google Fonts for good matches.
Choose a replacement with similar x-height, character width, and overall feel so the design doesn't break.
Option 3: Use System Fonts
As a last resort, replace custom fonts with system font stacks. Modern CSS stacks like -apple-system, BlinkMacSystemFont, "Segoe UI", Helvetica, Arial, sans-serif look professional and have zero licensing concerns.
This isn't ideal if the design relies on the original font's character, but it eliminates legal risk immediately.
Document Everything
Once you've sorted out the fonts, create documentation for the next person.
List for each font:
Font family and weight
Source (Google Fonts, self-hosted, etc.)
License type (OFL, commercial web license, etc.)
Purchase date and license holder name
Page view limits or domain restrictions
Renewal dates for subscription licenses
Store this in the project repository or give it to the client.
What if I can't identify a font on the website?
If browser tools and visual identifiers don't work, the font might be in an unusual format or heavily modified. Try downloading the font file from the Network tab in DevTools, then open it in a font viewer application. The font metadata should reveal the family name and foundry. If that fails, replace it with a similar alternative rather than spending hours on detective work.Can I keep using fonts if I can't find the original license?
No. If you can't verify that a commercial font is properly licensed, assume it isn't. Either purchase the correct license or replace the font with a properly licensed alternative. Using unlicensed commercial fonts puts both you and your client at legal risk.What happens if the previous developer used a font illegally?
You're not responsible for past violations, but you are responsible once you're aware. If you discover unlicensed fonts, address them promptly by purchasing licenses or replacing the fonts. Document when you discovered the issue and the steps you took to resolve it.Are fonts from theme bundles properly licensed?
Not always. Some WordPress themes bundle commercial fonts without proper licensing, or their licenses don't transfer when you purchase the theme. Check the theme documentation and, when in doubt, verify with the font foundry or replace with open source alternatives.Prevent This Problem Next Time
Make sure this doesn't happen again:
Document font sources and licenses at project start
Include font licensing in your handoff checklist
Store license receipts in a shared location with the client
Use FontReport periodically to verify nothing changed
Include font licensing requirements in agency contracts
The 30 minutes you spend documenting fonts now saves hours of detective work later.
Clean Up Your Font Situation Today
Don't know which fonts are on your inherited website? Scan your website with FontReport to get a complete breakdown of every font in use, along with potential licensing issues to address.
