Web scraping

CAPTCHA Solver for Web Scraping and Scrapy Crawlers

Keep crawlers, price monitors and lead scrapers moving past reCAPTCHA, Cloudflare Turnstile and image checks. CapSkip solves them on hardware you run, for a monthly price that ignores how big the crawl gets.

Windows x64·Runs locally, so no CAPTCHA leaves your machine
  • One bill, any crawl size
  • Unlimited threads
  • Targets stay on your PC
CAPTCHAs a month40,000
40.0k250.0k
Metered elsewhere, about $1.40 per 1,000$56.00
CapSkip Bronze, flat$35.00
$21.00stays in your pocketevery month, at this volume

A CAPTCHA solver for web scraping proves its value the moment a crawler that has run cleanly for hours meets a challenge wall and starts saving empty pages. CapSkip clears reCAPTCHA, Cloudflare Turnstile, GeeTest v3, image CAPTCHAs and more on a Windows machine you run yourself, from an office desktop to a rented VPS, then hands the answer straight back so your spiders keep collecting data instead of stalling.

Price monitoring, lead generation and SEO crawls all run into the same problem with per-solve services: the bill follows the crawl. Twice the pages means roughly twice the challenges, plus every retry, and the solving line on the invoice can end up larger than the proxy spend. CapSkip has no credits and no meter. A subscription costs $35 a month on a single machine, covers unlimited solves, and lets that machine run as many threads as it can carry.

It also fits the stack you already scrape with. Scrapy projects, Selenium, Playwright and Puppeteer scripts, and tools built around 2Captcha or Anti-Captcha are all able to pass their challenges to CapSkip, mostly without a rewrite. Because every solve happens on your hardware, the list of sites you crawl never leaves your network, which matters when that list is the business.

Double the crawl, keep the bill. When a job grows from ten thousand pages to a million, the challenges grow with it, but your CapSkip price does not. Add spiders, widen concurrency and rerun failed pages as often as you need: nothing is counted, so nothing is charged. See the three plans

A web scraping CAPTCHA solver built for big crawls

A crawl that grows, a bill that does not

More pages, more challenges, more retries: none of it changes what you pay. One monthly subscription covers every CAPTCHA your spiders meet, whether the job runs once a week or around the clock.

Concurrency set by hardware, not by a plan

No plan caps threads. Every spider, worker and container you run can send challenges to the same CapSkip machine at once, and throughput simply follows its processor and memory.

Solves through the proxies you crawl with

Send each reCAPTCHA or Turnstile job through the proxy your crawler already uses, so the pass comes from the address that will submit it. Image CAPTCHAs need no proxy at all.

Lightweight scrapers need no browser

Scrapers that never launch a browser can still get through. CapSkip does the browser work on its own side and returns a pass your scraper submits along with the form.

Existing crawler code keeps working

Has your crawler been sending its CAPTCHAs to CapSolver or Anti-Captcha for years? Leave the code alone. Choose the matching service inside the CapSkip window, and every job gets answered locally.

Your target list stays private

A remote solving service receives each URL and image you send it. CapSkip keeps that work on your own box, which means no outside vendor ever learns which sites you monitor.

Connect CapSkip to the way you scrape

Python
# pip install capskip
from capskip import CapSkip
import requests

solver = CapSkip(host="127.0.0.1", port=8080)
session = requests.Session()

# The search results are behind a reCAPTCHA, so solve it first.
token = solver.recaptcha(
    sitekey="YOUR_SITEKEY",
    url="https://example.com/search",
)["code"]

page = session.post(
    "https://example.com/search",
    data={"q": "widgets", "g-recaptcha-response": token},
)

print(page.status_code, len(page.text))

In this example a search form hides behind reCAPTCHA; the local CapSkip app clears it, the scraper posts the answer and keeps collecting results.

Extension for browser-based scraping

Collecting data in a visible Chrome or Firefox window? Install the add-on, leave the CapSkip app running in the background, and challenges on each page clear without a line of code.

SDKs for custom spiders

Writing your own spider in Python or Node.js? The official SDKs, with PHP and .NET versions too, return a pass in one call, inside a Scrapy project or a short standalone script.

Local API for tools you already run

Scraping tools and older code written for 2Captcha or Anti-Captcha can talk to CapSkip as if it were that service, so they run unchanged and stop buying credits.

Watch it solve a real CAPTCHA before you crawl

Before you send a production crawl through CapSkip, try it on our demo pages. Each one carries a real CAPTCHA, so you can watch a challenge get solved on your own machine first.

From install to an unblocked crawl in three steps

  1. Install CapSkip on your scraping box

    Put it on the Windows machine that already hosts your crawlers, or give it a box of its own that every scraper on the network can reach. Get the Windows installer

  2. Pick a plan sized to your crawl

    Choose a tier by how many machines you want solving at once, and your login for the app arrives by email. Prefer to test on your own targets first? Start with the no-card trial. Claim the free trial

  3. Point your spiders at it

    Add the SDK to your crawler, hand a 2Captcha-based tool over to CapSkip in the app, or let the extension work in browser sessions, then rerun a job that used to stall. Browse the SDKs

CapSkip vs per-solve CAPTCHA services for scraping

What changes for a crawl once nothing is counted per solve.

FeatureCapSkipPer-solve APIs
Cost as the crawl growsOne monthly price, however many pages you scrapeClimbs with every page that throws a challenge
Running more workersNo thread cap: scale until the hardware is busyEach extra worker drains the balance faster
Failed pages and retriesRerun them freely at no extra costEach retry costs as much as the first try
Where the solving happensOn your own scraping machine or VPSOn remote servers, one more hop per challenge
Waiting timeAbout 0.1s for image CAPTCHAs, no shared queue for the restA trip over the network plus a place in a shared queue
Who sees your targetsNobody: URLs and pages stay on your hardwareThe service receives the URLs and images you send
Fitting your stackOfficial SDKs, a browser extension and 2Captcha-ready toolsA separate client for each vendor

