FileHasher for macOS 1.1 is out in both editions: on the Mac App Store, and as a notarized direct download. It adds a Subfolders control that sets how deep a folder scan goes, remembers the settings you use on every run, and opens the Browse panels where you are already pointing.
Choose how deep a scan goes
Pointing FileHasher at a folder used to be a yes-or-no question: include subfolders, or don’t. That is now a Subfolders control with three settings. This folder only remains the default, so nothing changes unless you ask it to. All subfolders descends as far as the tree goes. Limit depth to a number of levels descends exactly that far and stops, which is the useful one when a folder has a few layers worth hashing and a great many that are not.
Verify Sidecars uses the same depth as the hash run. That matters more than it sounds: a verification that looked less deep than the run which wrote the sidecars would report files as having no sidecar, when the truth is that it never looked at them. Tying both to one setting means the two can never disagree about which files are in scope.
It remembers how you work, but not what you hashed
Your hash algorithm and the Include file metadata option now persist between launches. If you always work in SHA512, that is how the app will greet you.
What it deliberately forgets is just as considered. The two options that cause the app to write something, sidecar hash files and CSV export, always start switched off, so a run only ever creates files because you ticked the box in that session. The target path is not restored either: reopening on last week’s folder invites a run against the wrong thing. The rule, in one line, is that a setting describing how you work is remembered, and a setting describing what you were working on is not.
Browse panels open where you are already pointing
The file and folder pickers used to open wherever the system last left them, which was frequently some other application’s business. They now open at the path already in the box beside them, and the CSV panel keeps the filename you chose instead of replacing it with a fresh timestamp. If that path has since been deleted, or lives on a drive that is no longer attached, it falls back to the nearest folder that still exists rather than giving up.
Two editions, and why their version numbers differ
The Mac App Store edition is 1.1.0. The standalone edition is 1.1.2. Same app, same features; the standalone edition went through two extra releases to fix how it was packaged, and those two builds were withdrawn. If you downloaded 1.1.0 or 1.1.1 of the standalone edition and macOS would not open it, that is why; replace it with 1.1.2 and it will behave. The FileHasher page has the details.
One consequence worth stating plainly for standalone users on 1.0.2: the in-app updater cannot install this one for you, because the permission it needs is checked by the copy already running. Download 1.1.2 and replace the app by hand, once. Automatic updates work normally from there.
Getting it
FileHasher is free and MIT-licensed. The App Store edition is on the Mac App Store; the standalone edition, which is notarized and updates itself, is on GitHub alongside the source and the changelog. Every release publishes a .sha256 file beside the download, so you can verify it with FileHasher itself before installing.
Sidecar files and CSV exports still move cleanly between the Mac and Windows versions, which both gained this same scan model. The support page covers either one.