Are you an AI agent? To use String, read https://usestring.ai/agent-onboarding/SKILL.md first. You can start at https://mcp.usestring.ai with no key.
NewString UnraveledResearch powered by data we scrape from the web.Read the latest issue →
← Comparisons

Best Decodo Alternatives in 2026: 8 Tools Compared

Bruce Magness, Chief of Staff, String · Published October 27, 2026 · Updated November 11, 2026

Last updated: November 11, 2026. Benchmark figures come from the October 30, 2026 run of the Web Data Frontier Benchmark: 100 sites, 17 providers, 5 attempts per site. The per-attempt data is the public run file. Pricing and billing rules were checked against each vendor's own pages on October 27, 2026, and Oxylabs' and Scrapfly's on November 11, 2026.

What is the best Decodo alternative?

String for protected pages that have to come back: it passed 98.6% of 500 requests on 100 bot-protected sites in the October 30, 2026 run, against Decodo's 71.2%. Scrapfly for five APIs on one key, Firecrawl for crawl-to-content work, Bright Data for proxies and datasets on one contract, Context.dev for one flat credit per page, Oxylabs for PerimeterX-heavy lists, and Zyte for easy pages at a low rate.

Decodo is still the cheaper option on most protected-page paths. At its $99 plan it bills $1.10 per 1,000 requests with premium proxies and JavaScript rendering, the configuration the benchmark used. String Growth, also $99, bills $0.16 per 1,000 plain fetches, which is below Decodo's $0.30, and $3.25 for a browser on a premium proxy, which is well above Decodo's $1.10. This page compares all eight tools on benchmark success, latency, pricing at $100 a month, and MCP support. If you only want the two-way comparison, the String vs Decodo page goes deeper on both.

TL;DR

  • Decodo passed 71.2% of benchmark requests, or 356 of 500, eleventh of seventeen providers. It returned nothing on 19 of 100 sites. Its billing docs say you pay only for successful requests, and its response-code table counts a 2xx or 4xx response as successful when a result comes back.
  • String passed 98.6% (as of October 2026), or 493 of 500, the highest of the 17 web scraping APIs tested, with the fastest latency score. Blocked requests are not billed, and the first 20,000 standard fetches are free with no card.
  • String returned all five attempts on 18 of the 19 sites where Decodo returned nothing.
  • Decodo returned content with an average response time under five seconds on only 2 of 100 sites. Of the 17 providers, only ZenRows and Scrapingdog had fewer.
  • At about $100 a month, Decodo's $99 plan bills $0.30 to $1.10 per 1,000 requests by proxy pool and rendering, and String Growth bills $0.16 to $3.25 by fetch path (as of October 2026).
  • Decodo's own marketing cites a 99.92% success rate for its residential proxies, measured with 500 requests to ipinfo.io. That figure measures a different thing from a protected-page benchmark.
  • Every benchmark number comes from a public harness that anyone can rerun with their own API keys.

Decodo and seven alternatives at a glance

Provider Best for Benchmark success Latency score What $100 a month buys (per 1,000) Free tier The catch
String Protected pages that have to return content reliably 98.6% 4.24s Growth, $99: $0.16 plain fetch; $0.80 to $0.90 with a browser or a premium proxy; $3.25 with both. Blocked requests are free 20,000 standard fetches, no card No crawl-to-content endpoint, no site templates, no language SDKs
Decodo Cheap premium-proxy pages, and site templates 71.2% 28.29s $99 plan: $0.30 standard; $0.60 standard plus JavaScript; $0.70 premium; $1.10 premium plus JavaScript Up to 10,000 pages a month, no card Returned nothing on 19 of 100 sites; premium is the default proxy pool
Scrapfly Five APIs on one key 86.8% 19.62s Pro, $100: $0.10 datacenter; $0.50 with rendering or the Unblocker; $2.50 on residential proxies 1,000 credits, no card Credits do not roll over; tenth of 17 on latency
Firecrawl Crawl-to-content and fast failures 81.2% 8.87s Standard, $99 billed monthly: 100,000 credits, or $0.99 per 1,000 pages 1,000 credits a month A returned 403 or 404 page costs a credit; credits do not roll over below Scale
Bright Data Proxies, datasets and unblocking under one contract 75.4% 27.88s No plan near $100. Pay as you go: $1.50 per 1,000 successful requests 5,000 requests a month Premium domains bill higher at a rate shown only in the dashboard
Context.dev One flat credit per page 93.0% 10.96s Pro, $90: 100,000 credits, or $0.90 per 1,000 pages, protection included 1,000 credits a month, no card 79% on Akamai; a 404 response is billed
Oxylabs PerimeterX targets and bandwidth billing 67.4% 16.62s Basic, $100: Web Unblocker at $6 per GB, up to 16 GB. No per-page rate $5 welcome credit 16.7% on AWS WAF; heavy pages cost more
Zyte Easy pages at a low rate 79.6% 14.43s $100 commitment: $0.10 to $0.95 per 1,000 HTTP responses and $0.75 to $12.00 per 1,000 browser responses, by tier $5 credit Zyte assigns each site's tier and reviews it quarterly

