How to archive a local folder to Google Drive
Copy an approved local folder to Google Drive, keep a report in the destination, and review the archive before the local source is retired.
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 the approved local folders, sign in to Google Drive once in the browser, copy the source, and review the reports in the destination. Safe Archive leaves the local source untouched and names files that need attention.
1. Define what belongs in the Drive archive
List the source paths, project or date range, exclusions, and destination Drive folder before starting. If the files belong to an organization, confirm that the receiving account and Drive location are approved for the archive.
Keep the scope narrow enough to review. A broad user profile can contain personal files, application caches, or material that should not be transferred with the work archive.
2. Sign in to Google Drive once
The desktop workflow uses a one-time browser sign-in for the Drive destination. After authorization, the archive runs locally and sends the selected folder to the chosen Drive location.
Confirm the destination folder and receiving account before the copy. Do not put Google tokens or account passwords in the handoff documentation.
3. Create the copy and keep the report
Run Safe Archive with the local folder as the source and Google Drive as the destination. Ordinary files are hashed with SHA-256, and the destination receives _archive-report.html and_archive-report.csv.
Keep the report in the Drive destination. It gives the next owner a readable record of the upload and its exceptions.
4. Review the Drive destination
- Confirm the report is in the intended Drive folder.
- Compare the report scope with the approved local paths.
- Review total files, bytes, skips, and failures.
- Open important files from the receiving Drive account.
- Rerun the same archive if the report names incomplete work.
The local and NAS verification guide explains the report review sequence. The same checks apply when Google Drive is the destination.
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
Can a local folder be archived directly to Google Drive?
Yes. Safe Archive supports a local source and a Google Drive destination. The desktop workflow uses a one-time browser sign-in and writes the archive report into the destination.
How do I know the Google Drive archive is complete?
Review the HTML report and CSV report in the destination. Check the expected scope, totals, failed or skipped items, and SHA-256 values for ordinary archived files.
What if the Google Drive upload stops partway through?
The report names the files that could not be copied. Run the same archive again after fixing the problem; completed files are skipped and unfinished files are retried.
Does archiving to Google Drive remove the local files?
No. Safe Archive copies the local source and leaves it unchanged. Removing the original files is a separate decision after the archive review.