How to verify a Google Drive backup before you trust it
A backup that finished is not necessarily a backup you can rely on. Use a source list, an archive report, and a second check 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
Verify a Google Drive backup in four passes: define the folders you expected, archive them, read the report for skipped or failed items, and compare the result against the source before signoff. A file count or green completion message is useful, but it is not a complete evidence trail.
Why a completed export is not the same as a verified backup
Export tools can finish while the result still needs review. Google notes that some work or school account data may not be available for download, and large exports can fail. Google-native files also need conversion if the archive must work outside Drive.
The useful question is not simply "did the export run?" It is "did the expected records reach the intended destination in a form the next person can use?" That question requires a source scope and a report.
Build the expected set before the copy
Write down the source folders and the record types that matter. Include shared-drive folders, files created by Google Workspace apps, and any exclusions that the administrator approved. This list gives the reviewer something concrete to check against the result.
- Source folder and shared-drive location
- Expected folder count and important record groups
- Approved export formats for Docs, Sheets, and Slides
- Items that may be skipped because of permissions or export limits
- Archive destination, owner, and retention date
Read the archive report alongside the destination folder
Safe Archive writes an HTML report and a CSV report into the destination. Use the HTML version for a human review and the CSV version when the archive needs sorting or another system needs to ingest the results.
Check the report for four things: ordinary files that copied successfully, Google-native files that were converted, items that were skipped, and failures that need a retry. The report also includes SHA-256 values for archived files, which gives you a stronger baseline than names and file counts alone.
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.
Run a second check before you sign off
Open a sample of converted files, confirm the destination structure, and compare the archived folder with the source when both are available. For a repeatable workflow, use the folder integrity checksum guide or the Safe Archive CLI guide.
Keep the source scope, archive report, exception notes, and final approval together. That packet makes the decision explainable later, even when the original Drive access is gone.
Frequently asked questions
Is a successful Google Drive export proof that the backup is complete?
No. A successful run tells you that the process completed, but you still need to review the expected folders, converted files, skipped items, and failures. Verification checks the result against what you intended to archive.
Do I need checksums to verify a Google Drive backup?
Checksums are useful for ordinary files because they help detect content changes after the copy. Google-native files are exported into a chosen format, so the report should also record the conversion and any limitations.
How do I find missing files in a Google Drive backup?
Start with the source folder list, then compare it with the archive report. Safe Archive names files that were skipped or failed so you can retry the incomplete part instead of guessing from the final file count.
Can I verify a Google Drive backup without uploading my files to another website?
Yes. FolderManifest is a desktop workflow. The archive and report are created through the app or CLI, so the file contents do not need to be uploaded to an online comparison tool.