Anti-detect browser
Real Chrome.Real private.Provably yours.
Run hundreds of isolated profiles on one machine — each a real Chrome with its own verifiable fingerprint and its own storage. Everything stays on your disk.
Don’t trust the claim — verify the fingerprint yourself.
$
audit complete — 6/6 passed · recorded on our latest build · reproduce it yourself
Right now, on this page
This is what every site already sees.
No login, no permission. The moment you opened this page your browser handed over a fingerprint as unique as a face. Here's yours — read live, on your machine.
- reading…
- reading…
- reading…
- reading…
- reading…
- reading…
Cuttle is the bench where you set every one of these.
Each profile gets its own coherent OS, screen, timezone, GPU and canvas — real values, not blocked or faked. The same audit you ran on us, you run on yourself.
Control your fingerprint →−400 m
We don’t ask you to trust us.
Point BrowserScan and CreepJS at it. Here’s exactly what they see.
across creepjs, iphey, pixelscan and BrowserScan — recorded on our latest build
Passes these scanners on our latest build. Scanners evolve — re-run the audit any time; the result should hold.
−500 m
What people run on a hundred clean profiles.
One machine, hundreds of sealed profiles — each with the fingerprint of an ordinary computer. A few of the jobs it’s built for:
Ad accounts, kept apart
Run advertising accounts for different products and clients side by side. Every profile is its own browser with its own fingerprint and its own storage — nothing is shared between them.
A fresh identity per offer
Spin up a distinct browser per offer, geo and traffic source. Separate storage, separate fingerprint — no common footprint between them.
One profile per storefront
Keep each store and its account in its own browser profile — separate device, location and fingerprint, never mixed together.
Client work, cleanly separated
Give every client their own isolated profile, and point it at whichever of your own proxies you want it to use. No shared cookies or sessions between the accounts you manage — and handover is a folder, not a password list.
−550 m
What you actually get.
Not a checklist of features — the working kit for running hundreds of profiles, the one you touch every day.
Hundreds of profiles
Each one a separate identity with its own real fingerprint. Isolated and non-overlapping — nothing is shared between them.
Real, current Chrome
A genuine, current Chrome engine — not a fork or a wrapper. Sites see an ordinary browser, because that is exactly what it is.
Timezone and locale follow the IP
Point a profile at a proxy you bring yourself and its timezone, language and WebRTC follow that exit address — no mismatch between what the connection says and what the browser reports. None is included: you use the provider you already pay for.
Built-in fingerprint audit
Run the same public scanners from inside the app and see exactly what sites see. Nothing to take on trust — the result is reproducible.
Local API
Drive your profiles from your own code — Selenium, Puppeteer or Playwright — over an endpoint that runs on your machine.
Everything on your disk
Profiles, cookies and fingerprints live on your machine. Nothing to lose or seize from someone else’s server.
−600 m
Hundreds of identities. None of them touch.
Every profile is a separate, sandboxed browser with its own coherent fingerprint — and it all lives on your machine, not on a server.
Real Chromium 149
Not a fork, not a wrapper — the actual engine scanners expect, which is exactly why they can’t tell it apart.
Hundreds of isolated profiles
Cookies, storage and fingerprints are walled off per profile. Nothing is shared between them.
Provable, per-profile entropy
Each identity carries its own canvas, audio, WebGL and font signature — so two profiles never read as the same device.
Illustrative signatures — coherent OS · timezone · locale per profile, never fake precision.
−800 m·Local-first by design
Your profiles never leave your machine.
Cloud antidetect browsers store your sessions on servers you don’t control — and those servers get breached. Cuttle is local-first by design: profiles, cookies and fingerprints stay on your own disk.
Profiles live on your own disk with sensitive credentials DPAPI-encrypted — no cloud sync: nothing on a server to subpoena or breach.
Get early accessProfile store
Cloud tools → your accounts on a server you don’t control
- Location
- ~/Cuttle · on disk
- Credentials
- DPAPI-encrypted
- Cloud sync
- none
- Telemetry
- 0 endpoints
−1000 m
Common questions.
Short answers, no marketing fog — the things people ask right before they install.
Is this even legal?
An anti-detect browser is a legal privacy and multi-profile tool: it doesn’t break into anything and doesn’t impersonate anyone — it gives each of your profiles its own honest, coherent fingerprint. How you use it is on you: platform rules and the law are yours to follow.
How is this different from incognito mode or just changing my IP?
Incognito only clears cookies — the browser still reports the same device, so separate accounts still read as one machine. Changing the IP alone does not help either: the fingerprint (canvas, GPU, fonts, timezone) stays identical. Cuttle works on that layer — every profile gets its own coherent set of device characteristics and its own storage. It is not a VPN and does not replace one: we operate no network of our own.
Do I need anything else to use it?
A Windows machine, and — if you want profiles to leave from different addresses — an account with any external IP provider you choose. Cuttle is desktop software: it runs no servers that carry your traffic, and it neither sells nor resells any connection service. It simply applies the connection details you enter, exactly as a stock Chromium browser does.
Do you guarantee results on any platform?
No, and nobody honestly can. We answer for our side: every profile gets a genuine, coherent fingerprint and its own storage, and your data stays on your disk. Both are verifiable. What any given platform decides is outside our control, and we make no promises about it.
Is it really a genuine Chrome?
Yes. Not a fork wrapper — a real, current Chrome engine, so scanners read a genuine fingerprint. Check for yourself: the same audit is built into the app.
Is my data safe?
Profiles, cookies and fingerprints live on your own disk, never synced to the cloud. Anything sensitive you enter — connection logins, tokens — is encrypted with Windows DPAPI. The account is only for licensing — your profiles never pass through it.
What does it run on, and how many profiles?
Windows 10 / 11 today — macOS is coming soon. Hundreds of profiles on one machine — the only limit is your hardware: RAM and disk.
Why we built this
Your identity is not their inventory.
Cloud anti-detect tools rent your fingerprints back to you and keep your accounts on servers you don’t control. We think that’s backwards. Your profiles, cookies and fingerprints belong on your machine — set by you, owned by you, gone when you say so. Cuttle is built on that one belief.
— the Cuttle team
−1200 m · the floor
Now hold the build.
You watched all six checks pass. The same audit ships inside Cuttle — launching soon. Join the waitlist and run it on your own machine.