How Much Does It Cost to Solve Cloudflare Turnstile? (2026 Breakdown)

If you run automation, QA checks against your own infrastructure, or scrape public data at any volume, Turnstile is the line item nobody budgets for until the invoice shows up. The sticker price per 1,000 solves looks tiny. Then you add proxies, retries, and the attempts you paid for that returned nothing, and the real number drifts somewhere you didn't plan for.

This is the 2026 breakdown of what Cloudflare Turnstile actually costs to solve: the drivers that move the price, what the main solvers charge, and a worked example you can copy for your own volume. Keep it legit, respect the target site's terms, and don't point any of this at logins you don't own.

The four things that decide your Turnstile bill

Every solver quotes a per-1,000 price. That number is the start of the conversation, not the end. Four factors decide what you actually pay.

1. Per-1,000-solve pricing

Turnstile solving is priced per thousand solves, usually written as $X/1k. A $1/1k rate means a tenth of a cent per solve. At 100k solves a month that's $100 at list price, before anything else moves it. Most providers also split "managed" Turnstile (the fast, invisible widget) from the full interactive 5-second challenge, and the challenge costs more because it takes longer to clear.

2. Success-only vs pay-for-attempts

This is the one that quietly doubles bills. Some services charge per attempt, so a failed solve still costs you. Others charge only when they hand back a working token. If a provider runs an 80% success rate and bills every attempt, your effective price per working token is 25% higher than the sticker, because one in five of the things you paid for did nothing. Read the billing model before the price.

3. The hidden proxy cost

Here's what the comparison blogs skip. Most solvers run in "with proxy" mode, which means you supply the proxy and the solve happens through your IP. Residential proxies are billed per gigabyte, and a Turnstile solve through a browser session pulls real traffic: the page, the widget's scripts, the challenge assets. Figure somewhere around 1 to 3 MB of proxy traffic per solve depending on the site. At $3 to $8 per GB for residential bandwidth, that's a second bill running underneath your solve bill, and it's often larger than the solve bill itself. We dug into why in residential vs datacenter proxies for solving.

4. Volume discounts

Rates drop as you commit more volume. The gap between a hobby rate and a volume rate is often 2x or 3x on the same service, so the price you see on the homepage is rarely the price a real customer at scale pays. When you compare, compare at your actual tier.

What the main solvers charge per 1,000 Turnstile solves in 2026

Here's a fair, approximate snapshot. Treat these as ballpark figures, not quotes. Providers change pricing, and your tier and region shift the real number. Verify on each service's own pricing page before you commit.

Two reads come out of that table. First, the headline prices sit close enough that the billing model and the proxy question matter more than the per-1k rate. Second, a floor of $0.35/1k at volume is roughly a third of the common list rates, so where you land on the volume curve changes the math more than which logo you pick. For a deeper side-by-side, we keep an honest comparison of Turnstile solvers current.

Why "pay only for successful solves" changes the real cost

Turnstile isn't a coin flip, but no solver clears 100% of the time. Sites tune their widget, challenge difficulty shifts, and some sessions just fail. The question is who eats the cost of a miss.

Say you need 100,000 working tokens a month and the solver clears 85% of attempts. Under a pay-per-attempt model you'd fire roughly 117,600 attempts to land 100,000 tokens, and you pay for all 117,600. At a $1.20/1k attempt rate that's about $141, not the $120 the list price implied. The 15% you missed still billed you.

Under a success-only model you pay for 100,000 tokens, full stop. The misses are the provider's problem, which also lines up incentives: the service only makes money when it actually solves. Peak bills success-only, so the number you multiply is working tokens, not attempts. That's the number in the cost field of every response:

POST https://api.peak.fo/solve
X-API-Key: your_key_here
Content-Type: application/json

{
  "task_type": "turnstiletaskproxyless",
  "url": "https://example.com/login",
  "sitekey": "0x4AAAAAAA..."
}

