Selenium News and Updates: A Smattering of Selenium 92

Direct answer: “Selenium 92” is part of this article’s supplied title; the reviewed official Selenium release page does not identify a Selenium 92 release. As of October 3, 2026, the official downloads page lists Selenium 4.49.0, dated September 9, 2026, as the stable release for its listed bindings and Selenium Server. It also lists 4.50.0-SNAPSHOT nightly artifacts. Check the official downloads page and linked release notes for updates after that date.

This roundup explains what the release listing means, how Selenium’s components fit together, and how to assess an update for your project. It does not assign a meaning to “92” that the official release information does not establish.

1. What the current Selenium release listing says

The Selenium downloads page lists version 4.49.0, dated September 9, 2026, as stable for .NET/C#, Ruby, Java, Python, JavaScript, and Selenium Server (Grid). It also lists 4.50.0-SNAPSHOT artifacts under nightly builds. Selenium cautions that nightly builds can contain bugs or undocumented changes. These are the versions shown in the reviewed source on October 3, 2026; version listings can change, so confirm the current status before upgrading.

Listing	What it means	Practical action
4.49.0 stable	The downloads page identifies this as the stable release for the listed components.	Use the release notes for the binding or server component you run, then update through that component’s normal package or download process.
4.50.0-SNAPSHOT nightly	A development build, not the stable release. Nightly artifacts may include bugs or undocumented changes.	Use when you specifically need to check a pending fix or feature; isolate it from routine CI until you have validated it.

For an update after the research date, use the official Selenium downloads page for stable/nightly status and the Selenium release archive for versioned announcements. Read the notes for the exact component you use rather than assuming every binding and server artifact has identical packaging or timing.

2. Selenium is a suite of components

Selenium is not one browser or one application binary. You write a script with a language-specific WebDriver binding. The script can control a local browser through WebDriver or connect to Selenium Server using Remote WebDriver. Selenium Server is used for Grid configurations, which distribute test execution. The downloads page links to Grid documentation and Docker resources.

WebDriver bindings: client libraries for Java, Python, JavaScript, Ruby, and .NET/C#, among others listed on the downloads page.
Selenium Server and Grid: infrastructure for remote and distributed browser test execution.
Selenium IDE: a Chrome, Firefox, and Edge extension that records and plays back interactions; Selenium describes it as useful for simple scripts or exploratory testing.

When you read a release announcement, identify whether it concerns your language binding, Selenium Server/Grid, Selenium Manager, or another project component. A change in one component does not automatically describe a change in all of Selenium.

3. How to decide whether to update

Identify your exact components. Record the binding and version in your dependency file, plus the browser, driver-management setup, and whether tests use local WebDriver or a remote Grid.
Check the official downloads page. Confirm the current stable version and whether the artifact you need is stable or nightly.
Read the release notes between your current and target versions. Look for entries that name your binding or infrastructure, behavioral changes, deprecated APIs, migration steps, and experimental features.
Review your own API usage. Search for deprecated or internal Selenium APIs. Do not assume an earlier compatibility statement guarantees a frictionless upgrade to every later release.
Update in a controlled branch. Pin the intended version, run representative tests locally and in CI, and include remote/Grid coverage if that is how your suite runs.
Promote after checking results. Compare failures with the release notes and your baseline. Keep a path to restore the prior dependency version if the update blocks your pipeline.

Selenium 4.0.0 was announced on October 13, 2021. In that announcement, Simon Stewart said the team had focused on keeping public APIs stable for a “drop-in” upgrade, while warning that reliance on internal or deprecated Selenium code could cause difficulties. Treat that as historical context about the 4.0 release, not a promise about every subsequent version. See the official Selenium 4 announcement and check the specific release notes for your target.

4. A practical release review checklist

For each update you are considering, capture these details in your change review:

Component or language binding affected.
Version and release date.
Stable, nightly, or snapshot status.
Behavior or API changes relevant to your code.
Any stated breaking change, migration action, or experimental status.
Local and CI results, including remote/Grid runs where applicable.

The official downloads page exposes component and stable/nightly distinctions; the release archive organizes project updates by release. If a note does not say a change affects your component, avoid inferring that it does. Follow the linked documentation for the affected area.

5. Common update problems and how to investigate them

