How to Download and Install Selenium IDE for Firefox & Chrome

โšก Smart Summary

Selenium IDE installs as a browser extension rather than a standalone application, so the whole setup is an add-on download in Firefox or Chrome followed by a single click to open the recorder.

  • ๐Ÿ”˜ Firefox route: Add the extension from Firefox Add-ons, approve the permission dialog, then launch the recorder from the toolbar icon.
  • โ˜‘๏ธ Chrome route: Start from the official Selenium IDE download page, add the extension, and open it from the Extensions menu.
  • โœ… Element inspection: Firefox DevTools and Chrome DevTools both supply the CSS selector or XPath that a Selenese command needs.
  • ๐Ÿงช Legacy builds: The original Firefox-plugin release requires an old portable Firefox, so treat it as a historical reference only.
  • ๐Ÿ› ๏ธ Troubleshooting: A missing toolbar icon almost always means the extension is disabled or the toolbar is simply too narrow.
  • ๐Ÿ“Š Cross-browser runs: Installing the command-line runner through npm executes saved projects on other browsers and on a Grid.

Download and install Selenium IDE for Firefox and Chrome

In this tutorial, we will learn how to download and install Selenium IDE for Firefox and Google Chrome. Nothing is compiled and nothing is placed on the system path โ€” the IDE is a browser extension, so the install is finished the moment the browser reports that the add-on has been added.

โš ๏ธ A note on versions: the screenshots below come from the original Firefox-plugin Selenium IDE. That build stopped working when Firefox 55 removed support for legacy XUL add-ons in 2017. The Selenium IDE distributed today is a rewritten extension for Firefox and Chrome that saves projects in the .side format instead of HTML. Every original step is preserved here, with the current behaviour noted beside it.

How to Install Selenium IDE for Firefox

Below is a step by step process on how to download and install Selenium IDE for Firefox:

What you need

  • Mozilla Firefox
  • Active Internet Connection

If you do not have Mozilla Firefox yet, you can download it from firefox.com.

Steps 1) Open Firefox Add-ons & Download Selenium IDE

Launch Firefox and navigate to the Selenium IDE listing on Firefox Add-ons. Click on Add to Firefox. The add-on page looks like the screenshot below.

Selenium IDE listing on Firefox Add-ons with the Add to Firefox button

Steps 2) Click on Add

Wait until Firefox completes the download and then click โ€œAdd.โ€œ Firefox first shows the permission prompt below, which lists the access the extension is requesting.

Firefox permission prompt with the Add button for the Selenium IDE extension

Steps 3) Click on Ok

Once install is complete, you will get a confirmation message. Click โ€œOKโ€ on the notification shown here.

Firefox confirmation message stating that Selenium IDE was added

Steps 4) Click & Open Selenium IDE

Click on the Selenium IDE icon, which now sits in the Firefox toolbar as shown below.

Selenium IDE icon in the Firefox browser toolbar

Selenium IDE will open in its own window, as in the next screenshot.

Selenium IDE window open after installation in Firefox

Firefox DevTools in Firefox

Installing the IDE is only half of the setup. Recording a step is easy, but writing one by hand needs the identifier of the element the step acts on, and that comes from the browser’s own inspector.

Firefox DevTools is a Firefox feature that we will use to inspect the HTML elements of the web application under test. It will provide us the name of the element that our Selenese command would act upon.

Step 1) Right click anywhere on the page and select Inspect Element. You can also use shortcut Ctrl + Shift + I. The context menu is shown below.

Firefox right-click context menu with the Inspect Element option

Step 2) You will see the Interface pictured here, with the page markup on one side and the styles on the other.

Firefox DevTools inspector panel showing the HTML of the page under test

Step 3) You can right click on an element and chose CSS or XPath. This is useful in object identification, because the copied value can be pasted straight into the Target field of a command.

Copying a CSS selector or XPath expression from the Firefox DevTools inspector

Note: Likewise, you can also use Developer Tools in Chrome to identify object properties. The Chrome panel below performs the same job.

Chrome DevTools inspecting an element to read its object properties

Both inspectors also expose the id, name and class attributes that the IDE prefers when it builds a locator during recording.

Selenium IDE was deprecated, and the development had stopped. Only recently the project has been resurrected. The new Selenium lacks many features compared to the deprecated IDE. Features are being added but at a slow pace. To explore all the features of Selenium IDE, we recommend you use the old version. To use the old version of IDE

Step 1) Use Firefox 54 Portable Version check here

Step 2) Visit the Selenium IDE version history and install. The version list looks like this.

Version history page listing earlier Selenium IDE releases available for download

The following features may not be available in latest IDE version. We will keep updating the tutorials as the new version is updated.

โš ๏ธ Current status: running an unsupported browser purely to keep an unsupported add-on alive is no longer a practical option on a work machine, so treat the two steps above as historical context. The rebuilt IDE now covers most of what made the legacy tool useful, including stored variables, control-flow commands and code export.

Plugins

Selenium IDE can support additional Firefox add-ons or plugins created by other users. You can visit the official Selenium IDE site for a list of Selenium add-ons available to date. Install them just as you do with other Firefox add-ons.

By default, Selenium IDE comes bundled with 4 plugins:

  1. Selenium IDE: C# Formatters
  2. Selenium IDE: Java Formatters
  3. Selenium IDE: Python Formatters
  4. Selenium IDE: Ruby Formatters

These four plugins are required by Selenium IDE to convert Selenese into different formats.

