Safe Archive vs GoodSync: when you need a copy with proof
GoodSync is built for sync and backup jobs. Safe Archive is for a one-way copy that leaves a report behind. Use this guide to choose the right workflow.
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
Choose GoodSync when you want to synchronize or back up between locations as an ongoing job. Choose Safe Archive when the deliverable is a one-way folder copy plus a report that another person can review.
The main difference is the job you are trying to finish
GoodSync's Google Drive documentation describes jobs that synchronize or back up files between locations. That is useful when the relationship between the two locations should continue over time.
Safe Archive treats the copy as a record. It leaves the source alone, writes the archive to local storage, Google Drive, or S3-compatible storage, and produces an HTML and CSV report. The report is part of the result, not a log that only the operator can interpret.
| Question | Safe Archive | GoodSync |
|---|---|---|
| Primary job | One-way archive with evidence | Sync and backup jobs |
| Source behavior | Copy-only | Depends on the selected job direction |
| Review artifact | HTML and CSV archive reports | Job results and sync history |
| Best question to ask | What exactly arrived? | Are these locations in sync? |
When GoodSync is the better fit
GoodSync makes sense when the destination should keep following the source. Use that kind of workflow for recurring synchronization, scheduled backup jobs, or a working relationship between a local folder and a cloud location.
- You need repeated sync or backup jobs between the same locations.
- You want the tool to manage the direction of future changes.
- The main success condition is that the two locations stay aligned.
The existing FolderManifest and GoodSync comparison covers the broader product differences. This page focuses on the narrower archive decision.
When Safe Archive is the better fit
Safe Archive fits a handoff, offboarding run, migration checkpoint, or dated backup where someone needs to review the result later. It does not make deletion or synchronization decisions for you.
- You need a copy that will not change the source.
- You want a per-file SHA-256 report in the destination.
- You need skipped and failed items named instead of hidden in a console.
- You need local, S3-compatible, or Google Drive destinations in the same workflow.
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.
Which should you choose?
Start with the noun in the request. If the request says "keep these folders synchronized," choose a sync tool. If it says "make an archive before we close this project and prove what arrived," choose an archive workflow.
Some teams will use both. GoodSync can handle recurring movement between locations, while Safe Archive can create a reviewable archive at a milestone such as offboarding, migration signoff, or final delivery.
Frequently asked questions
What is the main difference between Safe Archive and GoodSync?
GoodSync centers on sync and backup jobs between locations. Safe Archive centers on a copy-only archive and a report that records what arrived, what was converted, and what failed.
Is GoodSync better for ongoing synchronization?
If the job is to keep two locations synchronized, GoodSync is the more natural fit. If the job is to make a dated archive and keep evidence for a handoff or review, Safe Archive fits that narrower job.
Can Safe Archive copy to Google Drive or S3-compatible storage?
Yes. Safe Archive supports local and NAS destinations, S3-compatible destinations such as B2 and R2, and Google Drive. It writes an archive report into the destination.
Does Safe Archive change or delete the source?
No. Safe Archive is copy-only. It leaves the source unchanged so the archive can be reviewed before anyone decides what to remove or transfer.