Back to blog

Why Incognito Mode Does Not Stop Browser Fingerprinting: Environment Isolation Explained Through a Popular Video

Why can websites still recognize your browser after you open an incognito window, clear cookies, or even change networks? Using a popular Better Stack YouTube video and its public demo code, this article explains browser fingerprints, the limits of private browsing, and the difference between privacy protection and environment isolation in multi-account work.

Incognito mode mainly reduces the browsing history and session data left on your device. It does not mean websites cannot recognize your current browser. Even after cookies are cleared, a website may read screen, language, time-zone, graphics, and audio-processing characteristics again and combine them into a browser fingerprint.

Better Stack's YouTube video How Websites Track You Without Cookies explores this problem. Published on October 16, 2026, it showed 100,074 views and 1,350 likes when checked on November 1, 2026. It is an accessible introduction to incognito mode and fingerprinting: short, with public demo code that can be examined.

This article uses that single video as its central source, alongside the author's code and technical material, to explain the question it raises and its implications for multi-account work.

The key idea in the video is recognizing a browser again

The video introduces its demo page at 0:26, compares cookies with fingerprints at 1:02, covers Canvas and audio fingerprints at 2:12, and suggests testing your own browser at 3:23.

A cookie is like a marker a website places in your browser. When the browser returns it on a later visit, the website may connect the two visits. Deleting that marker affects identification methods that depend on it.

Fingerprinting takes another route: the page reads characteristics of the current environment and combines them. Deleting stored data does not automatically change your screen, fonts, time zone, or graphics processing. The author's public code puts values returned by several interfaces into one signal collection and calculates the displayed ID.

This does not mean every visit can be tracked accurately, nor that a fingerprint is an unchanging identity number. Browser versions, device configuration, privacy settings, and the website's identification method all affect the outcome.

What does the author's demo code collect?

The video description links to public demo code. It collects signals, serializes them, and uses SHA-256 to generate a digest displayed as an ID.

Several signal groups deserve attention:

SignalWhat the demo doesHow to interpret it
CanvasDraws text and shapes, then hashes the rendered resultGraphics output can characterize an environment, beyond what is visibly displayed
WebGLTries to read graphics vendor and renderer informationResults depend on implementation and browser protections; this is not a universal hardware serial number
AudioProcesses a synthetic signal in an offline audio context and sums some samplesIt analyzes processing output, not sound recorded through your microphone
Screen and device capabilitiesReads resolution, pixel ratio, and exposed concurrency and memory informationThese are interface-reported values, not a complete hardware inventory
Languages, time zone, and fontsReads language lists and time zone, and probes candidate fonts using text widthOrdinary individual values can become more distinctive in combination

The code corrects a common misconception: a fingerprint need not be a fixed number hidden somewhere in your browser waiting to be deleted. The demo calculates its ID from values it reads at that moment.

It remains a simplified demonstration. It does not prove that a real website can identify the same person through every environmental change, or represent all commercial identification systems.

Incognito mode, clearing cookies, and changing IP address affect different things

Before asking whether something works, specify what you want to change.

ActionMain effectWhat you cannot directly conclude
Clear cookiesAffects sessions and markers relying on those cookiesAll device and browser characteristics have changed
Use an incognito windowChanges data retention and history in the private sessionWebsites cannot read any environmental characteristics
Switch proxy or VPNChanges the network exit visible to a websiteLanguage, time zone, Canvas, and other signals all change with it
Use separate browser environmentsOrganizes sessions, configurations, and daily work for different business accountsWebsites can never associate the accounts through other information

EFF's project and methodology description distinguishes fingerprinting from traditional identification using IP addresses and cookies. It also explains that the tool compares exposed browser characteristics with visitor configurations observed recently. Its uniqueness assessment therefore has a specific sample scope and cannot be generalized to every website.

Incognito mode has a clear purpose if you want to leave less browsing history on a shared computer. Reducing cross-site tracking also calls for attention to tracking and fingerprinting protections. Multi-account work adds another requirement: keeping account sessions, proxies, and configurations clearly separated over time.

Why a changed fingerprint ID does not automatically mean anonymity

The demo uses a digest algorithm, so changing one input can substantially change the final ID. For example, if normal and incognito windows expose different language lists, the digest may differ even when most other signals remain similar.

Two different IDs therefore show only that the demo's inputs or outputs changed. Which signals a website actually uses and how it compares visits require separate investigation. Conversely, the same demo ID does not prove cross-site tracking occurred.

Changing one setting to alter the displayed ID does not establish that every other signal has lost its distinguishing value. Instead of repeatedly pursuing a new digest, keep a baseline, check what changed, and verify page functionality. Frequent undocumented changes also make business environments harder to troubleshoot.

How to inspect your environment without being misled by a score

The video's suggested tool, Cover Your Tracks, helps reveal characteristics exposed to its test site. Its project description supports using the test as a documented comparison.

  1. Save a baseline. Record browser version, test time, proxy use, and major privacy settings. Inspect individual characteristics, not just the score.
  2. Change one thing at a time. Compare normal and incognito windows, or results before and after enabling one built-in protection.
  3. Find where the change occurred. Was it the language list, restricted graphics information, or randomized readings? Explaining the change is more valuable than a simple pass label.
  4. Verify your actual task. Do pages load, are required sessions retained as intended, and can you clearly distinguish accounts after switching environments?

A test reflects its methods, samples, and the environment at that time; it cannot judge on behalf of any arbitrary website. This article does not present cross-browser test results or a ranking of browser protections.

What should an antidetect browser solve in multi-account work?

Teams managing accounts for several clients face concrete problems: opening the wrong session, scattering proxy settings across chat messages, or not knowing which environment to keep during handover. New incognito windows alone are poorly suited to long-term configuration storage and team handovers.

In this situation, use the PurpleMark web app to associate accounts with reusable environments. Set an environment's name and group, bind the business account, and save its proxy, startup pages, language, and time-zone configuration. Returning through the corresponding environment can reduce repeated setup and session mix-ups.

Check session separation and exposed characteristics separately. For handovers, environment sharing, transfers, and member permissions can replace a shared browser session used for every client. These functions manage configurations, sessions, and responsibilities; they do not promise anonymity or guarantee that accounts cannot be linked.

Personal privacy focuses on reducing tracking opportunities. Multi-account collaboration also needs reusable environments, documented settings, and clear access permissions. The needs overlap, but one fingerprint score cannot settle both.

Define your goal before choosing tools

The video's useful reminder is that deleting a website's stored markers does not stop the browser itself from exposing potentially identifying characteristics.

Incognito mode addresses certain local privacy needs, tracking protection addresses some information collection, and separate environments organize account sessions and configurations. Before your next browser check, write down the problem you actually want to solve, then examine changed signals and established work boundaries. That is more dependable than chasing an impressive-looking test result.