Pricing

Stop paying per solve

Choose your license

Bronze License

$35/ month

Subscribe to Bronze

Instant license activation

Billed monthly. Cancel from your account whenever you like.

Same features. More machines, more throughput.

Every machine solves as fast as its own CPU and memory allow. More machines run more threads at the same time, so Silver solves twice as many CAPTCHAs at once and Gold three times as many.

  • Unlimited solving, no daily cap
  • Unlimited threads, speed scales with your hardware
  • 90% to 100% recognition accuracy
  • Drop-in replacement for the major solving service APIs
  • Works with almost any tool, no coding required
  • REST API, SDKs and a browser extension
  • Free training when a new CAPTCHA type appears
  • Runs on your machine, nothing leaves it

Every CAPTCHA type CapSkip solves is on every license. See the coverage band

Just want to try it first?

Start with a free 3-day trial and solve 500 CAPTCHAs of any type on your own targets.

Start the free trial

How to bypass CAPTCHAs in web scraping without paying per page

CAPTCHAs rarely break a scraping job loudly. More often a crawler that has run for hours starts receiving challenge pages instead of product listings, saves them as if they were data, and nobody notices until the report comes out half empty. Sites show these checks when traffic looks automated: many requests from one address, a steady rhythm, or a browser that does not behave like a person. The bigger and faster the crawl, the more often it happens.

That is why per-solve pricing and scraping fit badly together. A service that bills by the thousand turns every new category, every extra country and every rerun into a larger invoice. Teams end up throttling crawls to protect the budget, which is the opposite of what a data pipeline needs.

A flat subscription removes that trade-off. CapSkip costs the same whether it clears a hundred challenges this month or a few million, and threads are never rationed by plan, so the machine sets your concurrency rather than the bill. When one machine is no longer enough, Silver and Gold add a second and a third.

It also slots into the scraping stack you already have. Scrapy spiders and custom scripts use the official libraries, browser-driven crawls in Selenium, Playwright or Puppeteer can lean on the extension or a library call, and tools written for 2Captcha-style services switch over inside the app. Proxies still do their part by keeping the challenge rate low; CapSkip handles whatever gets through.

Related guides: Scrapy CAPTCHA middleware · CAPTCHA proxy rotation · HTTP 429 Too Many Requests

Is web scraping with a CAPTCHA solver legal?
It depends on the crawl, not the solver. What you collect, how you use it, the terms of each site and the law where you operate all decide whether a job is allowed. CapSkip is a tool for your own automation and data collection; making sure a particular crawl is permitted stays your responsibility, so check before you scale up.
Which plan fits a large crawl: Bronze, Silver or Gold?
All three solve without limit and cover the same CAPTCHA types; they differ in how many machines can run CapSkip. Bronze ($35 a month) is one device, Silver ($60) two and Gold ($75) three, so Silver doubles the number of challenges in flight and Gold triples it. Start with one box and add more when the crawl outgrows it.
Which CAPTCHAs do scrapers usually hit, and does CapSkip clear them?
Crawls most often meet Google's reCAPTCHA (whether v2, v3 or the Enterprise edition), Cloudflare's Turnstile check and old-style image or text CAPTCHAs, and CapSkip handles all of them. On top of that it covers ALTCHA, the GeeTest v3 slider, CaptchaFox, Friendly Captcha, the Capy puzzle piece, AWS WAF CAPTCHA, DataDome and MTCaptcha. It solves hCaptcha too. The ones it cannot handle are Arkose (FunCaptcha), reCAPTCHA Mobile and the newer GeeTest v4, so leave those targets out or route around them.
Do I still need proxies when CapSkip handles the CAPTCHAs?
Yes, because the two do different jobs. Good proxies and sensible pacing decide how often a site challenges you; CapSkip clears the challenges that still appear. For reCAPTCHA and Turnstile, solve through the same pool your crawler uses so the pass matches the address that submits it. A noisy pool that triggers extra challenges costs nothing more.
Will my existing scraper code work with CapSkip?
Very likely, yes. If your scraper already talks to 2Captcha, Anti-Captcha, CapSolver or one of six other services CapSkip can stand in for, you switch CapSkip to that service and your code stays exactly as it is. Spiders you write from now on can use an official library instead, and crawls driven through a real browser can lean on the extension.
How fast is it when a crawl throws thousands of challenges?
Each image CAPTCHA is done in about 0.1 seconds. Types solved in a browser take longer: reCAPTCHA and Turnstile typically finish within 3 to 10 seconds, GeeTest within 7 to 12. Nothing waits in a shared queue and no plan caps threads, so a stronger CPU and more RAM translate directly into more pages per hour. Browser-heavy crawls run best on a machine with 32 GB of memory or more.
Does anyone else see which sites I scrape?
No. Recognition runs on a computer or server that belongs to you, not on a remote solving farm, so target URLs, page images and results stay on hardware you control. For teams whose edge is the list of sites they watch, that privacy is often worth as much as the flat price.
My scraper never opens a browser. Can it still get through?
Yes. CapSkip does any browser work on its own side and gives back a pass that a lightweight scraper simply submits with the form, and image CAPTCHAs need nothing but the picture. A browser of your own is still handy when a site only builds its content inside the browser after the challenge is passed.

Let your crawl grow without the CAPTCHA bill

Put CapSkip next to your scrapers and stop counting solves. Pages, retries and extra threads all fall under one monthly fee that stays flat however large the job becomes.