> ## 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.

# Octoparse Cloud

> Understand what Octoparse Cloud Extraction does, when to use it, and how it supports unattended, recurring, and scalable data scraping.

Cloud Extraction runs an Octoparse task on Octoparse-managed cloud resources instead of on your computer. Once a tested task starts in the cloud, you can close the Octoparse app or turn off your computer without stopping the run.

The same cloud features work for tasks you build in [Octoparse Desktop](https://www.octoparse.com/docs/en/desktop/index.md) and for tasks built by [Cloud Agent](https://www.octoparse.com/docs/en/ai-assistant/cloud-agent.md) in AI Assistant: schedules, task splitting, run monitoring, and automatic export. Cloud [templates](https://www.octoparse.com/docs/en/templates/overview.md) run on Octoparse Cloud too. Schedules and automatic export need Standard or above.

## Why use it

* **Your computer stops being the limit.** A cloud run doesn't depend on your computer, your network connection, or an open Octoparse app. Start it and walk away.
* **Fresh data arrives without a manual start.** Put the task on a [schedule](https://www.octoparse.com/docs/en/cloud/cloud-schedules.md), and it runs again at the times you set.
* **Large jobs finish sooner.** Octoparse can split an eligible task into subtasks that run in parallel on several cloud nodes, and run several tasks at the same time. The actual speedup depends on the task structure, available nodes, target website, and your plan.
* **Every run is on record.** Check progress, data, subtask details, logs, and error screenshots for each run, even when nobody was watching it.

## When to use Cloud Extraction

Use Cloud Extraction when:

* A task needs to run after you leave the Octoparse app or turn off your computer.
* The same data needs to be scraped repeatedly.
* Several production tasks need to run using managed cloud resources.
* You need cloud run history and logs for unattended runs.

Use a local run first when you are still building or debugging the task, need to watch browser actions directly, or depend on a local session or network environment. See [Local vs Cloud Extraction](https://www.octoparse.com/docs/en/cloud/local-vs-cloud.md) for help choosing between them.

## How to use Cloud Extraction

**1. Build and test the task**

Run representative samples locally and confirm that the fields, loops, pagination, login, and page loading behave as expected.

**2. Start Cloud Extraction**

Open the task editor or Task List and start the task in the cloud. You can also start selected tasks together or configure a cloud schedule.

**3. Check the result**

Open Cloud Run Details to review progress and extracted data. If a run does not behave as expected, inspect its subtask details, logs, and available screenshots before changing the task or starting it again.

> [!NOTE]
>
> Cloud Extraction runs the workflow as configured; it does not automatically correct an inaccurate selector, an expired login, or a website that behaves differently in the cloud environment. Validate the task before relying on unattended or recurring runs.

For more information about managing your subscription, see [Billing and plans](https://www.octoparse.com/docs/en/billing.md).

## Which plans include Cloud Extraction

Running the tasks you build yourself on Octoparse Cloud starts on Standard. Each plan includes a different number of **cloud nodes**, which determine how much cloud execution capacity is available to the account.

| Plan | Cloud Extraction for your own tasks | Cloud nodes |
| - | - | - |
| Free | Not included; tasks run on your computer | None |
| Basic | Not included; tasks run on your computer | None |
| Standard | Included | 3 or 6 cloud nodes, depending on the option you choose |
| Professional | Included | 20 cloud nodes |
| Enterprise | Included | 40 or more, set for your account |

Templates and [Cloud Agent](https://www.octoparse.com/docs/en/ai-assistant/cloud-agent.md) scrapers can run on Octoparse Cloud on every plan. On Free and Basic, those runs are started by hand and count toward monthly rows. See [AI Assistant credits and plans](https://www.octoparse.com/docs/en/ai-assistant/credits-and-plans.md).

Cloud nodes can be used to run different tasks concurrently or to process a splittable task in parallel. The number of nodes therefore does not always equal the number of complete tasks that can run at once. When all available nodes are in use, additional cloud work waits until capacity becomes available.

## Learn more

> [card]
>
> **Cloud resources and queues**
>
> Understand nodes, subtasks, concurrency, and queued runs.
>
> [Open](https://www.octoparse.com/docs/en/cloud/cloud-resources-and-queues.md)

> [card]
>
> **Local vs Cloud Extraction**
>
> Choose the right execution environment for a task.
>
> [Open](https://www.octoparse.com/docs/en/cloud/local-vs-cloud.md)

> [card]
>
> **Standard vs boost mode**
>
> Learn how execution modes relate to task splitting and concurrency.
>
> [Open](https://www.octoparse.com/docs/en/cloud/standard-vs-boost.md)

> [card]
>
> **Schedule task runs**
>
> Configure recurring task runs.
>
> [Open](https://www.octoparse.com/docs/en/cloud/cloud-schedules.md)

> [card]
>
> **Logs & event tracking**
>
> Diagnose incomplete or stopped runs.
>
> [Open](https://www.octoparse.com/docs/en/cloud/logs-and-events.md)

For current interface details, see [What is Cloud Extraction?](https://helpcenter.octoparse.com/en/articles/6470910-what-is-cloud-extraction) in the Octoparse Help Center.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.