How to back up a local folder to S3, B2, or R2
Create an offsite copy of a local folder in S3-compatible storage, keep the report with the archive, and review failed files before signoff.
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 local source, prepare an S3-compatible bucket and prefix, run the copy, and keep the HTML and CSV reports in the destination. Review failed files and rerun the same archive before you call the offsite backup complete.
1. Prepare the local source
Record the source path, expected scope, hidden-file policy, archive date, and owner. Exclude temporary or restricted material deliberately rather than discovering the exclusion after the copy.
A local folder can be a project directory, an export, or a mounted working location. The important part is that the source set is clear enough for another person to compare with the report.
2. Configure the cloud destination
Safe Archive supports AWS S3, Backblaze B2, Cloudflare R2, Wasabi, and MinIO. Choose the bucket, prefix, and region, then add the endpoint for services that need one. Keep the archive credentials in the OS keychain.
- Reserve a prefix for the project, source, or archive date.
- Confirm the archive account can upload and review objects.
- Make sure the destination policy matches the retention needs.
3. Run the offsite backup
Run the archive from the Safe Archive tab or the CLI. The source is not modified. Each ordinary file is hashed with SHA-256 as it is copied, and the destination receives _archive-report.html and_archive-report.csv.
The cloud object list shows what exists. The archive report shows what the job expected, copied, skipped, or failed.
4. Review and retry incomplete work
Open the report after the upload finishes. Check total files and bytes, then read every failed or skipped row. If the network or permission problem is fixable, run the same archive again. Completed files are skipped and unfinished work is retried.
Use the S3, B2, and R2 verification guide for a destination-focused review sequence. Keep the final report beside the offsite copy.
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.
Frequently asked questions
Which cloud destinations can receive a local folder?
Safe Archive supports AWS S3 and S3-compatible destinations including Backblaze B2, Cloudflare R2, Wasabi, and MinIO. The compatible services use their endpoint with the bucket settings.
What does the local folder backup report contain?
The HTML and CSV reports record per-file paths, sizes, statuses, and SHA-256 values, along with the items that could not be copied.
Can I resume an interrupted upload?
Yes. After fixing the network, permission, or destination problem, run the same archive again. Files already recorded as complete are skipped and unfinished work is retried.
Does an offsite backup delete the local folder?
No. Safe Archive is copy-only and leaves the local source untouched. Retention and cleanup decisions happen separately.