Skip to content
SPECIFICTION
Get listed

No-Intro DAT Matcher vs verifydump

No-Intro DAT Matcher

github.com

verifydump

github.com

Side by side

FigureNo-Intro DAT Matcherverifydump
Price fromFreeFree
Free planYesYes
Free trial——
Open source——
Windows—Yes
macOS—Yes
LinuxYesYes
Plans published11
Spec score · ROM Management Software7.5 (#17)7.8 (#10)
File handlingThe example commands support copying or moving renamed files and skipping files already in the output folder.The README says verifydump never modifies users’ files and deletes temporary converted files after verification.
PurposeThe script matches ROM files to No-Intro or Redump DAT filenames and copies them to an output folder with those names.verifydump checks whether compressed .chd and .rvz disc images match Redump Datfiles.

Plans

No-Intro DAT Matcher

  • No-Intro DAT MatcherFree

No-Intro DAT Matcher pricing →

verifydump

  • FreeFree

verifydump pricing →

In their own words

No-Intro DAT Matcher

No-Intro DAT Matcher has no write-up on Specifiction yet; its figures are above.

Visit github.com

verifydump

verifydump is a free command-line tool for checking compressed .chd and .rvz disc images against Redump Datfiles. It converts each image into the original format described by the Datfile, adjusts the result to Redump conventions, then checks it against the Datfile. Users provide a Datfile, which can be zipped, followed by image files or folders containing them. The tool says it does not modify user files and stops checking an individual image after finding an error. CHD checks require chdman and binmerge, both available in the system PATH; RVZ checks require DolphinTool in the system PATH. Some Redump cue metadata cannot be represented in CHD. Users can provide original cue files with --extra-cue-source or ignore cue mismatches with --allow-cue-file-mismatches. Verification creates temporary converted files and deletes them afterward; the project suggests a RAM drive for frequent checks or large collections to reduce SSD writes. Windows users can use the offered executable, while Linux and macOS users can install through pipx or another Python package installation method. The package requires Python 3.10 or later and below 3.16. The project directs bug reports and questions to GitHub issues.

Visit github.com