{
  "success": true,
  "data": { "token": "1.7Nm..." },
  "cost": 0.0009
}

One request, token back in about a second, and the cost field tells you what that specific solve cost. No separate accounting for attempts that returned nothing.

Worked example: 100k Turnstile solves a month

Let's price a realistic month at 100,000 Turnstile solves, two ways. Round numbers so you can follow the shape.

Bring your own proxy

You pick a solver at a with-proxy rate and supply residential IPs yourself.

• Solving: 100,000 solves at ~$1.20/1k = $120
• Proxy traffic: ~2 MB per solve x 100,000 = ~200 GB. At $5/GB residential = $1,000
• Retries on failed attempts (if the service bills per attempt at 85% success): add roughly $18 in solve cost plus the proxy traffic those retries burned
• Running total: roughly $1,140+, and the proxy line dwarfs the solve line

The proxy bill is the story here. The thing you came to buy, the solve, is under 11% of what you spend. If you're surprised by that, you're not alone, and it's exactly why what captcha solving actually costs is worth reading before you pick a vendor.

Proxyless

Now the same 100,000 solves through a proxyless endpoint, where the provider's own exit IPs carry the traffic. You send a URL and a sitekey, nothing else.

• Solving: 100,000 successful solves. At Peak's $1/1k that's $100; at a volume rate near $0.60/1k it's $60
• Proxy traffic: $0, because you supply no proxy
• Retries: $0 extra, because you only pay for the 100,000 tokens you received
• Running total: $60 to $100

Same work, and the bill drops by an order of magnitude once the proxy line disappears. The catch worth naming: proxyless means the solve runs from the provider's IPs, which fits automation, QA, and public-data jobs cleanly. If your use case genuinely needs the request to originate from a specific residential IP you control, that's when bring-your-own-proxy earns its cost. We cover when each makes sense in solving Cloudflare Turnstile without a proxy.

How to estimate your own cost

Four inputs give you a number you can trust. Pull them in this order.

1. Monthly working tokens. Not attempts, the tokens your job actually consumes. Count a week and multiply.
2. Your volume tier rate. Check the provider's price at your real monthly volume, not the homepage rate. For Peak that's the Turnstile solving pricing curve from $1/1k down to $0.35/1k.
3. Billing model multiplier. Success-only? Multiply tokens by the rate and stop. Pay-per-attempt? Divide your token count by the success rate first, then multiply.
4. Proxy traffic, if any. With-proxy mode: estimate MB per solve, multiply by solves, multiply by your per-GB cost. Proxyless: this line is zero.

A quick formula for the proxyless case:

monthly cost = working_tokens x (rate_per_1k / 1000)

# 100k tokens at $0.60/1k:
100000 x (0.60 / 1000) = $60.00

For the with-proxy case, add the proxy term:

monthly cost = working_tokens x (rate_per_1k / 1000)
             + attempts x mb_per_solve / 1024 x proxy_cost_per_gb

Run both and the gap between them is the proxy tax you're choosing to pay or skip.

Where Peak lands

Put the pieces together and the value pick is the one that's cheap on all four drivers at once, not just the sticker. Peak sits at $1/1k for managed Turnstile falling to $0.35/1k at volume, $1.00/1k down to $0.40/1k for the full 5-second challenge, bills only for solves that return a working token, and runs proxyless so the residential-bandwidth bill never starts. Tokens come back in about a second from a single POST.

You can check the math on your own traffic before you spend anything: the first 1,000 solves are free, no card. Grab a key, point it at a sitekey you're allowed to test, and watch the cost field. If you're wiring it up in code, the Cloudflare Turnstile Python guide has a working client you can paste in.

Short version: the per-1k rate is the least interesting number on the page. Success-only billing and a proxyless endpoint are what keep your real cost close to the sticker, and that's where 100k solves a month comes in under $100 instead of over $1,000.