MD5 & SHA Checksum Utility — Batch Hashing for Large File Sets

MD5 & SHA Checksum Utility: Command-Line and Drag‑and‑Drop Hash Tool

Overview

A compact utility that computes file hashes (MD5, SHA-1, SHA-256, SHA-512) via both a command-line interface (CLI) and a drag‑and‑drop graphical workflow. Designed for quick file integrity checks, verification after downloads/transfers, and batch hashing.

Key features

• Multiple algorithms: MD5, SHA-1, SHA-256, SHA-512.
• Dual interfaces: CLI for scripting and automation; drag‑and‑drop GUI for quick manual checks.
• Batch processing: Compute hashes for many files at once and export results.
• Compare mode: Compare computed hashes against provided checksum files (e.g., .md5, .sha256).
• Export formats: Plain text, CSV, and JSON outputs.
• Progress & logging: Per-file progress, error reporting, and detailed logs for large transfers.
• Cross-platform: Works on Windows, macOS, and Linux (native binaries or small interpreter dependency).
• Performance: Streaming read to handle large files without high memory use; multithreaded hashing for multiple files.

CLI usage examples

• Compute hash for a single file:

  Code
  Copy CodeCopied
  md5sha util hash –alg sha256 /path/to/file 

• Batch hash directory and output CSV:

  Code
  Copy CodeCopied
  md5sha util hash –alg md5 –recursive /path/to/dir –output hashes.csv 

• Verify against checksum file:

  Code
  Copy CodeCopied
  md5sha util verify –checksums file.sha256 

GUI behavior

• Main window accepts drag‑and‑drop of files/folders.
• Select algorithm from a dropdown; results appear in a table (filename, size, algorithm, hash, status).
• Right-click menu: copy hash, open file location, remove entry.
• Load checksum file to auto-verify matching files; visual pass/fail indicators.
• Export results button for CSV/JSON/plain text.

Security and limitations

• MD5 and SHA-1 are fast but cryptographically broken for collision resistance; use SHA-256 or SHA-512 for security-sensitive verification.
• The tool verifies integrity (accidental corruption, transfer errors) but not authenticity unless checksums are obtained from a trusted source.

Suggested use cases

• Verify downloaded installers or ISO images.
• Post-transfer file integrity checks for backups and mirrors.
• Generate checksums for distribution and public release.
• Integrate into CI pipelines via the CLI for automated artifact verification.

If you want, I can draft a short README, CLI reference sheet, or a simple GUI mockup for this utility.