Multi-Account Browser Glossary: 40 Terms Every Team Should Know

The problem with this space: the terminology is half computer science, half operational jargon, and it rarely gets written down in plain language. People pick it up from scattered forum posts that explain things as if everyone already has a PhD in browser internals.

Here's a glossary of forty terms, explained for people who run client, storefront or QA accounts — not academics. If you're setting up your first multi-account browser or trying to understand how sites read a browser, start here.

Core Fingerprinting Terms

1. Browser Fingerprint

A unique identifier derived from your browser's characteristics — screen resolution, installed fonts, GPU renderer, timezone, language settings, and dozens more. Unlike cookies, you can't clear it. Unlike IP addresses, you can't change it with a VPN. The fingerprint is calculated from how your browser behaves, not from stored data.

Fingerprinting scripts combine dozens of signals. Each signal alone isn't unique. Combined, they can single out one browser among a very large population.

2. Canvas Fingerprinting

A technique that draws invisible graphics using the HTML5 Canvas API, then hashes the result. Different GPUs, drivers, and font rendering engines produce slightly different pixel outputs — even for identical drawing instructions. Your canvas hash is consistent across sessions but different from most other users.

Canvas fingerprinting is the most commonly discussed technique, but it is only one input. Audio and WebGL matter just as much for profile consistency, and they get less coverage because they're harder to explain.

3. WebGL Fingerprint

Similar to canvas, but for 3D graphics. WebGL fingerprinting extracts your GPU's renderer string ("ANGLE (Intel, Intel UHD Graphics 620...)") and renders 3D scenes to detect rendering variations. More entropy than canvas because GPU configurations vary more than 2D rendering. Our WebGL fingerprinting deep-dive covers the technical details.

4. Audio Fingerprinting

Uses the Web Audio API to process audio signals and measure how your browser handles oscillators, compressors, and analyzers. Different audio stacks produce different output values — even with identical input. Lower entropy than canvas or WebGL, but useful as a cross-validation signal. See the audio fingerprinting breakdown.

5. Font Fingerprinting

Detects which fonts your system has installed by measuring text rendering width and height. Different font sets produce different lists. A machine with Adobe Creative Suite has fonts a stock Windows install doesn't. The combination of installed fonts is often unique enough to identify users.

6. Entropy

A measure of how identifying a piece of information is. High entropy = distinctive. Low entropy = common.

Screen resolution of 1920x1080? Low entropy — millions of people. A weird resolution like 1847x923? High entropy — almost nobody. Fingerprinting scripts combine multiple low-entropy signals into one high-entropy fingerprint. This is why changing one parameter on its own does little — the combination is what identifies a browser.

7. Fingerprint Hash

A fixed-length string generated by hashing your fingerprint values. Sites don't store your raw fingerprint data — they store the hash. When you return, they hash your current fingerprint and compare. Match = same user.

8. Cross-Browser Tracking

Techniques that identify users across different browsers. Harder than same-browser fingerprinting, but possible through shared signals: screen resolution, timezone, IP address, installed plugins, and hardware characteristics that don't change between Chrome and Firefox.

Multi-Account Browser Concepts

9. Browser Profile

An isolated browser environment with its own fingerprint, cookies, localStorage, and session state. Each profile behaves as its own browser, so accounts you are allowed to hold stay separate. A good multi-account browser keeps each profile's identity internally consistent — canvas, WebGL, fonts, and Client Hints all agree.

10. Profile Isolation

