Selenium Grid 4.41.0 adds Kubernetes options, a session-scoped event API, and event-driven video recording in the described Docker Selenium setup. To try Grid locally, install Java 11 or later, a browser, and the Selenium Server JAR, then start standalone mode and point your tests to http://localhost:4444. The phrase “A Smattering of Selenium 85” could not be tied to an identifiable official issue or release, so this update covers verified Selenium Grid changes without treating “85” as a release number.
What’s new in Selenium Grid 4.41.0
The Selenium project’s Grid 4.41.0 deep dive, dated February 27, 2026, focuses on deployment flexibility, event handling, and operational fixes.
Dynamic Grid for Kubernetes
Dynamic Grid can provision browser Pods on demand in Kubernetes. This gives teams a way to create browser capacity as sessions need it rather than treating every browser worker as a permanently running instance. The release article also includes Docker image tags, a Helm chart version, and a standalone JAR example. Those commands are version-specific; check the release instructions before using them in a deployment.
Session Event API
The Session Event API provides an endpoint scoped to an active WebDriver session. Test code can send named events and optional payloads through the Grid node to its internal event bus. This creates a connection between what a test is doing and services that react to Grid events, without requiring those services to infer test state from unrelated signals.
Outdated Drivers Are Slowing You Down
One free scan finds every outdated or missing driver and matches the right update for your exact hardware.Free scan · exact hardware matchWindows Errors? Fix Them Before They Spread
Repair common Windows errors and clear accumulated junk for a smoother, more stable PC - no reinstall needed.Free scan · no reinstall#1 Best Overall
Event-driven video recording
In the Docker Selenium setup described in the release post, session events can drive video recording behavior, including failure-only upload configuration. This is a detail of the cited Docker Selenium version, not a guarantee that every Grid deployment or later version behaves the same way.
Operations and reliability
- Distributor reliability fixes address Grid coordination.
- WebSocket connection leak fixes target long-running connection handling.
- Structured logging options provide additional control over log output.
- Docker Selenium changes its default ingress to Traefik. If your deployment has custom ingress configuration, review the migration guidance before upgrading.
Run Selenium Grid locally
Selenium’s Grid quick start lists Java 11 or higher, browsers, browser drivers, and the Selenium Server JAR as the basic setup components. Selenium Manager can configure drivers automatically when enabled. Check the current quick start for the supported download and launch details for your platform.
Rank #2
- Install Java 11 or later and confirm it is available in your terminal.
- Install the browser or browsers your tests need.
- Download the Selenium Server JAR from Selenium’s official downloads and releases documentation.
- Start a local standalone Grid with the JAR:
java -jar selenium-server-<version>.jar standalone. Replace<version>with the JAR you downloaded. - Configure your test driver to use
http://localhost:4444as its remote WebDriver endpoint, then run the test.
Standalone mode is the quickest way to try Grid on one machine. Grid also supports hub-and-node and distributed deployment patterns for teams running sessions across machines or in Kubernetes; the right shape depends on concurrency needs and who will operate the infrastructure.
Choose a deployment approach
| Approach | Use it when | What to consider |
|---|---|---|
| Standalone | You want a local setup or a simple single-machine Grid. | It is straightforward to start, but capacity is bounded by that machine. |
| Hub and node | You need browser sessions on separate machines. | Plan for node management, connectivity, and the number of concurrent sessions required. |
| Distributed or Kubernetes-based | You need a multi-component deployment or want Kubernetes to provision browser Pods on demand. | Account for deployment ownership, scaling, observability, and upgrade coordination. Review the release’s ingress migration notes if you customize ingress. |
Selenium’s 2021 Selenium 4 announcement describes standalone, hub-and-node, and distributed Grid patterns, along with observability and a GraphQL interface. Those are release-era architecture notes; consult current Grid documentation for implementation details.
Upgrade considerations
- Confirm the exact server, Docker image, and Helm chart versions you intend to deploy against the current release information.
- For custom ingress, review the Docker Selenium migration guidance before adopting the Traefik default.
- If you rely on video recording or event integrations, validate their configuration in the specific deployment model and Docker Selenium version you use.
- Test the upgrade with your existing browser, driver, and language-binding combinations before rolling it out broadly.
The official Selenium releases index is the place to verify subsequent release information as versions change.
Common setup problems
- Java is missing or too old: Install Java 11 or newer and verify that the terminal resolves the intended Java executable.
- The JAR command fails: Check that the JAR path and filename match the file you downloaded, and use the full path if it is not in the current directory.
- The browser cannot start: Confirm that a supported browser is installed. If driver setup is the issue, verify Selenium Manager is enabled or configure a compatible driver according to Selenium’s current documentation.
- Tests cannot connect: Ensure standalone Grid started successfully and that the test points to
http://localhost:4444. If the test runs in a container or another host, localhost may refer to that environment rather than the Grid machine. - Upgrade changes ingress behavior: Review the migration guidance if you have custom ingress settings; the Docker Selenium default changed to Traefik.
When a screenshot API is a better fit
Selenium Grid is for running browser automation and WebDriver tests. If the job is simply to capture website screenshots or PDFs, a screenshot API can avoid managing browser sessions and Grid infrastructure. ScreenshotNeo is a website screenshot API and MCP server; it removes known consent banners, newsletter popups, and chat widgets before capture, and only clean shots are billed.
Or skip the browser setup:
One GET request returns a screenshot; see the ScreenshotNeo API documentation for parameters and response details.
curl -G "https://api.screenshotneo.com/v1/shot" -d access_key=YOUR_API_KEY --data-urlencode url=https://stripe.com -o shot.webpCookie 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 screenshot tools. The Free plan includes 1,000 screenshots a month with no card; paid plans start at $5 for 3,000. Sign up for ScreenshotNeo’s free plan.
Frequently Asked Questions
Does “Selenium 85” refer to Selenium Grid 4.41.0?
No. The phrase “A Smattering of Selenium 85” could not be identified as an official issue or release title; Grid 4.41.0 is a separate verified release.
Which programming languages have Selenium 4 bindings?
The Selenium 4 announcement lists Java, .NET, Python, Ruby, and JavaScript.
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.
