Comparison · Typography
Font identifier Chrome extension: which kind to install (and what to check)
The short answer
A font identifier Chrome extension is one of two things: an image matcher that guesses fonts in pictures, or a live-page inspector that reads the exact rendered font of real text. For live text, pick an inspector that works without all-sites access — Font Finder shows the rendered family, weight and size on hover, free and fully local.
- 1
Decide what you are identifying: live text on a page, or lettering inside an image. Only the first is an inspector job.
- 2
At install time, read the permission warning — a hover inspector should not need access to all websites.
- 3
Test it on a page with a fallback-heavy CSS stack and check that it reports the rendered family, not just the first name declared.
- 4
Pin a result and copy the CSS — the output should include weight, size, line height and letter spacing, not just a name.
- 5
Exit (Esc in Font Finder) and confirm the page is restored untouched.
Search for a font identifier Chrome extension and you get a wall of icons that all promise the same thing. Behind them sit two genuinely different kinds of tools — and a few permission habits worth screening for before you add anything to your browser.
Two tools that share one name
Image matchers compare letter shapes in a screenshot against a font database. They exist for lettering that is a picture — logos, posters, image banners — and their answer is a visual best guess. Live-page inspectors read the computed styles of real text on the page: exact and instant, but only for text the browser laid out. Neither replaces the other. Pick by what you are pointing at: pixels need a matcher, live text deserves an inspector.
The checklist before you install
Permissions. Many font extensions request the right to read and change your data on all websites — standing access to every page you ever open, for a tool you use a few times a week. A hover inspector does not need it: Chrome's activeTab grant can inject the inspector only on the tab where you click, only when you click.
Accuracy. The first name in font-family is a request, not a result. A good identifier tells you which family actually rendered and whether it is a web font the page loaded — otherwise you may "identify" a font nobody is actually seeing.
Privacy. Reading computed styles requires no network at all. If an extension phones home, page content may travel with it. Prefer tools that make zero network requests and say so.
Output. A font name is a start; weight, size, line height, letter spacing and a paste-ready CSS block save you the follow-up trip to DevTools.
How Font Finder measures up
Font Finder is built as the strict version of that checklist. It installs with no host permissions and runs on activeTab only; it makes no network requests and needs no account. Hovering any text shows the family that really rendered, with weight and size; clicking pins a detail card with the full stack — rendered family marked, web fonts flagged — and a one-click Copy CSS button. Esc removes the inspector and restores the page untouched. It is free, with no paid tier.
Where its boundary is
To be clear about scope: Font Finder identifies rendered text by reading the page's own computed styles. Lettering inside an image or a logo has no styles to read, so it is out of scope — that is image-matcher territory, and any tool that claims to do both with one mechanism deserves skepticism. Knowing which question you are asking is most of choosing the right extension.