Skip to main content
Using the Zenrows Browser (formerly, Scraping Browser) saves you from the hassle of managing proxies, rotating IPs, and dealing with browser automation setup. With just one line of code, you get access to a fully managed browser with residential proxies.
At the moment, the Zenrows Browser cannot solve CAPTCHAs. You will need to handle CAPTCHA solving through third-party services if required.
You can also try our Fetch, which comes with everything available on the Zenrows Browser, plus antibot capabilities, anti-CAPTCHAs and many more.
The Zenrows Browser uses the Chrome DevTools Protocol (CDP) as its communication standard. CDP is a powerful protocol used for browser automation and debugging, allowing you to control a browser instance programmatically.

​
Why CDP?

CDP is widely adopted because it provides deep control over browser behavior, offering features like:
  • Page interaction: Automate navigation, clicks, form submissions, etc.
  • Network monitoring: Access detailed network activity, including headers, responses, and requests.
  • DOM manipulation: Direct interaction with and modification of the Document Object Model (DOM).
  • JavaScript execution: Run JavaScript code within the page context.
  • Performance tracking: Monitor performance metrics, including rendering and page load speeds.
  • Screenshots & PDFs: Capture visual representations of the page.
By leveraging CDP, the Zenrows Browser allows you to interact with web pages just like a human user would, while also benefiting from additional features like IP rotation and proxy management.

​
How is CDP different from other protocols?

Compared to other protocols like WebDriver (used by Selenium), CDP is generally faster and more capable because it communicates directly with the browser’s core without the intermediary of a WebDriver layer. This direct interaction gives CDP greater flexibility and control, making it the protocol of choice for the Zenrows Browser.
No, the Zenrows Browser does not allow programmatically changing the viewport or window size. Methods like page.setViewportSize() or similar browser commands are blocked and will not take effect. The browser window and viewport are managed automatically to optimize for anti-bot protection and reliability.If you need to take screenshots at different sizes, this is currently not supported by resizing the window or viewport. The browser will always use a real, consistent window size that matches the fingerprint.For reference, Zenrows also restricts other browser-modifying actions, such as changing the user agent or certain device metrics. If you have specific requirements or questions about supported features, please contact our support team.