Feature

Names instead of phone numbers

Auto-fills from your device address book (vCard exported by Chat Hoarding for Android, or pulled via adb), or manually per JID. Handles @lid privacy IDs.

Three resolution sources, used in priority order

First, your device address book. Chat Hoarding for Android can export it as a vCard 3.0 (contacts.vcf) and bundle it alongside the backup file; the Mac app parses that vCard and stores the result inside the .tarc as contacts.json. Second, an adb-pulled or manually-imported CSV/vCard of contacts if you didn't use the companion (same downstream contacts.json). Third, manual mapping: tap an unknown JID inside the Mac app and assign a name; your edits land in a separate manual_contacts.json sidecar that wins over the auto-imported one. (WhatsApp's own contacts database, wa.db, lives inside /data/data/com.whatsapp on the phone and is not reachable without root, so Chat Hoarding does not read it.)

The @lid problem

In 2024 WhatsApp started using @lid-style privacy identifiers in addition to phone-number JIDs. A single contact can appear under both. Chat Hoarding handles this by matching on E.164 suffix when available and treating the @lid form as a fallback ID that you map manually if it never gets resolved.

Stable across reopens

Manual mappings ride inside the .tarc bundle as a manual_contacts.json sidecar (separate from the auto-imported contacts.json so your edits aren't overwritten by a re-import). Open the archive on a different Mac and the mappings come with it. Update the archive (snapshot merge is on the roadmap) and the mappings are preserved.

FAQ

  • Can I import a CSV of contacts?

    Yes. Chat Hoarding auto-detects delimiter and header names. Common exports from Google Contacts, iOS Contacts, or your CRM work.

Used in

Other capabilities

Save your WhatsApp history forever.

$99 one-time. 2 Macs, revocable. 14-day refund.

Names instead of phone numbers · Chat Hoarding