Guide and OAuth helper to generate keys for Chrome Extensions upload
Companion to Chrome Web Store Upload to publish extensions.
You can follow this complete guide or the official-but-partial one at: https://developer.chrome.com/docs/webstore/using-api
Tip
The names you enter here don't really matter. It's an app that only you will have access to. This will take approximately 10 minutes and Google likes to change these screens often. Sorry.
-
Visit https://console.developers.google.com/apis/credentials
-
Create a project:
-
Enter
chrome-webstore-uploadand Create -
Click Get started
-
Enter the Application name (e.g.
chrome-webstore-upload) and required email field
-
Select Internal
-
Fill in any required fields until Create becomes available
-
Click Create OAuth client
-
Select Desktop app, enter
Chrome Webstore Uploadas the name and click Create
-
Save your ✅
CLIENT_ID
-
Open the "Chrome Webstore Upload" client on screen
-
Click the Info button in the top right
-
Save your ✅
CLIENT_SECRET
-
Visit https://console.cloud.google.com/apis/library/chromewebstore.googleapis.com
-
Click Enable
-
Run this CLI tool to generate the required
refreshTokennpx chrome-webstore-upload-keys
or
bunx chrome-webstore-upload-keys
-
Done. Now you should have ✅
CLIENT_ID, ✅CLIENT_SECRETand ✅REFRESH_TOKEN. You can use these for all your extensions, but don't share them!
- Prompts you for the two keys you just generated
- Opens a local server to handle the OAuth redirect from Google's servers with an
approvalCode - Uses Google's
oauth2API to request arefreshToken