Benchmark figures come from the October 30, 2026 run, with 500 requests per provider across 100 sites. The latency score is failure-aware: per target, it takes the p75 of a provider's successful attempts, and a provider with no successful attempt on a target inherits the p75 of the providers that succeeded. Pricing comes from each vendor's published pages, checked October 27, 2026, at the plan closest to $100 a month billed monthly.

Why people leave Decodo

Decodo, formerly Smartproxy, sells proxies first and a scraping API on top of them. Its Web Data API now puts /scrape, /search, /map and /crawl behind one key, and its migration guide says it replaces the older Web Scraping API with the same request parameters. It ships 100+ prebuilt templates, an MCP server, Python, TypeScript and Go SDKs, a CLI, and n8n, Zapier, LangChain and LlamaIndex integrations. Its security page states an ISO/IEC 27001:2022 certification.

People generally look for a Decodo alternative for two reasons: the sites it does not return, and the time it takes on the sites it does.

Hard sites

Decodo returned nothing, across five attempts, on 19 of the 100 sites in the October run. The list includes Amazon, Google, eBay, arXiv, Yelp, G2, Kayak, Skyscanner and Bing. String returned all five attempts on 18 of those 19, and four of five on Skyscanner. Source: the October 30, 2026 benchmark run; the August and September comparisons use the same benchmark's earlier 2026 runs.

Decodo rose to 71.2% from 50.6% in the September run, back near the 70.7% it scored in August. Its Akamai result went from 57.0% in September to 68.0%, and Cloudflare from 46.7% to 73.3%. Decodo's adapter sent the same premium-plus-rendering request body in all three runs.

Some of the zeros are policy rather than failure. Decodo's security page says it "actively blocks access to sensitive targets like banking sites, government portals, streaming platforms, app stores, and ticketing services." Decodo returned 0% across the four ticketing sites and on congress.gov. No pricing tier changes that result, and a buyer with a ticketing list should know it before signing.

Below the zeros sit 27 sites where Decodo returned some attempts and not others. A target that passes three times in five corrupts a time series quietly, and retries to close the gap raise the bill.

Pricing

Source: Decodo's own pricing and billing pages, linked below and checked October 27, 2026. Decodo's $99 plan is "up to 141K crawls or 330K pages scraped." The billing docs give the per-1,000 rates on that plan: $0.30 on standard proxies, $0.60 with JavaScript rendering, $0.70 on premium proxies, and $1.10 on premium proxies with rendering.

The default matters. Decodo's docs say: "If you don't set proxy_pool, requests use the premium proxy pool and are charged at the premium rate." A request with no flags bills $0.70, not $0.30. Its docs also say protected targets want premium proxies with rendering, which is the $1.10 rate.

Failure billing is generous but not absolute. Decodo never charges for its own failures (500, 524 and 613). Its response-code table also says "Responses with 2xx or 4xx status codes are considered successful if the results are retrieved." A block page that comes back with a body can count as a result.

How we tested these web scraping APIs

Success rates come from the Web Data Frontier Benchmark. The October 30, 2026 run sent 17 providers to the same 100 live sites, five loads each, for 500 requests per provider and a 90-second timeout. A request passed only when the response contained a marker string from the real page. A captcha interstitial or an empty page that returns HTTP 200 counted as a failure. The full ranking of all 17 web scraping APIs uses the same run.

Decodo's adapter posts to /v2/scrape with target: "universal", proxy_pool: "premium" and headless: "html". That is the setup Decodo's own docs prescribe for protected or difficult targets, and it is the most expensive of its four rates. It returns raw HTML and does not use a site-specific template. A Decodo template could do better on the site it was built for, but no one template covers a 100-site list. Since October 29 the adapter also accepts a dashboard API key and sends the same body to the Web Data API's /v1/scrape; the migration guide says the new endpoint accepts the same parameters.

Decodo publishes its own success numbers, and they belong next to ours. Its residential proxy pages advertise a "99.92% success rate." The residential pricing page says that figure is based on Proxyway's research, and describes the method: "We sent 500 requests per endpoint to the http://ipinfo.io/ip website." ipinfo.io/ip returns the caller's IP address and is not a protected page, so that test measures whether a proxy connects, not whether a protected page comes back. The Web Data API page separately cites Proxyway's 2025 scraping API research as measuring "over 80% success on the hardest targets," with rendering and premium proxies enabled. Our 100-site suite measured 71.2% in the same configuration. The three numbers answer three different questions.

