WebDriver BiDi is the W3C’s evolving protocol for browser automation that adds two-way, event-driven communication to WebDriver. Classic WebDriver primarily exchanges HTTP commands and responses; BiDi uses a WebSocket connection so an automation client can subscribe to browser events as well as send commands. It is a promising route toward more interoperable browser observation and control—not a guarantee that every browser, driver, or framework supports every capability today.
What WebDriver BiDi is
The W3C defines the BiDirectional WebDriver Protocol as a mechanism for remote control of user agents. An automation client connects to a browser, sends commands, and can receive browser events over a bidirectional WebSocket connection. The protocol is intended to complement the familiar WebDriver model while adding an event stream. W3C WebDriver BiDi specification · MDN WebDriver BiDi reference
In practice, event-driven communication means a client can subscribe to an event and be notified when it occurs, rather than repeatedly asking whether something has happened. The value is not that every test becomes faster; it is that clients can observe browser activity through a shared protocol model where the relevant implementation supports it.
How BiDi differs from classic WebDriver and CDP
| Approach | Communication model | Standardization and portability | Practical consideration |
|---|---|---|---|
| Classic WebDriver | Primarily HTTP command-and-response interactions. | Established W3C WebDriver automation model. | Works well for command-oriented automation; observing asynchronous browser activity may involve polling or other tooling. |
| WebDriver BiDi | WebSocket-based, bidirectional communication for commands and browser events. | W3C-defined protocol intended to support interoperable browser automation; the BiDi specification remains a Working Draft as of 30 September 2026. | Exact command and event availability varies by browser, driver, framework, and version. |
| Chrome DevTools Protocol (CDP) | Browser debugging protocol with browser-specific capabilities. | Not the same cross-browser W3C protocol effort as BiDi. | Can remain useful when automation depends on Chrome-specific functionality; a framework may use CDP by default even where BiDi is available. |
BiDi is not simply a newer name for CDP, nor does its existence mean CDP is obsolete. A shared protocol can improve portability when implementations expose the same needed features, but browser-specific debugging capabilities may still make CDP the better fit for a particular task.
The Tool Desk
Outbyte Driver Updater FREEFix the driver behind crashes, sound loss and screen glitchesFind Drivers →Outbyte PC Repair FREEClear out junk files and repair common Windows errorsFree Scan →#1 Best Overall
- Read Before You Buy — No Video Output: These adapters support charging and USB 2.0 data transfer, but cannot transmit video signals. Except for standard USB webcams (which use USB data only), they are not compatible with HDMI/DisplayPort cables, video-capable USB-C hubs, or docking stations with video output.
- Convert USB-A Ports to USB-C: Designed to connect USB-C earphones, cables, flash drives, card readers, and other USB-C accessories to standard USB-A ports. Plug-and-play with no drivers or software required.
- Aluminum Alloy Housing: Built with a sturdy aluminum alloy shell that aids in heat dissipation and protects against daily wear and scratches. Designed to maintain a stable and secure connection.
- Compact & Travel-Friendly: The ultra-compact design allows the adapter to stay plugged into your device without blocking adjacent ports or adding bulk, reducing wear and tear on your original USB ports.
- 12-Month Warranty: Backed by a 12-month manufacturer warranty for peace of mind. Designed to meet strict quality control standards for reliable everyday performance.
What BiDi is designed to let automation clients do
The protocol and its design examples cover more than page navigation. MDN’s reference describes areas including browser and session management, script execution, network monitoring, DOM interaction, browser API emulation, and browser events. The W3C explainer gives examples of how event and command support could be used:
- Listen for DOM and browsing-context events.
- Collect console messages and JavaScript errors, or fail a test when an error occurs.
- Intercept requests, mock backend responses, or record network traffic.
- Run bootstrap scripts and gather performance timings.
- Capture full-page screenshots in a supported implementation.
These are design goals and examples, not a blanket compatibility promise. A protocol module or command may be implemented in one browser and absent or incomplete in another, and client libraries may expose only some of the underlying protocol. Check the exact feature path your tests need before committing to it. W3C WebDriver BiDi explainer
Rank #2
- 5-in-1 USB-C Hub: Experience comprehensive connectivity featuring a Power Delivery input, two USB-A 2.0 ports, a USB-A 3.0 port, and an HDMI port. (Note: The USB-C power delivery input port is only for connecting an external wall charger to power your laptop and cannot power peripheral devices.)
- 90W Pass-Through Charging: Achieve optimal charging with 90W pass-through power to your laptop, supported by a total input of 100W, with the hub reserving 10W for operational efficiency. (Note: Wall charger not included.)
- Quick Data Transfers: Accelerate your productivity with rapid data transfers using a high-speed 5Gbps USB 3.0 port and two 480Mbps USB 2.0 ports.
- 4K HDMI Display: Enhance your visual experience with a hub capable of delivering 4K resolution at 30Hz in both mirror and extend modes. Please note that this hub is compatible with MacBook (macOS 12 and newer), Windows 10 and 11, ChromeOS, and laptops equipped with DP Alt Mode and Power Delivery. Note: This device is not compatible with Linux.
- What You Get: Anker USB-C Hub (5-in-1, 4K HDMI), welcome guide, 18-month warranty, and our friendly customer service.
Is WebDriver BiDi the future of browser automation?
BiDi addresses a real limitation in the communication model: a shared WebDriver protocol can deliver events as well as accept commands. That design can give test frameworks a more consistent way to observe logging, network activity, and browser-context changes across browsers, if implementations converge on the relevant modules.
The status calls for measured expectations. The W3C cover page identifies the specification as a Working Draft dated 30 September 2026, meaning it is still work in progress rather than a finalized Recommendation. The W3C repository describes BiDi as a living standard receiving new features. Interoperability is therefore a direction of travel, not evidence that all browser automation stacks can switch without changes. W3C WebDriver BiDi repository
Quick wins for a faster PC:
Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →Clear out junk files and repair common Windows errorsFree Scan →Rank #3
- Sleek 7-in-1 USB-C Hub: Features an HDMI port, two USB-A 3.0 ports, and a USB-C data port, each providing 5Gbps transfer speeds. It also includes a USB-C PD input port for charging up to 100W and dual SD and TF card slots, all in a compact design.
- Flawless 4K@60Hz Video with HDMI: Delivers exceptional clarity and smoothness with its 4K@60Hz HDMI port, making it ideal for high-definition presentations and entertainment. (Note: Only the HDMI port supports video projection; the USB-C port is for data transfer only.)
- Double Up on Efficiency: The two USB-A 3.0 ports and a USB-C port support a fast 5Gbps data rate, significantly boosting your transfer speeds and improving productivity.
- Fast and Reliable 85W Charging: Offers high-capacity, speedy charging for laptops up to 85W, so you spend less time tethered to an outlet and more time being productive.
- What You Get: Anker USB-C Hub (7-in-1), welcome guide, 18-month warranty, and our friendly customer service.
Which browsers and frameworks support BiDi?
There is no useful single yes-or-no answer independent of versions and features. Support must be checked across the browser, its driver, the automation framework, and the particular BiDi module or command. The W3C repository links to browser compatibility data; consult that live data for the current implementation picture, then verify your own required operations in the versions you deploy.
A dated example: Firefox and Puppeteer
In a 7 August 2024 account, Chrome for Developers reported production-ready BiDi support in Firefox 129 and Puppeteer 23. The article said Puppeteer used BiDi by default for Firefox, while Chrome automation continued to default to CDP unless BiDi was explicitly requested. This is a useful illustration of framework defaults and protocol coexistence, not a complete browser-support matrix for 2026. Chrome for Developers: Firefox support in Puppeteer with WebDriver BiDi
Rank #4
- Dual Converters, Infinite Potential：Includes 2× USB C male to USB A female adapters and 2× USB A male to USB C female adapters. Perfect for a wide range of uses—tablets with Bluetooth keyboards, expand USB ports on macbook, and more. Two different converters for all your daily needs
- Next-Level 10Gbps & 3A Charging: No more slow 480Mbps, this usb to usb c adapter has a transfer speed of up to 10Gbps, allowing you to do more transferring in less time. This usb adapter fits both USB A and USB C charger, supporting up to 3A fast charging
- Upgraded Exquisite Craftsmanship: With an aluminum alloy housing and metal connector, the usbc to usb adapter is extremely durable and sturdy. Rigorously tested to withstand more than 10,000 times of plugging and unplugging, ensuring long-lasting performance
- Broad Compatible: The usb c to usb adapter widely supports all USB C/ USB A devices like laptops, tablets, cellphones, car chargers, and phone chargers. Such as compatible with MacBook Pro/Air 2023/2022, Thunderbolt 4/3 Devices,Apple MagSafe Watch 9/8/7/SE/Ultra, iPad Pro 2022/2021, Samsung Galaxy S23/S20/S10, and iPhone 17/16/15 Pro. Plug and play
- Please Note: To reach 10Gbps speed, keep the cable under 3.3 ft. For USB A Male to USB C adapters, try flipping the USB C connector. USB C Male to USB A adapters support bidirectional 10Gbps transfer within 3.3 ft
How to check your own stack
- List the exact events and commands your tests need—for example, console errors, request interception, or context notifications.
- Check the current compatibility information linked from the W3C repository for the target browser and feature area.
- Check the framework’s documentation and defaults for your installed version. Confirm whether BiDi must be selected explicitly or whether the framework chooses another protocol.
- Run a small integration test using the same browser, driver, framework, and versions as your CI environment. Verify the event subscription and expected payload, not merely that a session starts.
- Retain a fallback for features that are unavailable or still depend on a browser-specific protocol.
Should you adopt BiDi now?
Choose based on the behavior your automation needs and the support in your actual stack, rather than on the word “future” in the protocol’s promise.
BiDi is a good candidate when
- You need event notifications instead of polling for supported browser activity.
- Your framework and target browser expose the specific BiDi modules your tests require.
- Cross-browser consistency matters and the relevant implementations behave compatibly in your own test suite.
Keep classic WebDriver or CDP in the mix when
- Your current command-driven tests already meet their needs and a migration offers no concrete benefit.
- A required event or command is not implemented in one of your target environments.
- Your workflow depends on CDP-specific behavior or your framework selects CDP by default for the browser you automate.
Migration can be incremental: the W3C design calls for gradual interoperability with classic WebDriver commands. Evaluate one event-driven use case first, keep the existing test flow where it works, and avoid assuming that a BiDi session makes every classic command or browser-specific capability interchangeable.
Free tools Windows power users keep installed
One-click scans. No signup required.
Best Value
- 5-in-1 Connectivity: Equipped with a 4K HDMI port, a 5 Gbps USB-C data port, two 5 Gbps USB-A ports, and a USB C 100W PD-IN port. Note: The USB C 100W PD-IN port supports only charging and does not support data transfer devices such as headphones or speakers.
- Powerful Pass-Through Charging: Supports up to 85W pass-through charging so you can power up your laptop while you use the hub. Note: Pass-through charging requires a charger (not included). Note: To achieve full power for iPad, we recommend using a 45W wall charger.
- Transfer Files in Seconds: Move files to and from your laptop at speeds of up to 5 Gbps via the USB-C and USB-A data ports. Note: The USB C 5Gbps Data port does not support video output.
- HD Display: Connect to the HDMI port to stream or mirror content to an external monitor in resolutions of up to 4K@30Hz. Note: The USB-C ports do not support video output.
- What You Get: Anker 332 USB-C Hub (5-in-1), welcome guide, our worry-free 18-month warranty, and friendly customer service.
Or skip the browser setup
If the job is to capture a page image or PDF—not to run an interactive browser test—you may not need to configure WebDriver BiDi, a browser, and a driver at all. ScreenshotNeo is a website screenshot API and MCP server. A single GET request can return a screenshot or PDF; for a WebP screenshot:
curl -G "https://api.screenshotneo.com/v1/shot" -d access_key=YOUR_API_KEY --data-urlencode url=https://stripe.com -o shot.webpSee the ScreenshotNeo documentation for API options. Before capture, it accepts cookie or consent banners and removes more than 60 known consent platforms, newsletter popups, and chat widgets; those steps can be turned off. Bot checks, blank pages, timeouts, failed loads, and cache hits are not billed, and responses identify the page verdict and billing status. Its MCP server provides take_screenshot, get_page_info, and capture_pdf tools for AI agents and MCP clients. The free plan includes 1,000 shots per month without a card; paid plans start at $5 for 3,000 shots.
Sign up for ScreenshotNeo’s free plan: 1,000 screenshots a month, no card required.
Frequently Asked Questions
Does WebDriver BiDi replace Selenium or WebDriver?
No. BiDi is a protocol for browser communication; Selenium and other automation frameworks are clients that may support it alongside existing WebDriver workflows.
Does using BiDi guarantee faster tests?
No. The event-driven model can reduce polling for supported events, but the sources establish no general performance advantage. Measure the specific workflow and stack you use.
Is BiDi the same thing as a browser screenshot API?
No. BiDi is a browser automation protocol. A screenshot API such as ScreenshotNeo is a service for requesting page captures, not a replacement for interactive test automation.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
