FINGERPRINT · COMMUNITY

Browser fingerprint settings: complete hardware templates, consistent over time.

When it comes to fingerprints, more random is not better. Prism builds a stable identity for each profile from a “fingerprint seed + complete hardware template”: the same profile stays consistent at every launch, different profiles stay distinct, and the OS, CPU, screen, GPU and browser version all come from one coherent set.

Updated · Based on Prism 0.3.22

How it works: applied in the kernel, not injected into pages as scripts

Fingerprint settings do not rely on injecting JavaScript into web pages. Creating or editing a profile saves a configuration; when you open the profile, Prism converts it into launch arguments for the Chromium fingerprint kernel compiled by the maintainer (based on fingerprint-chromium patches, ungoogled-chromium build recipes and Prism’s own patches).

As a result, a web page reads the same identity in the main window, iframes, Dedicated / Shared / Service Workers, OffscreenCanvas and AudioWorklet. The maintainer’s audit tools check that these execution contexts are consistent and that the same seed stays stable across different data directories. For kernel versions and sources, see Fingerprint kernel.

Note: when you use the Pro multi-window synchronizer or MCP, Prism runs scripts in the page through the browser’s DevTools protocol to read and act on it; this is unrelated to fingerprint settings.

Prism fingerprint settings with the Windows 11 RTX 4060 template: 12 cores, 16GB, GeForce RTX 4060, 1920×1080 and the fingerprint seed
After you choose a template, the full combination and the fingerprint seed are shown (demo data).
Lower part of the Prism fingerprint settings: browser brand, brand version matched to the kernel automatically, CPU cores, screen resolution, interface language, time zone, Accept-Language and the option to disable selected spoofing
Leave the brand version empty to match the kernel automatically; disabling selected spoofing is for troubleshooting only (demo data).

10 hardware templates

A hardware template sets the platform, OS version, CPU cores, screen resolution and GPU together, avoiding implausible combinations such as “a Windows system reporting an Apple GPU”. New profiles use the “Seed-Based” template for your computer’s operating system by default.

Prism hardware templates (names as shown in the app)
TemplateCPUResolutionGPU
macOS · Native Hardware (Recommended)This computer’s actual core count1440×900Host GPU; keeps host fonts, Canvas and Audio; selectable on macOS only
macOS · Seed-Based Apple GPU (Recommended for Multiple Profiles)8 cores1440×900One of 11 Apple M1–M4 series GPUs, fixed by the seed
macOS · Apple M1 · 8GB8 cores1440×900Apple M1
macOS · Apple M3 Pro · 18GB12 cores1512×982Apple M3 Pro
macOS · Apple M4 Pro · 24GB12 cores1512×982Apple M4 Pro
Windows · Native Hardware (Recommended)This computer’s actual core count1920×1080Host GPU; selectable on Windows only
Windows · Seed-Based NVIDIA GPU (Recommended for Multiple Profiles)8 cores1920×1080One of the NVIDIA RTX 30 / 40 series desktop GPUs (18 models, 27 device IDs), fixed by the seed
Windows 10 · RTX 3060 · 16GB8 cores1920×1080NVIDIA GeForce RTX 3060
Windows 11 · RTX 4060 · 16GB12 cores1920×1080NVIDIA GeForce RTX 4060
Windows 11 · RTX 4070 · 32GB16 cores2560×1440NVIDIA GeForce RTX 4070

The memory size in a template name only distinguishes the combinations; navigator.deviceMemory, which web pages can read, reports at most 8 in Chrome, and Prism also reports 8. Except for “Native Hardware”, templates can be used on the other operating system — for example, to create a Windows identity on a Mac — in which case common fonts of the target system are mapped to local fonts.

Prism hardware template drop-down list: macOS native hardware, seed-based Apple GPU, Apple M1, M3 Pro, M4 Pro, Windows native hardware, seed-based NVIDIA GPU and more
The hardware template list (captured on a Mac, where Windows native hardware cannot be selected).

Fingerprint seed: what defines a profile’s identity

Each profile has a fingerprint seed between 0 and 4294967295, generated randomly when the profile is created. Together with the template, the seed determines details such as the GPU model, Canvas, WebGL, Audio and ClientRects: the same seed gives the same result at every launch, and different seeds stay distinct from each other.

  • Duplicating a profile or clicking “Regenerate” gives a new seed — that is, a new identity.
  • Do not change the seed or template of a long-term account profile casually; existing profiles never switch templates automatically when the app is updated.
  • When creating profiles in bulk, you can set the seed in the fingerprint_seed column of the CSV; leave it empty for a random seed per profile. See Bulk profile management.

