In Cypress 15.4 and later, open a test in the Cypress App, select Options in the Command Log header, and turn off Show HTTP Requests. This hides displayed XHR and Fetch entries; it does not stop requests or change test execution. For code-level control, use log: false on an intercept or, separately, on a cy.request() command.
Hide HTTP requests in the Cypress App
- Open the test in the Cypress App.
- In the Command Log header, open Options.
- Deselect Show HTTP Requests.
The setting hides XHR and Fetch entries from the visible Command Log. The requests still run, and you can still use cy.intercept() to spy on or stub them. This is a display preference, not a network filter. Cypress announced the option for Cypress 15.4 and later in November 2025; the release listing includes Cypress 16.0.0, released September 1, 2026. Cypress’s announcement and release listing provide the version details.
Suppress application request logs in test code
To suppress default Command Log entries for matched application XHR and Fetch traffic, Cypress documents this catch-all intercept:
cy.intercept({ resourceType: /xhr|fetch/ }, { log: false })Define the intercept before the action that triggers the requests, as you would with other intercepts. The option controls logging; it does not cancel, stub, or otherwise alter matching requests. Cypress’s cy.intercept() API reference marks resourceType deprecated since Cypress 14. Check the current reference and your installed Cypress version before adopting this exact matcher; don’t assume the deprecation note means the App toggle is unavailable.
The Tool Desk
Outbyte Driver Updater FREEScan for outdated or missing drivers - takes under a minuteDriver Scan →Outbyte PC Repair FREERepair Windows errors before they cause bigger problemsFix Now →Hide the log for one static stub
If you are intercepting a specific route with a static response, set log: false in the response object:
cy.intercept('GET', '/api/items', {
log: false,
statusCode: 200,
body: [{ id: 1, name: 'Example item' }]
})This example suppresses logging for that defined stub. The route still returns the specified response. Cypress illustrates the option in its network requests guide.
Hide a cy.request() command entry
cy.request() has a separate log option, which defaults to true. Set it to false in the command options to hide that command’s entry:
cy.request({
method: 'GET',
url: '/api/items',
log: false
})This is not the same as hiding browser-originated XHR or Fetch entries. Cypress issues cy.request() from its Node process, outside the browser proxy used by cy.intercept(). See the cy.request() API reference and Cypress App FAQ.
Choose the right logging control
| What you want to hide | Use | Scope and caveat |
|---|---|---|
| Visible XHR and Fetch entries while exploring or debugging | App Options → deselect Show HTTP Requests | Available in Cypress 15.4+; display only, no effect on execution. |
| Default logs for matched application XHR and Fetch traffic | cy.intercept({ resourceType: /xhr|fetch/ }, { log: false }) |
Code-level control; resourceType is deprecated since Cypress 14. |
| A particular static intercepted response | Put log: false in the static response object |
Applies to that defined route. |
A cy.request() command entry |
Set log: false in its options |
Separate from browser XHR/Fetch logging. |
Troubleshooting
The HTTP request entries are still visible
- Confirm you changed the Command Log header’s Show HTTP Requests option in the Cypress App, rather than expecting a test configuration or network setting to change the display.
- If you need a code-level rule, ensure the intercept is defined before the request-triggering action and that the request is in the traffic matched by your route.
- For the catch-all resource-type example, check the current
cy.intercept()documentation because Cypress marksresourceTypedeprecated since version 14.
The request stopped being intercepted or stubbed
Hiding a Command Log entry should not stop a request. Check the intercept’s route matcher and timing, and make sure the static response is configured as intended. log: false is a logging option, not a way to block traffic.
cy.intercept() did not hide cy.request()
Use log: false in the cy.request() options. It has its own command log setting and does not travel through the browser proxy intercepted by cy.intercept().
Rank #4
Or skip the browser setup
For a separate workflow—capturing clean website screenshots by API—ScreenshotNeo provides a one-call option. It does not change Cypress Command Log visibility or replace the Cypress settings above.
cURL:
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 setup and options. Before capture, it accepts cookie or consent banners as a visitor and removes more than 60 known consent platforms, newsletter popups, and chat widgets; each step can be turned off. Bot checks, blank pages, timeouts, failed loads, and cache hits are not billed. An MCP server provides screenshot tools for AI agents, and the free plan includes 1,000 screenshots per month with no card; paid plans start at $5 for 3,000. Sign up for 1,000 free screenshots a month, with no card required.
Quick wins for a faster PC:
Scan for outdated or missing drivers - takes under a minuteDriver Scan →Repair Windows errors before they cause bigger problemsFix Now →Frequently Asked Questions
Does hiding HTTP requests change Cypress test results?
No. The App option changes what is displayed in the Command Log; requests still run.
Best Value
Can I hide only one intercepted request’s log entry?
Yes. For a static stub, include log: false in its response object.
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.
