Checking and creating SFV, MD5 and SHA files

Verification files let you prove a download is intact, or ship a checksum with files you upload. Verify & Extract creates and checks them; the CLI does the same with -check.

Checking files against an SFV, MD5 or SHA file

1. Rename tab → tick the .sfv, .md5, .sha1, .sha256 or .ed2k file, or the folder that holds it.
2. Verify & Extract → Check selected.
3. Each listed file shows OK or BAD, or missing if it is not there. Names in the verification file are resolved relative to where it sits.

Creating a verification file

1. Tick the files or folder to hash.
2. Choose the format — SFV (CRC32), MD5, SHA-1, SHA-256 or ED2K — and click Create.
3. The file is written into the folder, named after it (Release/Release.sfv), with paths relative to that folder.

Which format

• SFV — what release groups ship; fastest.
• SHA-256 — when you want a real integrity guarantee.
• ED2K — for eDonkey links; computed the standard way (MD4 over 9,500 KiB chunks).

Note: hashing reads every byte, so a 50 GB folder takes minutes; the job runs in the background and the result appears when done.

← One library for Plex and Nuplex · EvoSeedboxBot guide · Extracting rar and zip archives automatically →