Signal by signal: how Prism handles each one

How Prism handles common browser fingerprint signals
SignalHow Prism handles it
User-Agent and Client Hints (UA-CH)Brand: Chrome or Edge. If the brand version is left empty, the kernel’s actual four-part version number is used, and the UA, UA-CH high-entropy fields and HTTP Client Hints all come from the same source. A manually entered major version that does not match the kernel blocks the launch. A fully custom UA string is not available.
OS platform and versionSet by the template (Windows or macOS). The macOS native template reads the host macOS version at launch; Windows templates (including those with “Windows 11” in the name) all report OS version 10.0.0 in Client Hints.
CPU coresThe template value (8 / 12 / 16) or the host’s actual number of logical cores.
Screen resolutionThe template value; screen and CSS device-width stay consistent, and the available height accounts for the Windows taskbar or the macOS menu bar.
Language and Accept-LanguageFollows the proxy exit by default and is matched to the country automatically (24 countries / regions built in); it can also be set manually. See Network identity.
Time zone (Date / Intl) and geolocationThe IANA time zone and city-level coordinates (accurate to about 25 km) of the proxy exit; in manual mode, you can enter any valid IANA time zone.
CanvasSmall, deterministic rendering differences derived from the seed (such as sub-pixel text offsets), with no random noise that changes on every read: stable within a profile, different between profiles.
WebGL and GPUWEBGL_debug_renderer_info reports the vendor and renderer of the template GPU (such as ANGLE NVIDIA GeForce RTX 4060 or Apple M3 Pro), and pixel reads vary slightly by seed; the vendor and architecture of the WebGPU adapter are adjusted to match.
AudioOfflineAudioContext output is subtly permuted by seed while keeping its overall statistical characteristics.
ClientRects / DOMRectElement and Range rectangles are scaled by a tiny, deterministic amount based on the seed.
FontsHost fonts are kept when the template matches the host system; when emulating another system, target-system fonts are mapped and most fonts that do not belong to the target system are hidden.
WebRTC“Leak Protection” by default, which blocks non-proxied UDP. See Proxies and network identity.
Automation tracesnavigator.webdriver is not set to true by automation switches, and the HeadlessChrome marker is removed.
Window identificationWindow titles show “[number] name”; the macOS Dock icon carries the profile number, and the Windows taskbar groups windows by profile and shows the number.

Native hardware, seed-based or a fixed template?

Choosing a hardware template by use case
NeedRecommendation
Only one or two profiles, with the most natural rendering signalsNative Hardware: keeps the host GPU, fonts, Canvas and Audio. Note that multiple profiles using a native template are identical in these signals.
Several profiles used at the same time that need to be told apartSeed-Based template (default): each profile’s GPU model and rendering details are fixed by its seed.
A specific device combination (such as a particular Mac or graphics card)Fixed template: Apple M1 / M3 Pro / M4 Pro or RTX 3060 / 4060 / 4070.
An account profile already in long-term useKeep its current template and seed. If you need to change something, duplicate it and test on the new profile first.

How to verify fingerprints

When checking with pages such as CreepJS, Pixelscan or BrowserLeaks, compare at least two profiles, test again after a restart to confirm stability, and record the OS, Prism and kernel versions, the test time and the specific failing fields instead of looking only at red and green. Results are also affected by proxy reputation, real hardware and changing website rules. For the full method, see What a browser fingerprint is and how to test it.

FAQ

A fingerprint test shows red. Is the profile broken?
Not necessarily. First identify the specific field: a detected proxy, a time zone that does not match the IP, font differences, or a test site applying rules for newer versions to an older kernel. Proxy problems need a different proxy; for time zone problems, use “Apply Proxy Time Zone” in the proxy settings.
Can I fully customize the UA, memory or resolution?
You cannot enter a free-form UA string; the brand version is matched to the kernel automatically. CPU, resolution and GPU are set together by the template to avoid contradictory combinations. Older profiles keep their “Legacy Custom Configuration” so their existing identity does not change.
Are mobile or Linux fingerprints supported?
No. Prism only emulates Windows and macOS desktop identities.
Do Community and Pro have the same spoofing capabilities?
Fingerprint settings are the same in both editions. Community uses the bundled Chromium 144 kernel; Pro can also use Chromium 150 / 153 kernels. See Fingerprint kernel.