Oxylabs Pricing and Real Cost per 1,000 Pages, Plans and Per GB Rates

Oxylabs prices well by the standards of this market. The plan cards are clear, the per target rates are published rather than hidden behind a credit multiplier table, and billing is success based. What the pricing page does not do is tell you what a thousand pages will cost, because the answer depends on which of six meters you end up on and which sites you point at.

This piece does that conversion. Every rate below was read directly from oxylabs.io on 23 September 2026. Oxylabs runs rolling coupons and adjusts plan sizes, so check the live page before committing a budget, and pay attention to which numbers are promotional.

The products and what each one meters

You are not choosing a plan so much as choosing a billing unit. These are the entry rates listed in the site navigation today.

Two lines decide almost every real bill. The Web Scraper API if you want Oxylabs to fetch and parse the page, Web Unblocker if you want to keep your own scraper and route it through their unblocking layer. Everything else is either a component of those or a niche buy.

Web Scraper API plans and the per target rates

This is the product most people mean when they compare Oxylabs with a scraping API. It is already priced per thousand results, so no conversion is needed. The complication is that there is not one rate, there are four, and which one applies depends on the domain you asked for.

All rates in USD per 1,000 results. Media downloads are billed separately at 3 USD per GB on Micro, 2.50 on Starter, 1 on Business and 0.95 on Custom+. Rate limits are 50 requests per second on Micro and Starter, 100 on Business and above.

The included results number assumes you are scraping Amazon

Here is the part that catches people out, and it is arithmetic rather than opinion. Micro is 49 USD and advertises up to 98,000 results. Multiply 98,000 by the 0.50 base rate and you get exactly 49 USD. The included figure is the plan fee divided by the cheapest per target rate on the card, which is the Amazon rate.

Scrape anything else and the same 49 USD buys considerably less.

Results the plan fee buys, rounded to the nearest hundred. Nothing is hidden here and the per target rates are printed right on the pricing page, but the headline number is the one that ends up in a budget spreadsheet, and it is the best case rather than the typical one. If you are pulling ordinary sites with rendering, the honest planning figure on Micro is about 36,000 pages for 49 USD, not 98,000.

The same distinction matters when you compare vendors. Our own plans are 49 USD for 50,000 successful requests, 149 for 250,000 and 499 for 1.5 million, and those counts do not move with the target. Rendering is not a surcharge, Amazon is not a discount, and a page behind Imperva Incapsula or Akamai Bot Manager costs the same as a static blog post.

Web Unblocker bills bytes, not requests

Web Unblocker is the product for teams that want to keep their own crawler and only outsource the getting through. It is a single entry proxy node, so integration is a one line change, and it is metered by bandwidth.

To turn that into pages you need a page weight. Oxylabs supplies one itself: the free trial is 1 GB and they describe it as up to 10,000 results, which works out at roughly 105 KB per result. That is a reasonable figure for raw HTML with images and fonts blocked. It is nowhere near what you get from a full browser render with assets, which is commonly 1.5 MB.

Cost per 1,000 pages. Read that table twice, because it contains the one lesson that saves real money on any per GB plan: blocking images, fonts and analytics in your crawler configuration is worth more than any discount tier. Going from a 1.5 MB render to a 500 KB one cuts the line by two thirds at every price point, and on most targets the data you want was in the HTML all along.

It also explains a result that surprises people: for light pages, Web Unblocker at 0.46 to 0.96 USD per 1,000 is cheaper than the Web Scraper API's 1.15 for the same sites. Oxylabs publishes a customer quote on that page claiming their cost per 1,000 requests fell to 0.60 USD after switching, which is consistent with a light page and a discounted per GB rate. Heavy pages invert the comparison completely.

Residential proxies as the raw network

If you run everything yourself and only want addresses, this is the meter. The pool is advertised at 177 million addresses across 195 countries.

These divide cleanly, which is more than can be said for some competitors. At 500 KB a page that is 2.93 USD per 1,000 pages on Starter and 1.22 on Corporate, before you have written a parser, maintained a fingerprint or paid for the compute that runs the browser. The proxy line is the floor of your cost, not the total.

The coupon, and a stale FAQ worth knowing about

Web Unblocker currently carries a 40 percent discount applied with a coupon code. That is a genuine saving and there is no reason not to take it. The mistake is building unit economics on it. If your model says a customer costs 4.50 USD per 1,000 pages to serve and the promotion ends at 7.50, your margin moves on a date nobody put in the calendar. Budget on the list rate and treat the discount as a cash bonus.

Second thing, and this one is small but telling. The FAQ on the residential proxy page still answers the question of what residential proxies cost with plans starting from 99 USD a month for 11 GB. The live plan cards on the same page say 30 USD for 5 GB and 100 USD for 20 GB. Neither matches. Vendor FAQ copy across this whole market ages badly, third party review blogs age worse, and the only number you should ever plan around is the one on the checkout screen the day you buy.