Disclosure: String built this benchmark and sells the product that ranks first in it. The answer to that conflict is a harness you can run yourself. The targets, pass criteria and every provider adapter are open on GitHub, and the repository accepts your own API keys. The original benchmark post explains the pass rule and why the latency score refuses to reward fast failures.

Firecrawl's engineer said its configuration was wrong, opened a pull request, and raised Firecrawl's score by 7.7 points. If Decodo believes a different general configuration is fairer, its adapter is one file.

Chart data
ProviderSuccess ratePassedLatency score
String98.6%493/5004.24s
Scrape.do94.0%470/5005.08s
Context.dev93.0%465/50010.96s
Scrapfly86.8%434/50019.62s
ScrapingBee85.2%426/50020.30s
Firecrawl81.2%406/5008.87s
Zyte79.6%398/50014.43s
Apify79.4%397/50024.87s
ScraperAPI76.4%382/50015.19s
Bright75.4%377/50027.88s
Decodo71.2%356/50028.29s
Nimble68.0%340/50022.65s
Oxylabs67.4%337/50016.62s
Browserbase43.0%215/50018.01s
ZenRows41.8%209/50021.91s
ScrapingAnt40.0%200/50018.39s
Scrapingdog27.6%138/50031.52s
Overall success rate across all 500 requests per provider. Web Data Frontier Benchmark · 100 targets · 500 requests per provider · October 30, 2026. Current leaderboard

String vs Decodo: 98.6% vs 71.2%, and no bill when a page is blocked

String is a web scraping API. Its Web Access API makes one HTTP call against any URL. Proxy rotation, anti-bot handling, captcha solving and JavaScript rendering happen behind the endpoint, and String picks the fetch path for each request.

Pricing. Usage-based: the monthly fee becomes usage credit, and unused credit rolls over. Growth is $99 a month (as of October 2026) and bills $0.16 per 1,000 plain fetches on a standard proxy, $0.90 on a premium proxy, $0.80 for a browser on a standard proxy, and $3.25 for a browser on a premium proxy. Starter is $19 at $0.25, $2.40, $1.20 and $4.80. Premium rates apply only when a site blocks the standard proxy. Against Decodo's $99 plan, String is cheaper on plain fetches ($0.16 against $0.30) and more expensive on every premium or browser path ($0.90 against $0.70, $0.80 against $0.60, $3.25 against $1.10).

Benchmark success. 98.6%, or 493 of 500, first of 17. String returned all five attempts on 95 sites and partial content on the other 5.

Latency. 4.24 seconds, the fastest of the 17. Decodo's score was 28.29 seconds, sixteenth of 17.

Strengths.

  • The highest pass rate in the run, including all five attempts on 18 of the 19 sites where Decodo returned nothing.
  • 100% against AWS WAF and Fastly, 98.7% against Cloudflare, and 97% against Akamai, where Decodo read 73.3%, 0%, 73.3% and 68.0%.
  • Blocked requests are not billed. None of String's failed attempts came back as a 2xx without the real page, against 48 for Decodo.

Weaknesses.

  • More expensive than Decodo on premium and browser paths.
  • No crawl-to-content endpoint, no site templates or parsers, no self-hosting, and no language SDKs.
  • Decodo beat String on four sites: it returned all five attempts on Yellow Pages, MarketWatch and Barron's, where String returned four, and three of five on Kroger, where String returned two.

MCP. String's hosted server is listed in the official registry as ai.usestring/web-access, at https://mcp.usestring.ai/v1/mcp, with fetch, search and sitemap tools (docs).

Try it on the URLs that fail on Decodo today:

curl https://request.usestring.ai/v1/fetch \
  -H "Authorization: Bearer $STRING_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"url": "https://www.example.com/the-page-that-blocks-you", "format": "markdown"}'

Leave out format and the page comes back in a JSON envelope.

Scrapfly vs Decodo: five APIs on one key vs one endpoint and templates

Source for this section: Scrapfly's pricing page, checked November 11, 2026, and the October 30, 2026 benchmark run.

Pricing. Pro is $100 a month for 1,000,000 credits, at $0.10 per 1,000 credits prepaid and $3.50 per 10,000 beyond that. A datacenter HTTP scrape is 1 credit, rendering or the Unblocker is 5, and residential proxies are 25, so the per-1,000-page rates are $0.10, $0.50 and $2.50. Scrapfly says a failed request is "$0, never charged on error," and that upstream 4xx and 5xx responses are free. Credits do not roll over: "Quotas reset at renewal."

Benchmark success. 86.8%, or 434 of 500, fourth of 17 and 15.6 points above Decodo. It returned nothing on 5 sites against Decodo's 19, and returned all five attempts on 13 of Decodo's 19.

