Local vs cloud extraction

Compare local extraction and cloud extraction in Octoparse, and learn when to use each run mode.

Octoparse tasks can run locally on your computer or in the cloud. Both modes use the task workflow you build, but they differ in where the task runs, how long it can continue, and how suitable it is for scheduled or unattended extraction.

Use local extraction for testing and debugging. Use cloud extraction when you need tasks to run without keeping your computer on.

Comparison

Area	Local extraction	Cloud extraction
Where it runs	On your own computer	On Octoparse cloud servers
Best for	Testing, debugging, small runs, environment-specific tasks	Scheduled, unattended, recurring, or larger runs
Computer required	Yes, the task depends on your device	No, the task can continue after your computer is off
Browser/session dependency	Uses your local environment	Uses cloud execution environment
Scheduling	Limited by your local device availability	Better suited for scheduled runs
Troubleshooting	Easier to watch and debug directly	Requires checking logs and cloud run history

When to use local extraction

Use local extraction when you want to:

• Test a new task before running it at scale
• Watch how the workflow behaves step by step
• Debug element selection, pagination, login, or page loading issues
• Use a local browsing session or local network condition
• Run a small one-off extraction

Local extraction is usually the safest first step when building or editing a task.

When to use cloud extraction

Use cloud extraction when you want to:

• Run tasks without keeping your computer on
• Schedule recurring collections
• Collect larger datasets
• Run tasks unattended
• Reduce dependence on your local device
• Send data to downstream exports automatically

Cloud extraction is better for production workflows after the task has been tested.

Typical workflow

1. Build the task locally

   Create the workflow, select fields, configure actions, and refine data.

2. Run a local test

   Check that the task extracts the right records and handles pagination or detail pages correctly.

3. Switch to cloud extraction

   Use cloud extraction when the task is stable and needs to run on a schedule or at larger scale.

4. Monitor cloud results

   Check run status, logs, and exported data after the task runs.

Things to check before cloud runs

Before moving a task to the cloud, confirm:

• The task does not rely on a local-only session
• Login and cookies are configured correctly if required
• Pagination and scrolling work in a sample run
• The website can load correctly in the cloud environment
• Export settings are configured
• The task supports the run mode you want to use

A task that works locally may still need adjustment before running reliably in the cloud, especially if the target website uses login sessions, location-sensitive content, anti-bot checks, or dynamic loading.

Related pages

Standard vs boost mode

Compare cloud run modes for speed and concurrency.

Logs & event tracking

Learn how to check task status and troubleshoot failed runs.