Google login says redirect_uri_mismatch? How to fix it
Ship ItChecked against the official source
Source checked 8 Oct 2026 · Published 23 Oct 2026 · Last reviewed 23 Oct 2026 · By Ctrl+Z Therapy (how we test)
The short answer
When your app sends people to Google to sign in, it tells Google where to send them back: the redirect URI. Google's docs say "the value must exactly match one of the authorized redirect URIs for the OAuth 2.0 client", and the http or https scheme, case, and trailing slash must all match. If it doesn't, you get a redirect_uri_mismatch error.
What to do
- In Google Cloud, open your OAuth client and add the exact address under Authorized redirect URIs.
- Using Supabase Auth? Add your Supabase project's callback URL there. You'll find it on the Google provider page in the Supabase dashboard.
- Also add your application's URL under Authorized JavaScript origins: your live domain, not just localhost.
Good to know
- Google's page doesn't say how long a change takes to apply.
Source
Checked on 8 Oct 2026. Prices, limits and settings change, so check the source before you rely on them.