PricingCompare CORS proxies

cors.dev vs codetabs

The free codetabs CORS proxy announced its shutdown for June 30, 2026, and its API host no longer answers. You can use cors.dev to cover the same keyless GET use with a one-line URL change.

Official pages checked 28 September 2026.

codetabs CORS proxy

Free, now offline

Status: Shutdown announced for June 30, 2026; repository archived; proxy disabled in June 2026
Requests: 5 per second, then 429 until the quota clears, as documented
Size limit: 5 MB per request, as documented
Methods: GET only; other methods returned 400
URL format: Target URL in the quest query parameter; upstream fetched over plain http, 10-second timeout
API key: None; no account

View codetabs README

cors.dev Pro

$5 / month

Plus tax where applicable.

Requests: 500,000 per monthly billing period
Throughput: 600 requests per minute and 10 concurrent requests per account; shared service limits also apply
Targets: Public HTTPS hostnames on port 443
Size & time: 1 MiB request body, 6 MiB response, 10 seconds
Methods: GET, HEAD, POST, PUT, PATCH and DELETE
Headers: Custom headers and explicit Authorization; no browser cookies or secret vault
Caching: Opt-in GET caching, 1 to 300 seconds. Eligible public responses only; cache hits count.

Check managed availability in your account. Free access is available now.

Create account

Replace api.codetabs.com in one line

You can update your code to replace codetabs with cors.dev by adjusting your request URL. The codetabs proxy took the target in a quest query parameter after https://api.codetabs.com/v1/proxy?quest=. With cors.dev, you place the target after https://proxy.cors.dev/ with query strings left as they are. GET and HEAD need no key. Unlike codetabs, the upstream is fetched over HTTPS.

codetabs to cors.dev

// Before: api.codetabs.com, offline since 2026
const before = await fetch('https://api.codetabs.com/v1/proxy?quest=https://api.example.com/path');

// After: cors.dev, no key for GET and HEAD
const after = await fetch('https://proxy.cors.dev/https://api.example.com/path');
const data = await after.json();

Choose for the requests you actually send.

Codetabs is shut down. The README announced closure on June 30, 2026, the repository is archived, and the maintainer disabled the proxy in June 2026 after an abuse notification. On 28 September 2026, codetabs.com returned Cloudflare error 522 while api.codetabs.com returned a rate-limit error. Before closing, codetabs offered 5 MB per request against 1 MiB on cors.dev anonymous access. It permitted GET only against GET and HEAD, 5 requests per second against 600 requests per minute per IP, and plain http upstream fetches against HTTPS only. Note that cors.dev managed access raises responses to 6 MiB.

When to stay with codetabs

You cannot stay with hosted codetabs because the hosted proxy is gone. However, you can run the archived Go source yourself to keep its GET-only, 5 MB, plain-http behavior. You also need this for image proxying. cors.dev anonymous access serves text formats such as JSON, XML, HTML and CSV rather than image files, so http images served over https need another route.

Try cors.dev with your own public HTTPS API if its request model fits your app. The managed trial includes 1,000 requests total over 7 days, without a card. For public GET and HEAD APIs, anonymous use needs no account.

Neither a request count nor a price establishes which service is faster or more reliable. Check your payloads, credentials and traffic pattern against the provider's current documentation.

Read the cors.dev request contract Test your API's CORS response