Do these 3 things before closing this tab:
1Fix the driver behind crashes, sound loss and screen glitches2Repair Windows errors before they cause bigger problems3Scan for outdated or missing drivers - takes under a minuteCypress Test Replay can show canvas elements as they rendered during a recorded CI run, giving you visual context for debugging interfaces such as maps, charts, and games. Cypress documents what you can see and how to turn canvas capture off, but does not publish the underlying capture mechanism or a numeric estimate of its performance cost.
What Test Replay shows for a canvas
Test Replay is a Cypress Cloud feature for examining recorded Cypress test runs. Its captured data includes the DOM, network activity, console output, JavaScript errors, and element rendering. For canvas elements, Cypress says you can see them as they rendered in the CI run.
This is visual context within a replay of a recorded run; the documentation does not describe it as a video of the canvas. It also does not explain the internal capture technique, so claims about how pixels are read, serialized, or captured over time would go beyond what Cypress documents.
When canvas capture is useful—and when it can cost performance
Seeing the canvas as it rendered can help when a failure involves a map, chart, game, or another interactive interface whose important output is drawn inside a canvas element. The trade-off is resource use: Cypress warns that capturing numerous or large canvases can be resource-intensive and recommends monitoring test performance.
Free tools Windows power users keep installed
One-click scans. No signup required.
There is no published canvas-specific overhead figure or universal threshold for deciding when to disable capture. Compare performance in your own CI environment, considering the number and size of canvases and how valuable their visual context is when investigating failures.
How to disable canvas capture
- Open the project in Cypress Cloud and go to the project settings.
- Find the Test Replay section.
- Locate the canvas capture control below the main Test Replay recording toggle, then turn canvas capture off.
- Compare test performance with canvas capture disabled and decide whether the reduction is worth losing the canvas context during replay.
Cypress also recommends disabling video recording when Test Replay is enabled to optimize performance. Treat video and replay as separate artifacts: keep the ones your debugging workflow needs, and assess their performance impact in your CI environment.
If canvas content is missing or replay is costly
- Check shadow DOM: Test Replay does not support shadow DOM canvases. Cypress also lists manual slot assignment as an unsupported shadow DOM behavior; check whether the canvas is inside a shadow root using that behavior.
- Check the capture setting: Confirm that canvas capture is enabled in the project’s Test Replay settings if you expect canvas content to appear.
- Check broader replay support: Cypress documents limitations for runs recorded below Cypress App v13 and for Firefox or WebKit test runs.
- Measure in CI: If replay capture appears expensive, compare runs with canvas capture enabled and disabled. Cypress advises monitoring performance but gives no numeric cutoff.
Test Replay is not visual testing
Test Replay provides a timeline for examining a recorded run and its debugging data. Cypress visual testing, by contrast, uses image snapshots; its guidance emphasizes stable application state and a consistent rendering environment for comparable results. A replay is useful for understanding what happened during a run, while snapshot-based visual testing is aimed at comparing rendered images.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.When a standalone screenshot is enough
If you need a standalone screenshot rather than a replay of a Cypress test run, ScreenshotNeo is a separate screenshot API and MCP server to consider. It is not a substitute for Test Replay’s timeline or debugging data; it is for capturing a page as an image or PDF. Its documented options include full-page capture and capturing an element by CSS selector.
For that narrower screenshot task, ScreenshotNeo’s stated billing policy is that bot checks/CAPTCHAs, blank pages, timeouts, failed loads, and cache hits cost nothing. Its MCP server includes screenshot and page-information tools for AI agents.
ScreenshotNeo offers 1,000 screenshots a month free with no card; paid plans start at $5 for 3,000. Sign up for free.
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.