Latency. 19.62 seconds, tenth of 17, against Decodo's 28.29.

Strengths. Fourth in the run, behind String, Scrape.do and Context.dev. Five APIs share one credit pool, with SDKs for Python, TypeScript, Go and Rust, a hosted MCP server, and SOC 2 Type II, ISO 27001 and GDPR on every plan per its pricing page, with HIPAA on Enterprise only. It passed 92.6% on DataDome and 96.7% on AWS WAF.

Weaknesses. The rate depends on what a page needs. A datacenter fetch is $0.10 per 1,000, the Unblocker is $0.50, and residential proxies are $2.50, so the bill on protected pages is hard to forecast before you run them. Decodo beat it on 15 sites, including Zara and Alibaba, where Decodo returned all five attempts and Scrapfly none.

Firecrawl vs Decodo: crawl-to-content vs raw retrieval

Source for this section: Firecrawl's pricing and billing pages, checked November 11, 2026, and the October 30, 2026 benchmark run.

Pricing. Standard is $99 a month billed monthly, or $83 a month billed annually, for 100,000 credits: $0.99 per 1,000 pages at full use. The enhanced proxy costs the same 1 credit as a basic request. Firecrawl's billing docs say the charge depends on "whether Firecrawl returned a document," so a page that comes back as 403 or 404 costs a credit and a scrape that fails outright costs nothing. Hobby, Standard and Growth credits do not roll over.

Benchmark success. 81.2%, or 406 of 500, sixth of 17. It returned all five attempts on 15 of Decodo's 19 zero sites.

Latency. 8.87 seconds, third fastest of 17.

Strengths. Crawl, map, search, monitor and document parsing on one API, an open-source core, SOC 2 Type II, and fast failures. It scored 98.7% on Cloudflare against Decodo's 73.3%.

Weaknesses. Social media. Firecrawl scored 25.0% across eight social platforms and Decodo scored 92.5%. Decodo returned all five attempts on Reddit, Instagram, Facebook, TikTok, Pinterest, The New York Times, AutoTrader and eMAG, where Firecrawl returned none. Firecrawl also bills x.com requests at 30 credits.

Bright Data vs Decodo: one enterprise contract vs one cheap endpoint

Source for this section: Bright Data's Web Unlocker pricing and feature pages, checked November 11, 2026, and the October 30, 2026 benchmark run.

Pricing. No plan near $100. Pay as you go is $1.50 per 1,000 requests, with "Pay only for success," and Scale starts at $499 for 383,000 requests. Two caveats change the real bill. Bright Data bills premium domains at a higher rate that appears only in the zone's "Estimated cost" section, and it updates that domain list quarterly with 30 days' notice. With custom headers, cookies or expect elements enabled, "you'll be billed for 100% of the requests (both successful and failed)." Because the premium rate is unpublished, Bright Data is not ranked as the cheapest option anywhere on this page.

Benchmark success. 75.4%, or 377 of 500, tenth of 17. It returned all five attempts on 7 of Decodo's 19 zero sites.

Latency. 27.88 seconds, fifteenth of 17, one place ahead of Decodo.

Strengths. Proxies, datasets, SERP APIs and unblocking under one contract, ISO 27001, a hosted MCP server, and 94.3% on real estate.

Weaknesses. Akamai, at 72.0%, and Kasada, at 66.7% against Decodo's 100% on three sites. Decodo returned all five attempts on Louis Vuitton, Canada Goose, Yahoo Finance, Reuters, eMAG, YouTube and buybuy BABY, where Bright Data returned none. Its pay-as-you-go rate is above Decodo's top $1.10 rate.

Context.dev vs Decodo: one flat credit vs four rates

Source for this section: Context.dev's pricing page, checked November 11, 2026, and the October 30, 2026 benchmark run.

Pricing. Pro is $90 a month for 100,000 credits, or $0.90 per 1,000 pages, with $2.00 per 1,000 credits of overage. Context.dev says "JS rendering, anti-bot bypass, and proxies are included in the base scrape price." Browser actions raise a scrape to 2 credits and JSON extraction to 5. On failures, Context.dev's pricing FAQ says "Most failed requests are not billed" and "Not-found responses (404) are billed at the request's base price."

Benchmark success. 93.0%, or 465 of 500, third of 17. It returned all five attempts on 16 of Decodo's 19 zero sites.

Latency. 10.96 seconds, fourth fastest of 17.

Strengths. The most predictable bill on this page. Decodo prices premium plus rendering at almost four times its standard rate, $1.10 against $0.30; Context.dev prices every page the same. It has SDKs in five languages and an MCP server.

Weaknesses. Akamai, at 79.0%, its weakest major wall. Decodo returned all five attempts on buybuy BABY, where Context.dev returned none.

