Get Google Refresh Token

Run a real OAuth flow against your own Google Cloud OAuth client and get back a long-lived refresh token.

Create client
Use RClone client
Use own client
Create your own OAuth client (2 minutes):
  1. Go to Google Cloud Console → Credentials (create a project first if you don't have one).
  2. Create Credentials → OAuth client ID. Application type: Web application.
  3. Under Authorized redirect URIs, add exactly:
    https://gd-token.cybar.to/tool/google/callback
  4. If prompted, configure the OAuth consent screen first — "External", add yourself as a test user, keep it in "Testing" mode (fine for personal use).
  5. Enable whichever API you need under APIs & Services → Library (e.g. Google Drive API).
  6. Copy the generated Client ID and Client secret into the fields below.
Keeping the app in "Testing" is fine — grants just need re-approval after 7 days unless you publish the app.
This tool doesn't ship rclone's built-in client credentials — those live obfuscated in rclone's source and using them from a third-party tool isn't something I'll bake in here. For your own token, use Create client above (takes ~2 minutes) or paste credentials you already have via Use own client. Rclone's own equivalent is rclone authorize drive, which uses its own hosted flow — see the rclone docs.
Already have a Google OAuth client? Fill in the three fields below and hit Go get.
Must exactly match a redirect URI registered on your OAuth client.

Nothing is stored server-side. Your client_id/secret/redirect are round-tripped through Google via the OAuth state parameter and only used once, at the callback, to exchange your auth code for tokens.