> ## Documentation Index
> Fetch the complete documentation index at: https://docs.browseract.com/llms.txt
> Use this file to discover all available pages before exploring further.

# How to Use BrowserAct Proxies

> Choose Static Proxy or Dynamic Proxy for BrowserAct browsers and workflows.

## Introduction

BrowserAct offers two proxy modes:

<Columns cols={2}>
  <Card title="Static Proxy" icon="shield-check">
    Keeps the same IP across sessions.
  </Card>

  <Card title="Dynamic Proxy" icon="refresh-cw">
    Rotates IPs between sessions.
  </Card>
</Columns>

In BrowserAct, the proxy mode is usually paired with a browser environment:

<Columns cols={2}>
  <Card title="Static Proxy + Standard Browser" icon="monitor-check">
    Use Static Proxy when you need a stable identity.
  </Card>

  <Card title="Dynamic Proxy + Private Browser" icon="shield">
    Use Dynamic Proxy when you need a rotating identity.
  </Card>
</Columns>

## Detail

### 1. Choose the right proxy mode

| Mode          | Browser environment | Best for                                                                                                    |
| ------------- | ------------------- | ----------------------------------------------------------------------------------------------------------- |
| Static Proxy  | Standard Browser    | Account management, long-lived logins, social media operations, e-commerce allowlisting, fixed-IP workflows |
| Dynamic Proxy | Private Browser     | Web scraping, price monitoring, anti-tracking, ad verification, rotating-IP workflows                       |

### 2. Use Static Proxy with CLI and Standard Browser

Use Static Proxy when you want to bind one proxy to one Browser or extraction task.

#### Create a browser with Static Proxy

```bash theme={null}
browser-act browser create --type stealth --name "<browser-name>" --desc "<browser-description>" --static-proxy <static-proxy-id>
```

#### Create a private-mode browser with Static Proxy

```bash theme={null}
browser-act browser create --type stealth --name "<browser-name>" --desc "<browser-description>" --mode private --static-proxy <static-proxy-id>
```

#### Update an existing browser with Static Proxy

```bash theme={null}
browser-act browser update <browser-id> --static-proxy <static-proxy-id>
```

#### Remove browser proxy

```bash theme={null}
browser-act browser update <browser-id> --no-proxy
```

#### Use Static Proxy during extraction

```bash theme={null}
browser-act stealth-extract "<url>" --static-proxy <static-proxy-id>
```

#### Extract and save the result

```bash theme={null}
browser-act stealth-extract "<url>" --static-proxy <static-proxy-id> --output <output-file>
```

#### Recommended flow

1. Buy a Static Proxy and copy its `static-proxy-id`.
2. Bind the proxy when you create or update a Browser.
3. Launch the Browser in **Standard Browser** mode.
4. Keep the same proxy bound to the same account or workflow whenever possible.

### 3. Use Dynamic Proxy with Private Browser

Dynamic Proxy is configured at the browser setting level.

#### For a Browser session

1. Open **BrowserAct Proxy Settings**.
2. Switch the browser mode to **Dynamic Proxy**.
3. Choose the region you want to use.
4. Save the setting and launch the browser in **Private Browser** mode.

#### For a workflow

1. Open **Workflow Browser Settings**.
2. Select **Dynamic Proxy**.
3. Choose the region.
4. Save the setting.
5. All browser tasks in that workflow will use the selected Dynamic Proxy configuration.

### 4. Use Static Proxy in Workflow

1. Open **Workflow Browser Settings**.
2. Select **Static Proxy** as the browser proxy type.
3. Choose a proxy from the **Select Static Proxy** list.
4. Save the setting.
5. All browser tasks in that workflow will use the selected Static Proxy automatically.

### 5. Business scenarios

The easiest way to choose a proxy is to match the proxy mode with the browser environment and the task goal.

#### Static Proxy + Standard Browser

Use this combination when stability matters more than rotation.

Typical scenarios:

* Account management
* Social media operations
* E-commerce operations
* Long-lived login sessions
* API allowlisting with a fixed IP

Why this combination works:

* Static Proxy keeps the IP stable across sessions.
* Standard Browser gives the task a consistent browser environment.

#### Dynamic Proxy + Private Browser

Use this combination when rotation and session isolation matter more than stability.

Typical scenarios:

* Web scraping
* Price monitoring
* Anti-tracking tasks
* Ad verification
* Other tasks that do not depend on a fixed IP

Why this combination works:

* Dynamic Proxy gives you a rotating IP.
* Private Browser keeps the browsing session isolated.

#### Quick decision guide

<Columns cols={3}>
  <Card title="Stable IP" icon="fingerprint">
    Need a stable IP for one account or workflow? Use **Static Proxy + Standard Browser**.
  </Card>

  <Card title="Rotating IP" icon="refresh-cw">
    Need a rotating IP for extraction or monitoring? Use **Dynamic Proxy + Private Browser**.
  </Card>

  <Card title="Shared workflow IP" icon="workflow">
    Need all tasks in one workflow to share the same IP? Bind a Static Proxy at the workflow level.
  </Card>
</Columns>

### 6. Tips

* Use Static Proxy for account-sensitive tasks.
* Use Dynamic Proxy for high-volume or scraping-heavy tasks.
* Avoid switching proxy mode too often for the same account unless you have a clear reason.
* If the proxy you need is not listed, contact support on [Discord](https://discord.com/invite/UpnCKd7GaU).