v0.1.17418 Aug 2026·Rendering, Networking, Privacy & Shields

Counterfactual Browsing: see exactly what a script did to your page (a world-first)

Every web user has asked the same question and no browser has ever answered it: what is this script actually doing to me? You can block a tracker on a hunch, but you cannot SEE what it changed, so the decision is folklore. Floati can answer it in pixels, because its render is a pure function of a saved page - the same bytes always paint the same picture, exactly. So it forks a sealed page, subtracts exactly one script, renders again, and shows you the difference: the pixels that script, and only that script, caused. Point at an ad-tech tag and the injected banner plus everything it shoved down the page lights up; point at a 'consent' or analytics tag and the answer is often that it painted NOTHING - it ran, it read your cookie and your user-agent, and it changed not one pixel, which is the pure-tracker signature laid bare. No mainstream browser can do this: their pixels are non-deterministic (two identical renders differ), their page execution is not replayable, and reloading a page minus a script fetches DIFFERENT bytes because ads rotate and experiments flip - so any diff they make is noise on top of confounds. Floati's diff is exact, and it can be sealed into evidence anyone holding the saved page can re-check offline, forever, so a tampered page cannot pass itself off as the honest one and forging a different claim is not feasible. It is shown from start to finish - a page with a silent tracker and a banner injector is saved, the site is taken offline, and the banner is attributed its exact pixels and the tracker zero, the same result every run - and it works entirely on your own machine with no internet. It is available today under the hood, not yet a one-tap panel in the app; Security moves 42 to 43, and the overall holds at 57 (a new capability like this is real, but not one of the big under-the-hood pieces the overall score waits on).

Parity with the reference browser

74overall, as of v0.1.343

Web APIs / DOM surface42

Security architecture66

GPU / graphics acceleration68

DevTools / extensions72

Networking85

Media85

Accessibility85

Real-world site compatibility99

HTML parsing100

CSS parsing + selectors100

Layout: block / flex / grid / tables / writing-modes100

Paint + visual100

JavaScript language100

JavaScript performance (JIT)100

HTML parsing100

What changed 4 changes

Privacy & Shields	Counterfactual Browsing: point at any script on a saved page and see, in pixels, exactly what it did - the banner it dropped in, the content it pushed around, or nothing at all. It works offline and the answer is exact, because the browser can show you the page with that one script removed and compare the two.
Privacy & Shields	It exposes the pure tracker: a script that reads who you are but draws nothing on the screen is shown to have changed zero pixels, while an ad tag lights up the banner it added and everything it shoved down the page. Blocking becomes a decision based on evidence instead of a hunch.
Networking	Every finding can be sealed into evidence anyone can re-check offline, forever, and a tampered page cannot pass itself off as the honest one - a kind of answer a browser whose rendering is not repeatable simply cannot give.
Rendering	Removing a script to test it never disturbs the ordinary page - a page you are just reading looks exactly the same as before - so the tool adds no risk to everyday browsing while giving you a clear before-and-after whenever you ask for one.