v0.1.2061 Sep 2026·Web APIs & DOM, Privacy & Shields, Memory & reading

Explain this page: the browser now understands what a site does, and can prove it

A new kind of privacy tool, built into the engine. Open a page and press Explain this page, and the browser tells you, in plain language, everything the page actually did: which outside companies it contacted, which of those are trackers or ads (and the exact filter rule that caught each one), whether anything was sent over an insecure connection, and whether the page tried to secretly identify your device - a trick called fingerprinting, where a site reads tiny quirks of your browser to recognise you without a cookie. It does not stop at listing things: it explains WHO on the page caused each one, will remove an ad and neatly close the gap it leaves as if the ad was never there, and gives you a short proof code so what it reports can be independently re-checked. All of it runs on your own device; nothing about the page is sent anywhere.

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 7 changes

Privacy & Shields	A new Explain this page button captures the current page and shows a full, plain-language report: the outside domains it contacted, each tracker or ad request with the exact rule that flagged it, any insecure or mixed-content connections, and any attempt to fingerprint your device. Every single line traces back to a real request or action - it is not a guess.
Privacy & Shields	Under the hood the browser builds a complete map of the page - linking every element, script, network request and pixel to what created it and what it did - so it can answer questions no ordinary browser can, like which script quietly loaded a tracker, or what changed on the page a moment after it opened (even something triggered later by a timer). A timeline lets you see, in order, everything that happened.
Privacy & Shields	You can set a rule in plain English - for example 'block fingerprinting and trackers' - and the browser turns your sentence into an enforceable policy, with no settings maze to dig through.
Privacy & Shields	Self-healing pages: when a tracker or ad element is removed, the engine re-lays-out the page as if that element had never been written, and can prove the result is identical to a genuinely ad-free version of the page - so you get no empty holes, collapsed boxes or leftover gaps where the ad used to be.
Privacy & Shields	Every analysis produces a tamper-evident receipt: a short code, computed on your device, that anyone can re-check to confirm exactly what the page showed and what was flagged. Change a single detail and the code changes, so the report cannot be quietly faked.
Web APIs & DOM	Pages that lean on animation - floating shapes, rotating headlines, effects that trail your cursor - now render dramatically faster on Floati's own engine. The engine used to try to run every animation frame a page could produce before it showed you anything, so a busy page could sit on a spinner for the better part of a minute; it now settles the page and paints it the way a normal browser does - present first, keep animating after. Some sites that took around forty seconds now appear in about four, with no change to what you finally see.
Memory & reading	You can now make Floati's own engine your default for browsing (Settings, under Floati engine). This is a real step toward the bigger idea: Floati is one of only a handful of browsers in the world built on a from-scratch engine of its own, and the plan is for it to render everything you browse - privately, on your device, with the memory and understanding features that only work when the browser genuinely reads the page rather than just displaying it. The system renderer stays as a safety net: anything the engine cannot draw yet quietly falls back to it and stays there, so a page never breaks.