One-click Cloudflare WARP for networks that block it. Zarp finds a zapret2 strategy that gets the WARP handshake through DPI, remembers it and connects. The macOS version of Zarp for Windows and Zarp for Android, a native app for Apple Silicon.
Note
Zarp won't open? The release is not notarized by Apple, so macOS blocks the first launch. Why won't Zarp open? shows the three clicks, with screenshots.
| Platform | Download | Requirements |
|---|---|---|
| macOS | DMG · all releases | Apple Silicon (M1 or newer), macOS 14+, an administrator password once. No WARP app needed |
| Windows | Zarp.exe · all releases · source | Windows 10/11 x64, administrator rights. Cloudflare WARP is installed by Zarp if it is missing |
| Linux | Ubuntu · Debian · Fedora · Arch Linux · all releases · source | Ubuntu 26.04, Debian 13, Fedora 44 or current Arch Linux; x86_64, systemd |
| Android | APK · all releases · source | Android 8.0+, no root, no WARP app needed |
Have questions, ideas, or feedback? Join our Zarp Community!
- ❓ Ask questions and get help
- 💡 Suggest new features
- 📢 Follow announcements
- 🗳️ Vote on upcoming improvements
- One button. The first press searches for the fastest working strategy, later presses connect right away.
- Its own WARP client. Zarp registers a free anonymous WARP account (after you accept Cloudflare's terms) and speaks MASQUE to Cloudflare itself, over HTTP/3 or HTTP/2. No
warp-cli, no official app. - The whole Mac. While it says Connected, all traffic (IPv4 and IPv6) and DNS go through WARP. The routes disappear with the tunnel, so even a crashed daemon leaves your network working.
- Honest testing. Quick Scan counts confirmed strategies and continues after failed rechecks. Two fresh successful connections confirm a candidate; the tooltip separately reports whether actual endpoints differed. A test passes only when the tunnel reports WARP traffic.
- Self-healing. If the saved strategy stops working, Zarp tries the other verified ones before searching again, and it reconnects by itself when the connection drops.
- Portable WARP strategies. Twenty-four executable profiles include the current Google x11/x12 and host/sld/endhost TLS splits. All/RU/IR/CN filters apply to scans, Connect, and fallback. Unsupported custom techniques carry a reason and never execute as direct connections.
- Your language. English, Русский, Español, Português, 中文, हिन्दी, Français, Deutsch and فارسی. Zarp follows the macOS language (English if it is not on the list), and the globe button switches it on the fly. Persian uses RTL with LTR technical inputs and tables.
- Protected account setup. If the account API cannot be reached, Zarp can try portable TLS zapret strategies for registration, MASQUE enrollment and WARP+ confirmation. Partial enrollment resumes with the same device. Lost creation responses pause automatic registration to avoid duplicate accounts. This does not start a tunnel or change routes, DNS or system proxies.
Current source builds also include WARP+ account management, manual servers and HTTPS subscriptions, source selection, and compatible server + zapret pairs. VLESS, Trojan, Hysteria2 and XHTTP use bundled, pinned engines through the outer strategy relay. These additions passed private HTTPS/UDP checks and build checks; actual product TUN and signed-installation acceptance remain unverified. See the Windows release review and implementation evidence.
Release 1.0.0 includes the WARP transport fixes and the source/server workflow. See the release notes for verified behavior and remaining limitations. Plain WARP connections are disabled.
- Open the disk image, drag Zarp.app to Applications and eject the image. Keep the installed name and path as
/Applications/Zarp.app: release connection preparation validates this location. - Open Zarp. macOS blocks the first launch; allow it once in System Settings > Privacy & Security > Open Anyway (screenshots below).
- Zarp prepares its connection automatically, including after an app update. If macOS requests authorization, approve it. If background activity approval is required, Zarp opens System Settings > General > Login Items & Extensions: allow Zarp under Allow in the Background.
- Turn off any other VPN, then press the power button. The first time, Zarp asks to create a free anonymous WARP account for this Mac and accept Cloudflare's terms on your behalf, then searches for a strategy and connects. The first search takes a minute or two.
Settings also accepts a custom public numeric WARP endpoint list with IPv4 and IPv6 addresses. A different list invalidates prior results. One endpoint can confirm fresh connections but cannot establish endpoint independence. Live verification of these implementation changes remains pending user-run checks.
Settings offer two searches. Quick scan (also used by the power button) stops after 3 confirmed strategies; the number is adjustable. Full scan tests every strategy: slower, but nothing is skipped, so it finds the fastest one for sure. Settings also has switches for Route all traffic through WARP and Use Cloudflare DNS.
Before showing Connected, Zarp checks traffic across a stability interval. Repeated short connection losses trigger a bounded search for other protected strategies, including a different transport. Results from another access network are rechecked when switching between Wi-Fi and a phone hotspot.
Settings > Servers and subscriptions imports VLESS, Trojan and Hysteria2 links, saves HTTPS subscriptions, downloads their server lists on Refresh, and keeps the last successful list if an update fails. You can cancel a download, delete a subscription and save a server selection for each source. Credentials and URLs are stored in private files. Select a source and server in the main window to find and confirm compatible server + zapret pairs. Product TUN and signed-release backend acceptance remain unverified.
Closing the window asks whether to hide Zarp in the menu bar or quit. Select Remember my choice to make that action the default; Settings > On close changes it later. Quitting disconnects WARP unless you turn off Disconnect WARP on exit.
Note
Turn off any other VPN (Happ, v2rayN, Clash, AmneziaVPN, ...) and Cloudflare's own WARP app before connecting. WARP traffic would go through that tunnel instead, and Zarp could not build its own. Zarp warns you when it sees one.
The release is not notarized by Apple (there is no paid Apple Developer membership behind this free project), so the first time you open Zarp macOS says it could not verify the app. Nothing is wrong with the download; you only have to allow it once.
1. Close the warning with Done.
Warning
Click Done, not the blue Move to Trash button: that would delete Zarp.
2. Open System Settings > Privacy & Security and scroll down to Security. Leave Allow applications from on App Store & Known Developers, the default (on macOS 14 it reads App Store and identified developers).
3. Click Open Anyway next to "Zarp" was blocked to protect your Mac and confirm with Touch ID or your password. If macOS asks once more, choose Open. Zarp starts, and macOS remembers your choice for this copy of the app.
No Open Anyway button? It shows for about an hour after the failed launch: open Zarp once more and look again. Zarp also has to be in Applications. On macOS 14 and earlier, Control-click on Zarp > Open works too (Apple removed that shortcut in macOS 15). Still blocked, or macOS says Zarp is "damaged"? Remove the download flag, then open Zarp again:
xattr -dr com.apple.quarantine /Applications/Zarp.appEvery new download (an update, for instance) is checked again, so you repeat this once for it. More help: docs/TROUBLESHOOTING.md.
The release notes list the SHA-256 of the disk image:
shasum -a 256 ~/Downloads/Zarp-*.dmg # compare with the release notes- A background service. Automatic preparation registers a root LaunchDaemon (
io.github.zarp.mac.zarpd). It is the only part with elevated rights and the only part that touches the network configuration, and it does nothing until the app asks. The app itself runs as you. - While connected: a
utuninterface, routes that send all IPv4 and IPv6 traffic through it (your real default route is not modified), one host route that keeps Zarp's own connection to Cloudflare off the tunnel, and the DNS of your active network service pointed at Cloudflare. Disconnecting removes all of it and restores your DNS exactly as it was. - Files: settings and results in
~/Library/Application Support/Zarp, logs in~/Library/Logs/Zarp, the WARP account (root-only) in/Library/Application Support/Zarp. The full list is in docs/ARCHITECTURE.md. - Only if you turn it on: Start with macOS adds Zarp to your login items.
-
In Settings, turn off Start with macOS (if it is on) and disconnect.
-
Quit Zarp. In System Settings > General > Login Items & Extensions, switch Zarp off under Allow in the Background, then delete
/Applications/Zarp.app. -
Optionally delete the data. This removes the WARP account too, so the next install registers a new one:
rm -rf ~/Library/Application\ Support/Zarp ~/Library/Logs/Zarp sudo rm -rf "/Library/Application Support/Zarp" /Library/Logs/Zarp /Library/Logs/zarpd.log /var/db/zarpd
Zarp has no telemetry and sends nothing to its author. It makes only these network requests:
- the one-time anonymous WARP registration with Cloudflare, after you accept Cloudflare's terms (no personal information is sent);
- the WARP tunnel itself, to Cloudflare's WARP addresses;
https://1.1.1.1/cdn-cgi/trace, through the tunnel, while testing and connecting, to check that traffic goes through WARP and to measure latency.
WARP is a Cloudflare service covered by the Cloudflare WARP privacy policy.
A strategy is a WARP transport (MASQUE over HTTP/3 or HTTP/2) plus a zapret2 profile. Before the real handshake, Zarp's background service sends a few decoy packets from the same UDP socket, so DPI classifies the flow as harmless and Cloudflare ignores the decoys; over HTTP/2 it splits the TLS ClientHello instead. A search tests each strategy on its own tunnel and endpoint and fetches cdn-cgi/trace through it. Score is connect time + 4 × ping, the same as on Windows and Android. The decoys are real captures from zapret2. The design, the security model and the failure behaviour are in docs/ARCHITECTURE.md.
Your own strategies go into strategies.txt (Custom strategies... in Settings), in the same format as on Windows:
# name | transport (h3, h2, wg) | zapret2 profile args | optional countries: ru,ir,cn
My QUIC | h3 | --payload=quic_initial --lua-desync=fake:blob=quic_google:repeats=8 | ru,ir,cn
Zarp supports plain fake packets (with ip_ttl, ip6_ttl, repeats) for h3 and multisplit / multidisorder for h2; anything else, including every wg line, is listed as unavailable. See the zapret2 manual for --lua-desync syntax.
Needs Xcode 16 or later, Go (the version in zarpd/go.mod) and XcodeGen.
brew install go xcodegen
make test # Go (vet, race detector) and Swift tests; no root, no network
make dmg # a signed disk image; needs your Apple Development teamInstalling the background service needs a signed app. Signing with your own team, running the daemon by hand and the real-network test (scripts/test-integration.sh) are in docs/DEVELOPMENT.md; releases are built locally, see docs/RELEASING.md. GitHub Actions builds and tests every push.
Bug reports, strategy results from your network and translations are welcome: see CONTRIBUTING.md. Please report security problems privately: SECURITY.md.
All UI strings live in Resources/Lang, one key = value file per language, with en.txt as the reference. To fix a translation, edit the file. To add a language, copy en.txt to <code>.txt, translate the values and add the code to Localization.languages (details). The tests check that every language has the same keys and placeholders as English.
MIT, see LICENSE. Zarp for Windows is MIT too; Zarp for Android is GPL-3.0 and was studied as a design reference, not copied (details).
Bundled components: usque, connect-ip-go, quic-go and the tun package of wireguard-go, all under permissive licenses, plus the fake packets from zapret2 (MIT). License texts are in Resources/Licenses, also reachable from Settings > Licenses.
Cloudflare and WARP are trademarks of Cloudflare, Inc. Zarp is an independent project, not affiliated with or endorsed by Cloudflare.


