← All projects
FINAL VALIDATION Backup · CLI

Signal Tools

Read, verify, merge and export multiple encrypted Signal backups without hiding data loss or exposing their keys.

Surface
Desktop · Command-line tool
Status
FINAL VALIDATION
Release
Version 0.1.0
Category
Backup · CLI
overview

Inspect and merge Signal backups

Signal Tools is a Rust pipeline for legacy Signal backups and local v2 snapshots. It detects formats, tries authorized keys, replays databases, normalizes conversations, deduplicates conservatively, applies retention and selects a final output according to lossless feasibility. Every phase produces actionable audits instead of an opaque success message.

Availability

Product validation before release

Version 0.1.0 has extensive test coverage and a v2 writer validated by Rust round trips. Real imports into Signal Android/Desktop and some portable formats still need confirmation before every output is presented as directly restorable.

Contact the studio →
At a glance

At a glance

Version
0.1.0
Technology
Rust 2024
Commands
10
Backups
Legacy · v2
Exports
HTML · CSV · TXT · XML
Execution
Local
What's in it

What's in it

  • F—01 Reads legacy backups and local v2 snapshots
  • F—02 Multi-source merge, identity normalization and conservative deduplication
  • F—03 Conversation, date and volume curation with optional TUI
  • F—04 Legacy Signal, encrypted v2 or local plaintext outputs
  • F—05 HTML, CSV, TXT, SMS-XML and attachment exports
  • F—06 Resume, parallelism, JSON/HTML reports and verify-final audit
Pipeline

Rejecting false success.

When a target format cannot represent data without loss, the tool reports it and selects a more faithful fallback instead of silently producing a degraded backup.

S—01

Discover and verify

Inputs, formats, fingerprints and candidate keys are checked before expensive processing.

S—02

Replay and normalize

Legacy databases and v2 snapshots converge into one stable internal model with their payloads.

S—03

Merge conservatively

Identities, messages and attachments are matched through strong evidence; ambiguous cases remain separate.

S—04

Export, then audit

Final format follows lossless feasibility and a semantic check runs after every successful merge.

Screens

Screens

Screenshot placeholder
UI—01 Backup scan and verification
Screenshot placeholder
UI—02 Conversation-curation TUI
Screenshot placeholder
UI—03 Merge and integrity HTML report
Screenshot placeholder
UI—04 Local HTML conversation archive
Security

Local secrets, restrained reports.

The tool runs locally on archives selected by the user. Generated passphrases stay in a dedicated file and reports retain only a masked representation.

  • P—01 No complete key written to JSON reports
  • P—02 Only synthetic data in the versioned test suite
  • P—03 Explicit failure when a required payload is missing or corrupt