Skip to main content
Deploy OpenBrowser with saved authentication using browser profiles.

1. Test Locally with Existing Chrome Profile

Use your existing Chrome profile with saved logins:
Close Chrome completely before running to avoid conflicts.

Chrome Profile Paths by OS

2. Use Persistent Browser Session

For production, use a dedicated user data directory:

3. Remote Browser via CDP

Connect to a remote browser using Chrome DevTools Protocol:

Best Practices

  1. Use environment variables for API keys
  2. Run headless in production (headless=True)
  3. Set allowed_domains to restrict navigation
  4. Use proxy for rate limiting and geo-targeting
  5. Monitor with telemetry for debugging