The breakeven against flat per request pricing

Our own pricing is one rate per thousand successful requests regardless of target difficulty, page weight or rendering: 49 USD for 50,000 requests, 149 for 250,000, 499 for 1.5 million, which is 0.98, 0.60 and 0.33 USD per 1,000. Here is the comparison at three real volumes on ordinary sites with JavaScript rendering, which is what most crawls actually are.

Drop the rendering requirement and the gap narrows but does not close: 57.50, 275 and 1,125 USD at the other sites rates. The one place it reverses is Amazon. At 0.30 USD per 1,000 on Business, Oxylabs undercuts our 0.33 Scale rate, and if your crawl is Amazon dominated above a million pages a month you should price that seriously rather than take our word for anything. We have written up how the Amazon scraping API side of this works on our own network, and the honest summary is that a specialist at volume on one marketplace is hard to beat on price alone.

Where Oxylabs is the right buy

More often than a competitor's blog post usually admits. The per target rate card is published in full, which is rarer than it should be in this market, and success based billing means 5xx and 6xx failures are not deducted. A free trial of 2,000 results with no credit card, plus a separate 1 GB Web Unblocker trial, is enough to actually test your targets before spending anything.

Every listed plan, including the 30 USD residential one, advertises 24/7 support and a dedicated account manager. If you have ever tried to get a human on a scraping vendor's support queue at the entry tier, you know what that is worth. They also sell the answer rather than the tool through prebuilt scrapers for e-commerce, SERP and real estate targets, and ready made datasets, so if your data already exists in their catalogue, buying it beats collecting it.

And if you need obscure geographies, a 177 million address pool across 195 countries covers more ground than most. Coverage is one of the few things in this business that genuinely scales with company size.

Where flat per request pricing wins

When you need to know the bill in advance. A per target rate card plus a per GB meter means your invoice is decided by which domains your crawler happened to hit this month, how heavy those pages were, and whether somebody shipped a change that stopped blocking images. None of those are things a finance team can forecast, and all of them arrive after the money is spent.

Flat per request pricing removes the variable. Multiply pages by the rate and you have the number, whether the target is a static blog or sits behind Cloudflare, DataDome or Imperva Incapsula and Kasada. Refused attempts are not billed, so a hard target does not quietly cost you three times a soft one through retries you never see on a dashboard.

It also wins on mixed workloads, which is what most teams really run. Ten thousand easy pages and two thousand heavily protected ones is the normal shape of a crawl, and rate card models charge a premium on exactly the pages you needed most. Worth saying too: if you end up splitting volume across two vendors to chase the cheapest rate per target, keep a record of which upstream each table's rows actually came from, because six months later a data quality question will turn into an archaeology project without it.

Questions buyers ask

How much does Oxylabs cost per month? There is no single price because every product meters differently. The realistic entry points today are 49 USD a month for the Web Scraper API, 75 USD for 8 GB of Web Unblocker, and 30 USD for 5 GB of residential proxies. Free trials exist on the Scraper API at 2,000 results and Web Unblocker at 1 GB, both without a credit card.

Is Oxylabs expensive? For ordinary sites with rendering, yes, compared with flat per request APIs: 1.35 USD per 1,000 on the entry plan against 0.98, and the gap widens with volume rather than narrowing. For Amazon at scale it is the other way round, and at 0.30 USD per 1,000 on the Business plan it is one of the cheapest options anywhere.

Does Oxylabs charge for failed requests? The Web Scraper API is success based and does not deduct for 5xx or 6xx failures. The proxy products bill bandwidth, which means a failed attempt still transfers bytes and still costs you, and on a heavily protected target retries can be a meaningful share of the bill.

What is the cheapest Oxylabs plan? Residential proxies at 30 USD for 5 GB is the lowest monthly commitment, but it is the rawest product and the total cost of running a crawler on it is much higher than the line item. For a fetch-and-parse comparison, Web Scraper API Micro at 49 USD is the entry point.

Oxylabs or Bright Data? They compete on almost identical ground, and Oxylabs publishes a migration guide for moving off Bright Data's Web Unlocker. Bright Data has the larger proxy pool and a bigger prebuilt dataset catalogue. Oxylabs publishes clearer per target rates. We converted both to the same unit, so compare Bright Data pricing per 1,000 pages against the tables above.

How do I compare scraping vendors properly? Convert everything to cost per 1,000 pages using your own measured page weight and your own mix of target domains, not a vendor's example. We have run the same conversion for ScraperAPI and Apify, and since then for Zyte, whose rates vary by tier. All of them sit next to our own flat plans in the same unit.