Roadmap

Roadmap

ByteRescue is early-stage (0.7.0). This page collects what's explicitly not implemented yet and what's under consideration, pulled from Contributing and the per-format notes in Recovery Signatures / Supported File Systems, so "is X planned" has one place to check.

This isn't a committed schedule — it's a map of known gaps or general direction as an open-source project. See Contributing if you want to help close any of these.

Not yet implemented

• NTFS and exFAT filesystem-aware recovery — "Recover by File System" only supports FAT12/16/32 today; selecting it against NTFS/exFAT reports a clear error instead of guessing
• RAID arrays — no RAID metadata parsing or member reconstruction
• Camera RAW formats (.cr2, .nef, etc.)
• Full container parsers for GIF, TIFF, RAR, legacy Office (OLE), MKV/WebM — currently carved as unverified/capped rather than structurally verified
• MP3 frame-based carving — only ID3v2 tag detection exists; raw MPEG frame-sync bytes are deliberately excluded as a signature (too many false positives)
• Forensic-grade acquisition — hashed imaging, chain-of-custody tracking, write-blocking enforcement

Under consideration (from Contributing.md)

• Linux and macOS support (currently Windows-only)
• Advanced carving techniques
• RAID recovery support
• File system reconstruction
• Automated recovery workflows

Development priorities

Priority	Focus
High	Crash fixes, stability, error handling, security vulnerabilities, critical bugs
Medium	New file signature support, performance, UI enhancements, documentation
Low	Nice-to-have features, minor UI polish, experimental features

Things that will not change

• SSD TRIM bypass — not something any software can do once flash has actually been erased
• Writing to the source drive — ByteRescue's read-only, separate-destination model is a safety design choice, not a current limitation (see Best Practices)

See also

FAQ for specific "does it support X" answers, and open issues / discussions for what's actively being worked on right now.