How to create a SHA-256 folder archive record
Create a folder copy and keep a per-file SHA-256 record beside it so a later reviewer can check what arrived without guessing from file names or sizes.
Safe Archive guide
Keep the copy, keep the context, and keep a record of what arrived.
Founder of ARCED Foundation, ARCED International, and Solutions of Things Lab (SoTLab). Built FolderManifest to help teams protect file integrity and stay audit-ready.
Published August 20, 2026
Scope first
Decide what you are allowed to copy before starting the archive.
Copy second
Use a destination that will remain available after access changes.
Verify last
Keep a report that names the files copied, converted, skipped, or failed.
Quick answer
Define the source folder, copy it with Safe Archive, and keep the generated HTML and CSV reports beside the destination. Each ordinary archived file gets a SHA-256 value that can be checked later against the record.
1. Define the baseline before the copy
Record the source path, expected scope, archive date, destination, and exclusions. The checksum record is only useful when the reviewer knows which source set it describes.
If the archive is for a handoff, migration, or project closeout, add the owner and the approval for the selected scope. Keep personal or restricted files out of the archive unless they are authorized for transfer.
2. Copy the folder and generate the hashes
Run Safe Archive from the app or CLI and choose a local, NAS, S3-compatible, or Google Drive destination. During the copy, ordinary files are hashed with SHA-256 and the destination receives_archive-report.html and _archive-report.csv.
The report is the archive record. Store it with the copied folder instead of leaving the checksum list on the computer that ran the job.
Google-native files are handled as exports because they do not behave like ordinary downloaded bytes. Review their conversion status and selected format separately from ordinary file hashes.
3. Check the record against the destination
- Open the HTML report and confirm the source and destination context.
- Review total files, bytes, skipped items, failures, and conversions.
- Use the CSV report to locate a path or filter by status.
- Re-hash selected destination files and compare their SHA-256 values.
For a browser-based spot check, use the free SHA-256 checksum calculator on a downloaded destination file. The full archive report remains the record for the complete folder.
Make the archive reviewable
FolderManifest copies the folder locally or to a supported destination, then creates a report with the files that arrived and the files that need attention.
4. Reuse the record during later reviews
Keep the archive report with the dated copy. A later reviewer can use it to identify the expected paths and compare important files without relying on the original machine or a memory of what was copied.
This record verifies the archive copy. It is not a duplicate finder and it does not decide whether the source should be deleted. Those are separate workflows and decisions.
Frequently asked questions
Why put SHA-256 values in a folder archive record?
A SHA-256 value gives each ordinary archived file a content-based reference. A later check can compare the destination file with the recorded value instead of relying on the name or size alone.
Where are the SHA-256 values stored?
Safe Archive stores them in the per-file rows of _archive-report.html and _archive-report.csv in the destination. The reports stay beside the archived files.
How are Google Docs and Sheets handled?
Google-native files are exported into the selected format, and the conversion is recorded in the report. Review the export result separately from ordinary byte-for-byte files.
Is the archive SHA-256 record a duplicate finder?
No. The archive hash is used to verify the copied file. It is not a deduplication workflow, and Safe Archive keeps the source unchanged.