
A faster, simpler way to drive browsers supporting the Chrome DevTools Protocol in Go.
Visit WebsitePros
Cons
Ratings aggregated from independent review platforms. Learn more
Free
No reviews yet. Be the first to review Chromedp!
Top alternatives based on features, pricing, and user needs.

Automate browser testing for websites and web applications without coding.

Professional-grade UI test automation for desktop, web, and mobile applications.
AI-powered autonomous testing for software development teams.

Browser automation framework
The simplest method is to run the Go program using chromedp inside the `chromedp/headless-shell` Docker image. This image includes a smaller, headless build of Chrome that chromedp can automatically detect and utilize.
By default, Chrome runs in headless mode when driven by chromedp. To override this, users can refer to `DefaultExecAllocatorOptions` and an example demonstrating how to modify these default settings.
On Linux, chromedp is configured to automatically force-kill any started Chrome child processes when the Go program concludes. If a long-running Chrome instance is required, it should be launched manually and connected using `RemoteAllocator`.
This error occurs when the connection to the browser is lost, leading chromedp to cancel the associated context. Common scenarios include manually closing the browser, or the browser process being terminated or killed.
To use an `Action` that returns multiple values with `chromedp.Run`, it must be wrapped with an `ActionFunc`. This allows the action to be executed within the `chromedp.Run` context while handling its return values.
Source: github.com