ByteCase by Forensics ByteExplore Tools

Hash Manifest and Verification Tool

v0.9.1 · Pre-release Ready First signed release cycle

ByteCase Verify

Create saved hash manifests, rehash evidence later, compare results, and generate integrity verification records.

Explore the module View on GitHub View roadmap →

Hashes should remain useful after the first calculation

ByteCase Verify is designed around a repeatable integrity workflow rather than a disposable result.

Current release status

ByteCase Verify v0.9.1 is prepared for its first pre-release cycle.

Signed Windows publication is pending Azure Artifact Signing certificate verification.

Explore the interface

See how the module structures the work.

Select a workspace to view the interface and understand how it supports the surrounding forensic workflow.

1 of 1

Hash Files and Preserve the Results

Select files or folders, calculate configured hashes, review progress, and preserve the resulting values in a structured manifest.

Capabilities

Built around the work.

Multiple hash algorithms

Generate MD5, SHA-1, and SHA-256 values for files or recursive folders.

Saved JSON manifests

Preserve paths, values, timestamps, case context, and manifest metadata.

Verification and comparison

Verify a saved manifest against current files or compare two manifests.

Readable exports

Generate TXT, CSV, DOCX, and XLSX records.

Who this is for

Designed for practical forensic environments.

Digital forensic examiners preserving integrity recordsLaboratories rechecking archived or transferred filesTechnical reviewers validating case deliverablesPractitioners who need more than a disposable hash result

When to use it

Good fits for the module.

  • Create an original saved hash manifest
  • Rehash evidence or deliverables later
  • Compare current files or two saved manifests
  • Preserve readable match, mismatch, missing, new, and error results

What it does not replace

Keep the boundary clear.

  • Authentication or attribution analysis
  • Chain-of-custody systems
  • Evidence management platforms
  • Agency validation and integrity procedures

Example workflow

From case input to saved record.

  1. 01

    Select the material

    Choose a file or folder and enter case information.

  2. 02

    Create the manifest

    Hash the material and save paths, values, and metadata.

  3. 03

    Preserve with the case

    Store the manifest and readable export in the Verify folder.

  4. 04

    Verify again

    Reopen the manifest, rehash current material, or compare manifests.

Detailed boundaries

What this module does not claim.

  • A matching hash does not by itself establish authenticity, lawful handling, or a complete chain of custody.
  • Moved or renamed files may require path reconciliation.
  • The v0.9.1 build is not yet presented as a signed public Windows release.

Development direction

Where the module can go next.

  • Publish the first signed Windows pre-release
  • Collect examiner testing feedback
  • Improve large-directory progress and path remapping
  • Prepare future Hub integrity history

Product status

v0.9.1 · Pre-release Ready

v0.9.1 prepared for the first signed pre-release cycle.

Current focusSigned publication, structured external testing, and refinement from examiner feedback.View development history →

ByteCase by Forensics Byte

Documentation that remains useful when the case returns.

Use focused standalone modules for specific workflow problems, then connect them only where shared data adds clear value.

Explore all toolsShare feedback →