Antidetect Engine Glossary: From Canvas Spoof to JA4 — 30 Feature Terms Defined

I spent my first month comparing antidetect browsers by looking at feature tables. Canvas spoof: check. WebGL spoof: check. They all said the same things.

Took me embarrassingly long to realize "canvas spoof" means completely different things depending on how it's implemented. Wasted three weeks on a tool that "supported" canvas spoofing but failed every detection test I threw at it. My fault for trusting checkboxes.

That's the trap. Everyone claims the same features. A "proxy manager" that just stores credentials is wildly different from one that validates geolocation and rotates on schedule. "Canvas spoof" via JavaScript override fails detection tests that native C++ spoofing passes. The checkboxes lie — or at least, they're too lazy to tell the whole truth.

We already have glossaries for general antidetect terminology and fingerprinting detection terms. This one covers the product features — the engine components you're actually evaluating when picking a tool.

Spoofing Engine Components

1. Canvas Spoof

Modifies canvas fingerprint output. Detection sites draw invisible shapes via the Canvas API and hash the pixels — your GPU and drivers produce a unique hash. JavaScript overrides intercept API calls and inject noise. Native spoofing modifies rendering at the C++ level. Detection systems like CreepJS cross-validate by running calls in Web Workers where JavaScript overrides don't reach. Extension-based tools fail this; native Chromium engines don't.

2. WebGL Spoof

Changes the WebGL renderer string and 3D rendering characteristics. WebGL exposes your GPU via strings like "ANGLE (Intel, Intel UHD Graphics 620..." Good WebGL spoofing changes the string and produces consistent rendering behavior — claiming NVIDIA while rendering like Intel is a detectable mismatch. See our WebGL fingerprinting deep dive for detection techniques.

3. Audio Context Spoof

Modifies Web Audio API fingerprints. Audio fingerprinting processes sound through oscillators and analyzers — different audio stacks produce different values. Lower entropy than canvas, but useful for cross-validation. If your canvas matches Windows but audio matches macOS, that's a flag.

4. Font List Control

Manages which fonts the profile reports as installed. Good implementations let you specify a font list matching your claimed OS — a Windows 11 profile should have Windows system fonts, not macOS-only fonts.

Here's a mistake I made early on: randomizing fonts sounds clever. It's not. Random sets don't match real populations. Detection systems know what fonts ship with Windows 11. Random font lists are statistically impossible.

5. Client Hint Control

Configuration for User-Agent Client Hints (Sec-CH-UA, Sec-CH-UA-Platform). These HTTP headers replaced user-agent parsing and sites cross-check them against JavaScript navigator values. A profile sending Chrome Client Hints while navigator.platform says "Linux" is instantly suspicious. See our Client Hints breakdown.

6. Timezone and Locale Spoof

Sets the profile's timezone and locale. Must match your proxy's geographic location. A profile claiming Tokyo timezone through a New York proxy gets flagged immediately. Our timezone and geolocation mismatch guide covers common pitfalls.

7. Screen Metrics Spoof

Controls screen.width, screen.height, devicePixelRatio. Real spoofing accounts for window chrome too — the relationship between innerWidth and screen.availWidth should make sense.

8. Hardware Concurrency Spoof

Sets navigator.hardwareConcurrency — reported CPU core count. A "mobile" profile reporting 32 cores is obviously wrong.

9. Device Memory Spoof

Sets navigator.deviceMemory — approximate RAM. Combined with hardware concurrency, it reveals device class. A claimed mobile with 4GB memory but 16 cores is a mismatch.

10. WebRTC Policy Control

Configures how WebRTC handles IP discovery: disable entirely, proxy-only, or controlled exposure. WebRTC can leak your real IP even through a proxy. ClickzProtect sees traffic that passed fingerprint checks but leaked via WebRTC all the time.

Profile Management Features

11. Browser Profile

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

12. Profile Template

A preset configuration you clone to create new profiles. Templates include fingerprint settings, proxy config, warm-up preferences. Define once, clone 50 times, tweak individual proxies.

13. Profile Snapshot

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

14. Profile Aging

Simulates usage history over time. New profiles with perfect fingerprints but zero history look suspicious. Profile aging fills in realistic browsing activity before you use the profile for real accounts.

15. Cookie Warm-up

Automated browsing across 50+ popular sites to accumulate cookies before sensitive accounts. A fresh profile with zero third-party cookies looks like automation. JustAnalytics deals with the opposite problem — privacy analytics that doesn't set cookies. Antidetect profiles need the cookies real users have.

Annoying truth: warm-up takes time. You can't rush it. I've tried shortening cycles and accounts get flagged faster. Just let it run.

