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

# Scraping browsers

> Choose the Octoparse browser mode that fits a task, then validate page access and extracted data in the applicable run environment.

Octoparse uses browser-based environments to open websites, interact with page elements, and build extraction workflows. Browser choice changes how a page is rendered and what manual controls are available; it does not guarantee that a site will permit automated access.

## Built-in browser

The built-in browser is where you build and test tasks. It lets you open the target website, select elements, create actions, and preview extracted data.

You can use it to:

* Open target URLs
* Select text, links, images, and other elements
* Click buttons or menu items
* Handle pagination or infinite scroll
* Log in when a task requires session setup
* Test how a page loads during extraction

## Select Mode vs Browse Mode

Octoparse uses different interaction modes when building a task.

| Mode | Use it for |
| - | - |
| Select Mode | Select page elements and create extraction actions |
| Browse Mode | Interact with the page like a normal browser |
| Workflow testing | Watch the task execute actions and collect sample data |

Use Browse Mode when you need to manually interact with the page before continuing task setup, such as logging in, closing a popup, opening a menu, or reaching the page state you want to scrape.

## Local-run browser choices

To choose which browser runs a Local run, or to sign in or pass a verification by hand during one, see [User-Agent and browser modes](https://www.octoparse.com/docs/en/desktop/user-agent-and-browser-modes.md).

## Dynamic pages

Many websites load data after the initial page load. The built-in browser helps you configure actions for these cases.

Common dynamic behaviors include:

* Infinite scroll
* “Load more” buttons
* Dropdown filters
* Tabs
* Popups
* JavaScript-rendered content
* Login walls
* Detail pages opened after clicking a list item

For these pages, the task may need waits, scroll actions, clicks, or pagination steps.

## Best practices

* Wait until the page is fully loaded before selecting fields.
* Use Browse Mode for manual navigation, then switch back to Select Mode.
* Add wait steps when content loads slowly.
* Test a small sample before running the full task.
* Recheck field selection if a website changes its layout.
* Use [logs](https://www.octoparse.com/docs/en/cloud/logs-and-events.md) when a task behaves differently during a run.

> [!NOTE]
>
> A browser-based task depends on the target website's structure and behavior. After changing a browser mode, validate the final page, screenshot, and sample fields before you schedule or scale the task.


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