Oxylabs vs Decodo: bandwidth billing vs per-request billing

Pricing. Oxylabs now sells one subscription across its products. On Basic, $100 a month (as of November 2026), Web Unblocker costs $6 per GB, up to 16 GB; Starter, $15, is $7.20 per GB up to 2 GB. There is no per-page rate to set beside Decodo's, because the bill depends on page weight. Oxylabs says "We will only charge you for successfully extracted data. Failed scraping attempts won't be included into your traffic usage calculation" (Web Unblocker FAQ).

Benchmark success. 67.4%, or 337 of 500, thirteenth of 17. It returned all five attempts on 4 of Decodo's 19 zero sites, the fewest in this group.

Latency. 16.62 seconds, seventh fastest of 17.

Strengths. 91.1% on PerimeterX and 100% on Kasada, ISO/IEC 27001:2022, an MCP server, and a bill that suits small pages.

Weaknesses. 16.7% on AWS WAF and 0% on the one Fastly site. Decodo returned all five attempts on Apartments.com, Louis Vuitton, Zara, Facebook, eMAG and Booking.com, where Oxylabs returned none. Both returned 0 of 5 on amazon.com through the general path; each vendor sells a dedicated Amazon product the benchmark did not test, and it may do better.

Zyte vs Decodo: a vendor-assigned tier vs a published card

Source for this section: Zyte's pricing pages, checked November 11, 2026, and the October 30, 2026 benchmark run.

Pricing. Zyte API starts "From $0.06 per 1,000 successful responses," and the real rate depends on a tier. At the $100 monthly commitment, the five HTTP tiers run $0.10, $0.17, $0.33, $0.53 and $0.95 per 1,000, and the browser tiers run $0.75 to $12.00. Zyte's pricing docs say "Tier assignment is automatic," and "We review tier assignments quarterly. Affected customers receive 2 weeks notice of any tier changes." Unsuccessful responses are free. The commitment is paid at the start of the month, and "If usage is below the commitment, no refund is provided."

Benchmark success. 79.6%, or 398 of 500, seventh of 17 and 8.4 points above Decodo.

Latency. 14.43 seconds, fifth of 17.

Strengths. The lowest published rate on this page for easy pages, $0.10 per 1,000 on tier 1. 100% on Kasada and 91.1% on PerimeterX. The strongest Scrapy integration for teams that already run spiders.

Weaknesses. You cannot price a list before you sign up, because Zyte assigns the tier. That is the mirror image of Decodo: Decodo publishes four rates and defaults to premium, while Zyte publishes five and tells you which one applies afterwards. Zyte scored 68.0% on Akamai, the same as Decodo.

The anti-bot cut

Success rates by protection vendor, from the October 30, 2026 benchmark run. Site counts are in the column headers.

Provider DataDome (19) Akamai (20) Cloudflare (15) PerimeterX (9) AWS WAF (6) Kasada (3) Proprietary or other (27)
String 97.9% 97% 98.7% 97.8% 100% 100% 100%
Scrapfly 92.6% 78% 93.3% 93.3% 96.7% 86.7% 83%
Firecrawl 85.3% 80% 98.7% 100% 83.3% 100% 60%
Bright Data 74.7% 72% 74.7% 86.7% 73.3% 66.7% 75.6%
Context.dev 100% 79% 96% 97.8% 100% 100% 92.6%
Oxylabs 67.4% 53% 68% 91.1% 16.7% 100% 80%
Zyte 68.4% 68% 92% 91.1% 70% 100% 84.4%
Decodo 65.3% 68% 73.3% 86.7% 73.3% 100% 70.4%

Fastly protects one site and is left out of the table. Kasada protects three, so read that column as an anecdote.

Decodo's strongest columns are Kasada at 100%, level with String, and PerimeterX at 86.7%, level with Bright Data. Its weakest are DataDome at 65.3%, Akamai at 68.0%, and the proprietary group at 70.4%. By industry, Decodo is strongest on news and finance at 100%, ahead of String's 95.6%, on social media at 92.5%, ahead of Firecrawl's 25.0%, and on fashion and luxury at 81.8%, ahead of Scrapfly, Bright Data, Oxylabs and Zyte. If your list is mostly news, finance or fashion and luxury retail, Decodo's overall rank understates it.

