Skip to content
midgeDocs
Browser DevToolsHow to capture network traffic in Chrome
Browser DevTools

How to capture network traffic in Chrome

Capture network traffic in Chrome with the DevTools Network panel: record, preserve the log, disable cache, throttle, filter, copy as cURL and save.

To capture network traffic in Chrome, open DevTools (F12, Ctrl+Shift+I, or Cmd+Option+I on Mac), click the Network tab, check Preserve log, and reload the page or perform the actions you want to record. Chrome lists every request the page makes, with its status, type, size, timing and a waterfall, and records as long as DevTools stays open. Click any request to see its headers, payload, response and timing breakdown.

From there you can filter to the requests that matter, slow the connection down with throttling, copy a single request as a cURL command, or export the whole session as a HAR file. This guide covers each of those, following Chrome’s DevTools documentation. Labels move between Chrome versions now and then, so look for the closest match if a name differs slightly.

Open the Network panel

  1. Go to the page you want to inspect.
  2. Open DevTools: F12 or Ctrl+Shift+I on Windows and Linux, Cmd+Option+I on Mac, or the three-dot menu, then More tools, then Developer tools.
  3. Click the Network tab.

The first time, the table may be empty. Chrome records only while DevTools is open, so requests made before you opened it are not there. Reload the page to capture everything from the start.

By default the table shows columns such as Name, Status, Type, Initiator, Size and Time, plus a waterfall. Right-click the table header to add more, such as Domain or Method. Hover over a name to see the full URL.

Control the recording

Record button. The round button at the top left is red while Chrome is recording. Click it, or press Ctrl+E (Cmd+E on Mac) with the panel focused, to pause and resume.

Clear. The clear button empties the table. Clear right before you reproduce something, so the list is short and easy to read.

Preserve log. Check this to keep requests across page loads. Without it, every navigation clears the table, which hides requests made just before a redirect, such as a failed sign-in or a payment callback.

Disable cache. Check this to emulate a first-time visitor. Chrome stops using its cache while DevTools is open, so you see every file being downloaded. It also helps when you suspect a stale file. To clear the cache once instead, right-click the table and choose Clear browser cache.

Simulate slow or offline connections

Many bugs only appear on slow networks: spinners that never stop, double submissions, timeouts. Use the Throttling drop-down in the action bar. It is set to No throttling by default and offers presets for fast 4G, slow 4G and 3G, as well as Offline.

To create your own profile, open the drop-down and choose Custom, then Add…, and set download speed, upload speed and latency in the Throttling settings. DevTools shows a warning icon on the Network tab while throttling is on, so you do not forget it. Throttling also applies to WebSocket connections.

Throttling is an approximation. It is useful for reproducing timing bugs, but it is not a precise measurement of how your site performs on a real mobile network.

Filter to the requests that matter

A modern page can make hundreds of requests. Filters get you to the right one quickly.

Type buttons. Click Fetch/XHR to see only the API calls the page’s JavaScript made. Other buttons include JS, CSS, Img, Media, Font, Doc, WS (WebSocket), Wasm, Manifest and Other. Hold Ctrl (Cmd on Mac) to select more than one.

Filter box. Type text to match URLs, a regular expression like /api\/(cart|checkout)/, or a negative filter like -analytics. Check Invert to show everything that does not match.

Property filters. Combine them with spaces; they work as AND:

status-code:500
method:POST domain:api.example.com
larger-than:100k
mime-type:application/json domain:*.example.com

More filters. Options such as Hide data URLs, Hide extension URLs, Blocked requests and 3rd-party requests cut more noise. Hiding extension URLs is useful when a browser extension is making its own requests.

Time filter. Drag across the overview timeline at the top to show only requests that were active during that window.

Inspect a request

Click a request to open its details:

  • Headers: the URL, method, status code, and request and response headers.
  • Payload: query string parameters and form data or JSON sent with the request.
  • Preview: a formatted view of the response, such as a JSON tree or a rendered image.
  • Response: the raw response body.
  • Initiator: what triggered the request, such as a script and line number, and the chain of requests that led to it.
  • Timing: how long each phase took: Queueing, Stalled, DNS Lookup, Initial connection, Request sent, Waiting (TTFB) and Content Download.
  • Cookies: cookies sent and received, including any that were blocked.

To search across all captured headers, payloads and responses, press Ctrl+F (Cmd+F on Mac) with the panel focused. This is the fastest way to find which request returned a specific error message or ID.

Copy a request as cURL or fetch

Right-click a request and choose Copy to get it in a form you can rerun or share:

  • Copy as cURL for the command line.
  • Copy as fetch or Copy as fetch (Node.js) for JavaScript.
  • Copy as PowerShell on Windows.
  • Copy response for just the body.

A copied request is great for a bug report because a developer can run it directly. Be careful: it carries the request’s headers, which can include cookies and an Authorization token. Replace those values before you paste the command into a shared channel.

Chrome can also resend a request: right-click and choose Edit and resend as fetch to open it in the Console, change it, and press Enter.

Capture screenshots of the page loading

To see what the page looked like while requests were loading, open the Network panel’s own settings (the gear inside the panel) and select Capture screenshots. Reload, and Chrome shows thumbnails of the page as it loaded. Click one to filter out the requests that started after that moment.

Save and share what you captured

To give someone the whole session, export it as a HAR file. Click Export HAR (sanitized)… in the action bar, or right-click and choose Copy, then Save all as HAR (sanitized). The sanitized export leaves out Cookie, Set-Cookie and Authorization headers, but URLs, bodies and responses can still contain tokens and personal data. Clean the file with the HAR sanitizer before sending it. The full walkthrough is in how to export a HAR file in Chrome, and the HAR viewer opens the result in any browser.

To open a HAR file someone sent you, click Import HAR in the action bar or drag the file onto the table.

A practical routine for bug reports

  1. Open DevTools and the Network panel before you start.
  2. Check Preserve log and clear the list.
  3. Reproduce the bug once, slowly.
  4. Filter to Fetch/XHR and look for red rows or 4xx and 5xx status codes.
  5. Click the failing request and copy the URL, status and error message from Response into your report.
  6. Check the Console for errors at the same moment; see how to export console logs in Chrome.
  7. Attach a sanitized HAR file if the developer needs the full picture.

Capture network traffic without opening DevTools

The routine above works, but it relies on DevTools being open before the bug happens. Midge, a free Chrome extension, captures fetch, XHR and WebSocket traffic with bodies and timings, plus status, size and timing for other resources, and keeps recent activity in memory so a screenshot taken right after a failure still includes it. Every recording includes console logs, network requests, user actions and device info. Passwords, card numbers, tokens and cookies are redacted in your browser before anything leaves your device. See the network logs feature page for details.

Official documentation

The browser steps above were checked against these pages on November 10, 2026. Browser menus change between versions, so the official pages are the place to look if a label has moved.

Frequently asked questions

Does Chrome record network traffic when DevTools is closed?

No. The Network panel records requests only while DevTools is open, so open it before you reproduce the problem.

How do I keep requests after a page reload or redirect?

Check Preserve log in the Network panel. Chrome then keeps every request until you turn the option off or clear the list.

How do I share captured network traffic?

Export it as a HAR file with Export HAR (sanitized) in the Network panel action bar, then remove remaining secrets with a HAR sanitizer before sending it.

Can I capture traffic from other apps on my computer?

Not with DevTools. The Network panel only shows requests made by the page or tab you are inspecting. System-wide capture needs a proxy or packet capture tool.