Context
rclone has announced that Google will start charging for API requests made through rclone's shared OAuth client ID for Google Drive and Google Photos. Because shared-client usage is far over the free quota, rclone is retiring the shared client ID entirely later in 2026, following a 90-day notice period (not yet started as of July 2026).
After retirement, every user will need to use their own OAuth credentials (client_id / client_secret). Service-account users are unaffected.
Impact on rclone4gdrive
Today the tool defaults to, and recommends, rclone's shared credentials:
init prompts "Use rclone's shared credentials (recommended for most users)?" defaulting to yes
- the README positions shared creds as the zero-setup selling point ("no Google Cloud setup")
Bringing your own credentials is already supported today (--client-id / --client-secret, or the interactive prompt), so there is no breakage right now — but the current default and recommendation are on borrowed time.
Proposed work
References
Raised in response to community feedback on the forum thread.
Context
rclone has announced that Google will start charging for API requests made through rclone's shared OAuth client ID for Google Drive and Google Photos. Because shared-client usage is far over the free quota, rclone is retiring the shared client ID entirely later in 2026, following a 90-day notice period (not yet started as of July 2026).
After retirement, every user will need to use their own OAuth credentials (
client_id/client_secret). Service-account users are unaffected.Impact on rclone4gdrive
Today the tool defaults to, and recommends, rclone's shared credentials:
initprompts "Use rclone's shared credentials (recommended for most users)?" defaulting to yesBringing your own credentials is already supported today (
--client-id/--client-secret, or the interactive prompt), so there is no breakage right now — but the current default and recommendation are on borrowed time.Proposed work
initand the README that rclone's shared credentials are being retired later in 2026, and that bring-your-own credentials will become the normal path.--bundled) kept as an explicit opt-in fallback while it still works.References
Raised in response to community feedback on the forum thread.