Audit Trail Generator
Take a hashed snapshot of a folder today, take another later, and generate a precise audit trail of exactly which files were added, removed, or modified in between.
Snapshot Files
Load Two Snapshots
Create a file change audit trail with snapshots
Generate a SHA-256 snapshot of the files you select, save the resulting JSON, and repeat the process later. Comparing the two snapshots identifies files that are new, missing, or have different content. Because the comparison uses content hashes rather than modification dates alone, it can catch edits even when timestamps are unreliable after copying or syncing.
What a snapshot can and cannot prove
A snapshot contains file names, sizes, hashes, and a creation time, not the files themselves. Keep the JSON snapshots in a controlled location and label them clearly so you can tell which capture is older. This browser-based comparison is useful for routine change checks and release records, but it does not authenticate who created a snapshot or replace a managed, tamper-evident compliance logging system.
What's inside a snapshot file?
A JSON file listing every filename, its size, and its SHA-256 hash, plus the timestamp it was generated. It contains no file contents — just fingerprints.
How do I compare file snapshots later?
Download and keep the first JSON snapshot. When you want to check for changes, create a second snapshot of the files and load the older and newer JSON files in the comparison tab.
Does a matching file name mean the file is unchanged?
No. The audit trail compares the SHA-256 fingerprints as well as file entries, so a file with the same name but different content is reported as changed.