so i have a browser now. it's called catweb, a pixel cat named tuft lives on the new tab page.
download: https://yupthatscole.github.io/catweb-releases/
what it is
catweb is a windows browser written in rust.
websites run on webview2, the same engine microsoft edge uses, so most sites just work. catweb draws everything around the page itself: tabs, address bar, menus, settings, downloads, and tuft.
there's also catweb native, a from-scratch rendering engine. it's an experimental side project, and tabs using it get an "Experimental" label. don't sign in to anything in those.
what it does
built-in ad and tracker blocking (easylist), toggle per site
tries https first, strips tracking junk from links
private tabs that forget everything when closed
tabs in the title bar, drag to reorder, reopen closed tabs (ctrl+shift+t)
address bar suggestions, bookmarks bar, history, downloads panel
imports your chrome bookmarks and history
themes and accent colors (default is "lavender soft")
updates itself and checks a signature before installing anything
silly settings, off by default. yes, the switches meow.
privacy
no accounts, no analytics, no telemetry. on its own, catweb only talks to:
github, once a day, to check for updates (can be turned off)
sites you visit, to grab their icons (never in private tabs)
microsoft smartscreen, for dangerous sites and downloads (on by default, can be turned off)
history and bookmarks stay on your pc. catweb doesn't save passwords.
it hasn't had an outside security audit, so i wouldn't use it for banking yet.
the smartscreen thing
catweb isn't code-signed (that costs money every year), so windows will warn you. click "More info", then "Run anyway".
if you want to check it first:
virustotal: https://www.virustotal.com/gui/file/ea48b93c00d2345afdcbc42327ce868ffac0f0fcb33bd4c1df12320d2c864cec/detection
every release has a sha-256 checksum next to the download
what's next
a vpn/proxy option someday, making catweb native good enough for real sites.
bugs
found one? open an issue at https://github.com/yupthatscole/catweb-releases/issues and say what you did and what happened.
meow

Top comments (7)
Using WebView2 for compatibility while keeping the privacy defaults strict is a sensible trade off. How do you handle sites that break when per-site blocking is on, and is there a quick way to report those breakages?
thanks! if a site breaks just hit the shield button in the address bar and it turns blocking off for only that site. it remembers it next time too, everything else stays blocked. if something’s broken just reply here or open an issue on the releases page and ill take a look
That per-site memory is the key detail for me, since it avoids turning protection off everywhere just to fix one page. I would also value a visible indicator for sites where blocking is paused, so the exception does not stay forgotten.
oh yeah that's actually already there. the shield turns purple when blocking is on and gets crossed out when it's disabled for a site. i probably should've shown that in the article lol
Thanks for clarifying that the purple shield already shows the per-site state. Does that state survive a restart, or does it reset when the browser closes? I am curious how you store that preference while keeping the no telemetry promise.
it resets when you close the browser, planning on changing it later but i honestly cant be bothered right now lol
That reset behavior actually makes sense as a safe default, since a fresh session cannot leak an earlier exception. When you revisit persistence, storing only the domain and toggle locally would keep the no telemetry promise while avoiding repeated setup.