Symptom	Likely cause to check	Next step
A dependency update does not change the browser behavior you expected.	The change may belong to a different binding or component, or may require a documented migration.	Confirm the release note’s affected component and inspect the binding-specific changelog or documentation linked from the official release materials.
A nightly build behaves inconsistently.	Nightly artifacts can contain bugs or undocumented changes.	Reproduce with the stable version, record the exact snapshot dependency, and use the project’s issue/documentation channels to investigate the specific change.
Compilation or runtime errors appear after upgrading.	Your code may use an API changed, deprecated, or internal to Selenium.	Search the versioned notes and migration guidance for the symbol, replace unsupported usage with documented public APIs, and narrow the change to the relevant binding.
Local tests pass but remote/Grid tests fail.	The local and remote paths use different server, browser, or binding versions or configuration.	Record versions on both sides, check the Grid/server release notes, and reproduce against the same target configuration.
You cannot tell which release is current.	Search results or cached documentation may be older than the live downloads listing.	Use the official downloads page, note the date checked, and follow its release-note links.

These are investigation paths, not claims that a particular release has a known defect. Use the version-specific notes to confirm the cause before changing your test code.

6. Selenium and website screenshots are different jobs

Selenium is appropriate when your task is browser automation: interacting with a page, validating behavior, or running tests. If your task is simply to obtain a website screenshot, setting up and operating a browser is a separate workflow. ScreenshotNeo is a website screenshot API and MCP server for developers, made by Yorker Media. One GET request can return a PNG, JPEG, WebP, or PDF. See ScreenshotNeo and its API documentation.

ScreenshotNeo is an alternative to try first for screenshot capture: cookie banners, popups, and chat widgets are removed before the shot, and only clean shots are billed.

Or skip the browser setup

Make one request with a URL and save the returned image. This cURL example saves a WebP screenshot of Stripe:

curl -G "https://api.screenshotneo.com/v1/shot" -d access_key=YOUR_API_KEY --data-urlencode url=https://stripe.com -o shot.webp

The equivalent Python request is:

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)

And in Node.js with a runtime that provides fetch:

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 import('node:fs/promises').then(fs => fs.writeFile('shot.webp', Buffer.from(await res.arrayBuffer())));

ScreenshotNeo accepts screenshot API parameter names used by other screenshot APIs, which can make switching easier. The service can remove more than 60 known consent platforms, newsletter popups, and chat widgets before capture; each cleanup step can be turned off. Bot checks/CAPTCHAs, blank pages, timeouts, failed loads, and cache hits cost nothing, and response headers report the page verdict and billing status. Its MCP server provides take_screenshot, get_page_info, and capture_pdf tools for Claude, Cursor, and other MCP clients.

Plans include 1,000 screenshots per month free with no card; paid plans start at $5 for 3,000 shots. Higher listed plans are Growth at $15 for 15,000, Pro at $39 for 60,000, Scale at $99 for 250,000, and Business at $249 for 1,000,000. Yearly billing gives two months free, and every feature is on every plan. Sign up free for 1,000 screenshots a month with no card.

7. Performance, reliability, and cost considerations

Release validation: an upgrade can affect test runtime or reliability through the binding, browser, server, or your own suite. The reviewed sources provide no comparable performance benchmark, so measure your workload before and after instead of assuming a speed change.
Nightly risk: nightly builds are useful for checking a fix or feature ahead of release, but the project warns they may contain bugs or undocumented changes. Keep them separate from a stable production test lane unless you have chosen to validate them.
Distributed runs: Grid is designed for distributed test configuration. Validate the client and server sides that your setup actually uses.
Maintenance cost: include the effort to maintain browser automation, drivers, infrastructure, and CI in your decision. For screenshot-only work, compare that operational effort with a screenshot API’s per-plan limits and behavior.
Screenshot API billing: ScreenshotNeo says clean shots are billed; specified failed or non-page outcomes and cache hits are not. Check X-Page-Verdict and X-Billed in responses when accounting for requests.

8. Frequently asked questions

Is Selenium 92 the latest Selenium version?

The reviewed official downloads listing does not show a Selenium 92 release. It listed 4.49.0 stable on October 3, 2026; recheck the official downloads page for the current listing.

Should I install a nightly build?

Only when you need to evaluate a pre-release fix or feature and can tolerate the project’s stated possibility of bugs or undocumented changes. For normal use, start with the stable artifact for your component.

Does every Selenium component update together?

Do not assume that. Identify the binding or server component you use and follow its own release information and packaging instructions.

Is Selenium IDE the same as WebDriver?

No. Selenium IDE is a browser extension for recording and replaying interactions; WebDriver bindings are libraries used by scripts to control browsers.

Can I use ScreenshotNeo from an AI agent?

Yes. ScreenshotNeo provides an MCP server with screenshot, page-info, and PDF capture tools for MCP clients.