Signal pendingNo paid features detectedMedium-risk permissions

Font Detector

Use font detector to identify any font on a webpage instantly with this font identifier and recognition tool!

Users850Current public install base

Rating--Store average score

Reviews0Public review volume

Manifest versionV3Extension platform version

7-day growth--Net users gained this week

7-day growth rate--Relative weekly velocity

Preview

Font Detector Media preview

2 assets

Trend

30-day user trend

Review user movement over the last 30 days.

User Growth Over Time

Rating trend

30-day rating change

Track rating movement over time to see whether quality signals remain stable.

Not enough rating snapshots yet. More data will appear as new snapshots are collected.

Growth overview

Daily, weekly, and monthly growth

Compare 1-day, 7-day, and 30-day net growth and growth rate.

1-day growthNo data

----

7-day growthNo data

----

30-day growthDeclining

-58-6.39%

Technical snapshot

Version, languages, and crawl freshness

Review publication date, version, supported languages, and crawl timestamps.

Version1.2

ManifestV3

Size161KiB

Languages52Deutsch / English / Filipino +49

Published--

Store updated--

Last crawled--

Overview

Product summary

Review the store description, core capabilities, and common use cases.

🔍 This extension is a very helpful tool for every designer, developer, and typography enthusiast. Font Detector is your go-to solution for identifying fonts on any webpage with ease.

💯 Whether you're looking for a new typeface for your project or simply exploring the world of fonts, our extension has got you covered.

🧐 Why choose our font detector?

👍🏼 Effortless font detection: say goodbye to the guesswork! With our font detector extension, discovering the name, style, and family on webpages is as simple as a click.

👍🏼 Comprehensive database: leveraging an extensive database, our app can accurately identify a wide range of typefaces, from the most popular to the obscure.

👍🏼 User-friendly interface: designed with simplicity in mind, our font identifier provides a seamless user experience, making font discovery accessible to everyone.

Reviews

Recent review snapshot

Inspect the latest comments and rating distribution.

5★

4★

3★

2★

1★

Similar and related extensions

Review related products from the Chrome Web Store detail page.

Web Scraper - Free Web Scraping

Workflow & Planning

Web data extraction tool with an easy point-and-click interface for modern web

Whats the Font

Tools

Use Whats the Font – a simple typeface recognizer for any site. Check typeface with this font finder and easy font identifier tool.

Font Detector – What font is this?

Developer Tools

Font Detector is a fast and free font finder tool that helps you identify any font on a webpage instantly. What font is used here?

Font Recognition

Tools

Use the Font Recognition to quickly identify types on any page. Our font Finder also makes it easy to download the identified font.

Font Finder & Style Detector

Tools

Discover the perfect font effortlessly with our Font Finder & Style Detector extension! Seamlessly integrated into your browser.

Font identifier

Tools

Font identifier - simplifies the process of identify fonts on any webpage with a one-click font finder tool, saving users time.

AI product read

Identify fonts used on webpages

Helps designers and developers quickly identify typography (font name, style, family) on any webpage without manual inspection.

User installs extension -> Extension adds context menu and action button -> User clicks icon or right-clicks -> Extension injects content script -> User hovers over text -> Extension displays font information in a popup.

Target users: Designers / Developers / Typography enthusiasts

The store description mentions an 'online font detector' and 'AI-powered' recognition, but the source code only implements local CSS-based font detection. The external URL is only opened on install. It is unclear if the external service offers additional features not present in the extension.

Monetization

No paid features detected

The extension is explicitly described as 'Free to use' in the store description. No payment APIs, subscription logic, or premium feature gating were found in the source code. The keyword 'pro' found in locale files is part of the word 'project' or similar context, not a paid tier.

Confidence: 95
Payment platform: --
Source: AI / High
Login required: Yes
Reason: The extension's background script opens the URL 'https://font-detector.tilda.ws/' upon installation (background.js). This external web service is the primary interface for the 'comprehensive database' and 'AI-powered' detection mentioned in the store description. While the extension itself performs local font-family detection via CSS, the store description implies a deeper service. However, looking closely at content.js, the actual font detection is done locally using `getComputedStyle`. The external URL is likely a landing page or a separate web tool. The extension itself does not require login to function (it uses contextMenus and activeTab). The question is whether the *core product workflow* requires login. The extension works locally. The external site might require login for advanced features, but the extension's core function (detecting font on hover) works without it. However, the prompt asks to judge login from the user's ability to complete the core product workflow. If the extension is just a wrapper for a web app, it's destination_service. Here, the extension *is* the tool. It detects fonts locally. The external link is likely for more info or a separate web version. Let's re-read the description: 'Our online font detector works tirelessly...'. This suggests a web component. But the extension code `content.js` clearly implements the detection logic locally (`getComputedStyle`). The extension does not send data to the server. Therefore, the extension itself does not require login. The external site might, but that's a separate product. Wait, the instruction says: 'If a launcher redirects to a web app that requires an account, requiresLogin.decision should be yes with scope=destination_service.' The extension opens the URL on install. It doesn't force login for every use. The core function (detecting font) is local. So `requiresLogin` should be `no` for the extension. But does the *product* require login? The product is the extension. The extension is free and works locally. The external site is likely just a landing page. I will set `requiresLogin` to `no` because the extension's primary function works without it. If the user clicks the icon, it works. The external link is only opened on install. So the user can use the extension without logging into the external site. Thus, `decision: no`. Wait, let's look at `scope`. If the extension works without login, scope is `none`. If it required login to the extension's own account, it would be `extension_account`. Since it doesn't, `none` is appropriate. However, if the 'product' is considered the service at tilda.ws, then it might be different. But the extension is the product here. It's a local font detector. So `requiresLogin: no`.)

Permission risk

Medium-risk permissions

This estimate uses declared permissions and host permissions to assess access scope and sensitivity.

扩展能力较强：scripting、activeTab

Publisher

The four B

Independent publisher

Email: [email protected]
Phone: --
Address: --

Public contact fields are shown above. Developer portfolio pages are available on paid accounts.

View developer portfolio

Permissions

Host access