Some links on this page are affiliate links: if you buy through them we may earn a commission, at no extra cost to you.
Start by checking that Cypress is actually recording: video recording is off by default, and Cypress records videos during cypress run, not cypress open. Then determine whether the video file itself is blank or whether only Cypress Cloud’s playback view is stuck. Those are different symptoms and need different checks; there is no single documented fix for every blank Cypress video.
First confirm Cypress is supposed to record a video
Cypress records a video for each spec when video recording is enabled and the tests run with cypress run. It does not record videos during cypress open, so switching to the interactive runner will not produce a video artifact.
In cypress.config.js, enable recording in the configuration object:
const { defineConfig } = require('cypress')
module.exports = defineConfig({
video: true,
e2e: {
// Keep your existing e2e configuration here.
},
})For a TypeScript configuration, use the equivalent setting in cypress.config.ts:
import { defineConfig } from 'cypress'
export default defineConfig({
video: true,
e2e: {
// Keep your existing e2e configuration here.
},
})Run the suite from a terminal with npx cypress run. Cypress saves videos per spec in the configured videosFolder; unless changed, that folder is cypress/videos. Cypress clears the videos folder before a run by default. If you need to preserve existing assets while diagnosing, check the trashAssetsBeforeRuns setting and set it to false only if retaining the folder contents is intended.
If you already use a configuration file, add or verify video: true without replacing your other project settings. A missing file after a run may mean video is disabled, the run used cypress open, the output folder is different from the one you checked, or cleanup removed an older artifact.
Determine whether the file or the Cloud player is blank
Before changing browser settings or adding CI capacity, inspect the actual video artifact if you can access it. Compare the downloaded or locally saved file with the Cypress Cloud playback view:
- The artifact plays normally, but Cloud remains on a loading screen: investigate the Cloud playback display separately from recording. A historical Cypress issue reported a Cloud view stuck at “tests loading” even though test outcomes were available. That report is an example of a playback symptom, not evidence of how often it occurs now or of a confirmed cause.
- The artifact itself is blank, frozen, or incomplete: focus on recording, the browser, the spec, and the execution environment.
- No artifact exists: verify recording is enabled, that you ran
cypress run, and that you checked the configured output directory after the run.
Do not treat a stuck Cloud player as proof that the underlying video file is empty. Conversely, a Cloud page that loads correctly does not establish that every downloaded artifact is playable.
Reduce the failure to a reproducible test
Unexpected recording behavior is easier to isolate when the test is small and the run conditions are recorded. Cypress recommends reducing a problem to the smallest reproduction that still shows it, splitting large spec files and long tests, and comparing browsers and environments.
- Record the conditions. Note the Cypress version, browser, operating system, whether the run was local or in CI, the exact command or invocation mode, and whether the problem affects one spec or several.
- Run the affected spec alone. If the video is blank only in a long suite, run the smallest affected spec rather than repeatedly changing unrelated tests.
- Compare local and CI runs. Use the same spec and browser where possible. If only CI shows the symptom, investigate the CI environment; if both do, look for a reproducible project, browser, or configuration factor.
- Compare browsers and versions. Change one variable at a time so a result can be attributed to the browser or version being tested rather than several simultaneous changes.
- Keep other evidence. Screenshots and, where available, Cypress Cloud Test Replay can help show what happened during the test even when the video is unhelpful.
A historical GitHub report described a blank video in a specific old environment (Cypress 1.4.2, Electron 53, Windows 10). It is useful only as evidence that blank-video reports have occurred; those version details are not current compatibility guidance. Likewise, a report involving headed mode does not establish headed mode as a fix. Reproduce the issue with the Cypress version and runner mode you actually use.
If CI video freezes or drops frames, check resources
Cypress identifies insufficient CI container resources as a possible cause of recordings that freeze or drop frames. This guidance applies to those symptoms; it does not prove that low resources explain every completely blank page or video.
Quick wins for a faster PC:
Clear out junk files and repair common Windows errorsFree Scan →Scan for outdated or missing drivers - takes under a minuteDriver Scan →Repair Windows errors before they cause bigger problemsFix Now →- Enable or inspect CPU and memory logs for the CI job while the failing spec runs.
- Check whether the problem correlates with a larger spec, a busy runner, or a particular CI environment.
- If measurements indicate resource pressure, try a more powerful CI container or provider and compare the resulting artifact.
Make a capacity change as a test of the resource hypothesis, not as a guaranteed cure. Preserve the same spec and other relevant conditions during the comparison.
Use Cypress logging and targeted diagnostics
If a minimal reproduction still fails, use diagnostics that match the suspected stage of the failure.
Turn on video recording logs
Cypress documents the DEBUG=cypress:server:video environment variable for video recording logs. For example, on macOS or Linux:
DEBUG=cypress:server:video npx cypress runOn Windows Command Prompt, set the variable for the command session and then run Cypress:
set DEBUG=cypress:server:video
npx cypress runUse the resulting log output to investigate recording behavior around the affected run; the setting is diagnostic, not a repair by itself.
Isolate Command Log performance or browser-crash symptoms
If the failure comes with performance problems or browser crashes and you suspect the Command Log, Cypress documents two diagnostic options: CYPRESS_NO_COMMAND_LOG=1 and --no-runner-ui. For macOS or Linux, the environment-variable form is:
CYPRESS_NO_COMMAND_LOG=1 npx cypress runThese options are for isolating a suspected Command Log or runner UI issue. Disabling the Command Log means screenshots and videos will not include it, so this comparison also changes what appears in the artifact.
Investigate compression only when it fits the symptom
Cypress exposes videoCompression as a CRF setting. Cypress documents that setting it to false or 0 skips encoding. This is worth investigating when the available evidence points to compression or encoding; it is not a documented general fix for blank video.
Do not change compression, browser, CI capacity, and runner UI together. If you need to test a compression hypothesis, keep the rest of the reproduction stable and compare the resulting artifact. A configuration change that alters file processing will not explain a Cloud-only loading display unless the artifact itself also changes.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Common symptoms and the next check
| Symptom | Check first | What the result tells you |
|---|---|---|
| No video file after the run | Confirm video: true, use cypress run, and inspect the configured videosFolder. |
These checks establish whether a recording was requested and where Cypress writes it. |
| Cloud is stuck loading, but the downloaded file works | Separate the Cloud playback issue from the artifact and retain the file for comparison. | The recording exists and plays; the symptom is specific to the Cloud view. |
| Video freezes or drops frames in CI | Inspect CPU and memory logs and compare the same spec in another environment. | If resource pressure is present, test a more capable container or provider. |
| Video is blank in both local and CI runs | Reduce to one spec, note the browser and Cypress version, and compare browser/environment conditions. | A small reproduction gives a more useful basis for further diagnosis than a full-suite change. |
| Browser crashes or performance degrades while recording | Try the documented Command Log diagnostics and note that the artifact will omit the Command Log. | This can test whether the Command Log or runner UI is implicated; it does not establish a universal recording fix. |
Or skip the browser setup
ScreenshotNeo is a website screenshot API, not a Cypress video recorder, so it does not repair or replace Cypress test videos. It can provide a separate screenshot of a URL when you need a visual reference alongside your Cypress diagnostics. For example, this cURL request captures a page as a WebP image:
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 for request details. ScreenshotNeo removes cookie/consent banners, newsletter popups, and chat widgets before capture, with each step configurable. 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 offers take_screenshot, get_page_info, and capture_pdf tools for AI agents. The free plan includes 1,000 shots per month with no card, and paid plans start at $5 for 3,000 shots.
Sign up for ScreenshotNeo’s free plan to try up to 1,000 screenshots a month with no card.
The Tool Desk
Outbyte PC Repair FREERepair Windows errors before they cause bigger problemsFix Now →Outbyte Driver Updater FREEFix the driver behind crashes, sound loss and screen glitchesFind Drivers →When to escalate a persistent blank artifact
If the file remains blank after confirming the recording configuration and reproducing the issue in a small test, prepare a concise report rather than a list of speculative fixes. Include the Cypress version, browser and version, operating system, exact run command, local-versus-CI result, relevant configuration, the smallest reproducible spec, and whether the local artifact and Cloud playback behave differently. Attach the relevant video or diagnostic logs when appropriate. This gives maintainers enough context to distinguish a recording failure from a playback display problem or an environment-specific failure.
Frequently Asked Questions
Does Cypress record videos while I use cypress open?
No. Cypress video recording is for runs started with cypress run.
Is a blank Cypress Cloud player proof that the video file is blank?
No. Check the actual video artifact separately; a Cloud playback display and the saved file can show different symptoms.
Will increasing CI resources fix every blank test video?
No. Cypress connects insufficient CI resources to frozen or dropped frames, not to every possible blank-video failure.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
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.
