Selenium IDE records browser actions as editable Selenium-command tests, then lets you replay those tests in the IDE. A project can contain suites of tests and is saved as a single .side file. For repeatable work beyond the IDE window, the separate side-runner can execute projects locally or connect to a Selenium Grid—but that path also requires suitable browser, driver, and runtime setup.
One important version distinction: Selenium’s overview page, last modified December 7, 2021, describes a browser extension for Chrome, Firefox, and Edge, while Selenium IDE v4 materials and the current SeleniumHQ repository describe a desktop Electron application. Check the current installation source and release information before following older setup instructions.
As an Amazon Associate I earn from qualifying purchases.
What Selenium IDE does—and what it does not do
Selenium IDE is a visual starting point for browser test automation. It records and plays back a user’s actions using Selenium commands, and those commands can also be added or edited manually. That makes it useful for learning the command model and quickly creating a first draft of a test without beginning by writing automation code.
A recording is not automatically a robust test. The SeleniumHQ project identifies selector accuracy as an area of ongoing work. Review the generated locators, make sure they identify stable elements in your application, and replay the test more than once before relying on it.
#1 Best Overall
What changed in Selenium IDE v4?
Older Selenium materials describe Selenium IDE as a browser extension. Selenium IDE v4 project materials explain a move away from the web-extension model, and the current SeleniumHQ repository describes an Electron application with release binaries, npm installation, and manual-build options. These descriptions refer to different product generations and distribution approaches; they should not be collapsed into one timeless installation instruction.
The v4 project materials discuss browser-level operations and constraints of the extension model as reasons for the change. Since the repository information does not establish a definitive current runtime and browser support matrix, use the current SeleniumHQ release and package information for installation and compatibility rather than relying on old prerequisites or examples.
How to record your first test
The documented getting-started workflow is straightforward, though its interface instructions were last updated February 19, 2019. Labels and controls may have changed, so treat this as the sequence to follow and confirm the exact controls in the version you install.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
Rank #2
- Create a project: Start a new Selenium IDE project and give it a name.
- Set the base URL: Enter the application’s starting address. The project uses this as the base for the test.
- Record a scenario: Have the IDE open the application, start recording, and perform the user actions you want to test—for example, navigating to a page and submitting a form.
- Inspect and edit: Review the recorded commands and selectors. Correct weak or overly specific locators, and add commands manually where the recording missed an important check or action.
- Organize tests: Keep related tests in suites. A newly created project includes a default suite; you can add tests to it or organize them into additional suites.
- Save the project: Saving produces a single
.sideproject file containing the project and its tests. - Replay: Run an individual test or a suite in the IDE. Playback uses the existing recording window when available, or opens another window.
How to save and run a .side file
The .side file is the project artifact you can reopen and edit in Selenium IDE. In-IDE replay is the simplest way to check a recording. It is distinct from command-line execution: Selenium’s runner documentation describes a separate selenium-side-runner package for running projects outside the IDE.
Local command-line runs
The runner documentation describes installing the side-runner, installing the target browser, and providing that browser’s driver for local execution. It also describes selecting browsers through capabilities, configuring headless Chrome, and overriding the project’s base URL. These are setup categories, not a reliable current compatibility recipe: the same documentation names Node.js 8 or 10 as a prerequisite and contains older browser examples. Confirm supported Node.js, browser, driver, and package versions from current project release information before setting up a runner.
Grid and parallel execution
A Selenium Grid lets a runner send work to remote browser sessions through a server URL instead of relying only on a local browser and driver. The runner documentation also describes suite-level parallelism and a configurable worker count. Remote execution can reduce the need to provision every browser locally, but it introduces Grid or hosted-infrastructure configuration and its own capacity and availability considerations. The documentation names Sauce Labs as an example of a hosted Grid; no current pricing or service terms are established here.
Exports and code-oriented workflows
The current SeleniumHQ repository describes a modular implementation: an Electron IDE, a Node.js side-runner, a shared side-runtime, and exporters for C#, Java, JavaScript, Python, and Ruby. Exporting can help when a team wants to continue in a code-based workflow, but it does not remove the need to inspect selectors and maintain the resulting tests.
Free tools Windows power users keep installed
One-click scans. No signup required.
When Selenium IDE is a good fit
- Fast first draft: Record ordinary interactions and then refine the commands instead of starting entirely from hand-written automation.
- Learning Selenium commands: The IDE is presented as an entry point to Selenium syntax, with visible commands that can be reviewed and edited.
- Small, editable project: Tests can be grouped into suites, saved together as a
.sidefile, and replayed in the IDE. - Broader execution needs: A side-runner and Grid provide a path toward other browsers, parallel runs, or remote infrastructure, provided the team is prepared to manage the associated setup.
Where recorded tests need extra care
Recorded flows can be convenient but brittle if their selectors depend on incidental page structure or if the application changes. Review each locator and choose stable application attributes where available. Also check whether the test actually verifies an outcome; a sequence that merely clicks through the happy path may not detect a regression. Keep tests focused enough that a failure points to a useful part of the workflow.
For a team deciding between IDE-first and code-first work, consider authoring effort, readability, selector stability, execution targets, environment management, and export needs. Recording may lower the effort of a first draft, while hand-coded automation may better fit workflows that demand highly customized logic and review practices. Neither approach removes maintenance. Likewise, local browsers provide direct control but require browser and driver setup; Grid execution broadens where tests can run but adds infrastructure to configure and monitor.
Or skip the browser setup
If the job is to capture a webpage image or PDF rather than test an interactive browser flow, ScreenshotNeo is a separate screenshot API and MCP server—not a replacement for Selenium IDE test automation. One GET request can return a PNG, JPEG, WebP, or PDF. Example using cURL:
curl -G "https://api.screenshotneo.com/v1/shot" -d access_key=YOUR_API_KEY --data-urlencode url=https://stripe.com -o shot.webp
See the ScreenshotNeo documentation for request details. It removes cookie banners, newsletter popups, and chat widgets before capture; bot checks, blank pages, failed loads, timeouts, and cache hits are not billed. Its MCP server lets AI agents use screenshot tools. The free plan includes 1,000 screenshots a month with no card, and paid plans start at $5 for 3,000. Sign up for the free plan.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Common setup and test problems
- Old installation instructions do not match your IDE: The extension-era overview and newer Electron-app materials describe different generations. Check the current SeleniumHQ release information and use instructions for the distribution you actually installed.
- The runner will not start or cannot find a browser: Local command-line execution requires a compatible browser and driver, in addition to the runner and supported runtime. Verify all three against current package and release information; do not assume the old Node.js 8/10 prerequisite is current.
- A test passes once but fails later: Inspect recorded selectors and replace fragile locators with stable ones where the application permits. Replay after changes to confirm the test remains repeatable.
- Playback uses an unexpected window: IDE playback may use the existing recording window if available or open another one. Check the active test and browser window before diagnosing the page itself.
- Remote or parallel runs fail while local replay works: Treat Grid connectivity, remote browser availability, capabilities, and worker configuration as separate from the IDE recording. Validate the runner-to-Grid connection and target browser setup independently.
Frequently Asked Questions
Can Selenium IDE run tests in other browsers?
The IDE’s in-window replay and the command-line runner are different execution paths. The runner documentation describes browser selection through capabilities, but current supported browsers and versions should be confirmed in current package and release information.
Can I use Selenium IDE without writing code?
You can record and replay tests and edit Selenium commands in the IDE without starting from hand-written automation code. Reliable tests still require reviewing selectors and checking that the test verifies the intended behavior.
What is the difference between a .side file and a Selenium Grid?
A .side file stores the IDE project and tests. A Selenium Grid is remote execution infrastructure that a runner can connect to using a server URL.
The Tool Desk
Outbyte Driver Updater FREEScan for outdated or missing drivers - takes under a minuteDriver Scan →Outbyte PC Repair FREEClear out junk files and repair common Windows errorsFree Scan →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.
