Why installed font permission is restricted in browsers

You open an installed-font checker and it asks to access local fonts, or it shows only a partial list. That restriction comes from the browser, not usually from a Windows or macOS setting. Browsers treat a full list of installed fonts as private information because it can reveal details about your device and contribute to identifying your browser.

Here is what the permission allows, why some browsers cannot provide a complete list, and what to try if the check is blocked. TooLab’s Installed Fonts tool runs in your browser and previews fonts available on your computer.

Check installed fonts in your browser

1. Open the Installed Fonts tool on a computer using Chrome or Edge.
2. If the browser asks to access local fonts, read the prompt and allow access for the TooLab page if you want a full list.
3. Wait for the font list to appear. Select a font to view its preview, or enter your own sample text to see how it looks.
4. If there is no permission prompt or the list is incomplete, check whether your browser supports local font access and whether permission was denied earlier.

Font names and previews are different from font files. The browser can provide the page with names and access to use a font for rendering, but the permission does not give the page general access to browse your computer’s folders or copy font files.

What the result means

The full font list appears

Your browser supports the local font access feature, and the page has permission to use it. The tool can show the fonts the browser reports as installed on that computer. This does not mean every app will use every listed font, since an app can have its own font rules or cache.

The browser asks for permission

This is expected when a site requests the browser’s Local Font Access capability. The browser asks first because a broad font list can reveal information about the device. Allow access only on a site where you want to use this feature. You can revoke it later in the site’s permissions.

The list is missing or incomplete

Your browser may not support full font enumeration, may offer only a reduced version, or may have blocked the permission. Installed Fonts works in Chrome and Edge on a computer. Other browsers may show fewer fonts or none, so a short list is not proof that fonts are missing from the computer.

The permission is disabled or controlled by an administrator

A browser setting, work or school policy, or privacy-focused configuration may prevent the request. If the browser is managed by an organization, its administrator may disable local font access. Changing a Windows or macOS font setting will not override a browser policy.

How to allow or restore font access

1. Check the browser prompt. If it appears when you open the tool, allow local font access only if you want the page to show your installed fonts. If you dismissed it, reload the page and check whether the browser offers the request again.
2. Review the site permission. In Chrome on Windows 11 or macOS, open the browser menu, then go to Settings › Privacy and security › Site settings › Additional permissions › Local fonts. Find the TooLab site and change its setting if it is blocked. Menu labels can differ slightly by version.
3. Check Edge’s site settings. In Edge on Windows 11 or macOS, open Settings › Cookies and site permissions › All permissions › Local fonts, then review the permission for the TooLab site. If you do not see this option, your Edge version or settings may not expose the feature.
4. Reload the tool. After changing a permission, return to Installed Fonts and reload the page. A permission change may not update a page that was already open.
5. Try a supported desktop browser. If you are using a browser that does not provide local font access, open the tool in an up-to-date desktop version of Chrome or Edge. Phones and tablets are not the intended environment for this full font check.
6. Check for managed settings. If the permission is locked, or the browser says it is controlled by your organization, contact your IT administrator. Do not change system font files to fix a browser permission problem.

There is no general Windows 11 or macOS privacy switch that grants a website access to every installed font. This is a browser-level site permission. You do not need to reinstall fonts or give the browser access to your documents.

Why browsers limit access to fonts

A list of fonts can act like a device clue. People who install specialist, regional, or less common fonts may have a more distinctive list than someone using only common system fonts. A site could use that information along with other browser details to help distinguish one browser from another.

Modern browsers therefore put full font enumeration behind a permission or limit which fonts a page can inspect. This is a privacy safeguard, not a sign that fonts are dangerous. The permission lets a site use the browser’s font-list feature, but it does not make the site an administrator or give it access to your font folders.

The restriction is not a complete shield against every kind of font detection. A page can sometimes infer whether a particular font is available by comparing how text is rendered. That is different from receiving a complete list, and browser protections vary. If you only need to check a font for a project, use the permission for that site and revoke it afterward if you prefer.

For a quick guide to checking fonts on your computer, see How to see which fonts are installed on your PC.