Optional · ~10 minutes · One time
YouTube API & OAuth setup
TubeStack works locally without Google sign-in. Set this up only if you want YouTube Data API features (metadata, channel scans) or OAuth features (import/export playlists on your account).
Install TubeStack first. After loading the extension, open
Connect YouTube or Settings → YouTube OAuth in the dashboard to copy your
exact redirect URI and extension ID. Each install has its own ID.
Google Cloud
Use one project for both the API key and OAuth client. Open Google Cloud Console
-
1 Create a project
- Create or select a project (for example TubeStack).
-
2 Enable YouTube Data API v3
- Go to APIs & Services → Library.
- Search YouTube Data API v3 and click Enable.
-
3 Create an API key
- Go to APIs & Services → Credentials.
- Create credentials → API key.
- Optional: restrict the key to YouTube Data API v3 only.
- Copy the key (starts with
AIza).
-
4 OAuth consent screen
- Go to APIs & Services → OAuth consent screen.
- Choose External. Fill in app name and support email.
-
Add scope
https://www.googleapis.com/auth/youtube - Keep the app in Testing. Add your Google email under Test users. Do not publish unless you need production verification.
-
5 OAuth Client ID (Web application)
- Go to Credentials → Create credentials → OAuth client ID.
- Type: Web application.
- Under Authorized redirect URIs, paste the exact URI from TubeStack Connect YouTube or Settings (not from this page).
- Copy the Client ID (ends with
.apps.googleusercontent.com).
https://<extension-id>.chromiumapp.org/
Paste into TubeStack
Finish in the extension
- YouTube Data API key → Setup Integrations or Settings → save, then Test API key.
- OAuth Client ID → Connect YouTube or Settings → YouTube OAuth → save, then Test Google sign-in.
Troubleshooting
- Access blocked — your Google account must be listed under OAuth Test users.
- Redirect URI mismatch — copy the URI again from TubeStack after installing this build; dev and Chrome Web Store installs use different extension IDs.
- Nothing is sent to a TubeStack server. Keys and Client IDs stay in Chrome extension storage on your device.