Keeping browser profiles completely separate, so each keeps its own identity settings, storage and network path. Isolation covers identity (each profile has its own values), storage (cookies and localStorage don't leak between profiles), and network (each profile can use its own proxy).

11. Native Engine

A multi-account browser that builds its identity settings into the browser source code (C++ for Chromium) rather than using JavaScript overrides or extensions. Native engines apply the same values at every layer — main thread, Web Workers, and internal APIs. Extension-based tools can leave gaps because their overrides don't reach everywhere. JustBrowser uses a custom Chromium engine with native C++ integration for this reason.

12. Identity Parameters

The individual settings that make up a profile's identity: user agent, platform, screen, timezone, language, GPU, fonts, audio and more. JustBrowser exposes 40+ of them per profile. Good values are consistent and plausible together — not random noise.

13. Fingerprint Consistency

When all of a profile's values agree logically. A profile presenting Windows should have Windows fonts, Windows-style path separators, Windows screen dimensions, and Windows GPU naming conventions. Contradictions — Mac fonts on a Windows profile, for instance — make a profile read as broken, which is worse than leaving the values at their defaults.

This is one of the most common mistakes. People spend hours on canvas and ignore that their navigator says "MacIntel" while their fonts say "Windows 11."

14. Cookie Jar Isolation

Each profile keeps its own cookies, so a login in one profile never appears in another. This is what keeps client A's session separate from client B's, and a teammate's shared profile separate from your own.

15. Session Persistence

A profile keeps its cookies, local storage and logins between launches, so you sign in once and the session is still there next time. With cloud sync, the same profile can be opened from another device, one device at a time.

How Sites Check Browsers

16. Bot Detection

Systems that identify automated or non-human traffic. Cloudflare, PerimeterX, Akamai, DataDome — these analyze fingerprints, behavior patterns, and network signals so site owners can filter automated traffic. It is useful to understand if you run a site, or if your own legitimate automation needs to work with such systems rather than around them.

17. Fingerprint Inspector

A public page that shows what your browser reports — canvas hash, WebGL renderer, fonts, timezone, WebRTC addresses. They are useful for privacy checks and for confirming that a profile's values agree with each other. Our own fingerprint checker is one example. Read the output as information, not as a grade.

18. Cross-Context Consistency Checks

Techniques that compare values from different places in the browser: main thread against Web Worker, a property's timing, or its prototype chain. A browser that reports one thing in one context and another elsewhere is inconsistent. Engine-level settings stay consistent because the same value is used everywhere.

19. Headless Detection

Identifying browsers running without a graphical interface (headless mode). Headless browsers have telltale signals: missing plugins, absent window dimensions, specific automation flags. Many sites treat headless traffic as automated by default.

20. JA3/JA4 Fingerprinting

Fingerprinting based on TLS handshake characteristics — cipher suites, extensions, and their ordering. Your TLS fingerprint is computed from the handshake itself, separately from anything the page can read in JavaScript. JA4 is the newer standard with better collision resistance.

21. WebRTC Leak

WebRTC can expose your real IP address even when using a proxy or VPN. It was designed for peer-to-peer communication and sometimes bypasses proxy settings. JustBrowser's WebRTC protection keeps a profile's WebRTC from exposing your real IP.

22. DNS Leak

When DNS queries bypass your proxy and go directly to your ISP's DNS servers, revealing your real location. Similar to WebRTC leaks — the proxy handles HTTP traffic but DNS slips through a different path.

Network & Proxy Terms

23. Residential Proxy

A proxy IP assigned by an ISP to a home connection. Often needed to see a site as a local visitor would. More expensive than datacenter IPs.

24. Datacenter Proxy

A proxy IP from a hosting provider (AWS, DigitalOcean, etc.). Cheap and fast, but many sites treat hosting addresses differently from home connections. Useful for scraping public data; a poor fit for logged-in account work.

25. Mobile Proxy

A proxy IP from a mobile carrier. Mobile IPs are shared via carrier-grade NAT, so many people share each address.

Most expensive proxy type by a lot, and overkill for most teams.

26. Sticky Session

A proxy configuration that maintains the same IP for extended periods (hours or days) rather than rotating per request. Useful for logged-in work — an IP that changes mid-session is a common reason a site asks you to verify again.

27. Rotating Proxy

A proxy that changes IP with each request or at fixed intervals. Good for scraping where you don't need session continuity. Bad for account management where session consistency matters.

28. Geo-Matching

Aligning your proxy location with your account's expected location. A US account accessed from a German IP can trigger a security check on the platform's side. Proper geo-matching means your proxy's country, state, and sometimes city match the account's registration or billing location.

Automation & API Terms

29. CDP (Chrome DevTools Protocol)

The protocol Chromium uses for remote debugging and automation. Tools like Playwright and Puppeteer communicate with the browser via CDP. A multi-account browser with CDP support lets you automate your own workflows in a specific profile. JustBrowser exposes CDP through its local REST API: starting a profile returns its CDP URL.

30. Headless Launch

Running a browser without a visible window. Faster for automation. A headless session has no real window, so its screen and viewport follow headless defaults; launch headed when a session needs a normal window. JustBrowser's API starts profiles headless unless the request says otherwise.

31. REST API

An interface for controlling browser profiles via HTTP requests — create profiles, configure fingerprints, launch sessions, manage cookies. Engineering teams use REST APIs to integrate a multi-account browser into their own automation pipelines. JustBrowser's REST API is local, bound to 127.0.0.1.

32. Playwright/Puppeteer over CDP

Playwright and Puppeteer can attach to a running profile through its CDP endpoint instead of launching their own browser. The profile keeps its own cookies, storage, proxy and identity, and your script drives it. See the Playwright and Puppeteer tutorial.

Advanced Fingerprint Signals

33. Client Hints (UA-CH)

HTTP headers that replaced the user-agent string for conveying browser and device information. Sec-CH-UA, Sec-CH-UA-Platform, Sec-CH-UA-Mobile, etc. Sites request specific hints and can compare them with other reported values. Hints that disagree with the user agent show a profile is inconsistent.

34. Navigator Object

The JavaScript object containing browser identification properties — navigator.userAgent, navigator.platform, navigator.language, etc. The challenge is keeping it consistent across main thread, Web Workers, and iframes.

35. Screen Fingerprint

Properties like screen.width, screen.height, screen.colorDepth, and window.devicePixelRatio. Common resolutions have low entropy, but unusual combinations are identifying. A virtual machine with an unusual resolution stands out.

36. Timezone Fingerprint

Your browser's reported timezone offset and Intl.DateTimeFormat output. Should match your proxy's geographic location. A profile set to Tokyo timezone while using a New York proxy contradicts itself.

37. WebGL Renderer String

The GPU identification string exposed via WebGL: manufacturer, model, and driver info. High entropy because GPU configurations vary widely. Setting it means matching the renderer string to plausible canvas and WebGL rendering behavior.

38. Hardware Concurrency

The navigator.hardwareConcurrency property reporting CPU core count. Modern phones have 8 cores; servers have 64+. A profile presenting a phone with 32 cores is obviously inconsistent.

39. Device Memory

The navigator.deviceMemory property reporting approximate RAM in gigabytes. Combined with hardware concurrency, it reveals device class. Mismatches between device memory and other hardware values make a profile inconsistent.

40. Prototype Tampering

Modifying JavaScript built-in objects to change what a script sees. Pages can examine whether property descriptors, prototype chains, and function toString() outputs look native, and JavaScript-level overrides often don't. Engine-level changes don't have this problem because the values are generated at the source rather than patched on top.

Honorable Mentions

Supercookies: Tracking methods that persist across cookie clears — HSTS state, favicons, cached resources. Profile isolation keeps these separate per profile, just like regular storage.

Behavioral Fingerprinting: Tracking mouse movements, scroll patterns, typing cadence. A different layer of the stack from the browser's own settings, and not something a multi-account browser changes.

EME/CDM Fingerprinting: Using encrypted media extensions to detect device types. Mostly relevant for streaming services. Low priority for typical team use cases.

Quick Verdict

If you remember one thing from this glossary: consistency beats randomization. Every time. A profile with matching, plausible values across all 40+ parameters beats a profile with random values that contradict each other.

Teams that run stable, permitted setups understand what they're configuring. They know what their Client Hints report, why a profile's timezone should match its proxy, and what each profile shares with the others. Now you have the vocabulary.

For click fraud protection on your ad accounts, ClickzProtect handles the traffic quality layer. For privacy-first analytics without adding fingerprinting signals, JustAnalytics works. For the email layer of client work, JustEmails handles custom domains and mailboxes.

But the browser is where it starts. Get the terminology right, and the technical decisions start making sense.

Frequently Asked Questions

What's the difference between fingerprinting and tracking?

Tracking uses identifiers you can delete — cookies, localStorage, session IDs. Fingerprinting identifies your browser through its characteristics: how it renders graphics, which fonts it has, how its audio stack behaves. You can clear cookies. You can't change your GPU's rendering signature without specialized tools.

Why do I need a multi-account browser if I already use proxies?

Proxies change your IP address. A multi-account browser gives each profile its own browser identity and storage. Sites see both layers — network (IP) and browser (fingerprint, cookies, storage). Using proxies alone means every account still shares the same canvas hash, WebGL signature, font list and cookie jar. A multi-account browser keeps each profile's identity, cookies and proxy separate and consistent, which suits agencies and teams working in accounts they are allowed to hold. Check what each platform's rules allow before running more than one.

What does entropy mean in fingerprinting?

Entropy measures how identifying a piece of information is. High entropy means few people share that value — it's distinctive. Low entropy means lots of people share it — it's common. A rare GPU has high entropy (easy to track). A common screen resolution has low entropy (hard to track). Fingerprinting scripts combine several low-entropy signals into one high-entropy fingerprint.

Are multi-account browsers legal?

The browser itself is legal — it's modified Chromium. Legality depends on what you do with it. Running separate client or storefront accounts within a platform's terms is generally fine. Account fraud, identity theft, or working around a platform's enforcement isn't. Check the specific platform's terms and your jurisdiction's laws.

---

Try JustBrowser

Native Chromium multi-account browser for teams — not extension-based. Real C++ engine patches at the canvas / WebGL / audio / font / screen layer, so 40+ identity parameters are genuine, not faked. Local REST API + CDP for Playwright, Puppeteer, Selenium. $9.99/month or $99.99/year. 7-day free trial, card required — cancel any time in the seven days and you are not charged. Unlimited profiles.

Get started → · How it differs from Multilogin / GoLogin / AdsPower