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.

Google Chrome Rate Limits is the machine-readable rate-limit profile for Google Chrome on the APIs.io network, conforming to the API Commons Rate Limits specification.

It captures 7 rate-limit definitions, measuring requests_per_day, requests_per_minute, requests_per_100_seconds, bytes, and writes_per_minute.

The profile also includes 3 backoff/retry policies defined and response codes documented for throttled and quotaExceeded.

Tagged areas include Browser, Chrome Extensions, Developer Tools, Web Platform, and Rate Limiting.

7 Limits Throttle: 429 Quota: 403
BrowserChrome ExtensionsDeveloper ToolsWeb PlatformRate Limiting

Limits

CrUX API queries per day api-key
requests_per_day · day
150
Default per-API-key daily quota; can be raised via the Cloud Console quotas page.
CrUX API queries per minute per user user
requests_per_minute · minute
30
PageSpeed Insights queries per day api-key
requests_per_day · day
25000
PageSpeed Insights queries per 100 seconds api-key
requests_per_100_seconds
400
400 queries per 100 seconds per API key.
Chrome Web Store Publish API developer-account
requests_per_day
see Cloud Console quota
Standard Google API project quota; raise via the Cloud Console.
Extension chrome.storage.sync per item extension
bytes
8192
8 KB per item; 100 KB total quota for sync storage.
Extension chrome.storage.sync write operations extension
writes_per_minute · minute
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.

Sources

Work with this as data

Every rate limit here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for rate limits

4 MCP tools reach this
  • find_rate_limitsBrowse and filter every rate limit in the catalog.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools →

Call it yourself

curl for this page
This rate limit 
curl "https://apis.io/api/v1/rate-limits/google-chrome-rate-limits"
All rate limits 
curl "https://apis.io/api/v1/rate-limits?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have.