Google Chrome · Rate Limits
Google Chrome Rate Limits
Most Chrome developer APIs run in-process inside the browser and have per-extension or per-API internal limits rather than network-rate limits. Two cloud-hosted Chrome APIs do enforce server-side quotas: the Chrome User Experience (CrUX) API and PageSpeed Insights API, which share the standard Google Cloud API project quotas (default 25,000 queries per day per API key with per-100-second per-user caps). The Chrome Web Store publishing API has per-publisher daily limits.
7 Limits
Throttle: 429
Quota: 403
BrowserChrome ExtensionsDeveloper ToolsWeb PlatformRate Limiting
Limits
CrUX API queries per day api-key
150
Default per-API-key daily quota; can be raised via the Cloud Console quotas page.
CrUX API queries per minute per user user
30
PageSpeed Insights queries per day api-key
25000
PageSpeed Insights queries per 100 seconds api-key
400
400 queries per 100 seconds per API key.
Chrome Web Store Publish API developer-account
see Cloud Console quota
Standard Google API project quota; raise via the Cloud Console.
Extension chrome.storage.sync per item extension
8192
8 KB per item; 100 KB total quota for sync storage.
Extension chrome.storage.sync write operations extension
120
Maximum sustained write operations to chrome.storage.sync.
Policies
API project quotas
Cloud-hosted Chrome APIs (CrUX, PageSpeed Insights) follow the standard Google Cloud API project quota model and can be raised via the Cloud Console quotas page.
In-browser API rate limits
Extension APIs enforce per-extension internal limits (e.g., chrome.storage.sync write throughput, chrome.alarms minimum interval, chrome.tabs operation rates). These are not network-rate limits and are documented per API in developer.chrome.com.
Backoff
Honor 429 / 403 quotaExceeded with exponential backoff and jitter; cache CrUX responses since underlying data updates only daily/weekly.