Chart data
ProviderDataDome (19 sites)Akamai (20 sites)Cloudflare (15 sites)PerimeterX (9 sites)AWS WAF (6 sites)Kasada (3 sites)Fastly (1 sites)Proprietary / other (27 sites)
String97.9%97.0%98.7%97.8%100.0%100.0%100.0%100.0%
Scrape.do97.9%87.0%93.3%100.0%100.0%100.0%100.0%92.6%
Context.dev100.0%79.0%96.0%97.8%100.0%100.0%100.0%92.6%
Scrapfly92.6%78.0%93.3%93.3%96.7%86.7%40.0%83.0%
ScrapingBee85.3%74.0%97.3%88.9%63.3%100.0%100.0%88.1%
Firecrawl85.3%80.0%98.7%100.0%83.3%100.0%100.0%60.0%
Zyte68.4%68.0%92.0%91.1%70.0%100.0%100.0%84.4%
Apify85.3%69.0%86.7%86.7%63.3%100.0%0.0%80.7%
ScraperAPI75.8%81.0%70.7%82.2%76.7%53.3%100.0%76.3%
Bright74.7%72.0%74.7%86.7%73.3%66.7%100.0%75.6%
Decodo65.3%68.0%73.3%86.7%73.3%100.0%0.0%70.4%
Nimble64.2%51.0%68.0%82.2%40.0%86.7%100.0%81.5%
Oxylabs67.4%53.0%68.0%91.1%16.7%100.0%0.0%80.0%
Browserbase31.6%28.0%6.7%73.3%16.7%33.3%0.0%80.7%
ZenRows52.6%57.0%33.3%73.3%36.7%60.0%0.0%17.8%
ScrapingAnt7.4%33.0%24.0%53.3%13.3%53.3%100.0%74.8%
Scrapingdog16.8%27.0%29.3%6.7%13.3%20.0%0.0%46.7%
Success rate by anti-bot vendor. Web Data Frontier Benchmark · 100 targets · 500 requests per provider · October 30, 2026. Current leaderboard

Decodo has almost no fast path: two pages under five seconds

Source: the October 30, 2026 benchmark run. Across all 100 sites, Decodo returned content with an average response time under five seconds on only two: Zoopla at 1.4 seconds and Reuters at 4.2. Of the 17 providers, only ZenRows, with none, and Scrapingdog, with one, had fewer such sites. String had 78, Zyte 44, and Firecrawl 39.

Decodo had two more sites under five seconds, and on both it returned nothing: arXiv at 2.3 seconds and Temu at 3.7.

The easy sites show the same shape. On the 40 sites where the 17 providers averaged 80% success or better, Decodo returned one in under five seconds, and its median was 20.95 seconds. String's median on the same 40 sites was 1.35 seconds, and Zyte's was 1.5.

This is the difference between a hard-site tax and a floor. A provider that slows down on protected pages makes a trade you can reason about: route the easy half of the list somewhere fast. Decodo charged roughly 20 seconds whether the page was easy or not, so there was no easy half to route.

Two limits on this number. It is a per-site average over five attempts, not a per-request timing. And it says nothing about throughput: Decodo's $99 plan allows 50 requests per second, so a batch job can hide a slow floor behind concurrency. An agent loop or a live lookup cannot, because one page's latency is the user's wait.

Why pricing is hard to compare across these providers

The rate cards do not describe the same thing, so no single number ranks them. Rates below come from each vendor's own pricing and billing pages, checked October 27, 2026 (see Sources). Seven reasons:

  1. The unit differs. Decodo, String and Zyte bill per request. Scrapfly, Firecrawl and Context.dev sell credits. Oxylabs bills Web Unblocker per gigabyte. Bright Data bills per successful request, with an unpublished class for premium domains.
  2. A credit is not a page. One Context.dev credit is one scrape. One Scrapfly credit is a datacenter fetch, and the same page on residential proxies is 25. A Firecrawl page in JSON format is 5 credits, and an x.com request is 30.
  3. Browser and proxy choices move the rate. Decodo's premium-plus-rendering rate is almost four times its standard rate, and premium is its default. String's browser-on-premium path is about 20 times its plain fetch.
  4. What counts as billable differs. String does not bill a blocked request, but bills a site's own 404. Decodo bills a 2xx or 4xx response that returns a result. Firecrawl bills a returned 403 or 404 page. Context.dev bills a 404. Scrapfly calls upstream 4xx and 5xx free. Bright Data bills every request once custom headers or cookies are on.
  5. The vendor may decide the rate. Zyte assigns a tier per site and reviews it quarterly. Bright Data reclassifies premium domains quarterly.
  6. Annual prices pose as monthly. Firecrawl's $83 is the annual rate; the monthly rate is $99. Context.dev's annual billing saves two months.
  7. Prepaid balances behave differently. String's credit rolls over. Scrapfly's, and Firecrawl's below Scale, reset each month. Zyte's commitment is not refunded when usage falls short.

What $100 a month buys

