2. The two engines
This is the single most important thing to understand about Clout, and the thing most likely to confuse you if nobody tells you.
Clout does not have one browser. It has two, and which one runs a given profile is decided by where that profile came from, not by a setting you choose.
A customer who does not know this will not understand why a profile imported from Kameleo behaves differently from one imported from AdsPower, why one of them survived the move with its canvas fingerprint intact and the other did not, or why one of them refuses to start on a machine where the other starts fine.
The routing
WHERE IT CAME FROM STORED AS RUN BY
────────────────────── ──────────────────── ─────────────────────
AdsPower ┐
Dolphin Anty │
Multilogin ├───────► AdsPower format ──────► SunBrowser
GoLogin │ (AdsPower's Chromium)
made in Clout ┘
Kameleo ────────► Kameleo format ───────► Chroma
(kept as it was) (Kameleo's Chromium)
Five of the six sources converge on one format and one binary. Kameleo is the exception, and it is an exception on purpose.
Why Kameleo keeps its own format. We can already drive Kameleo's engine at very close to parity with Kameleo itself. Converting a Kameleo profile into the AdsPower format would throw that away and pay a fingerprint cost (below) on the one vendor where we do not have to pay it. So a Kameleo profile arrives as a Kameleo profile, stays one, and runs on Kameleo's own browser. From the site's point of view nothing about it changed.
You cannot switch a profile between engines. There is no toggle, and there should not be: getting it wrong is not a crash, it is a browser that presents the wrong machine.
What conversion costs, precisely
If your profiles come from Dolphin, Multilogin or GoLogin, they are converted into the AdsPower format. Three fingerprint surfaces change:
- Canvas
- WebGL image
- Audio
Those three are not copied values; they are noise, applied to what the browser draws, seeded from four numbers stored on the profile. Every vendor's noise function is different, so carrying the old seed across would not help. The same seed through a different function gives different output. Preserving them would mean reimplementing each vendor's noise algorithm inside a browser binary we do not build. It is not a thing we chose not to do; it is not available.
What is preserved across every conversion:
user agent · platform · screen size and pixel ratio · timezone · geolocation · language and Accept-Language · fonts · CPU core count · device memory · WebGL vendor and renderer strings · WebRTC mode · proxy, and, where the importer can reach them, your cookies and stored passwords, so the account stays signed in.
Nothing is paid at all on the Kameleo path. A Kameleo profile keeps its format and its engine, so all three noise surfaces read exactly as they did.
How much this matters to you
| Your profile | Risk |
|---|---|
| New, or lightly used | Low. Nothing has recorded its old canvas hash |
| An aged account moved together with its cookies | Higher. The site sees the same signed-in identity with three surfaces changed at once |
| A site that never fingerprinted canvas | None in practice |
We have not yet measured this as a number. A before-and-after fingerprint run on one real profile per vendor is outstanding work. Until it exists, treat the table above as a judgement, not a measurement, and move your most valuable aged accounts last.
Where the browser itself comes from
Neither engine is bundled inside the Clout app, and they arrive by two different routes. This is the thing most likely to catch you out on a new computer.
SunBrowser, we host. The app downloads and installs it from our own servers the first time it needs one, about 340 MB per version. You do not need AdsPower installed, signed in, or on the machine at all. If you do have AdsPower, its own installation is used as a second place to look, so an existing machine does not download what it already has.
You will meet this as a strip at the top of the window. Press Start on a profile whose engine is not here, and the launch parks rather than failing: the strip offers Install, fetches that exact version, and opens the profile when it lands.
Chroma, Kameleo hosts. We do not redistribute it. A Kameleo profile runs on the Chroma build in Kameleo's own kernel directory, so:
- To run Kameleo profiles you need Kameleo installed on that machine.
- If you import from Kameleo and then uninstall Kameleo, those profiles stop launching. Your data is not gone; the engine that opens it is.
Published versions
SunBrowser packages are available for these hosts:
| Your computer | SunBrowser versions published |
|---|---|
| macOS, Apple silicon or Intel | 143, 144, 145, 146, 147, 151 |
| Windows, x64 | 143, 144, 145, 146, 147, 151 |
| Linux, x64 | 143, 144, 145, 146, 147, 151 |
A pinned profile requires its exact major. Clout does not substitute a newer browser to make a missing version appear to work: changing the browser version changes part of the identity a site sees. Imported profiles keep that version sealed along with their fingerprint.
If a profile needs a version outside this table, tell us its version and your platform. An engine being published for another platform does not make that package runnable on your computer.
Choosing a version
When you create a profile you can pick which browser version runs it, from the ones installed on that computer:
Browser - Auto - newest installed Installed SunBrowser kernels. The newest is used when unset.
The list comes from the machine, so it differs per computer. Leave it on Auto unless you have a reason: an unpinned profile is created against the newest version installed here, and a profile pinned by hand is a profile that will not start anywhere that version is missing.
The fleet list shows each profile's version in a Browser column (C146, C145), so you can see at a glance what your fleet is spread across. That column is the first thing to look at before you sign in on a second computer.