chromedp

chromedp is a Go package for automating browsers that support the Chrome DevTools Protocol, without relying on an external driver. It is best suited to developers building browser workflows into Go applications; readers seeking a visual, no-code automation tool should look elsewhere. Its broad range of browser tasks is paired with a free MIT-licensed package, but Go requirements and concurrency caveats make it a focused choice.

Overview

chromedp puts browser control inside Go code rather than offering a standalone automation interface. Its examples cover navigating pages, clicking elements, reading text, running JavaScript, filling and submitting forms, and waiting for elements. That breadth suits application workflows that need to combine browser actions with Go logic, but it leaves people who want to record or configure tasks through a graphical interface out of its target audience.

Chrome runs headlessly by default, and a headless-shell Docker image supports containerized environments. The standard connection uses remote-debugging pipes, so Chrome does not open a debugging port. For a browser already running in a container or hosted service, a separate remote module connects over WebSocket; that option uses a debugging port, so deployment choices affect the security posture.

Key features

The network controls extend chromedp beyond simple page interaction. Examples cover setting cookies and HTTP headers, authenticating to a password-protected proxy, intercepting requests, and saving or restoring login sessions. HAR recording is also supported. These capabilities are useful for workflows that need to reproduce authenticated or network-sensitive browser activity, though they require implementation in Go rather than configuration in a separate interface.

For output, chromedp can capture screenshots, print pages to PDF, and save screencast frames as JPEG files. That makes it relevant to automated capture and document-generation tasks as well as interaction. Parallel work is possible by using separate browser contexts as tabs. Sharing a single context between goroutines can cause races, however, so concurrency requires care in how work is partitioned.

The project cautions that disabling Chrome site isolation can expose a security feature and should be done only for pages you trust. The default pipe connection avoids an open debugging port, but WebSocket connections use one; teams should account for that distinction when choosing a browser connection method.

Pricing

chromedp is free: its plan costs nothing and provides the MIT-licensed Go package. There is no paid tier, seat count, usage quota, or trial to weigh. The trade-off is not a reduced feature set but the need to work within its technical requirements: the package requires Go 1.25 or newer, and browser automation is implemented in code.

Platforms

chromedp is available as an API for Linux, macOS, Windows, and self-hosted environments. It supports one browser engine, not a range of engines. The headless-shell Docker image is a practical fit for headless deployment, while the remote module can connect to an already running browser over WebSocket.

Who it's for

Choose chromedp if you are developing in Go and need browser actions, network controls, or capture output within an application, especially in a headless or self-hosted environment. It is less suitable if your project uses another programming language, needs multiple browser engines, or depends on a graphical workflow builder. Questions and feature ideas go to GitHub Discussions, bugs to the issue tracker, and chat to Discord.

Pros and cons

• Pro: A broad set of browser actions, network controls, session handling, and capture outputs supports varied Go automation workflows.
• Pro: The default pipe connection keeps Chrome’s debugging port closed, and the headless-shell image supports headless environments.
• Con: Go 1.25 or newer is required, limiting its fit for teams working in other languages or on older Go versions.
• Con: Sharing a context between goroutines can cause races, so parallel jobs need separate contexts.
• Con: It supports one browser engine, and WebSocket connections use a debugging port.

Alternatives

For a broader set of browser automation options, browse Browser Automation Tools. The following linked alternatives focus on game memory editing rather than Go-based browser automation, so they are not direct substitutes for chromedp.

• DOSBox Cheat Engine is free and open source for Linux, macOS, Windows, and web, and requires DOSBox Staging 0.83 or newer.
• ReClass.NET is a free, open-source option for Linux and Windows, supplied without warranty.
• scanmem is a free, open-source option for Android and Linux under GPLv3, with libscanmem under LGPLv3.
• CoSMOS is free for Linux and Windows, with no registration, locked features, or adware according to its plan description.
• MemDBG is a free, open-source option for Android, iOS, Linux, macOS, and Windows.
• PINCE is a free, open-source Linux reverse engineering tool under GPLv3+.
• ProMod offers a free iOS and macOS option; its mobile plan supports up to six mods toggled on at a time.
• ArtMoney offers free Windows freeware with some features unavailable in its SE edition, plus a PRO plan priced at $24.90, paid once.

For more options in that category, see Game Memory Editors.

Verdict

For Go developers who need embedded browser automation without adding an external driver, chromedp is a capable free choice, with useful network and capture controls and a secure-by-default pipe connection. Look elsewhere if you need a no-code interface, multiple browser engines, or a workflow that can safely share one context across concurrent goroutines.