At the plan nearest $100, per 1,000 pages, on each vendor's own terms (source: each vendor's pricing page, checked October 27, 2026):

  • String Growth, $99 (as of October 2026): $0.16 plain fetch, $0.90 premium fetch, $0.80 browser, $3.25 browser on premium. Blocked requests are free, and credit rolls over.
  • Decodo, $99: $0.30 standard, $0.60 standard with rendering, $0.70 premium, $1.10 premium with rendering. Up to 330,000 pages at the standard rate.
  • Scrapfly Pro, $100: $0.10 datacenter, $0.50 with rendering or the Unblocker, $2.50 residential. Failures are free; no rollover.
  • Firecrawl Standard, $99 billed monthly: $0.99 flat at full use. Returned 403 and 404 pages are billed.
  • Context.dev Pro, $90: $0.90 flat, protection included. A 404 is billed.
  • Oxylabs Basic, $100: Web Unblocker at $6 per GB, up to 16 GB. No per-page rate.
  • Zyte, $100 commitment: $0.10 to $0.95 across five HTTP tiers, assigned by Zyte.
  • Bright Data: no plan near $100. $1.50 on pay as you go, with premium domains higher at an unpublished rate.

String against Decodo at this level, in both directions. A page that clears on a plain fetch costs $0.16 on String and $0.30 to $0.70 on Decodo, depending on whether you set the standard pool. A page that needs a browser on a premium proxy costs $3.25 on String and $1.10 on Decodo. Decodo is cheaper on every premium or browser path. If the 48 Decodo attempts that came back as a 2xx without the real page were billed, which Decodo's response-code rule allows, its benchmark configuration cost about $1.25 per 1,000 usable pages rather than $1.10. Decodo returned nothing on 19 of the 100 sites, and no rate applies to those pages.

Which Decodo alternative should you pick?

Figures below are from the October 30, 2026 benchmark run.

Pick String when your list is protected and the pages have to come back. It passed 98.6% against Decodo's 71.2%, and returned all five attempts on 18 of the 19 sites Decodo could not return.

Pick Scrapfly when you want one key for scraping, screenshots, extraction, crawling and a cloud browser, and latency is not the binding constraint. It placed fourth at 86.8%.

Pick Firecrawl when the job is crawl-to-content on cooperative sites and you want fast failures. Do not pick it for social media, where Decodo did better.

Pick Bright Data when proxies, datasets and SERP data under one contract matter more than the published unit price.

Pick Context.dev when one predictable per-page number in the budget matters most. It placed third at 93.0%.

Pick Oxylabs when your blocks are PerimeterX and your pages are small enough for bandwidth billing to work in your favor.

Pick Zyte when most pages are easy and you have mapped your targets to its tiers.

Stay on Decodo when your list is mostly news, finance or fashion and luxury retail, premium-plus-rendering price decides the purchase, a 20.95-second median on easy pages is acceptable, and you need its templates, raw proxy pools or ISO/IEC 27001:2022 certificate. Leave it if your list includes ticketing or government sites, which Decodo blocks by policy.

Switching from Decodo to String

What carries over. A POST to data.decodo.com/v1/scrape, or to the legacy scraper-api.decodo.com/v2/scrape, becomes a POST to String's /v1/fetch with a bearer key. Keep the URL list and the code that reads HTML or Markdown. Decodo's markdown: true maps to "format": "markdown", because String returns a JSON envelope by default. headless: "html" maps to "executeJS": true, and browser actions map to String's actions. You can usually drop proxy_pool: String picks the proxy class per request and bills the path it used.

What you rebuild. Decodo's 100+ target templates and their parsers, async tasks and batches with callbacks, the /crawl endpoint, and the residential, mobile, ISP and datacenter proxy pools have no String equivalent. String's /search endpoint and asynchronous sitemap crawl cover search and URL discovery, and jsonSchema extraction covers the fields you name. If a Decodo template returns a site well today, keep Decodo for that site; running both is a reasonable end state.

Integrations to reconnect. Decodo publishes Python, TypeScript and Go SDKs, a CLI, a hosted MCP server, and n8n, Zapier, LangChain and LlamaIndex integrations. String ships no language SDK, so an SDK call becomes one HTTP POST. String's hosted MCP server runs at mcp.usestring.ai, n8n calls String through the HTTP Request node, and Zapier, LangChain and the Vercel AI SDK have setup guides in String's docs.

Test on your own failing URLs first. Take the URLs that fail on Decodo today, and the ones where Decodo bills a 2xx or 4xx that holds no data, and run them through String. In the October 30, 2026 benchmark run Decodo returned nothing on 19 of 100 sites, and String returned 18 of those on every attempt. Compare pages returned and cost per usable page, then move only the targets that improve. Leave custom headers off for the test: String does not bill a blocked request unless that request sent custom headers. The first 20,000 String standard fetches are free with no card. The String vs Decodo page compares the two products in more depth.

FAQ

What is the best Decodo alternative for Cloudflare-protected sites?

