Show HN: Zigzag, a native Mac browser for people leaving Arc

  • Posted 3 days ago by ZigaoWang
  • 102 points
https://github.com/ZigaoWang/zigzag
Hello HN! I am Zigao, a high school student from Shanghai. I am new to HN so hello to y’all!

I used Arc everyday, and I never had any issues with it. So when The Browser Company announced that they will shut down Arc on Dec 22 I was devastated. I don’t want to switch back to boring tabs along the top. Everything else i’ve tried is either a Chromium fork or an AI integrated browser that I don’t want. Therefore, I’ve been building my own browser for the last three weeks. Its name is Zigzag, a free and open source Mac browser that works just like Arc, written in Swift and based on WebKit. It is lightweight and fast.

Zigzag has:

- The stuff you missed from Arc (obviously, that’s the point)...

- Import from Arc (or any other browser) brings everything (your spaces, pins, history, passwords, cookies, etc)

- Chrome extension support! Even though its based on WebKit, you can install them from the Chrome Web Store. Extensions such as 1Password, Bitwarden, dark reader, Return Youtube Dislike, Tampermonkey all work)

And most importantly:

- Privacy: no account, no telemetry, no analytics

- Free and open source: no one can shut it down, anyone can contribute and fork their own copy!

- It’s tiny and fast! Around 18 MB installed (Arc is over 800 MB), no Chromium, no Electron (eww)

Some minor features that are nice-to-haves:

- Built in ad blocker using uBlock origin’s and Easylist’s filter lists

- Cookie popups turned down for you automatically, never accepted

- Split view up to four pages, drag pages intuitively

- Install any website as apps (still polishing it)

- Developer mode for web devs

- Little Arc (called Zigzag Mini)

- AI apps can use your browser if you want (MCP, off by default), stop button built in

- AppleScript and Shortcuts support, written in the conventional way

Why WebKit?

- I once tried to fork Helium and build on that. But the source was around 100 GB and builds took 3 to 4 hours on my Mac. Shipping Chromium is nearly impossible for me as a solo dev

- Battery and RAM: WebKit is built for Mac by Apple, its generally easier on battery and memory than Chromium

- Native: Swift + WebKit = behaves like a real Mac app, explained later (e.g. Zen)

- Chrome extensions already works on Zigzag, so the point of using Chromium is mostly gone

Why not Zen or Orion?

I tried both before building this, because I was looking for alternatives. They are good browsers, just not what I wanted.

Zen is based on Firefox. It is basically an Arc replica but it’s a Firefox under the hood, so you get Firefox extensions instead of Chrome extensions, and it doesn’t really feel like a native Mac app, which was kinda backwards. If you love Firefox it’s great, but it didn’t feel like Arc to me.

Orion is the closest to what I wanted in terms of speed, lightweightness and nativeness (are these even words?). It is WebKit and runs Chrome extensions. But it is closed sourced, and it is nowhere like Arc. It has vertical tabs but no real spaces, pins or favorites like Arc. It feels like a Safari clone instead of an Arc clone, so I turned it down. I love how it supports Chrome extensions, so that’s why I’ve done the same in Zigzag.

So how do Chrome extensions work on WebKit?

This is probably the part people ask about the most, so here you go.

In macOS 15.4, Apple added web extension support to WebKit itself. Safari only takes extensions that come wrapped in an app from the App store, but the engine underneath can load a normal Chrome extension folder. So when you click “Add to Zigzag” on the Chrome Web Store, Zigzag downloads the extension straight from Google. It checks its signatures, unpacks it, and hands it to WebKit.

That’s the easy part, and frankly most WebKit browsers can do that easily. However, WebKit doesn’t have every Chrome API. Stuffy like history, bookmarks, downloads, side panels, notifications and a few others just aren’t there. So Zigzag fills those in itself. When an extension calls one, Zigzag answers it, but only if that extension asked for that permission. 1Password and Bitwarden works, because they talk to their Mac apps the same way they do in Chrome.

The hardest one was Tampermonkey. WebKit has no userScripts API at all, so I had to build my own on top of WebKit’s content scripts, with each extension’s scripts kept separate from the extension itself like in Chrome.

What doesn’t work yet:

- the debugger API (so things that control the browser like Claude for Chrome cant control the pages, but there’s MCP that you can turn on if you want)

- Chrome’s own Google sign in for extensions (chrome.identity)

- Some old way of blocking requests that some extensions still use (webRequest from manifest V2) (e.g. uBlock origin full doesn’t work, but lite version works)

Most popular extensions are fine though. If any extension doesn’t work, leave a comment below or open an issue and I will look into it.

How I build it

Honest up front: I built Zigzag with the help from Claude Code. But it is not another piece of AI slop app. I decide what it does and how it should feel, and every change goes through my own daily browsing before it ships. It is my daily browser now for three weeks, and I am just like any of you, I don’t want trash apps! Claude writes most of the code, but I am the one reviewing the quality, the functions and the UI/UX decisions. Try it out yourself or open a PR if you can do better!

What’s missing

It is still a beta. No sync between Macs yet (passwords sync through iCloud keychain though). No boosts or easels. Needs macOS 15.4 or newer.

Try it

https://zigzagbrowser.com

https://github.com/ZigaoWang/zigzag

If you try it I’d love to know what didn’t went so well (or what did went well!), which extensions you need, and any sites that break. I read every issue on GitHub and every comment below! Thank you for your time!

31 comments

    Loading..
    Loading..
    Loading..
    Loading..
    Loading..
    Loading..
    Loading..
    Loading..
    Loading..
    Loading..
    Loading..
    Loading..
    Loading..
    Loading..
    Loading..
    Loading..
    Loading..
    Loading..
    Loading..
    Loading..
    Loading..
    Loading..
    Loading..
    Loading..
    Loading..
    Loading..
    Loading..
    Loading..
    Loading..
    Loading..
    Loading..