Skip to main content
Browser is a stateless rendering service. Each request is independent — render a web page to screenshots, structured HTML, or extract data, with no session persistence between calls.
Browser vs Computer: Browser is stateless — each call renders a fresh page with no memory of previous requests. If you need persistent browser sessions (logged-in state, multi-step navigation, cookies preserved across calls), use the Computer capability with its browser subsystem enabled.

Key Features

  • Screenshot Rendering - Capture web page screenshots
  • Structured Data - Extract HTML and page text
  • JavaScript Support - Pages with dynamic content fully rendered
  • Custom Viewport - Control screen resolution
  • Element Interaction - Click, scroll, form fill (advanced)
  • Network Isolation - Secure rendering environment

How to Enable

For Agents

  1. Agents > Select Agent > Settings > Capabilities
  2. Attach Browser

For MCP Gateways

  1. Gateways > Select Gateway > Capabilities
  2. Attach Browser

Usage Examples

Capture Screenshot

Returns:
  • PNG image of rendered page
  • Page title and URL
  • Viewport dimensions

Extract Page Content

Returns:
  • Full page text (markdown formatted)
  • Headings and structure
  • Links and metadata

Capture Dynamic Page

JavaScript executes, page fully renders before capture.

Rendering Options

Screenshot

Captures visual rendering of the page:

HTML Extraction

Gets raw HTML:

Text Extraction

Gets readable text:

Configuration

Optional gateway specifications:

Advanced Features

Wait Conditions

Control when rendering completes:
  • load - DOM loaded
  • domcontentloaded - Initial HTML parsed
  • networkidle - Network quiet (default)

Custom Headers

Set request headers:

Cookies

Include cookies in request:

Common Use Cases

Price Monitoring

  1. Render competitor pages
  2. Extract prices
  3. Compare with your prices

Content Scraping

  1. Get page text
  2. Parse structure
  3. Extract key information

Visual Testing

  1. Render at desktop size
  2. Render at mobile size
  3. Compare visuals

Data Extraction

  1. Get HTML
  2. Parse with Code Runner
  3. Extract data

Resource Limits

Cost

For current pricing details, see Pricing. Monitor in Account > Usage dashboard.

Browser vs Computer Browser

Choose Browser when: You need quick, one-shot page rendering — screenshots, content extraction, or data scraping where each request is self-contained. Choose Computer browser when: You need persistent sessions, login state, multi-page navigation, or complex web application automation.

Limitations

  • Stateless: no session persistence between requests
  • Cannot maintain logged-in state (use Computer for that)
  • Cannot interact with complex multi-step JS applications
  • Some sites may block automated rendering
  • Timeouts on very slow pages

Best Practices

Use Screenshots for Visual Content

Screenshots best for:
  • Product pages
  • Design verification
  • Visual inspection
  • Chart/graph capture

Use Text for Content Extraction

Text/HTML better for:
  • Article content
  • Structured data
  • Link extraction
  • SEO information

Set Appropriate Timeouts

Handle Errors Gracefully

Some pages may fail to render. Implement retry logic.

Troubleshooting

Screenshot is blank

  • Page loading failed
  • Wrong viewport size
  • Page requires authentication
  • Try increasing timeout

Timeout error

  • Page too slow
  • Waiting for external resources
  • Reduce timeout or increase wait condition
  • Simplify the URL

Access denied

  • Site blocking automated access
  • Use different User-Agent header
  • Try at different time

Content missing

  • Content loaded via JavaScript asynchronously
  • Increase timeout
  • Use “load” wait condition instead of “networkidle”

Privacy & Security

  • Rendering is isolated per request
  • No cookies stored between requests
  • Headers/auth not retained
  • Rendered pages not logged
  • Results deleted after delivery

Next Steps