The Plugins tab shows a list of all your installed add-ons, together with the version number and name of the creator of each, as in the screenshot below.

Selenium IDE Plugins tab listing the four bundled formatter plugins

User Extensions

Selenium IDE can support user extensions to provide advanced capabilities. User extensions are in the form of JavaScript files. You install them by specifying their absolute path in either of these two fields in the Options dialog box.

The two path fields are highlighted in the Options dialog below.

Options dialog fields for the Selenium Core extensions and Selenium IDE extensions file paths

You will be able to find tons of user extensions on the Selenium downloads page. Note that this mechanism belonged to Selenium Core, which was removed in Selenium 3; the modern IDE is extended through its own plugin API instead.

How to Install Selenium IDE in Chrome

Below is a step by step process on how to download and install Selenium IDE for Google Chrome:

Step 1) Go to the Selenium IDE site & Click the Chrome Download button.
Step 2) Open the Chrome Web Store listing for the Selenium IDE extension and install it.
Step 3) Click the Add to Chrome button to add the Selenium IDE to Google Chrome.
Step 4) Go to the Extensions menu, click on that icon, and open Selenium IDE to record a new test in a new project.

The Chrome build and the Firefox build are the same extension, so a project recorded in one opens in the other. Because browser stores change their listings over time, always start from the official site in Step 1 rather than from a bookmarked store URL.

How to Verify the Installation and Record a First Test

An extension that loads is not proof that the setup works. The quickest check is to record something trivial and play it back.

  1. Click the Selenium IDE icon. The welcome dialog offers four options: record a new test in a new project, open an existing project, create a new project, or close the IDE.
  2. Choose the first option and give the project a name.
  3. Enter a base URL. This is the address of the application under test, and it is reused by every test in the project.
  4. A new browser window opens on that URL and recording starts. Click a link or type into a field, then switch back to the IDE and click the recording icon to stop.
  5. Click the save icon. The IDE writes a single file with a .side extension.
  6. Select the test and click play. If the recorded steps replay without a red failure marker, the installation is sound.

A first playback that fails on the very first command usually points at the base URL rather than at the install. A playback that fails midway is a locator problem, which is where the verify and wait commands earn their keep.

How to Fix Common Selenium IDE Installation Problems

Almost every install complaint falls into one of a handful of patterns. The first two are the ones documented by the Selenium project itself.

  • No icon in the toolbar. Confirm the extension is enabled. Type chrome://extensions in Chrome, or about:addons in Firefox, and check that Selenium IDE is switched on.
  • The extension is enabled but still invisible. The icon may simply be hidden because the toolbar is too narrow. In Chrome, drag the area to the right of the address bar. In Firefox, right-click the toolbar, choose Customize, adjust it, and click Done.
  • The IDE opens but records nothing. The recording window must be the one the IDE launched. Recording in a tab opened by hand is not captured.
  • Nothing works on an internal page. Extensions cannot script browser-internal pages such as the settings or extensions screens, so record against an ordinary web page.
  • A managed browser blocks the install. On a corporate profile, extension installation is often controlled by policy and needs an administrator to allow the extension ID.

How to Install the Selenium IDE Command-Line Runner

The extension plays tests back only in the browser it is installed in. To run a saved project on other browsers, in parallel, or on a Grid, install the command-line runner. It needs Node.js and npm.

npm install -g selenium-side-runner

Each browser also needs its own driver binary. Install the driver for the browser you intend to target.

npm install -g chromedriver
npm install -g geckodriver
npm install -g edgedriver

With the runner and a driver in place, point the runner at the project file that the IDE saved earlier.

selenium-side-runner /path/to/your-project.side

The runner spreads suites across as many processes as the machine has CPU cores. Two flags cover most day-to-day needs: -c sets the browser, and --base-url retargets the whole project at a different environment, which is what makes the same recording usable against a local build and a staging server.

selenium-side-runner -c "browserName=firefox" --base-url https://localhost

From here, the natural next step is to leave record-and-playback behind and write the same checks in code โ€” see the first WebDriver script walkthrough and the wider Selenium series.

FAQs

No. It is open source and distributed free through the browser add-on stores, with no account, licence key or trial period. The command-line runner is equally free and installs from the public npm registry.

Not for the extension itself, which runs entirely inside the browser. A language runtime only matters once you export a recording to code, or when you install the command-line runner, which requires Node.js rather than a JDK.

Any platform that runs a supported browser, so Windows, macOS and Linux all work. The extension inherits the browser’s requirements, which means there is no separate installer and no operating-system specific build to choose.

Remove it from the browser’s extensions page, then add it again from the store. Saved projects are ordinary files on disk, so they survive a reinstall untouched. Reinstalling is the usual fix for an IDE window that opens blank.

Yes, because it records inside a real browser session and inherits whatever cookies that session holds. Single sign-on redirects still record, although the resulting steps are often brittle and better replaced by a direct login step.

Machine learning is applied mainly after recording: self-healing engines propose a replacement selector when markup shifts, and flaky-test models flag steps that fail intermittently. Neither changes the install, but both reduce the maintenance that follows it.

It cannot drive the extension, but it is useful on the exported file. Copilot readily turns a raw exported script into page objects, adds explicit waits, and writes the CI job that calls the command-line runner.

Wherever you choose when saving. The IDE writes one JSON file per project with a .side extension, which is plain text and therefore safe to commit to version control and to diff during review.

Summarize this post with: