Learning objectives
After reading this article you will be able to:
- Explain candidate-font testing and fallback behavior
- Distinguish indirect measurement from permission-controlled font access
- Interpret matching or missing font results
Why fonts can distinguish browser environments
The fonts available to a page reflect the system, installed resources and browser policy.
Operating systems ship different default fonts. Language support and applications may add more. A page can also download its own web fonts, which can make its normal text look similar across computers while leaving other font tests possible.
Even when a font name matches, font versions and text-rendering components can affect spacing or pixels. Font availability and rendering output are related observations, but they answer different questions.
How a website tests for a font
A common method compares the dimensions of a sample rendered with a candidate font and a fallback.
If the candidate is available and used, the width or height may differ from the fallback measurement. A test repeats this across a chosen list. The resulting list reflects the tested candidates and method, rather than automatically enumerating every installed font.
Text can also be drawn into Canvas. That combines font selection with other rendering behavior. Broader access through a local-font API is a separate browser capability and may require permission; it should not be confused with ordinary indirect measurement.
How to read a font result
Check what the test actually tried before interpreting a font as present or absent.
| Result | Check next |
|---|---|
| A candidate appears available | Was it measured indirectly or returned by a permission-controlled API? |
| A font is missing from the report | Was it in the candidate list, and did browser policy allow access? |
| Two profiles have the same list | Do they use the same device and font-access policy? |
| Text metrics changed | Did the font, zoom, browser version or rendering path change? |
Use one test for before-and-after comparisons. Changing the candidate list or sample text can change the report even if nothing was installed or removed.
Why font measurements need context
A distinctive font combination can contribute to an environment comparison. Context keeps that observation useful: a measured font does not by itself identify the application that installed it or the person using it.
Interpreting the result
- A candidate-font test covers its chosen list, not necessarily every installed font.
- Browser protections can restrict font availability or expose a standardized set.
- Matching font results are compatible with many separate devices.
Frequently asked questions
Can websites see every font I have installed?
Ordinary candidate tests provide indirect evidence about the fonts they try. A browser may offer broader local-font access under separate permission and support requirements.
Do web fonts prevent font fingerprinting?
A downloaded font can reduce differences in the page’s own text. A script can still attempt other supported measurements.
Is font fingerprinting the same as Canvas fingerprinting?
Font tests can measure availability or dimensions. Canvas tests measure rendered output that may include text. They can overlap without being identical.