Anti-detect browsers
Che Browser
Che Browser’s documentation describes profiles collected from real devices and assigned to one user. The product is also described as a browser for managing multiple accounts on different websites.
For media buyers comparing profile tools, the key question is whether the documented setup and its technical limits fit their workflow.
Editorial review based on public sources, without hands-on testing; facts checked on 2026-11-01.
This page contains no partner link to this service.
- Name
- Che Browser
- Category
- Anti-detect browsers
- Official site
- chebrowser.site · No link provided
- Facts checked
Which parts make up Che Browser?
The documentation describes a native application and browser extension, according to the two documentation sources checked on 2026-11-01.
- Application: native profile-management app for Linux or Windows (chebrowser-beta-doc.readthedocs.io, checked 2026-11-01).
- Extension and browser: Chrome extension that alters browser data, plus patched Chromium (chebrowser-doc.readthedocs.io, checked 2026-11-01).
How are real-device profiles assigned?
The documentation says profiles come from real devices and are provided to only one user.
Separately, che-browser.install.download says Che Browser can block ads and trackers. That is the page’s description of the feature; it does not establish how well blocking works.
What does the free-license listing cover?
che-browser.install.download lists Che Browser for Windows with a free license, according to the page checked on 2026-11-01.
- License: free, for Windows (che-browser.install.download, checked 2026-11-01).
Which proxy and display limits matter?
The documentation says Chrome must be installed for the software to work. That requirement is a practical dependency to account for when assessing the application.
Display handling has documented limitations: native resolution spoofing can leave pages extending beyond the window without scrollbars, and the documentation describes scrolling shortcomings. Another documentation page says resolution spoofing works at the JavaScript level, while media-query spoofing remains in development.
The proxy notes flag two different behaviors. The beta documentation reports that DNS traffic can periodically bypass the proxy on a new profile’s first browser launch; it also says WebRTC spoofing retains the previous proxy address after a SOCKS change. A separate documentation page says the browser closes and restarts automatically in the first-launch DNS case. The install page also reports that some popular plugins and extensions are unsupported. Several purchase details are listed under What we could not confirm.
What does the documented app bring together?
The documented advantages are a profile-management application, a browser extension with patched Chromium, and profiles the documentation describes as sourced from real devices.
- The native application manages browser profiles on Linux or Windows.
- The documentation describes an extension that alters browser data alongside patched Chromium.
- Profiles are described as real-device data assigned to one user.
What we could not confirm
- Pricing: plan structure, profile or user limits, and payment terms.
- Trial and refunds: whether either is offered and under what conditions.
- Terms: usage restrictions and acceptable-use rules.
- Company details: legal entity, address, and company history.
- Support: available channels and expected response times.
- Integrations and setup: supported connections and requirements.
- Beta documentation PDF: the page could not be read because it was not HTML.
Does a new profile change DNS behavior?
What happens to DNS traffic on a new profile’s first launch?
The documentation says DNS traffic may bypass the SOCKS proxy on a new profile’s first launch, prompting the browser to close and restart automatically, according to chebrowser-doc.readthedocs.io, checked 2026-11-01.
What happens to WebRTC spoofing after a SOCKS change?
The beta documentation says changing the SOCKS proxy does not require a browser restart, but WebRTC spoofing retains the previous proxy address, according to chebrowser-beta-doc.readthedocs.io, checked 2026-11-01.
How does the documentation describe screen-resolution spoofing?
chebrowser-doc.readthedocs.io says screen-resolution spoofing operates at the JavaScript level, while media-query spoofing is still in development, according to the page checked 2026-11-01.
Are the profile and proxy details enough?
Fits if… the documented profile-management app and its supported operating systems match the workflow you need.
Probably not if… media-query spoofing is essential, since the documentation says it remains in development.
Main risk… a SOCKS change leaves WebRTC spoofing with the previous proxy address, according to the beta documentation checked 2026-11-01.
Sources
Below are the public pages behind the facts above, together with the date each one was read.
How this page was prepared
Editorial team of Spend Ledger. The editors at Spend Ledger wrote this page from the public sources listed above, which were read on 2026-11-01. No hands-on trial of the service took place. If a source changes, the page is revised.
Last updated:
Right of reply
To dispute this entry, Che Browser or its representatives should write to us with evidence that it is inaccurate or outdated. A documented refutation leads to a correction or removal of the entry. No payment changes what we publish.
- Our contact for replies
- No data available
- Response time
- No data available