Drive Batch Receipt

Download selected Google Drive files individually and keep a local receipt of each file's outcome.

Download selected Google Drive files as individual files, then see what happened to each one. Choose up to 100 files with Google's official file picker. Review the entire selection before clicking Start downloads. Files with the same name remain separate entries. Unsupported or unavailable files stay visible instead of silently disappearing from the batch. Each receipt records the selected file and outcome, plus expected size, observed Chrome download ID and local filename when available. Chrome manages the actual downloads. Files are not repackaged into a ZIP by this extension. If a download fails, explicitly retry eligible failures after checking the original Google account, source metadata and earlier Chrome download outcome. Completed or uncertain downloads are not automatically restarted. Some ambiguous or older multi-attempt histories require review rather than another retry. Access tokens are kept in browser memory. Your Google authorization grant remains until you revoke it in your Google Account. If Chrome suspends the extension worker or authorization becomes unavailable, remaining work pauses. Reconnect and Start are separate actions; the extension does not silently log in or resume a new transfer after restart. Refresh checks only recorded download IDs and pauses scheduling. Clear receipt removes the current local receipt after safety checks; it does not delete downloaded files or Chrome's download history. Supported: ordinary downloadable Google Drive files. Not supported: folders, shortcuts, Google Docs/Sheets/Slides exports or whole-Drive scanning. Browser completion and expected-size/MIME checks are not cryptographic integrity verification. Google's drive.file permission can read and modify selected or previously authorized files. This extension only uses Drive read requests; it does not edit, delete or share your Drive files. Its dedicated HTTPS companion temporarily receives the token in browser memory to run Google's official Picker. The companion's top-level address contains no token. Google uses the token in its embedded Picker URL and authenticated requests. The app does not save tokens in page storage, receipt records or a developer server database. No advertising, analytics or AI processing.