How to Restore Files from a Safe Archive
A careful restore workflow for bringing files back from a local, NAS, S3-compatible, or Google Drive archive without overwriting the working copy first.
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
Safe Archive is a copy-and-proof workflow, not a hidden restore vault. Copy the archived files into a separate staging folder, read the archive report, verify what you recovered, and only then replace files in the working folder.
1. Stage the restore somewhere safe
Start with a new folder on a local disk or another destination with enough free space. Keeping the first restore separate protects the current working copy while you inspect filenames, file types, and timestamps.
- Record the archive location and the date or job that you intend to recover.
- Copy only the needed folder or files into a new staging directory.
- Keep the original working folder untouched while the staged copy is being checked.
If the archive is in S3-compatible storage or Google Drive, download or copy it to the staging location first. A local staging pass gives you a stable folder to inspect before you put anything back into a live project.
2. Read the archive report before trusting the copy
Safe Archive writes _archive-report.html and _archive-report.csv into the destination. Open the HTML report for a human review, or use the CSV when you need to filter a large result.
Confirm the scope
Make sure the report belongs to the source folder and archive run you meant to use.
Check failures
Look for files that were skipped, failed, converted, or could not be written.
Choose the restore set
Restore the smallest set that solves the problem instead of replacing everything.
A successful archive run means the destination received the items that the report marks as successful. It does not mean that every file is the version you want to put back today. Treat the report as the evidence for selecting the restore set, not as permission to overwrite the working folder blindly.
3. Verify the staged files before replacing anything
Compare the staged folder with the archive report or with a known-good manifest. Matching SHA-256 values give you a content check; filenames and modified dates alone cannot tell you whether a file changed silently.
If the report lists failures or a cloud export was converted, pause before replacement. Recover the missing item from another known-good copy or ask the owner to confirm which format and version is needed.
- Compare the staged folder with the current working folder to see what will change.
- Open a sample of important documents, images, or project files using the software that owns them.
- Move the current file aside before replacement so you have a rollback copy during review.
- Keep the archive report next to the restored set for future troubleshooting.
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.
Cloud archive restores need one extra check
S3-compatible storage preserves the stored bytes, but Google-native Docs, Sheets, and Slides are exported to a selected Office format during an archive. That export is useful for a portable copy, but it is not the same thing as restoring the original Drive revision history, comments, or ownership model.
For a Google Drive recovery, confirm the destination account, download to staging, review the report, and decide whether the result should be a local file, a new Drive file, or an owner-managed handoff. TheGoogle Drive permissions checklist covers the access boundary separately.
Frequently asked questions
Does Safe Archive have a one-click restore button?
Safe Archive creates a copy and a report at the destination. Restore by copying the needed files from that destination into a staging folder, reviewing them, and then moving the approved files into place.
Can the archive report prove that a restored file is the right file?
The report records the archived file paths, statuses, and SHA-256 values for the archive result. Compare the staged restore with the report or a known-good manifest before replacing the working copy.
Can I restore a Google Drive archive back to Google Drive?
You can copy archived files from the chosen destination into a staging folder and then upload or copy them where they belong. Google-native documents may have been exported to Office formats, so review the report and file types before treating them as a byte-for-byte restore.