Cypress Studio is an interactive feature in the Cypress App’s open mode that records browser actions as editable Cypress end-to-end (E2E) test code. You can add assertions yourself without Cypress Cloud; the optional Studio AI layer can recommend assertions, but requires a Cypress Cloud account and a linked project.
What Cypress Studio does
Studio turns supported interactions with your application into Cypress commands and writes them into a spec file. You can record a new test or add steps to an existing one, then inspect and edit the generated code inline. It is a way to bootstrap or extend an E2E test—not an automatic crawler that explores the whole application.
As an Amazon Associate I earn from qualifying purchases.
Studio runs in the Cypress App’s open mode. Cypress describes the generated tests as readable, editable code, so treat the recording as a starting point: review its selectors, assertions, and behavior before relying on the test.
See Cypress’s Cypress Studio guide and documentation on open mode.
Studio versus Studio AI
| Capability | Studio without AI | Studio AI |
|---|---|---|
| Record interactions and generate E2E commands | Yes | Yes |
| Add assertions | Manually | Manually, or review and select AI recommendations |
| Edit generated test code inline | Yes | Yes |
| Cypress Cloud account and linked project | Not required | Required |
Studio AI observes the interactions you perform and may suggest assertions based on resulting UI changes. You choose whether to keep its suggestions. It does not replace reviewing the test yourself. Cypress explains the broader distinction in its AI in Cypress overview.
Check requirements and fit before recording
- Internet access and sourcemaps: Studio requires both. Sourcemaps are enabled by default in most Cypress configurations, according to the Studio guide; check your project configuration if Studio does not work as expected.
- For Studio AI: use Cypress 15.11.0 or later, sign in to Cypress Cloud, and link the project. Core Studio recording and manual assertions do not require Cloud.
- Test type: Studio is for E2E tests. It does not support Component Testing or Cucumber-style tests.
- Browser context: it cannot record across multiple origins and does not support interactions inside iFrames or Shadow DOM.
- Dynamic pages: animation or transitional UI states can affect AI recommendations. Large pages may exceed the AI context window and return no recommendations.
Studio is available by default in the current Cypress documentation. Do not add experimentalStudio to your configuration: the option is retired and causes Cypress to error if configured. See the experimental features reference and version migration guide.
Record a new test
- Open the Cypress App and choose the spec file or suite where the test belongs.
- Choose New Test, enter a descriptive test name, and provide your application URL.
- Cypress adds a
cy.visit()command and opens the Studio panel. Interact with the application as a user would. - Studio records supported actions in real time:
.click(),.type(),.check(),.uncheck(), and.select(). - Add assertions manually, or review Studio AI’s recommendations if you have enabled it. Keep only assertions that express behavior your test should verify.
- Inspect and edit the generated code inline, then save and run the test to confirm it works as intended.
Extend an existing test
- Run the spec in the Cypress App.
- In the Command Log, hover over the test you want to extend and choose Edit in Studio.
- Studio runs the test through its last command. Continue interacting with the application to record additional steps.
- Review the appended actions and assertions in the code panel, edit as needed, and save the spec.
New actions and assertions are appended to the end of the test. If you need to change earlier logic, edit the generated test code rather than expecting the recording to rewrite existing steps.
Recommended Free Tools
Pause, inspect, and choose selectors carefully
You can pause recording to inspect elements or debug with browser DevTools, then resume. Studio chooses a unique selector using this priority order:
data-cydata-testdata-testiddata-qanameidclass- tag
- attributes
nth-child
Check that the selector it generated matches your team’s conventions and stays stable as the UI changes. Cypress documents Cypress.ElementSelector as the API for changing selector preferences used by Studio and cy.prompt(); consult the Studio guide for the current configuration details.
Troubleshoot common problems
- Studio is unavailable or recording does not start: confirm you are working with an E2E spec in the Cypress App’s open mode, that internet access is available, and that sourcemaps are enabled.
- Cypress errors at startup about
experimentalStudio: remove that retired configuration option; Studio is available by default in current documentation. - AI recommendations are unavailable: verify Cypress is version 15.11.0 or later, and that you are signed in to Cypress Cloud with the project linked. Core recording and manual assertions remain available without AI.
- No useful AI suggestion appears: the page may be too large for the AI context window, or an animation or transitional state may have obscured the UI change. Record a focused interaction and inspect the page in a stable state.
- An interaction cannot be recorded: check whether it crosses origins or takes place in an iFrame or Shadow DOM; these contexts are unsupported.
- The test breaks after recording: inspect the generated selector and command against the application’s current markup, then edit the spec and rerun it. A recording captures actions, but it does not guarantee the resulting test expresses the right assertion or remains valid after later UI changes.
Or skip the browser setup
If your goal is a screenshot rather than an E2E test, ScreenshotNeo offers a website screenshot API and MCP server. One GET request captures a URL as an image or PDF; its cleanup steps accept cookie and consent banners and remove known consent platforms, newsletter popups, and chat widgets before capture. Those steps can be turned off.
For example, save 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.webpSee the ScreenshotNeo API documentation. Bot checks and CAPTCHAs, blank pages, timeouts, failed loads, and cache hits cost nothing; response headers identify the page verdict and whether the request was billed. Its MCP server lets AI agents use take_screenshot, get_page_info, and capture_pdf. The free plan includes 1,000 screenshots per month with no card; paid plans start at $5 for 3,000.
Free tools Windows power users keep installed
One-click scans. No signup required.
Quick Recap
Sign up for ScreenshotNeo’s free plan.
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.
