A website can recognize your browser without a login.
Websites can combine ordinary details about your browser, device, and connection into a profile that may recognize the same browser later—without relying on one cookie or learning your name first.
Explore a fingerprint
Anatomy of a browser profile
Open any signal for its full guide. On smaller screens, scroll sideways.
A small, local demonstration
See what your browser makes visible.
Each button reads one ordinary browser API. A real fingerprinting system can collect many more values, test rendering behavior, and compare the result on a server.
Nothing in this demonstration is transmitted or stored.
Choose a signal to inspect.
These values describe a configuration. They do not prove who is using it.
From observation to recognition
A fingerprint is assembled from many signals
The page observes characteristics. Software normalizes them into a profile. A service then compares that profile with previous visits and decides whether the evidence is close enough.
Observe
Read values and run small tests.
Combine
[2d:7c, gpu:07, tz:−6,
font:12, tls:C, hdr:4A]Create a comparable feature vector.
Compare
Allow for normal changes and uncertainty.
Assign
Browser · XYZAppend this visit to a recurring profile.
Cookie versus fingerprint
A fingerprint can be reconstructed many times
The website writes an ID.
- Visit 1save
ABC - Visit 2send
ABC - Clear storageremove
ABC - Visit 3no stored ID
The observer measures again.
- Visit 1compute
XYZ - Visit 2compare
XYZ′ - Clear storagestored state removed
- Visit 3recompute
XYZ″
Real systems may tolerate changed values, combine server-side history, and return a confidence score rather than require an exact match.
From browsing to a marketable profile
Recognition turns separate moments into a history.
A fingerprint does not need to contain a name to be commercially useful. If the same browser can be recognized, new events can be attached to an existing pseudonymous profile. 404 Privacy’s original research on fingerprinting and advertisingfollows this shift from cookie rejection to reconstructed identifiers.
- Product viewedrunning shoes
- Article readmarathon training
- Cart startedsame browser profile
- Email submittedpseudonymous history can meet a known account
The same capability, different purposes
Recognition can protect a session—or profile a customer.
Intent changes. The underlying capability remains the ability to recognize a browser across moments.
Fraud and abuse controls
Estimate whether a login, checkout, or account action resembles a known device or an unusual environment.
Analytics and attribution
Estimate repeat visits, conversion paths, and campaign performance when ordinary identifiers are unavailable.
Advertising and marketing
Place a returning browser into an audience, limit ad frequency, personalize an offer, or measure whether an ad preceded a sale.
Account security
Add a device signal to risk scoring, session protection, or prompts for additional authentication.
For higher-risk workflows, see how linkability affects journalists,legal teams, andhuman-rights organizations.
What common privacy actions change
Different controls operate at different layers.
A useful defense claim should say which signal it changes, who can still observe the rest, and whether many users receive the same protection.
| Action | What it changes | What remains |
|---|---|---|
| Clear cookies | Removes stored identifiers | The browser can expose the same characteristics again. |
| Open a private window | Separates local history and storage | Many browser, device, and network signals remain observable. |
| Change VPN server | Changes the IP address and route | It does not change the local graphics, fonts, screen, or browser APIs. |
| Use anti-fingerprinting protections | Can reduce, standardize, or partition signals | Effectiveness depends on the browser, defaults, and observer. |
Minimize
Expose fewer unnecessary characteristics.
Standardize
Make more browsers look alike.
Partition
Prevent one observer’s identifier from becoming universal.
Separate the network
Reduce linkability at the IP and transport layers too.
The shortest accurate definition
A browser fingerprint is a repeatable profile built from observable characteristics.
It can recognize without naming. A pseudonymous browser history can still reveal patterns and support decisions.
It becomes more consequential when associated. Accounts, purchases, and submitted details can connect that history to a person.
Defense is a system property. The strongest approaches reduce linkability across browser, device, and network layers.
Sources and technical references
This page describes capabilities and illustrative data flows. It does not claim that every website, advertiser, or security service collects the same signals or performs every association shown.
Published 2025-01-15 · Reviewed 2026-09-19