Fingerprint identity
The device identity a profile presents
A browser tells every site what kind of machine it is running on. PowerOps decides what a profile says, generates the answer as one coherent set, and gives the same answer every time.
001Facebook Adsadsfacebook.com · opened 2 min agoPaid socialNL · socks5Open002Instagram Shopshopinstagram.com · opened just nowPaid socialDE · httpSyncing003TikTok Creatororganictiktok.com · opened yesterdayCreatorsGB · socks5Closed004YouTube Channelvideoyoutube.com · opened startingCreatorsUS · socks5Opening005Pinterest Boardsboardspinterest.com · opened 3 days agoResearchDE · directClosed006X Brandbrandx.com · opened 1 hr agoPaid socialUS · httpOpenCoherent beats novel
The failure mode of a fingerprint tool is not being too visible. It is being self-contradictory.
Randomising values one by one
- Each value randomised on its own, producing machines that could not exist
- A timezone in one country and a language list from another
- Four cores and 64 GB of memory in the same device
- A Windows user agent over a macOS font list
- A new identity on every launch, which is stranger than never changing
With PowerOps
- Every value derived from one seed, so the same profile is the same device each time
- Timezone, locale and language list chosen together from one region
- Core count and memory chosen together from real hardware pairings
- Fonts and graphics strings that match the operating system being claimed
- An advanced editor for the values you have a real reason to set
The identity card
What is pinned, and what is observed
Two lists, kept apart on purpose: what PowerOps sets, and what still comes from the machine you are sitting at.
PowerOps generates and pins the target identity
- Operating system
- Windows 11, including the platform version reported to client hints
- User agent
- Derived from the browser version and the target operating system, not the host's
- Timezone
- From a region preset, so it can never disagree with the locale
- Language & locale
- From the same region preset, as an ordered language list
- Screen resolution
- A real desktop resolution, with the available height a taskbar would leave
- CPU cores
- Paired with memory, so the two cannot describe a machine that does not exist
- Device memory
- Paired with the core count from a fixed set of plausible desktops
- Graphics adapter
- A Windows GPU reported with the exact ANGLE/Direct3D string shape Chromium uses
- Installed fonts
- The real Windows 11 font list, not a sample of it
- Canvas, WebGL and audio
- Seeded per profile by the browser, so readings are stable for that profile
The observed environment follows the computer
- Colour depth and pixel ratio
- Follow the display the browser is actually running on
- Speech voices and AudioContext
- Follow the host operating system
- Some font families on macOS
- A few macOS families remain visible when the host is a Mac
A short list, and a deliberate one: a list of what a tool sets is only readable next to a list of what it does not.
Generated as one set
Nothing above is rolled independently. The region decides timezone, locale and language order together. The hardware level decides cores and memory together. The target operating system decides the platform version, the font list and the shape of the graphics strings. A profile cannot end up claiming a timezone its locale contradicts, because there is no code path that would produce one.
How an identity is produced
- 1
A seed is stored on the profile
One number, kept inside a range every part of the browser reads identically, so two components can never derive different values from the same profile.
- 2
The set is derived from it
Region, screen, hardware, graphics, fonts and platform version are all derived from that seed, in combinations chosen so they agree with each other.
- 3
The browser is launched with it
Orbit Browser receives the identity for the whole session, alongside the profile's own browser directory and network route. It holds for as long as the profile is open, and it is the same identity the next time you open it.
What you actually control
The editor exposes the choices that have a reason behind them, and derives the rest.
Region
One choice that sets timezone, locale and language order together. Eight presets covering common desktop regions.
Screen size
A real desktop resolution, with the available height a taskbar leaves behind.
Hardware level
A core-and-memory pairing from a fixed set of plausible desktop machines.
Advanced overrides
Timezone, languages, resolution, pixel ratio, cores, memory and WebGL strings, for the cases that need them.
Regenerate
Roll a new seed for a profile and get a new coherent identity. You do it deliberately, and a launch never does it for you.
Target operating system
Windows 11 is the identity this build targets, including the platform version reported to client hints.
Fingerprinting, answered plainly
What is a browser fingerprint?
The set of values a page can read about the browser and the machine under it: the user agent, the screen, the timezone, the language list, the graphics adapter, the fonts installed, how canvas and audio render. Individually they are unremarkable. Together they are specific enough to recognise the same browser again without a cookie.
How many parameters does PowerOps control?
The ten groups listed on this page, generated together from one seed. There is no bigger number on this site because a count of individually randomised values measures nothing. A set that contradicts itself is worse than a smaller set that does not.
Why does the identity stay the same instead of rotating?
Because a device that changes its screen, its graphics adapter and its font list between visits is stranger than one that never changes. A profile's identity is derived from a stored seed, so the same profile presents the same device every time it opens.
Can I edit the identity myself?
Yes, for the parts you have a real reason to set: region, screen size and hardware level, with an advanced editor for timezone, languages, resolution, cores, memory and WebGL strings. Everything you do not set stays derived from the seed, so it stays coherent.
Do you publish a fingerprint score?
No. Scores come from third-party checkers that change without notice, and a screenshot of a good one proves what happened on one machine on one day. If PowerOps ever publishes numbers, the method will be printed next to them.
Give every profile a device of its own
One seed per profile, one coherent device, the same answer every session.