Packet Path/

10 Wireshark Display Filters You'll Use Every Week

Display filters turn a million-packet capture into an answer. Ten patterns that cover 90% of real troubleshooting, plus the two mistakes everyone makes.

Troubleshooting · Beginner · 8 min · September 30, 2026

Illustration of a magnifying lens over flowing packet streams
In plain EnglishA packet capture is hours of security-camera footage: the answer is in there, but you can't watch it all. Display filters are the search box — they hide everything except the packets you ask about, without deleting anything. This article gives you the ten searches you'll reuse every week, shows where they differ from capture filters (which decide what gets recorded in the first place), and lets you click a filter against a real dissected frame to see exactly which bytes it matches.

The security-footage analogy

Imagine a convenience store with 20 cameras recording around the clock. When something goes wrong, nobody watches all 20 feeds end to end — you search: "show me camera 4 between 2 and 3 a.m." Wireshark's display filter is that search box. The full recording (the capture file) stays intact; the filter just decides which moments appear on screen. A capture filter, by contrast, is deciding before the incident which cameras even record — great for saving disk, terrible if you guessed wrong and the crucial camera was off.

The one distinction that matters

Wireshark speaks two filter languages. Capture filters (BPF, Berkeley Packet Filter — the kernel-level syntax used when capturing) decide what gets recorded — syntax like host 192.168.1.10 and tcp port 443. Display filters hide what you don't want to see after the fact — syntax like ip.addr == 192.168.1.10 && tcp.port == 443. Capture filters save disk; display filters save sanity. Watch the difference:

Capture filter (BPF) tcp port 443 — decides what is recorded Display filter tcp.port == 443 — decides what is shown BPF drops non-matching here display filter hides here capture file: 2 pkts capture file: 4 pkts :443 :80 :443 :80 ✕ ✕ :443 :80 :443 :80 Left: port-80 packets are destroyed at capture time. Right: everything is recorded; the filter only hides.
Capture filter vs display filter. On the left, BPF discards non-matching packets before they reach the disk. On the right, all 4 packets are recorded and the display filter merely dims the non-matches. When in doubt, capture wide and filter the display.

Watch: a display filter at work

Six packets stream past. The filter tcp.port == 443 keeps the HTTPS traffic bright and dims the rest:

capture: everything view: matches only tcp.port == 443 port 80 port 443 port 53 port 443 port 22 port 443 ▼ filter gate ▼
Six packets captured, three shown. Port-443 packets stay bright past the filter gate; everything else dims.

The ten

Each of these is a display filter (Wireshark syntax). The Wireshark display filter builder tool on this site constructs them for you — but knowing what they mean is what makes you fast in an incident:

Try it: click a filter, see the bytes it matches

Below is one real frame — Ethernet + IPv4 + TCP, 54 bytes — as Wireshark would dissect it. Click any filter chip to light up the exact bytes that filter looks at:

Click a filter above — matching bytes highlight in amber.

offset  00 01 02 03 04 05 06 07 08 09 0a 0b 0c 0d 0e 0f
0000    00 1b 2c 3d 4e 5f 00 1a 2b 3c 4d 5e 08 00 45 00
0010    00 36 1c 46 40 00 40 06 6b 2c c0 a8 01 0a 5d b8
0020    d8 22 cc 75 01 bb 8f 2c 41 d0 5e 11 22 33 50 18
0030    fa f0 9a bc 00 00