Selenium News and Updates: A Smattering of Selenium 86
Selenium 4.50.0 arrived on September 30, 2026. Here are the release highlights, recent BiDi developments, and what to check before upgrading.
Selenium 4.50.0, released September 30, 2026, is the latest release identified in the official Selenium GitHub release feed at the time of this roundup. Its notes highlight a .NET WebDriver BiDi screenshot change that exposes image size. The Ruby 4.50.0 change log lists additional changes: support for CDP versions v152, v153, and v154; BiDi methods for installing and uninstalling browser extensions; and removal of deprecated Firefox profile extension and certificate methods. These are component-specific changes, so check the notes for your language binding before relying on a capability.
This roundup reflects project information retrieved on October 3, 2026. The Selenium homepage’s news section showed 4.49 in the search results, while GitHub’s release feed showed 4.50.0. Use the release feed for the latest release number and the project’s blog and category pages for broader context.
What Selenium is, and what changed
Selenium is a set of browser automation components. The project describes its purpose as “Selenium automates browsers. That’s it!” WebDriver drives browsers for automation and testing; Selenium IDE offers simple record-and-playback; Selenium Grid distributes test execution across machines and browser/OS combinations.
The practical news in 4.50.0 is continued work across browser protocols and language bindings, plus the .NET BiDi screenshot update. The release notes do not mean every binding exposes the same feature in the same way.
Selenium 4.50.0 highlights by component
.NET: BiDi screenshot image size
The GitHub release notes call out a .NET WebDriver BiDi screenshot change that adds image size to captured screenshots. If your code consumes BiDi screenshot results, review the .NET release details and adjust result handling as needed. The dossier does not establish the exact API shape, so consult the release notes and binding documentation before changing code.
Ruby: CDP and BiDi changes
The Ruby 4.50.0 change log lists support for CDP v152, v153, and v154, along with WebDriver BiDi methods to install and uninstall browser extensions. It also removes deprecated Firefox profile extension and certificate methods. Ruby projects that still call those deprecated methods should consult the binding’s migration guidance and replace those calls before upgrading.
CDP (Chrome DevTools Protocol) and WebDriver BiDi are distinct browser communication protocols. Recent project work increasingly includes BiDi. Do not assume a CDP capability exists through BiDi, or that support listed in one binding applies to another.
Recent release timeline
| Release | Date | Reported changes |
|---|---|---|
| Selenium 4.50.0 | September 30, 2026 | .NET BiDi screenshot image-size highlight; Ruby CDP v152–v154, BiDi extension install/uninstall methods, and removal of deprecated Firefox profile methods. |
| Selenium 4.49.0 | September 9, 2026 | Change logs record CDP v151–v153 support and continued BiDi schema work; a prebuilt Selenium Manager Linux ARM64 binary is listed across bindings. |
| Selenium 4.48.0 | August 27, 2026 | Change logs list low-level BiDi integration work, WebSocket frame hang fixes, and stricter handling of malformed BiDi values. |
| Selenium 4.47.0 | August 10, 2026 | The Ruby change log lists WebDriver BiDi support on Safari Preview. This is binding-specific and should not be generalized to all Safari configurations. |
The Selenium blog index also shows a separate Grid update stream: posts for Grid 4.41.0 and Selenium 4.41 appeared in February 2026, followed by Selenium 4.40 in January. Grid changes matter to distributed test operators, while language-binding notes matter to developers updating their client library.
How to decide whether to upgrade
- Identify your binding and browser protocol. Check whether the affected code uses WebDriver, BiDi, CDP, Selenium Manager, or Grid.
- Read the binding-specific change log. Confirm that a feature mentioned in the general release notes is available in your language and version.
- Search for removed or deprecated APIs. In particular, Ruby users should look for the removed Firefox profile extension and certificate methods listed for 4.50.0.
- Update in a controlled environment. Pin the intended Selenium version, run representative tests across your supported browser and OS combinations, and review failures before rolling the upgrade into wider CI.
- Check the release feed again before publication or rollout. Selenium releases move quickly, and the website news index and GitHub feed may not update at the same time.
What the recent BiDi focus means
Recent release notes repeatedly mention WebDriver BiDi work, from schema integration and malformed-value handling to binding-specific browser features. The project release index also identifies removal of Chrome DevTools support for Firefox and describes WebDriver BiDi as the direction forward. Treat that index entry as project direction, not as a claim about a specific current release.
For a migration or new automation project, choose the protocol based on the browser features and binding support you need. Confirm the exact support in your binding’s current documentation; protocol names alone do not establish that every browser, feature, or Selenium language client is supported.
Performance, reliability, and cost considerations
The cited release material does not provide performance benchmarks, reliability figures, or a cost comparison. Selenium is open-source software, and the project components do not require a paid service. Grid can distribute tests across machines and browser/OS combinations, but the dossier does not quantify how much faster a particular setup will be. Measure your own suite with the same test set and environment when evaluating an infrastructure change.
For reliability, keep browser versions, Selenium bindings, drivers or Selenium Manager behavior, and Grid nodes consistent enough to diagnose failures. Record the binding and browser versions in CI output, and separate protocol or browser startup failures from application test failures. These are operational practices, not claims that a particular release guarantees an outcome.
Capture a page without managing a browser
If the task is simply to produce a website screenshot rather than automate an interactive browser flow, ScreenshotNeo is the alternative to try first. It is a website screenshot API and MCP server from ScreenshotNeo; a GET request with a URL returns PNG, JPEG, WebP, or PDF. Its capture flow accepts cookie and consent banners like a visitor and removes more than 60 known consent platforms, newsletter popups, and chat widgets. Each of those steps can be disabled. Only clean shots are billed: bot checks, CAPTCHAs, blank pages, timeouts, failed loads, and cache hits cost nothing, with the outcome indicated in response headers.
Or skip the browser setup
Use this cURL request to save a WebP screenshot. Replace the placeholder with your API key; see the ScreenshotNeo API docs for the request options.
curl -G "https://api.screenshotneo.com/v1/shot" -d access_key=YOUR_API_KEY --data-urlencode url=https://stripe.com -o shot.webpThe same endpoint works from Python and Node.js:
import requests
r = requests.get(
"https://api.screenshotneo.com/v1/shot",
params={"access_key": "YOUR_API_KEY", "url": "https://stripe.com"},
timeout=90,
)
open("shot.webp", "wb").write(r.content)const q = new URLSearchParams({ access_key: 'YOUR_API_KEY', url: 'https://stripe.com' });
const res = await fetch(`https://api.screenshotneo.com/v1/shot?${q}`);
if (!res.ok) throw new Error(`Screenshot request failed: ${res.status}`);
await Bun.write('shot.webp', res);Cookie banners, popups, and chat widgets are removed before the shot. Bot checks, blank pages, and failed loads are never billed. An MCP server lets AI agents use the screenshot tools. The free plan includes 1,000 screenshots a month with no card; paid plans start at $5 for 3,000.
Create a free ScreenshotNeo account to get 1,000 screenshots a month without a card.
Troubleshooting upgrade issues
| Symptom | Likely cause | What to check |
|---|---|---|
| A method is missing after upgrading | The API was removed, deprecated, or is not present in your binding. | Read that binding’s 4.50.0 change log; Ruby users should check calls to the removed Firefox profile extension and certificate methods. |
| A protocol feature works in one language but not another | Release changes are binding-specific. | Confirm the feature in the exact language binding’s notes and documentation before porting code. |
| BiDi values or WebSocket interactions fail | Protocol integration behavior changed, or values do not match the expected schema. | Review the 4.48.0 notes about malformed values and WebSocket frame hang fixes, then capture the browser, binding, and protocol details in a minimal reproduction. |
| Safari Preview BiDi behavior differs from expected support | The cited 4.47.0 support is in the Ruby change log and does not imply universal Safari support. | Check the binding-specific documentation and the precise Safari or Safari Preview configuration. |
| The homepage appears to show an older version | The homepage news section and GitHub release feed can be out of sync. | Use the official GitHub release feed for the latest version, and date any release roundup. |
FAQ
Is Selenium 4.50.0 the latest version?
It was the latest version found in the official GitHub release feed on September 30, 2026, based on research retrieved October 3, 2026. Check the feed for releases published after that date.
Does Selenium 4.50.0 add the same features to every language?
No. The cited CDP and extension changes are listed in the Ruby change log, while the screenshot image-size highlight is in the .NET release notes. Verify each capability in the binding you use.
Is Selenium Grid required to use Selenium?
No. Grid is the project component for distributing tests across machines and browser/OS combinations; it is not required for local browser automation.
Does the release roundup include a performance comparison?
No benchmark was verified in the cited project material, so this article makes no quantified speed or reliability claim.
Sources
- Selenium project homepage for project components and framing.
- Official Selenium GitHub releases for release chronology and release highlights.
- Selenium blog index for dated Grid and project news.
