Answers before
your first transfer.

DriveDock is a focused transfer utility, not a background sync client. You choose exactly what to upload or download, where it should go, and which Google account to use, without creating a local sync folder.

No. DriveDock does not continuously watch folders or mirror changes. It handles transfer jobs that you start and keeps a persistent queue so you can pause, resume, retry, and review them.

Yes. You can browse My Drive and Shared Drives, choose a destination folder, create a folder, and upload wherever the connected Google account has permission.

Yes. DriveDock is released under the MIT License. The source code, issue tracker, release history, and current downloads are public on GitHub.

Use the latest GitHub Release. The release page provides the current DMG, zip archive, and SHA-256 checksums. The current build is unsigned or ad-hoc signed, so macOS may require Control-click, then Open, on first launch.

DriveDock retries eligible transfers with exponential backoff and jitter. Large files use Google Drive's resumable upload protocol, so an interrupted upload can continue instead of starting over.

The queue pauses safely when the Mac sleeps and resumes when the Mac wakes and the network is available. Persistent queue state also allows eligible work to continue after the app restarts.

Yes. Large files use resumable sessions and are sent in 8 MB chunks. DriveDock shows per-file progress, transfer speed, estimated time remaining, and status while the upload runs.

Yes. You can pause, resume, cancel, retry, reorder, and prioritize queued work. Controls are available for individual items and for the queue as a whole.

Choose the policy that fits the job: keep both, automatically rename the new item, skip it, or replace the existing Drive item. DriveDock can apply the selected policy across the batch.

Yes. DriveDock scans the selected folder, prepares matching folders in Google Drive, and uploads nested files without flattening the hierarchy. Folder preparation can continue in the background.

Yes. DriveDock supports upload bandwidth limits and adjustable concurrency. Its adaptive mode can respond to network quality, errors, battery state, and Google Drive rate limits.

Yes. Use the Drive browser to select files and start parallel downloads. Download jobs use the same persistent queue model so their state survives an app restart.

DriveDock keeps local transfer history and completion summaries. You can review completed work and export reports in CSV, JSON, or plain-text format.

Yes. Connect multiple accounts, choose the account for each transfer batch, and switch accounts without removing the others. Queued items remain associated with the account you selected.

OAuth access and refresh tokens are stored in macOS Keychain. They are not written to a plain settings file, stored by this website, or sent to the developer.

DriveDock uses drive.file to create and upload files. It uses drive.readonly to browse existing Drive items, My Drive folders, and Shared Drives when you choose a destination.

Yes. DriveDock can use macOS authentication, including Touch ID or Apple Watch approval when available, to protect sensitive app access on your Mac.

DriveDock requires macOS 14 Sonoma or later. It is a native Swift and SwiftUI app built for macOS rather than a browser wrapper.

You need an internet connection to authenticate, browse Google Drive, upload, or download. The local queue remains available offline and can continue eligible work when connectivity returns.

No. DriveDock includes no analytics SDK, advertising, anonymous usage tracking, or third-party crash reporting. File transfers go directly from your Mac to Google Drive APIs.

Open a GitHub Issue with the steps to reproduce the problem, the result you expected, and your macOS version. Check existing issues first to avoid duplicates.

Use the repository Security tab to report a vulnerability privately. Do not post sensitive security details in a public GitHub Issue.