Network Tab+

A DevTools network panel you can tidy up: hide noisy requests for good and save the filters you keep reaching for.

Network Tab+ adds a network panel to Chrome DevTools that you can tidy up and keep tidy. The built-in Network tab shows you everything, every time. Every analytics beacon, every polling request, every font. Network Tab+ remembers what you don't want to see and what you keep looking for, so the list in front of you is only the traffic you care about. It sits next to Network as its own DevTools tab. Nothing to configure, no account, no servers. ━━ HIDE REQUESTS, PERMANENTLY ━━ Right-click any request and choose how much to hide: • This request only — removes that single row until you clear the log • All with this path — hides every request to that path, whatever the query string, so /heartbeat?t=1739 and /heartbeat?t=1740 both disappear from one rule • All from this domain — hides everything from that host Before you choose, tick "Apply on every site" and the rule follows you everywhere. Leave it unticked and the rule only applies to the site you made it on. Site-scoped is the default, so a rule you create while debugging one app will not quietly affect another. Rules are saved immediately and survive page reloads, DevTools being closed, and browser restarts. The Hidden button in the toolbar carries a live count of how many requests are currently being suppressed. Click it and a drawer lists every rule you have, split into "This site" and "Everywhere", each showing what kind of rule it is and how many requests it has swallowed in this session. Hover any rule to un-hide it, or clear them all at once. The status bar keeps a running "N hidden by M rules" so hidden traffic is never invisible in a way that could mislead you. ━━ SAVE THE FILTERS YOU KEEP RETYPING ━━ Build up a filter, then save it as a named tab. Click a tab to apply it, and the text box, method, status and type selections all restore together. • Double-click a tab to rename it • Change anything while a saved filter is active and a dot appears next to its name, with a Save button to update it in place • Click "All" to clear back to everything • Press the + to save whatever you currently have set up Saved filters are stored per browser, not per site, so the views you build are available wherever you are working. ━━ FIND ANYTHING, INSIDE ANY REQUEST━━ The filter box only matches URLs. Press ⌘F (Ctrl F on Windows and Linux) and search inside the requests themselves — the URL, the headers, the payload, the response body, or any combination of them. • Pick your scope. All is the default; narrow it to just URL and Headers when you want instant results, or include Response to search bodies. • Matching requests filter the table, and a "Where it matched" column tells you which part of each one hit. • Narrow by field: type "status" in the field box and "active" in the search, and it matches only where a key named status holds that value. Works on JSON keys at any depth, header names and URL parameters. • Response bodies load in batches behind a progress bar you can stop at any time. Results appear as they are found. • The same syntax as the filter box: plain text, -word to exclude, /regex/ for patterns. ━━ FILTERING ━━ The filter box understands three things, and you can combine them: • Plain text matches anywhere in the URL — api • A leading minus excludes — -heartbeat • Slashes make it a regular expression — /v[12]\/users/ So "api -telemetry /graphql|rest/" is a valid filter. Resource type chips match Chrome's own set: All, Fetch/XHR, Doc, CSS, JS, Font, Img, Media, Manifest, Socket, Wasm and Other. "All" clears the type selection. Method and status filters are available but hidden by default, because most people do not change them daily. Open "More filters" and tick Method or Status to reveal those rows. Each entry shows how many values are currently active, so a filter you have hidden can never silently affect your results. "More filters" also holds: • Hide data: URLs — drops inline data: URIs from the list • Third-party only — hides requests to the page's own origin, leaving only external traffic ━━ GRAPHQL ━━ GraphQL requests all look identical in a normal network tab: a column of rows called "graphql" with no way to tell them apart. Network Tab+ detects GraphQL by the shape of the request body rather than the URL, so it works whatever your endpoint is called — /graphql, /api/gql, anything. • The query is printed using the official GraphQL parser, correctly indented with one field per line. This works even when your production build has minified the document onto a single line, which is where copying from the raw payload normally falls apart. • Variables are shown as a separate block, because every GraphQL IDE wants the query and variables pasted into different panes. • Each has its own one-click Copy button, and the right-click menu adds "Copy GraphQL query" and "Copy GraphQL variables" — but only on GraphQL requests, so the menu stays short everywhere else. • Turn on the "GraphQL operation" column and five rows called "graphql" become GetViewer, UpdateTask, SearchTasks and so on. Batched requests, where a client sends several operations in one POST, are listed and numbered individually. GraphQL sent over GET with the query in the URL is handled too. Persisted queries, where the client sends only a hash, are labelled as such rather than showing an empty or broken panel. ━━ INSPECTING A REQUEST ━━ Click a row to open the detail pane: • Headers — request URL, method, status, remote address, protocol and timing, plus the full response and request headers • Payload — query string parameters and the request body, pretty-printed when it is JSON • Response — the response body, pretty-printed and syntax-highlighted when it is JSON Payload and Response each have a one-click Copy button. No selecting, no unescaping, no scrolling to find where the JSON ends. Drag the pane's left edge to resize it, or press Expand to give it the full panel width for reading a long response. Your chosen width is remembered. ━━ THE TABLE ━━ Fourteen columns are available. Seven are shown by default — Name, Method, Status, Type, Size, Time and Domain — and the rest can be switched on from the Columns button or by right-clicking any column header: GraphQL operation, Path, Full URL, Initiator, Protocol, Started, Priority Every column is sortable and resizable, columns can be dragged into a different order, and each has a minimum width so the table scrolls sideways rather than squashing a column into nothing. Your column choices persist. Status codes are colour-coded: green for 1xx and 2xx, amber for 3xx, red for 4xx and 5xx. Methods are colour-coded too. Sizes and times use tabular figures so the columns line up. Other controls: pause and resume recording, clear the log, and Preserve log to keep requests across page navigations. ━━ COPYING ━━ From the right-click menu on any request: • Copy URL • Copy as cURL — a complete, runnable command with headers and body • Copy payload • Copy response • Copy GraphQL query and Copy GraphQL variables, on GraphQL requests • Filter to this domain, to narrow the list to one host in a click ━━ APPEARANCE ━━ The panel follows your DevTools theme automatically, in both light and dark. The layout reflows rather than clipping, so it stays usable in a narrow docked panel as well as full screen. ━━ PRIVACY ━━ Network Tab+ requests one permission: "storage". That is used to remember your hide rules, saved filters and column preferences between sessions. There is no account, no sign-in, no backend, and no network access of any kind. The extension cannot make requests and does not ask for access to any website. Everything it records stays in your browser, and nothing is ever transmitted, analysed or sold. ━━ NOTES ━━ Like the built-in Network tab, Network Tab+ only records while DevTools is open. The most recent 5,000 requests are kept per session. Requires Chrome 111 or later. Works in any Chromium browser, including Brave and Edge.