16. Profile Health Score

Diagnostic rating of fingerprint cleanliness. Good implementations run the same tests detection sites use — canvas consistency, prototype tampering, timing analysis. Surface problems before you burn accounts discovering them.

17. Profile Sync

Cloud synchronization across machines. JustBrowser syncs complete profiles with no storage cap — not just settings, but full storage and warm-up state.

Automation and API Features

18. REST API

HTTP endpoints for programmatic profile management. Create profiles, configure fingerprints, launch sessions via API calls. Engineering teams integrate antidetect browsers into automation pipelines this way.

19. CDP Endpoint

Chrome DevTools Protocol access for Playwright, Puppeteer, Selenium. Stock CDP leaves fingerprints — Runtime.enable traces, debugger presence. An antidetect CDP endpoint normalizes these signals. The Playwright/Puppeteer tutorial covers integration.

20. Headless Launch

Running profiles without a visible window. Headless browsers have detection signals — missing dimensions, absent plugins. Proper headless support normalizes these so headless sessions pass the same tests headed sessions do.

21. Profile State Polling

Alerts pushed to your endpoint when events occur — proxy failures, health degradation. Useful for hands-off automation instead of polling status.

Network and Proxy Features

22. Proxy Manager

Interface for storing, organizing, and assigning proxies. Beyond credential storage: health checks, geo-validation, rotation schedules. A good proxy manager verifies proxies work before sessions and validates geolocation.

23. Per-Profile Proxy Binding

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

24. Proxy Health Check

Automated verification that proxies work and geolocate correctly. Catches connection timeouts, auth failures, geo-mismatches before they burn accounts.

Most frustrating thing in multi-account work: dead proxies you didn't know were dead. Health checks save you from finding out mid-session.

25. DNS-over-HTTPS

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

26. Proxy Rotation Rules

Configurable IP rotation — per session, on schedule, or manual. Account management wants sticky sessions; scraping wants per-request rotation.

Import/Export and Interoperability

27. Cookie Import/Export

Moving cookies between profiles or from other browsers. Formats vary — Netscape format, JSON, SQLite. The cookie format guide covers compatibility.

28. Profile Export

Packaging a profile for transfer or backup. Full export includes fingerprint config, all storage, warm-up state. Partial exports lose warm-up progress.

29. Fingerprint JSON

Machine-readable fingerprint configuration. Defines all 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 leak signals or override spoofed values.

Honorable Mentions

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

Profile Tagging/Folders: Organization 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 accounts get flagged and you need to audit what happened.

Quick Verdict

One thing matters: implementation, not checkboxes.

Every antidetect browser claims canvas spoofing. Native C++ spoofing holds up on CreepJS — JustBrowser's recorded result is 0% stealth / 0% headless — where JavaScript injection gets caught by the worker and prototype checks. That's the entire difference. Everyone claims a proxy manager. Credential storage burns accounts. Geo-validated health checks catches problems first.

I'm biased toward tools that let me test detection before I commit accounts. (Obviously — we build JustBrowser with real-time health scoring for exactly this reason.) But whatever tool you pick: ask how the feature works, not just whether it exists.

For detection terminology — entropy, JA4, CDP leaks — the detection glossary covers that. For email infrastructure in multi-account operations, 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 antidetect browser?

Native engines modify Chromium source code at the C++ level — fingerprint values are generated genuinely, not overridden after the fact. Extension-based tools inject JavaScript to intercept API calls, but detection systems check for tampering by comparing main thread vs Web Worker values, examining prototype chains, and measuring call timing. Extensions fail these cross-validation checks.

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

A proxy manager handles assignment, health checks, and rotation — not just routing traffic. It tracks which proxy goes with which profile, verifies proxies are alive before sessions, rotates IPs on schedules you set, and alerts when proxies fail geo-validation. If you're managing 10+ profiles with external proxies, manual assignment becomes error-prone fast.

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, fingerprint config, warm-up status. Export/import typically handles cookies and basic settings. Snapshots let you restore a profile to exactly how it existed before a session went wrong, including all the warm-up state that took hours to build.

Why does cookie warm-up matter for new profiles?

New profiles with zero cookies look like fresh browser installs or automation. Platforms expect real users to have tracking cookies from Google, Facebook, news sites, and retailers. Cookie warm-up visits 50+ popular sites to accumulate normal cookies before you touch sensitive accounts. The difference in account survival rate is significant.

---

Try JustBrowser

Native Chromium antidetect browser — not extension-based. Real C++ engine patches at the canvas / WebGL / audio / font / screen layer, so 40+ identity parameters are genuine, not faked. REST API 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