> ## Documentation Index
> Fetch the complete documentation index at: https://www.octoparse.com/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Cloudflare verification

> Learn what Cloudflare Turnstile is, when Octoparse can handle it automatically, and how to confirm that the page and data load correctly.

Cloudflare Turnstile is a verification prompt that a website may show before allowing access. If a task cannot move past that prompt, it cannot reach the page state where Octoparse extracts data.

Octoparse 8.7.2 and later provides an automatic option for supported Turnstile verification, labelled **Bypass Cloudflare with credit** where available. You can enable or disable it in the applicable editor setting. The automatic option can be used during task editing, Local runs, and Cloud runs.

## What automatic Cloudflare verification does

When the option is enabled, Octoparse checks for a supported Turnstile prompt after a **Go to Web Page** action loads. If it finds one, it obtains the information required for that prompt, requests a verification result, supplies the result to the page, and waits for the page to continue loading.

This can help a task reach the page it needs for extraction. It does not change the task workflow, selected data fields, IP or region, User-Agent, Cookies, or login state. It also does not guarantee that the website will accept the result or return complete data.

For the same Turnstile prompt, Octoparse makes up to **three** automatic handling attempts. This limit is separate from the ordinary retry setting for a **Go to Web Page** action. After the third attempt, Octoparse does not make another automatic Cloudflare attempt for that prompt; check the final page and choose a different supported path if needed.

## What it means for access and data collection

| If you see                                             | What automatic verification can do                                                          | What you still need to check                                                            |
| ------------------------------------------------------ | ------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------- |
| A supported Turnstile prompt during **Go to Web Page** | Try to complete that verification so the task can continue to the target page               | The final page is no longer a verification page and contains the expected content       |
| A page that loads but returns empty or incomplete data | Nothing by itself; the cause may be a wait, workflow, login, browser, IP, or region setting | Screenshot, final URL, and several extracted rows                                       |
| A login page or expired session                        | Nothing by itself; Turnstile verification does not restore a session                        | Sign in and Cookie state; see [Auto-login and cookies](/docs/en/platform/auto-login-cookies) |
| A location- or IP-specific result                      | Nothing by itself; Turnstile verification does not select the network route                 | IP or region selection; see [Proxies and IP rotation](/docs/en/platform/proxy)               |

Because Octoparse checks the page for Turnstile after navigation, enabling the option can add time to a **Go to Web Page** action. Use it when a supported Turnstile prompt is the actual reason the task cannot reach the target page, not as a default setting for every task.

## Test the result

1. Reproduce the issue with a small test and keep the page screenshot.
2. Confirm that the page is showing a supported Turnstile prompt rather than a login page, Cookie banner, or another access error.
3. Enable the automatic option, then run the same small test.
4. Check the final page, relevant resource event, and several output rows.
5. Keep the option only when the page and data are correct in repeated small tests.

A Cloudflare-related resource event shows that an automatic attempt occurred. It is not proof that the website accepted the result. The final page and extracted data are the proof that matters.

## Manual fallback

In the task editor, use Browse Mode for an applicable manual verification. For a Local-run workflow, use the supported pause, show-browser, handle, and resume sequence. Cloud runs do not provide a manual browser handoff; validate the supported automatic result through their run evidence.

## Cloudflare pricing

Automatic Cloudflare verification costs **\$1.50 per 1,000 attempts**. Charges use your account's available credits; there is no separate Cloudflare credit balance. Each automatic attempt is charged at this rate, whether the website accepts the result or not.

Enabling the option does not itself use a credit. An attempt occurs when Octoparse finds a supported Turnstile prompt during **Go to Web Page** and starts automatic handling. Check your available account credits before a larger run, and review the resource events with the final page and output after a small test.

Cloudflare verification is priced separately from [automatic CAPTCHA solving](/docs/en/platform/captcha-handling): automatic CAPTCHA solving costs \$1 per 1,000 attempts.