Skip to main content
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

​
Selection mode vs Browse Mode

Octoparse uses different interaction modes when building a task. 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

For a Local run, start with the Built-in Browser as a baseline. Choose Chrome for Testing when you need a clean, separate browser environment, or Local Browser when the task needs your selected Chrome or Edge profile. These choices change the browser environment, not the workflow or data fields. Local Browser can make page behavior closer to normal browsing and may improve compatibility with some sites, but no browser choice guarantees access or prevents every block. For the complete choice guide, including manual login and verification during a Local run, see User-Agent and browser modes.

​
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 selection 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 when a task behaves differently during a run.
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.