A free anti-detect browser with an engine of our own
Most anti-detect browsers wrap the browser's own functions in JavaScript, and a page can find a wrapper. Proxya Anty is a source-patched Chromium 152: the fingerprint is applied inside the engine, there is nothing wrapped to find, and there is no profile limit.
Free anti-detect browser, without a profile cap
Proxya Anty costs nothing to download and nothing to keep using. The only paid thing on this page is the proxies, and those do not have to be ours.
$0, no trial clock
There is no free plan that expires and no paid tier that unlocks the engine. The browser you download is the whole product.
No profile limit
Ten profiles or a thousand, on one machine or a farm. There is no per-profile and no per-seat charge to grow into.
An account, not a card
A Proxya account is required: the licence, the engine download and your proxy list hang off it. Creating one costs nothing.
Proxies are optional
Proxies you add by hand work exactly like the ones from your account. Buying them here is a convenience, not a condition.
An anti-detect browser with an API: Python, Node, Playwright, MCP and Docker
Node, Python and MCP control the running desktop app through its authenticated loopback API. Playwright and Puppeteer attach to a started profile over DevTools. Docker provides the pinned Linux runtime for CI and farms.
pip install proxya-anty
export PROXYA_ANTY_API_TOKEN="..."
from proxya_anty import ProxyaAnty
anty = ProxyaAnty()
profile = anty.create_profile(platform="windows")
session = anty.start(profile["id"], headless=True)
print(session["cdp"]["web_socket_debugger_url"])
anty.stop(profile["id"])Two credentials, two separate jobs
For Node, Python and MCP, copy the Local API token from the desktop app under Settings → Local API. Docker uses PROXYA_ANTY_LICENCE from your proxya.co account under Settings → Proxya Anty. Neither value is your account password.
Anti-detect browser test results: BrowserScan, PixelScan, SannySoft
Public detector runs on the release build of the engine, next to the acceptance and leak suites every release has to pass.
Bot signal and browser authenticity
No bot detectedFingerprint consistency, masking and automation
Consistent · no masking · no automationHeadless and stealth scoring against stock Chrome on the same host
0% headless · 0% stealthBrowser automation surfaces
55 / 55 passVisitor ID stability within a profile and separation between profiles
Stable per profileisBot and CDP automation signals
isBot: false · no CDP signalNon-interactive challenge, no solver and no token injection
PassHuman score on the public demo
0.9Transport fingerprint parity with Chromium 152
Matches Chrome 152Local-address leak with a proxy bound
No leakEngine-level fingerprint surfaces, read back from a page
43 / 43 passHost values cannot escape the selected profile
11 / 11 passCheck the proxy exit with our anonymity checker.
What a Chromium-level anti-detect browser spoofs: 25 surfaces
Each of these is answered from the profile at the point Chromium computes it, not from a script layered on top. Twelve of the twenty-five, in the order a detector reads them.
Navigator
Platform, vendor, cores, memory, languages. Answered in Blink, where User-Agent Reduction reads them.
Canvas
Both readback paths — getImageData and toDataURL. Stable across reads, different from the machine underneath.
WebGL
Vendor and renderer strings, masked and unmasked, where ANGLE reports them.
Audio
Sample data perturbed once per buffer, so a page that reads twice sees no drift.
Fonts
The list the process can enumerate. Both document.fonts.check and the width-measuring trick get the same answer.
Client rects
Sub-pixel geometry, nudged in the report rather than in the layout — nothing on the page moves.
TLS handshake
The ClientHello, read before a line of script runs. Measured against stock Chrome on the same machine: the same JA4, to the character.
Text metrics
Windows returns a glyph's box in whole pixels and macOS in fractions, so a masked font list still measured in the host's fractions until this.
Media queries
Dark mode, reduced motion, forced colours. CSS asks the operating system directly, and the host was answering.
WebRTC and QUIC
UDP is carried over the proxy's own relay, so HTTP/3 works and WebRTC candidates report the exit. Where a proxy has no UDP path, nothing is gathered rather than leaking around it.
Screen and client hints
Resolution, colour depth, device pixel ratio and User-Agent Client Hints drawn from the same device as the GPU and core count.
Extensions per profile
From a Web Store link, a .crx, a .zip or a folder. Each profile carries its own copy, so a page cannot pair two profiles by the extension they share.
An anti-detect browser with proxies from one account: residential, ISP, mobile
The browser is one half of the disguise. The address it comes out of is the other, and a profile whose timezone argues with its exit IP has given itself away before the first page loads.
Your proxies, already in the list
Sign in and everything on your Proxya account is there — nothing to copy across by hand.
- Residential, ISP, datacenter and mobile, from the same account as the website
- Timezone, locale and geolocation resolved from the exit before the browser starts
- The exit is given a TCP fingerprint matching the operating system the profile claims
- Credentials sit in a loopback relay, so the browser is never asked for a proxy password
Devices that hold together
A fingerprint is not a list of random values. The GPU, the core count, the screen and the font list are drawn as one machine.
- A library of coherent devices rather than fields you fill in one at a time
- Canvas, audio and WebGL noise seeded per profile — stable for that profile, different from every other
- Choose from 168 curated fingerprints, or import one you already use
- Every value visible and editable, with the reason it matters written next to it
Multi-accounting with a separate device per account
Every profile is its own machine: a coherent fingerprint, isolated cookies and storage, and a proxy exit whose timezone agrees with it.
For Playwright, Puppeteer and AI agents: local API, SDKs, MCP, Docker
The same profiles, without a person clicking Launch. Playwright and Puppeteer attach over DevTools, and an assistant drives the same profiles through the MCP server.
Local API
An HTTP API on loopback, authenticated with a token, off until you turn it on.
- Start, stop and list profiles
- Create profiles and bind proxies
- Import and export cookies
SDKs and MCP
Wrappers for the two languages this gets written in, and a server an assistant can drive.
- Node and Python packages
- An MCP server with 39 tools
- Same auth as the API
Docker runtime
A pinned Linux x64 image for CI and farms, with the engine and SDK runtimes already installed.
- Versioned proxya/anty image
- Runs as a non-root user
- Licence supplied only at runtime
Automated, and still not read as automated
Automation reaches the profile through the local API and Chromium's debugging protocol. Fingerprint changes remain inside the patched engine rather than being injected into the page.
- Attaching a debugger changes how the browser describes an error, and the widely used check reads exactly that. Here it reads nothing.
- It also makes a console call about fifteen times more expensive, which a page can time. The patched engine removes that measured difference.
- The release table compares the same public detectors, on the same day, against a stock Chrome driven by Playwright.
Free anti-detect browser: questions people ask before downloading
Short answers, and where they are checkable, the way to check them.
No browser can promise that, and any that does is selling you something. What can be said is where the disguise lives: inside the engine rather than in a script layered on top, which removes the whole class of checks that compare a function against a clean copy of the browser. The rest — how you behave, whether your proxy is clean, whether the account history makes sense — is not something a browser controls.
A wrapper is a replacement function. A page can create a fresh iframe, take the original function from it, and compare — they differ. Proxya Anty changes the values where Chromium computes them, so the function a page inspects is the browser's own. The verification the engine ships with runs the binary with nothing but a profile file and reads back what a page sees. A stock Chromium fails every line of it.
No. Proxies you add by hand work exactly the same, and so do profiles and fingerprints. Signing in only saves you copying credentials: the proxies on your account appear in the list, and the exit's country is used to resolve the timezone and locale before the browser starts.
Yes. Windows x64 and macOS Apple Silicon builds are both on GitHub Releases. The Mac build is ad-hoc signed rather than notarized, so the release includes a one-time Gatekeeper installation step. Linux x64 ships as AppImage, DEB and RPM packages, and as the Docker runtime.
No browser can guarantee a verdict on every site, so we publish measured results instead. A stock Chrome driven over DevTools exposes automation signals unrelated to its fingerprint. The patched engine closes the tested error-stack, console-timing and WebDriver traces. Run the same public detection page through Proxya Anty and plain Playwright and compare the two results for your own workflow.
Yes. There is a local HTTP API on loopback, authenticated with a token and off until you switch it on, plus packages for Node and Python and an MCP server. Every profile also exposes DevTools, so Playwright and Puppeteer attach the way they would to any Chromium.
It is free with a Proxya account, and the account is the only condition: the licence, the engine download and your proxy list are attached to it. There is no profile cap, no per-seat charge and no trial that runs out. The only paid thing is proxies, and proxies you add by hand work exactly the same as the ones bought here.
Partly. The Node and Python SDKs and the MCP server are MIT-licensed and their source is in the GitHub repository. The desktop launcher, the fingerprint catalogue and the Chromium patches are proprietary and ship only as signed release binaries, with SHA-256 checksums published next to every file. If you need a fully open-source browser, Camoufox or Donut Browser are the honest pointers. If you need engine-level patches with a free desktop app, that is this one.
Yes. Linux x64 ships as an AppImage, a .deb and an .rpm, and as the Docker image for servers and CI. Text metrics are handled per platform, so a Linux host can run a Windows or macOS profile without the glyph-box mismatch a masked font list normally gives away.
Profiles, cookies, storage and fingerprints live on your own disk. The desktop app encrypts its account and application state at rest. What goes to proxya.co is the sign-in, the licence check and, if you use them, the proxies on your account. Proxy credentials are held by a loopback relay on your machine, so the browser itself is never handed a proxy password.
Running a browser with a fingerprint you chose is legal almost everywhere. What a site's terms allow is a separate question, and multi-accounting can breach them. Proxya Anty is a tool for managing separate identities on your own machine. It does not make any account immune to a platform's rules, and it is not sold as a way around them.
Camoufox is an open-source Firefox fork for Playwright and scrapers, without a profile manager. Donut Browser is an open-source Chromium-based desktop app with unlimited local profiles. Proxya Anty is a source-patched Chromium with a desktop app, no profile cap, proxies from the same account that sells them, and published detector results. Its engine is closed. Which one fits depends on whether you need the source or the measured engine.
Download the free anti-detect browser for Windows, macOS and Linux
Builds for all three platforms are on GitHub Releases. Proxya Anty is free with an account, and proxies you add yourself work too.