A fast, native WhatsApp client for Linux, macOS and Windows written in Rust and egui, with no browser engine.
- Language
- Rust
- License
- MIT
- Try it
yay -S zapfast-bin # Arch; Homebrew cask, AppImage, Nix and Windows builds also available
ZapFast is an open-source WhatsApp client for Linux, macOS and Windows written in Rust with the egui GUI toolkit, and it contains no browser engine at all. Its developer, GitHub user crmne, says it opens in under a second and idles at about 200 MB of RAM on Linux, against 1.13 GB for WhatsApp Web in the same test. The project drew a lively Hacker News thread this weekend, and GitHub's API showed it at roughly 3,500 stars and 350 forks on November 8.
Why it matters: most desktop chat apps are web apps in a wrapper, and users are noticing the memory bill. Discord's move away from Electron for its desktop app put that argument back in the spotlight this week. ZapFast applies the same idea, from the open-source side, to WhatsApp. It also comes with a real catch, covered below.
What it does
According to the README, ZapFast links to your phone as a companion device, the same way WhatsApp Web does. You either scan a QR code from WhatsApp's Linked Devices screen or type an eight-character pairing code on your phone. Recent chats sync first, and older messages load as you scroll.
Features listed in the README:
- formatted text, replies, edits, reactions, forwards, stickers, GIFs, polls and voice messages, with media playing inline;
- several linked phone numbers in one window;
- a local message archive encrypted with SQLCipher, unlocked through the OS keyring (added in version 0.14.0), with export to plain text or ZIP;
- per-chat and whole-app locks, tray presence, notifications and keyboard shortcuts;
- light, dark, system and custom JSON themes;
- eleven interface languages, according to Tech Bytes (Chinese in both Simplified and Traditional).
The protocol work is done by whatsapp-rust, a separate library that describes itself as an unofficial, open-source Rust implementation of the WhatsApp Web API, inspired by the Go library whatsmeow and the TypeScript library Baileys.
The numbers, and how far to trust them
| Claim | Source | Caveat |
|---|---|---|
| Under 1 second to launch | Developer's README (Linux) | Not independently tested |
| ~200 MB idle RAM | Developer's README (Linux) | Compared with WhatsApp Web, not the official desktop app |
| 1.13 GB for WhatsApp Web | Developer's README (Linux) | Single measurement, setup not described |
Tech Bytes, which wrote up the project on November 8, notes it found no independent verification of these figures, and neither did we. daily.dev's summary of the Hacker News thread (72 points and 96 comments at the time) says many commenters were skeptical: some argued 200 MB is still a lot for a chat client, and others warned that egui's immediate-mode rendering may run poorly on machines without a usable GPU.
The catch: it's unofficial
Both ZapFast's README and the whatsapp-rust README say plainly that unofficial clients may violate Meta's terms of service and can lead to your account being suspended, and that you use them at your own risk. Tech Bytes repeats the warning, saying suspensions can be temporary or permanent. ZapFast is not affiliated with WhatsApp or Meta.
Project history
The repository was created on August 29, 2026. The app was first released as FastsApp and renamed ZapFast in version 0.13.0 on September 14, when the macOS build also became signed and notarized by Apple. Version 0.14.0 (September 16) added polls, themes, the encrypted archive, in-app updates with checksum checks, and packages for AUR, DEB/RPM, Flatpak and Homebrew. On Linux it needs glibc 2.39 or newer and a working Secret Service keyring. It's MIT-licensed.
Should you try it?
- Curious, but cautious: run the demo mode first. Tech Bytes reports you can try the interface with no WhatsApp account using
cargo run --features demo -- --demo. - Using a spare or secondary number: that's the lower-risk way to test the real thing, given the suspension warning.
- Your main or work account: think twice. If WhatsApp is how you reach family or clients, a ban costs far more than the RAM you'd save. The official apps are the safe choice.
What to watch: whether Meta responds to the attention, and whether someone independently measures memory use against WhatsApp's current official desktop app rather than WhatsApp Web.
Sources
- GitHub — crmne/zapfast github.com
- GitHub — crmne/zapfast releases github.com
- Tech Bytes — ZapFast: A fast, native WhatsApp client in Rust and egui techbytes.app
- daily.dev — ZapFast: A fast, native WhatsApp client in Rust and egui daily.dev
- docs.rs — whatsapp-rust README docs.rs