chromedp
github.com
- Free plan
- Windows
- macOS
- Linux
- API
- Self-hosted
What chromedp is
chromedp is a free, open-source Go package for controlling browsers that support the Chrome DevTools Protocol, without an external driver. Its examples cover navigating pages, clicking elements, reading text, running JavaScript, filling and submitting forms, and waiting for elements. They also show setting cookies and HTTP headers, authenticating with a password-protected proxy, intercepting requests, and saving or restoring login sessions.
For output, chromedp can capture screenshots, print pages to PDF and save screencast frames as JPEG files. Separate browser contexts can act as tabs for parallel work, but sharing one context across goroutines can cause races. By default it starts Chrome with remote-debugging pipes, so Chrome does not open a debugging port. A separate remote module connects to an already running browser over WebSocket, including one in a container or hosted service. The project also offers a headless-shell Docker image. The README requires Go 1.27 or newer and warns that disabling Chrome site isolation can expose a security feature; it advises doing that only for trusted pages.
Who it suits
chromedp suits Go developers building browser automation for Chrome DevTools Protocol-compatible browsers. It may also fit teams running browser tasks in headless or remote environments.
Good to know, and what to watch
- Controls browsers without an external driver.
- Supports screenshots and PDF output.
- Remote module connects over WebSocket.
- Default pipe connection opens no debugging port.
- MIT-licensed and free.
- Requires Go 1.27 or newer.
- Sharing a context across goroutines can cause races.
- Disabling site isolation can expose a security feature.
Plans
Every plan and pricechromedp
Open source
The Club's review
chromedp is a Go package for controlling Chrome DevTools Protocol-compatible browsers from application code. It suits developers building browser tasks into Go projects; teams seeking a visual automation tool should look elsewhere. Its range of browser actions and remote options is useful, but the Go requirement and concurrency warning narrow its fit.
Overview
Instead of providing a standalone interface for configuring automation, chromedp lets Go programs drive browser workflows directly. Examples cover navigation, clicks, reading page text, running JavaScript, filling and submitting forms, uploading files, and waiting for elements. That makes it a practical option when browser steps need to sit alongside application logic, but a poor fit for users who want to build workflows without writing code.
Chrome runs headlessly by default, and the project provides a headless-shell Docker image for headless environments. By default, chromedp communicates over remote-debugging pipes, which keeps Chrome from opening a debugging port. A separate remote module can connect to an already running browser, including one in a container or hosted service, over WebSocket; that approach uses a debugging port and should be weighed against deployment security needs.
Key features
Network controls make chromedp more capable than a basic sequence of page interactions. Its examples include setting cookies and HTTP headers, using a password-protected proxy, intercepting requests, and saving or restoring login sessions. HAR recording is also covered. These features suit scripted workflows that need to manage authenticated or network-sensitive browsing, although they remain capabilities to use through Go code rather than a graphical control panel.
For output, chromedp can capture screenshots, print pages to PDF, and save browser screencast frames as JPEG files. Those options make it useful for capture and document-generation tasks as well as page interaction. Browser contexts can be separated into tabs for parallel work, but the README warns that sharing one context across goroutines can cause races. Developers need to keep context ownership clear; treating a context as freely shareable can make concurrent workflows unreliable.
There is also a security trade-off around site isolation: the README warns that disabling Chrome site isolation can expose a security feature and advises doing so only for pages you trust. That is a meaningful constraint for workflows involving untrusted content.
Pricing
chromedp is free: its sole plan costs nothing and is an MIT-licensed Go package. There is no paid tier or free trial to evaluate. The trade-off is that the package is intended for developers and requires Go 1.25 or newer; it does not offer a lower-cost, lower-capability plan for people who want browser automation without that technical setup.
The project is open source and self-hosted. Users can run it with their own browser environment, including the supplied headless-shell Docker image, rather than choosing among hosted service tiers. That suits teams that want control over execution, but means it is not a turnkey hosted automation service.
Platforms
chromedp is listed for API use, Linux, macOS, Windows, and self-hosted deployments. Its scope is one browser engine: browsers that support the Chrome DevTools Protocol. This is a sensible cross-platform choice for Go projects targeting that protocol, not a multi-engine option for teams that need browser-engine diversity.
Who it's for
Choose chromedp if you write Go and need browser navigation, form handling, network controls, screenshots, PDFs, or remote-browser connections as part of an application or automation workflow. It is especially suitable when headless execution or self-hosting matters and the team can manage browser contexts carefully.
Look elsewhere if you need a no-code interface, support for multiple browser engines, or a workflow that can freely share browser contexts across goroutines. The Go version requirement also makes it unsuitable for projects that cannot use Go 1.25 or newer.
Pros and cons
- Broad browser task coverage: navigation, JavaScript, forms, request interception, session restoration, screenshots, and PDFs support workflows beyond simple page loading.
- Flexible execution: headless operation, a Docker image, and a remote WebSocket module cover local, container, and already-running browser setups.
- Safer default connection: remote-debugging pipes avoid opening a Chrome debugging port by default.
- Go-specific and version-bound: the package requires Go 1.25 or newer, limiting its usefulness outside suitable Go projects.
- Concurrency needs care: sharing a context between goroutines can cause races, so parallel work requires deliberate context separation.
- One engine: support is limited to browsers implementing the Chrome DevTools Protocol.
Alternatives
For a broader comparison of browser automation software, start with Browser Automation Tools. The other linked options below are memory editors or reverse-engineering tools rather than direct browser-automation substitutes.
- CoSMOS is a free Linux and Windows option, with no registration required and no features locked.
- ProMod has a free iOS plan and a macOS option distributed and supported through Patreon.
- Bit Slicer is free, open source, and for macOS.
- DOSBox Cheat Engine is a free, open-source choice for Linux, macOS, web, and Windows that requires DOSBox Staging 0.83 or newer.
- ReClass.NET is free and open source for Linux and Windows, supplied without warranty.
- scanmem is free and open source for Android and Linux.
- memwatch is MIT-licensed macOS software that users build and install from source.
- PINCE is a free, open-source Linux reverse-engineering tool.
For game-memory editing specifically, see Game Memory Editors.
Verdict
chromedp is a strong fit for Go developers who want browser control, network handling, and capture tasks inside self-hosted or headless workflows. Its free MIT-licensed package and remote-browser support are compelling reasons to choose it. Look elsewhere if you need a visual tool, multiple browser engines, or concurrency without careful context management.
The verdict
chromedp provides a broad set of browser-control and output tasks for Go projects, with remote and headless options. Developers should account for its Go requirement and avoid sharing a context across goroutines.
What the maker publishes
- Automation
- It supports browser actions such as navigation, reading page content, running JavaScript, clicking elements, filling forms, and uploading files. source
- Browser actions
- Its examples cover navigation, clicking, reading page text, running JavaScript, filling and submitting forms, and waiting for elements. source
- Browser connection
- By default it starts Chrome and communicates over pipes; a separate remote module supports connecting to an already-running browser over WebSocket. source
- Compatibility
- The current module requires Go 1.25 or newer. source
- Concurrency
- A browser can use separate contexts as tabs for parallel work, but the README warns that sharing one context between goroutines can cause races. source
- Concurrency
- Multiple contexts sharing one browser can run in parallel in separate tabs, but a single context should not be shared between goroutines. source
- Headless mode
- It runs Chrome headlessly by default, and can use the chromedp/headless-shell container image in headless environments. source
- Integration
- The project provides a headless-shell Docker image for running chromedp in a headless environment. source
- License
- The repository lists an MIT license. source
- License
- The repository identifies its license as MIT. source
- Network
- Its examples cover setting cookies and HTTP headers, proxy authentication, request interception, session restoration, and HAR recording. source
- Network features
- Examples show setting cookies and HTTP headers, using a password-protected proxy, intercepting requests, and saving or restoring login sessions. source
- Output
- chromedp can capture screenshots, print pages to PDF, and save browser screencast frames as JPEG files. source
- Output
- It can capture screenshots, print pages to PDF, emulate devices, and save screencast frames. source
- Purpose
- chromedp is a Go package for driving browsers that support the Chrome DevTools Protocol, without an external driver. source
- Remote browsers
- The separate remote module can connect to an already running browser, including one in a container or hosted service, over a WebSocket. source
- Requirements
- The README says the module requires Go 1.27 or newer. source
- Security
- By default, chromedp starts Chrome with remote-debugging pipes, so Chrome opens no debugging port. source
- Security detail
- The default pipe connection does not open a Chrome debugging port; switching to WebSocket uses a debugging port. source
- Security limitation
- The README says disabling Chrome site isolation can expose a security feature and advises doing so only for pages you trust. source
- Security limitation
- The README says disabling Chrome site isolation can enable access to some cross-site iframe content, and advises doing so only for trusted pages because it turns off a Chrome security feature. source
- Support
- The README directs users to GitHub Discussions for questions and feature ideas, the issue tracker for bugs, and Discord for chat. source
- Support
- The project directs questions and feature suggestions to GitHub Discussions and Discord, and reserves the issue tracker for bugs. source
- What it does
- chromedp is a Go package for driving browsers that support the Chrome DevTools Protocol, without an external driver. source
Checked against the maker's pages on 9 Oct 2026.