# Install ZapFast with Homebrew Cask

Native WhatsApp client. Version 0.19.0 via Homebrew Cask; verified from local package data.

## Install

```sh
sudo av install cask:crmne/tap/zapfast
```

Additional install commands:

### macOS

- Homebrew Cask (100%):

```sh
brew install --cask crmne/tap/zapfast
```

  Evidence: local Homebrew cask metadata

## Package facts

- **Package key:** cask:crmne/tap/zapfast
- **Package manager:** Homebrew Cask
- **Package manager page:** <https://github.com/crmne/homebrew-tap/blob/136c968086f77356cd075966d90487b6129599b8/Casks/zapfast.rb>
- **Version:** 0.19.0
- **Source summary:** Native WhatsApp client
- **Homepage:** <https://zapfast.rocks>
- **Repository:** <https://github.com/crmne/zapfast>
- **Upstream docs:** <https://zapfast.rocks>
- **Source archive:** <https://github.com/crmne/zapfast/releases/download/v0.19.0/zapfast-v0.19.0-macos-universal.dmg>
- **Generated:** 2026-10-23T08:12:40+00:00

## Install behavior

- Bottle: not available

## Freshness

- Page generated: 2026-10-23
- Package-manager version: 0.19.0
- Local data: ok
- Upstream repository: https://github.com/crmne/zapfast
- info: No package-manager update timestamp was available.
- info: No cached GitHub release or tag data was available.
## Project history and usage

ZapFast is an independent native Rust desktop client that links to WhatsApp as a companion device, supports common messaging and media operations, and keeps synchronized chat history in a local encrypted archive.

### Project history

The application was originally named FastsApp and developed as an unofficial native WhatsApp companion client. It links as a companion device rather than embedding WhatsApp Web, and stores synchronized history locally.

Version 0.13.0 introduced the ZapFast package and executable names. The application retained migration paths from FastsApp and the still earlier fastwhatsapp data directories while expanding multi-account, privacy, messaging and desktop-integration features.

### Adoption history

ZapFast distributes native builds for Linux, macOS and Windows, with documented Homebrew, Arch, Nix, AppImage and standalone installation routes. Its multi-platform packaging and in-application updater make it usable beyond source-build audiences.

The project is recent, so available evidence supports active packaging and development rather than broad or long-established adoption.

### How it is used

Open ZapFast and scan its QR code from WhatsApp's Linked devices screen, or use phone-number linking. Each linked number receives separate session, archive, settings and cache storage.

Users can send messages and media, record voice messages, manage multiple linked numbers and keep the application connected in the system tray. Because ZapFast is unofficial, its documentation warns that using it may carry account risk.

### Why package nerds care

ZapFast is an unusual desktop package because it replaces the common embedded-web-view approach with a Rust and egui client linked through whatsapp-rust. It keeps chats in a local encrypted archive while exposing the file layout clearly enough for backup and troubleshooting.

Its rename and migration support are also noteworthy: packages, executable names and per-user state moved from FastsApp to ZapFast while preserving existing linked sessions and local archives.

### Timeline

- 2026: The application is developed under the FastsApp name.
- 2026: Version 0.13.0 introduces the ZapFast package and executable names.
- 2026: Later releases expand multi-account support, local history, privacy controls and cross-platform packaging.

### Related projects

- whatsapp-rust supplies the protocol implementation used to link ZapFast as a companion device.
- Spotifast is the author's sibling native application; both use egui and the shared fastframe application framework.

### Sources

- <https://github.com/crmne/zapfast#readme>
- <https://zapfast.rocks/>
- <https://zapfast.rocks/download/>
- <https://zapfast.rocks/how-it-links/>
- <https://zapfast.rocks/settings-and-files/>


## Security Notes

No matching local secret-handling manifest was found for ZapFast. Package metadata is still published here so future coverage has a stable package URL.



## Configuration and credential file locations

These source-backed paths show where this package keeps local settings or durable credentials. Automic Vault can use them as review targets for secret scanning, migration, and command approval.


## Configuration files

- Linux: ~/.config/zapfast/settings.json
- macOS: ~/Library/Application Support/me.paolino.zapfast/settings.json
- Windows: %APPDATA%\paolino\zapfast\config\settings.json

## Credential files

- Linux: ~/.local/state/zapfast/accounts/<id>/session.db
- macOS: ~/Library/Application Support/me.paolino.zapfast/accounts/<id>/session.db
- Windows: %LOCALAPPDATA%\paolino\zapfast\data\accounts\<id>\session.db

## Related links

- [Desktop app packages](https://pkg.so/desktop-app-packages/) - Matched curated package taxonomy and local package facts.
- [whatsapp](https://pkg.so/cask/whatsapp/) - Choose the official WhatsApp desktop client for first-party support and the complete vendor-supported feature set; choose ZapFast for its lightweight native interface and documented local storage model.

  Sources: <https://zapfast.rocks/what-is-zapfast/> · <https://www.whatsapp.com/download>

## Combined YAML source

View the package source record on GitHub. [combined/tap-crmne-tap-zapfast-03f79e85.yml](https://github.com/mxcl/pkgdb/blob/main/combined/tap-crmne-tap-zapfast-03f79e85.yml)


## Sources

- pkg.so package database
- curated configuration and credential file locations
- curated package history
- package version freshness
- package relationship graph
- cross-ecosystem install command graph