String and Firecrawl, tied. In the October 2026 Web Data Frontier Benchmark each passed 98.7% of requests across 15 Cloudflare sites, against Decodo's 73.3%. Context.dev passed 96.0%. Across all 100 sites, String passed 98.6%, Firecrawl 81.2% and Decodo 71.2%.

Why is Decodo slow even on easy pages?

Decodo does not publish a cause, and we do not know it. The October 30, 2026 benchmark run shows a floor rather than a hard-site tax: Decodo returned content with an average response time under five seconds on only 2 of 100 sites, and only two of the 17 providers had fewer. On the 40 sites where the field averaged 80% or better, its median was 20.95 seconds against String's 1.35.

What is Decodo's real success rate?

It depends on the test. As of October 2026, per its residential pricing page, Decodo advertises a 99.92% residential proxy success rate, and its FAQ says the test sent 500 requests per endpoint to ipinfo.io, which is not a protected page. It cites Proxyway's 2025 research for "over 80% success on the hardest targets." On our 100 protected sites, with premium proxies and rendering, Decodo passed 71.2%.

Is there a free Decodo alternative?

Several have free allowances, per each vendor's pricing page as checked October 27, 2026. String gives the first 20,000 standard fetches free with no card. Scrapfly gives 1,000 credits with no card and no time limit. Firecrawl and Context.dev each give 1,000 credits a month. Bright Data gives 5,000 requests a month. Oxylabs gives a $5 welcome credit and Zyte a $5 credit. Decodo's own free plan covers up to 10,000 pages a month.

What is the cheapest Decodo alternative?

No single answer holds, because the vendors bill different units. Per each vendor's pricing page, checked October 27, 2026, at the $100 level, Zyte bills $0.10 per 1,000 on its easiest tier and Scrapfly $0.10 for a datacenter fetch. String Growth bills $0.16 (as of October 2026) for a plain fetch, below Decodo's $0.30 standard rate. On the protected path Decodo is cheapest at $1.10 with premium proxies and rendering. Bright Data is excluded because it does not publish its premium-domain rate.

Is String cheaper than Decodo?

Per each vendor's pricing page, checked October 27, 2026: on plain fetches, yes. String Growth bills $0.16 per 1,000 (as of October 2026) against $0.30 on Decodo's $99 plan, and $0.70 if you leave Decodo on its default premium pool. On premium and browser paths, no: Decodo bills $0.70 to $1.10 where String bills $0.80 to $3.25. String does not bill blocked requests; Decodo bills a 2xx or 4xx that returns a result.

Which Decodo alternatives have an MCP server?

All seven, and Decodo itself. String's server is ai.usestring/web-access in the official registry, with fetch, search and sitemap tools. Scrapfly, Firecrawl, Bright Data, Context.dev, Oxylabs and Zyte each document their own, as does Decodo.

Can I verify these numbers myself?

Yes. The harness, the 100 targets, the pass criteria and every provider adapter are open on GitHub, and the harness runs with your own API keys. The October 30, 2026 run file holds every attempt. A full run makes thousands of billable requests, so start with a subset of your own URLs.

Sources

Checked October 27, 2026 unless noted.

Benchmark

  1. Web Data Frontier Benchmark leaderboard and the October 2026 results post
  2. Benchmark harness repository
  3. October 30, 2026 run file
  4. Decodo adapter
  5. Firecrawl adapter correction, pull request 6

Decodo

  1. Web Data API
  2. Web Data API pricing
  3. Web Data API billing
  4. Web Data API response codes
  5. Migrating to Web Data API
  6. Web Scraping API page
  7. Residential proxy pricing and test method
  8. Security and compliance
  9. MCP server
  10. AI integrations
  11. Proxyway web scraping API report 2025

String

  1. Pricing
  2. Web Access API
  3. MCP server docs
  4. Integrations
  5. Structured extraction

Other vendors

  1. Scrapfly pricing
  2. Scrapfly Unblocker
  3. Firecrawl pricing
  4. Firecrawl billing
  5. Bright Data Web Unlocker pricing
  6. Bright Data Web Unlocker features
  7. Context.dev pricing
  8. Context.dev MCP
  9. Oxylabs Web Unblocker pricing
  10. Oxylabs Web Unblocker
  11. Oxylabs MCP
  12. Zyte pricing
  13. Zyte API pricing docs

Related String pages: String vs Decodo, the 17 web scraping APIs ranked, Firecrawl alternatives, Bright Data alternatives, Oxylabs alternatives, Zyte alternatives.

Best Web Scraping APIs 2026: 17 Compared by Success RateUpdated November 11, 2026Web Scraping API Pricing in 2026: 17 Providers ComparedUpdated November 11, 2026Best Scrape.do Alternatives in 2026: 8 Tools ComparedUpdated November 11, 2026
Get your API key →Explore the Web Access API