Multi-Account Browser Engine Glossary: From Canvas to JA4 — 30 Feature Terms Defined

Feature tables for multi-account browsers all say the same things. Canvas: check. WebGL: check. Proxy manager: check.

That's the trap. "Canvas control" means completely different things depending on how it's implemented, and a feature list hides the difference. A "proxy manager" that just stores credentials is a different thing from one that shows where a proxy actually exits. A JavaScript override and an engine-level change both get a tick in the same box. The checkboxes are too brief to tell the whole truth.

We've covered common myths about multi-account browsers and how WebGL fingerprinting works elsewhere. This one covers the product features: the engine components you're actually evaluating when picking a tool.

Identity Engine Components

1. Canvas Control

Sets the canvas output a profile reports. Websites draw shapes via the Canvas API and hash the pixels, and your GPU and drivers produce a particular hash. JavaScript overrides intercept API calls and change the result after the fact. Engine-level control sets rendering at the C++ level. Checks that run the same calls inside Web Workers, where a JavaScript override doesn't reach, show the difference: see how a server-side view of a browser is assembled from several layers. Extension-based tools can only reach the page; native Chromium engines cover both.

2. WebGL Control

Sets the WebGL renderer string and 3D rendering characteristics. WebGL exposes the GPU via strings like "ANGLE (Intel, Intel UHD Graphics 620...". Good WebGL configuration sets the string and produces consistent rendering behaviour, since claiming NVIDIA while rendering like Intel is an internal inconsistency. See our WebGL fingerprinting deep dive for how sites read it.

3. Audio Context Control

Sets Web Audio API output. Audio fingerprinting processes sound through oscillators and analyzers, and different audio stacks produce different values. Lower entropy than canvas, but useful for cross-checking. If a profile's canvas suggests Windows but its audio suggests macOS, the profile disagrees with itself.

4. Font List Control

Manages which fonts the profile reports as installed. Good implementations restrict the list to the set for the profile's platform identity, so a Windows 11 profile has Windows system fonts, not macOS-only fonts. At engine level that means CSS enumeration, the Font Access API and @font-face local() are all covered.

Randomising fonts sounds clever. It isn't: a random set describes no real machine, so the profile stops agreeing with itself. A consistent platform set is the point.

5. Client Hint Control

Configuration for User-Agent Client Hints (Sec-CH-UA, Sec-CH-UA-Platform). These HTTP headers are taking over from user-agent string parsing, and sites cross-check them against JavaScript navigator values. A profile sending Windows Client Hints while navigator.platform says "Linux" disagrees with itself. Our audio, font and hardware fingerprinting post covers related signals.

6. Timezone and Locale Control

Sets the profile's timezone and locale. It should match your proxy's geographic location. A profile with a Tokyo timezone behind a New York proxy gives pages two answers about where the visitor is, which spoils a geo test.

7. Screen Metrics Control

Controls screen.width, screen.height, devicePixelRatio. Good implementations account for window chrome too: the relationship between innerWidth and screen.availWidth should make sense.

8. Hardware Concurrency Control

Sets navigator.hardwareConcurrency, the reported CPU core count. A desktop profile reporting 32 cores on a laptop-class configuration is internally odd.

9. Device Memory Control

Sets navigator.deviceMemory, approximate RAM. Combined with hardware concurrency, it indicates device class, so the two should be plausible together.

10. WebRTC Policy Control

Configures how WebRTC handles IP discovery: disable entirely, proxy-only, or controlled exposure. WebRTC can reveal your real IP even through a proxy, which matters for privacy. ClickzProtect sees how this looks from the site-owner side.

Profile Management Features

11. Browser Profile

An isolated environment with its own identity parameters, cookies, localStorage, and session state. What separates these profiles from Chrome's built-in profiles: identity generation per profile, storage separation between profiles, and proxy binding.

12. Profile Template

A preset configuration you clone to create new profiles. Templates include identity settings and proxy config. Define once, clone 50 times, tweak individual proxies.

13. Profile Snapshot

Point-in-time capture of a profile's complete state: configuration, all storage, history. Snapshots let you restore to exactly how a profile existed before a session went wrong. Export/import typically only handles cookies.

14. Profile Sharing

Giving a teammate access to a profile without sharing its password. Role-based permissions (owner, admin, member, viewer) govern who can edit, and direct shares can be view-only or launch. Useful for agencies working in client accounts they have access to.

15. Cross-Device Lock

When a profile is synced across machines, it runs on one device at a time. The lock stops two machines from writing to the same profile state at once.

16. Profile Health Score

A diagnostic rating of how consistent a profile's configuration is: whether its timezone, language, proxy location and identity parameters agree with each other. It surfaces problems before you discover them in a live session.

17. Profile Sync

Cloud synchronisation across machines. JustBrowser syncs complete profiles with no storage cap: not just settings, but full storage state.

Automation and API Features

18. REST API

HTTP endpoints for programmatic profile management. Create profiles, configure identity parameters, launch sessions via API calls. In JustBrowser the API is local, bound to 127.0.0.1. Engineering teams integrate multi-account browsers into automation pipelines this way.

19. CDP Endpoint

