Browser fingerprinting is the practice of identifying a browser by the combination of characteristics it exposes: screen size, fonts, graphics card, time zone, language, installed features and dozens more. None of these is unique alone, but together they often are, and unlike cookies they can't simply be deleted. For proxy users the key point is that a proxy changes only your IP. Everything in the fingerprint passes through unchanged, so a site can recognise the same browser across many IPs, or notice when the IP and the browser don't agree.
What a Browser Fingerprint Includes
Passive signals (sent with every request)
- User agent and client hints: browser, version, operating system, platform.
- Accept-Language and the order of HTTP headers.
- TLS fingerprint: the cipher suites, extensions and their order in the TLS handshake. Libraries like Python requests have very different TLS fingerprints from real browsers.
- HTTP/2 settings and frame ordering.
Active signals (collected by JavaScript)
- Screen resolution, colour depth, device pixel ratio, window size.
- Time zone and locale formatting.
- Canvas and WebGL rendering output, which varies with GPU, drivers and fonts.
- Installed fonts, audio stack output, number of CPU cores, memory hints.
- Automation markers such as navigator.webdriver being true in automated browsers.
- WebRTC, which can reveal local and public IP addresses.
How Sites Use Fingerprints
- Recognising returning visitors even after cookies are cleared.
- Linking many requests from different IPs to the same automated client.
- Spotting inconsistencies: a US residential IP with a browser set to a Moscow time zone and Russian locale; a mobile carrier IP with a desktop screen size; a Chrome user agent with a non-Chrome TLS handshake.
- Feeding risk scores alongside IP reputation.
Why a Proxy Alone Doesn't Hide You
Rotating through a thousand residential IPs with one unchanged browser looks like one browser hopping across a thousand homes, which is not how people behave. And a perfect IP paired with a mismatched time zone is a stronger signal than a mediocre IP with a consistent profile. The goal isn't to look unique or random; it's to look consistent and ordinary.
Keeping IP and Fingerprint Consistent
With Playwright you can set the proxy and align locale and time zone with the proxy's country in the same place:
from playwright.sync_api import sync_playwright
with sync_playwright() as p:
browser = p.chromium.launch(proxy={
"server": "http://global.nodeproxies.xyz:8080",
"username": "USERNAME-country-de-session-profile1-time-30",
"password": "PASSWORD",
})
context = browser.new_context(
locale="de-DE",
timezone_id="Europe/Berlin",
viewport={"width": 1366, "height": 768},
)
page = context.new_page()
page.goto("https://example.com")
print(page.evaluate("Intl.DateTimeFormat().resolvedOptions().timeZone"))
browser.close()The session ID keeps one German residential IP for the whole browsing session, and the context tells the page it's in Germany too. More Playwright patterns are in headless browser proxies.
A Consistency Checklist
- Time zone and language match the proxy's country.
- Device type matches the IP type: mobile user agent and viewport with mobile proxies, desktop with residential.
- One sticky IP per browser session; don't rotate mid-session.
- One stable fingerprint per account profile you manage, reused each time with the same session ID.
- WebRTC disabled or routed through the proxy so it can't reveal your real IP.
- For scripts, use an HTTP client or headless browser whose TLS fingerprint fits the user agent you send. Claiming to be Chrome from a plain HTTP library is an easy mismatch to spot.
Scripts Without a Browser
Plain HTTP clients don't run JavaScript, so they expose only passive signals: headers, header order and the TLS handshake. That's fine for APIs and simple pages. For sites that check active signals or TLS closely, a real browser driven by Playwright or Selenium is usually more reliable than trying to make a raw HTTP library imitate one.
Testing Your Fingerprint
Open a fingerprint test page through your proxy and compare what it reports with what you intended: IP country, time zone, language, WebRTC addresses and whether automation is detected. Also confirm the IP with what is my IP. Repeat after any change to your setup.
Where Antidetect Browsers Fit
Antidetect browsers manage many separate profiles, each with its own stored fingerprint, cookies and proxy, which is useful for agencies managing clients' accounts. They don't remove the need for good proxies; they pair each profile with one. See proxies for antidetect browsers. Use them within each platform's terms.
Pairing Profiles With NodeProxies
Give each browser profile its own NodeProxies username with -country-xx and a fixed session ID, and set the profile's time zone and language to match. Residential IPs cover 195+ countries; mobile IPs suit mobile profiles. Sign up or see pricing.
FAQ
Can a proxy prevent browser fingerprinting?
No. A proxy changes your IP address only. Fingerprinting reads your browser's characteristics, which pass through the proxy unchanged.
Is browser fingerprinting legal?
It's widely used for fraud prevention and security. Privacy laws in some regions restrict its use for tracking without consent.
Does incognito mode stop fingerprinting?
Not really. Incognito clears cookies and history after the session, but most fingerprint signals stay the same.
What is a TLS fingerprint?
A summary of how a client sets up TLS: its cipher suites, extensions and their order. It reveals which software made the connection, regardless of the user agent string.
