Skip to content

Changelog

WhatsApp Web Extractor release history from 1.0.0 to 1.1.0, covering history recovery, raw output, multi-session profiles and the window.

Versions follow the releases on GitHub. Each release ships wawf-windows-x64.exe and wawf-linux-x64. Dates are release dates.

Released 2026-10-18. Forensic coverage, contributed in pull request #1.

  • Partitioned and damaged profiles. Partitioned Chromium storage and the legacy layout, any Chromium-family browser or Firefox, and profiles given as a folder, a parent folder or loose stores (--idb, --local-storage, --media-cache). Unreadable tables and torn log records are skipped and reported.
  • Several sessions in one profile. Each WhatsApp session is identified and exported to its own folder; --partition selects one, and --key can be given once per linked device.
  • Richer exports. Message bodies decoded with WhatsApp Web’s own schema (link previews, locations, polls, events, quotes, view-once records), groups with members and past members, contacts, calls, reactions and receipts.
  • Server queue. --queue records what the server is holding for the device, acknowledging nothing.
  • History without Node.js. --history uses a Python implementation of the linked-device client, so it runs inside the .exe.
  • Case details (--case-id, --examiner, --case-notes) recorded in the audit database.
  • Window with steps for browser data, outputs, message key and case details, and the exact command shown for copying.

Released 2026-10-10.

  • History recovery no longer stalls: the device’s offline queue is drained first, progress is saved per chat, and recovered messages merge into the same chats as the browser cache with a source field on each row.
  • No message text is truncated any more (it was cut at 2,000 characters in JSON and text, and 8,000 in SQLite), and text the old string scraper dropped is back.
  • SQLite output uses Android’s message types for deleted and system messages.
  • The raw output manifest lists a SHA-256 for every file, and the audit database hashes every evidence file it reads.
  • --log-file is UTF-8; on Windows, lines with non-Latin names were being dropped.

Released 2026-10-03.

  • History recovery works: chats are now requested in the form WhatsApp Web itself uses, and the request matches the reference client field for field. Rate limits are respected, with backoff and resume from a checkpoint.
  • New --out raw:DIR format: every store decrypted and otherwise unchanged.

Released 2026-09-19. First release, with Windows and Linux binaries.