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

# Cloud extraction

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

Its essential role is to separate data scraping from your local device. This makes it practical to run tasks unattended, scrape data on a recurring schedule, and use cloud resources to process larger workloads or shorten the completion time of splittable tasks.

## What Cloud Extraction gives you

<Columns cols={2}>
  <Card>
    **Run without your computer**

    A cloud run continues without depending on your computer, local network connection, or an open Octoparse app.
  </Card>

  <Card>
    **Scrape data on a schedule**

    Start recurring runs at configured times so updated data can be scraped without a manual start each time.
  </Card>

  <Card>
    **Scale and accelerate eligible tasks**

    Octoparse can run multiple tasks using account-level cloud capacity. It can also divide a splittable task into parallel subtasks across available nodes, reducing the time needed to process the workload compared with one sequential execution path.
  </Card>

  <Card>
    **Review runs in one place**

    Check run progress, cloud data, subtask details, logs, and available error screenshots from the task's cloud run views.
  </Card>
</Columns>

Together, these capabilities turn a task you have already built into a repeatable data scraping process: test the workflow, run it in the cloud, monitor the result, and export the data you need. Parallel execution can shorten a splittable task's completion time, while account-level cloud capacity can support several tasks at the same time. The actual acceleration and capacity depend on the task structure, available nodes, target website, and your plan.

## 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](/docs/en/platform/local-vs-cloud) for help choosing between them.

## How to use Cloud Extraction

<Steps>
  <Step title="Build and test the task">
    Run representative samples locally and confirm that the fields, loops, pagination, login, and page loading behave as expected.
  </Step>

  <Step title="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.
  </Step>

  <Step title="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.
  </Step>
</Steps>

<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.
</Note>

For more information about managing your subscription, see [Billing and plans](/docs/en/platform/billing).

## Which plans include Cloud Extraction

Cloud Extraction is available on paid plans. Each plan includes a different number of **cloud nodes**, which determine how much cloud execution capacity is available to the account.

| Plan         | Cloud Extraction                | Cloud nodes          |
| ------------ | ------------------------------- | -------------------- |
| Free         | Not included; tasks run locally | None                 |
| Standard     | Included                        | Up to 6 cloud nodes  |
| Professional | Included                        | Up to 20 cloud nodes |
| Enterprise   | Included                        | Custom capacity      |

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

<Columns cols={2}>
  <Card href="/docs/en/platform/cloud-resources-and-queues">
    **Cloud resources and queues**

    Understand nodes, subtasks, concurrency, and queued runs.
  </Card>

  <Card href="/docs/en/platform/local-vs-cloud">
    **Local vs cloud extraction**

    Choose the right execution environment for a task.
  </Card>

  <Card href="/docs/en/platform/standard-vs-boost">
    **Standard vs boost mode**

    Learn how execution modes relate to task splitting and concurrency.
  </Card>

  <Card href="/docs/en/platform/schedules">
    **Schedules**

    Configure recurring task runs.
  </Card>

  <Card href="/docs/en/platform/logs-and-events">
    **Logs & event tracking**

    Diagnose incomplete or stopped runs.
  </Card>
</Columns>

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.