Chrome DevTools Protocol access for Playwright, Puppeteer, Selenium. A profile started over the API returns a cdp_url that your script attaches to. The Playwright/Puppeteer tutorial covers integration.

20. Headless Launch

Running profiles without a visible window. A headless session has no real window, so its screen and viewport follow headless defaults. In JustBrowser the start endpoint launches headless unless you send {"headless": false}.

21. Status Polling

Asking the API for a profile's state on a schedule, with GET /profiles/{id}/status. It is how a script knows a launch has finished or a profile has stopped before it attaches or moves on.

Network and Proxy Features

22. Proxy Manager

Interface for storing, organising, and assigning proxies. Beyond credential storage, a good proxy manager lets you test a proxy and see where it exits before a session.

23. Per-Profile Proxy Binding

Locks each profile to a specific proxy. Launch the profile and it routes through its assigned proxy automatically. Without binding, you're setting proxies per session by hand, which is error-prone across hundreds of profiles. The ISP proxy setup tutorial shows how to configure this correctly.

24. Proxy Tester

Verification that a proxy works and where it exits. JustBrowser's tester shows exit IP, ISP or organisation name, country, city and timezone, latency, and a reputation note. It catches connection timeouts, auth failures and location mismatches before they break a live session.

25. DNS-over-HTTPS

Per-profile encrypted DNS through Cloudflare, Google, Quad9 or a custom resolver. Standard DNS can bypass your proxy and reach your ISP's resolver. JustBrowser includes per-profile DoH configuration.

26. Proxy Rotation

Changing a profile's exit IP per session, on a schedule, or manually. Account management usually wants sticky sessions; data collection from public pages sometimes wants rotation. In JustBrowser, rotation for your own proxies is configured with your provider, not by the browser.

Import/Export and Interoperability

27. Cookie Import/Export

Moving cookies between profiles or from other browsers. Formats vary: Netscape format, JSON, SQLite.

28. Profile Export

Packaging a profile for transfer or backup. A full export includes configuration and all storage; JustBrowser's encrypted export uses AES-256-GCM with a passphrase.

29. Identity JSON

Machine-readable configuration of a profile's identity parameters: OS, browser, GPU, screen, fonts, timezone. Enables programmatic profile generation via scripts.

30. Extension Support

Installing Chrome extensions in profiles. Useful for password managers and ad blockers. Risk: poorly written extensions can change values the engine sets.

Honorable Mentions

Multi-Window Consistency: Keeping multiple windows from the same profile consistent. Some tools drift between windows. For JA4 TLS fingerprinting implications, see the JA4 TLS fingerprint guide.

Profile Tagging/Folders: Organisation for hundreds of profiles. Trivial-sounding until you have 200 and need to find the German-proxy ones.

Session Recording: Capturing session state for debugging. Useful when a session misbehaves and you need to audit what happened.

Quick Verdict

One thing matters: implementation, not checkboxes.

Every multi-account browser lists canvas control. Native C++ implementation is consistent across the page and its Workers, where JavaScript injection can disagree with itself. That's the entire difference. Everyone lists a proxy manager. Credential storage alone leaves you guessing; a tester that shows where the proxy exits tells you. Whatever tool you pick, ask how the feature works, not just whether it exists.

For how sites read these values, the WebGL fingerprinting deep-dive is a good next step. For email infrastructure across client profiles, JustEmails handles domain separation. For privacy analytics that doesn't add fingerprinting, JustAnalytics works.

The browser engine is the foundation. These terms are what it's built from.

Frequently Asked Questions

What's the difference between a native engine and an extension-based multi-account browser?

Native engines modify Chromium source code at the C++ level, so identity values such as canvas, WebGL and audio output are produced by the engine itself and are consistent across the main thread and Web Workers. Extension-based tools inject JavaScript to intercept API calls, which leaves the browser's own settings able to disagree with the identity a profile presents, for example between a page and a Worker, or between a JavaScript value and an HTTP header.

Do I need a proxy manager if I already have my own proxies?

A proxy manager handles assignment and health checks, not just routing traffic. It tracks which proxy goes with which profile, lets you verify a proxy is alive and where it exits before a session, and shows exit IP, country, city and timezone. If you're managing 10+ profiles with external proxies, manual assignment becomes error-prone fast. With JustBrowser you bring your own proxies (rotation is then configured with your provider) or buy a proxy plan in the app.

What does profile snapshot do that export/import doesn't?

Snapshots capture the full profile state at a specific moment: cookies, localStorage, IndexedDB, cache, history and identity configuration. Export/import typically handles cookies and basic settings. Snapshots let you restore a profile to exactly how it existed before a session went wrong.

How do teams share profiles without sharing passwords?

Through role-based permissions. JustBrowser has owner, admin, member and viewer roles, and direct shares can be view-only or launch. Team seats are free; a seat can run the profiles shared with it but cannot create or sync its own, or use the API. Everyone works in the same named profile without anyone passing a password around.

---

Try JustBrowser

Native Chromium multi-account browser — not extension-based. Real C++ engine patches at the canvas / WebGL / audio / font / screen layer, so a profile's 40+ identity parameters are consistent with each other. Local REST API and 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