What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
Short answer: Selenium IDE’s documented command list does not include a native screenshot command. Use the IDE to record and replay the browser flow, then capture the page or an element with Selenium WebDriver code. A saved .side file is the test project, not a screenshot.
Does Selenium IDE have a screenshot command?
No native screenshot command appears in Selenium IDE’s documented command catalog. The IDE can author and replay browser actions—such as clicks, waits, assertions, and scripts—but the actual screenshot operation belongs to WebDriver or another host-side runner.
| # | Preview | Product | Price | |
|---|---|---|---|---|
| 1 |
|
Selenium IDE - A Practical Guide | $14.99 | Buy on Amazon |
| 2 |
|
Selenium By Example - Volume I: Selenium IDE | $19.85 | Buy on Amazon |
| 3 |
|
Selenium IDE 3 Reference Guide: Version 3.4.4 (English Book 181230) | $4.99 | Buy on Amazon |
| 4 |
|
Learning Selenium IDE Automation Testing Tool | $1.99 | Buy on Amazon |
| 5 |
|
Selenium Testing Tools Cookbook | $22.90 | Buy on Amazon |
This distinction matters because Selenium IDE runs as a browser extension. The Selenium IDE FAQ explains that the extension does not have access to the file system. It can download a project file through the browser, but it cannot use a built-in command to write an image to an arbitrary local path. The IDE’s documented project output is a single file with a .side extension; that file stores the test, not captured pixels.
Choose the right screenshot workflow
| Workflow | Screenshot support | File access | Browser coverage | Programming required |
|---|---|---|---|---|
| IDE-only playback | No documented native screenshot command | Extension cannot directly write arbitrary files; project is downloaded as .side |
Playback in the browser where the IDE is installed | Low for authoring and replaying tests |
| WebDriver implementation | Page and element screenshot methods | Code running on the host saves image files | Depends on the WebDriver language and browser setup | Some code required |
| Selenium IDE command-line runner | Use runner configuration or an exported/recreated WebDriver implementation for capture | Runner runs outside the extension; configure capture in the runner or code | Use the browsers supported by the runner setup | Configuration or code required |
For a one-off capture, WebDriver is usually the most direct route. If you need to run an existing .side test across additional browsers, the Selenium IDE getting-started guide points to its command-line runner; configure screenshot capture there or recreate/export the flow in WebDriver code.
#1 Best Overall
Record and save the browser flow in Selenium IDE
- Install Selenium IDE from the Chrome or Firefox web store.
- Record a test or create its steps in the IDE. Include the navigation, interactions, and waits needed to reach the exact state you want to capture.
- Save the project from the IDE. The downloaded
.sidefile is the test project, not a screenshot image. - Replay in the IDE for quick in-browser playback, or use the command-line runner when your workflow calls for runner-based or additional-browser execution.
- At the desired point in the test, perform the screenshot operation in a WebDriver implementation or configure the host-side runner to capture it.
Capture a page screenshot with Python WebDriver
The following runnable example opens a page and saves a screenshot of the current browser view. Install Selenium and the appropriate browser and driver setup for your environment first. The example uses Selenium’s current Python API method save_screenshot; create the output directory before running it if it does not already exist.
from pathlib import Path
from selenium import webdriver
output = Path("screenshots")
output.mkdir(parents=True, exist_ok=True)
driver = webdriver.Chrome()
try:
driver.get("https://example.com")
driver.save_screenshot(str(output / "example.png"))
finally:
driver.quit()The saved image represents the current browsing context at the moment the screenshot method runs. If the site has asynchronous rendering, wait until the page reaches the intended state before capture; otherwise, the file can be valid but show incomplete content. Add the same interactions and synchronization used in the IDE test to your WebDriver flow.
Capture only one element
Use an element screenshot when you want a component—such as a chart, product card, or banner—rather than the current page view. Locate the element after it appears, then call its screenshot method:
from pathlib import Path
from selenium import webdriver
from selenium.webdriver.common.by import By
from selenium.webdriver.support.ui import WebDriverWait
from selenium.webdriver.support import expected_conditions as EC
driver = webdriver.Chrome()
try:
driver.get("https://example.com")
target = WebDriverWait(driver, 10).until(
EC.visibility_of_element_located((By.CSS_SELECTOR, "main"))
)
Path("screenshots").mkdir(parents=True, exist_ok=True)
target.screenshot("screenshots/main.png")
finally:
driver.quit()Replace main with a selector that identifies the element you need. WebDriver element screenshot methods capture the selected element, whereas page methods capture the current browsing context. Exact behavior and method names vary by language binding.
Where the screenshot belongs in a Selenium IDE test
A screenshot must happen after the browser reaches the target state. In a WebDriver recreation, put the screenshot call after the navigation and the actions that establish that state. For a runner-based .side workflow, configure the capture in the runner or in the host-side implementation rather than trying to save a file from an IDE page script.
Selenium IDE’s execute script command runs JavaScript in the page. It can perform page operations such as scrolling with window.scrollTo(0,1000), but it does not expose WebDriver’s screenshot endpoint or provide arbitrary local-file writing. Scrolling may help position content for a view capture, but it is not itself a screenshot mechanism.
Or skip the browser setup:
If you need a screenshot of a URL rather than a Selenium test flow, ScreenshotNeo is a website screenshot API and MCP server for developers. One GET request returns an image or PDF; its consent-cleaning steps can accept cookie banners and remove known consent platforms, newsletter popups, and chat widgets before capture.
curl -G "https://api.screenshotneo.com/v1/shot" -d access_key=YOUR_API_KEY --data-urlencode url=https://example.com -o shot.webpSee the ScreenshotNeo documentation for API parameters and options. Bot checks, blank pages, timeouts, failed loads, and cache hits are not billed; response headers identify 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. The free plan includes 1,000 screenshots per month with no card; paid plans start at $5 for 3,000 screenshots.
Quick wins for a faster PC:
Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →Repair Windows errors before they cause bigger problemsFix Now →Sign up for ScreenshotNeo’s free plan to try 1,000 screenshots a month without a card.
Other useful WebDriver language examples
The API call is language-specific, but the workflow is the same: navigate, wait for the desired state, then save the page or selected element screenshot from host-side code. These short examples illustrate the documented WebDriver methods; install and configure the relevant Selenium binding and browser driver for your language.
JavaScript
const { Builder } = require('selenium-webdriver');
const fs = require('node:fs/promises');
(async () => {
const driver = await new Builder().forBrowser('chrome').build();
try {
await driver.get('https://example.com');
const image = await driver.takeScreenshot();
await fs.writeFile('example.png', image, 'base64');
} finally {
await driver.quit();
}
})();Java
import java.io.File;
import org.openqa.selenium.OutputType;
import org.openqa.selenium.TakesScreenshot;
import org.openqa.selenium.WebDriver;
import org.openqa.selenium.chrome.ChromeDriver;
WebDriver driver = new ChromeDriver();
try {
driver.get("https://example.com");
File image = ((TakesScreenshot) driver).getScreenshotAs(OutputType.FILE);
// Move or copy image to the desired output path using Java file APIs.
} finally {
driver.quit();
}Use the equivalent page or element screenshot API in your chosen binding. Do not assume that a browser-side Selenium IDE script and host-side WebDriver code share file permissions or screenshot capabilities.
Troubleshooting screenshot failures
- No screenshot command appears in the IDE. This is expected: the documented Selenium IDE command list has no native screenshot command. Use WebDriver or runner-side capture.
- The
.sidedownload is not an image. It contains the test project. Run or recreate the flow, then invoke a WebDriver screenshot method to produce an image file. - The screenshot file is missing. Confirm the code is running on the host, the output directory exists, and the process can write to it. A page script executed by the IDE extension is not an arbitrary filesystem writer.
- The screenshot is blank or incomplete. The capture may run before navigation, rendering, or a needed interaction finishes. Wait for a visible selector or other reliable page condition before calling the screenshot method.
- The wrong part of the page is visible. A page screenshot captures the current browsing context. Scroll or interact before capture, or use an element screenshot if only a particular component is needed.
- The element screenshot fails. Check that the selector matches an element and wait until it is visible before capturing. A missing or hidden target cannot produce the intended element image.
- The test works in IDE playback but not in the runner. The runner is a separate execution path. Verify its browser and driver setup, reproduce the test steps in the configured environment, and set up screenshot capture in the runner or exported WebDriver code.
- The browser remains open after an error. Put
driver.quit()in afinallyblock so the browser closes whether the test succeeds or fails.
Cost, performance, and reliability considerations
WebDriver capture adds work to your test: the browser must load the page and reach the target state before the image can be saved. Reliability depends on synchronizing against meaningful page conditions rather than capturing immediately after navigation. Prefer explicit waits for the content or element you need over arbitrary timing where possible.
PC Slower Than It Used to Be?
A free scan shows the junk files, broken settings and background clutter dragging Windows down - then fixes them in one click.Free scan · Windows 10 & 11Outdated 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 matchFor repeatable evidence, use stable selectors, deterministic test data, and a predictable viewport and browser setup. Save files with distinct names when capturing multiple cases so later captures do not overwrite earlier ones. Selenium IDE and WebDriver are software workflows; no screenshot pricing or usage allowance is specified in the Selenium IDE documentation cited here.
Frequently asked questions
Can I take a screenshot from a Selenium IDE .side file?
Yes, as part of an execution workflow that adds screenshot capture in the command-line runner or in a WebDriver implementation of the flow. The .side file itself does not contain the resulting screenshot.
Best Value
Can execute script save an image?
Not to an arbitrary local path through the documented IDE extension workflow. It runs page JavaScript; use host-side WebDriver code for screenshot capture and file saving.
Can WebDriver capture a single element instead of the page?
Yes. Selenium WebDriver provides element screenshot methods in addition to page screenshot methods; use the element method after locating the target.
