PricingCompare CORS proxies
cors.dev vs corsproxy.io
cors.dev Pro gives you 500,000 requests for $5 a month with no bandwidth metering, where corsproxy.io Hobby gives 250,000 requests and 25 GB at the same price. cors.dev accepts the same ?url= syntax and needs no key for public GET and HEAD requests, so migrating is a host swap plus removing the key.
Official pages checked .
cors.dev Pro
$5 / month
Plus tax where applicable.
- Requests
- 500,000 per monthly billing period
- Throughput
- 1,200 requests a minute per IP; shared service limits also apply
- Targets
- Public HTTP or HTTPS hostnames, any port
- Size & time
- 1 MiB request body, 6 MiB response, 30 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, kept separate per credential; cache hits count.
Check managed availability in your account. Free access is available now.
Create accountcorsproxy.io Hobby
$5 / month
- Requests
- 250,000 per month, monitored as a rolling 7-day quota
- Bandwidth
- 25 GB per month
- Throughput
- 300 requests per minute; limited concurrent connections
- Size & types
- 1 MB max file size; text and simple media types
- Free option
- 10,000 requests, 1 GB and 60 requests per minute; browser requests only, no SLA
- API key
- Required in every proxy URL, free accounts included
- Domains
- 3 production domains
Migrate from corsproxy.io: swap the host, drop the key
corsproxy.io needs ?key= plus a percent-encoded url parameter. cors.dev accepts the same ?url= parameter, plain or percent-encoded, so change the host to proxy.cors.dev and remove the key: GET and HEAD to public APIs need no key, and a query that starts with key= instead of url= is rejected with HTTP 400. Anything after a percent-encoded target is ignored. The path form https:// also works and needs no encoding. Write methods need a managed key on cors.dev.
// Before: corsproxy.io, API key plus a percent-encoded target
const target = encodeURIComponent('https://api.example.com/path?limit=10');
const before = await fetch(`https://corsproxy.io/?key=YOUR_API_KEY&url=${target}`);
// After: same ?url= call, new host, no key for GET and HEAD
const after = await fetch(`https://proxy.cors.dev/?url=${target}`);
const data = await after.json();
// Or skip the encoding and put the target URL in the path
const direct = await fetch('https://proxy.cors.dev/https://api.example.com/path?limit=10');Why choose cors.dev over corsproxy.io
At the same $5, cors.dev Pro includes 500,000 requests against 250,000 on corsproxy.io Hobby, with no bandwidth metering. Free cors.dev needs no account at all for public GET and HEAD calls, where corsproxy.io requires a key in every proxy URL, free accounts included, and limits its free tier to 10,000 requests, 1 GB and 60 requests per minute.
Try cors.dev on the API you are calling right now: public GET and HEAD calls need no account, and the managed trial includes 1,000 requests total over 7 days, without a card.