Wireshark for Beginners: Your First Capture in Ten Minutes
Pick the busy interface, filter out the noise, follow one conversation and save it cleanly, all in your first session.
Ever wondered what your PC is actually saying to the internet while you sit there doing nothing? Wireshark shows you. Every DNS lookup, every connection, every packet, scrolling past in neat colored rows. The first time you open it, that wall of data looks like the Matrix. Ten minutes from now, it'll look like a list you can read.
This tutorial covers the basics in Wireshark 4.6: picking the right network interface, capturing, filtering the noise away, following a single conversation and saving the result. One ground rule first. Only capture on networks you own or are allowed to analyze, like your home network. Sniffing other people's traffic isn't a hobby, and in many places it's illegal.
Trick 1: Install it with Npcap and pick the busy interface
On Windows, Wireshark needs Npcap to capture live traffic. The Wireshark installer includes it, so leave that option ticked during setup. Without Npcap, you can still open saved capture files but you won't see any live interfaces. (If you skipped it, Npcap is also available on its own.)
Start Wireshark and you land on the welcome screen. The Capture section lists every interface Wireshark can use, each with a small sparkline graph showing current activity.
- Look at the sparklines. The interface whose line wiggles is the one carrying traffic. On a desktop that's usually Ethernet, on a laptop typically Wi-Fi.
- Hover over an interface to see its IP addresses. That's a quick way to confirm you have the right one.
- Double-click the interface. Capturing starts immediately.
The Capture section of the welcome screen on Windows. The wiggly line tells you which interface is busy.
Don't see any interfaces at all? Npcap is missing or didn't install correctly. Run the Wireshark installer again and make sure the Npcap component is selected.
Trick 2: Capture something worth looking at
Packets now pour in. To give yourself a clean sample, open a browser and visit two or three websites. Then stop the capture with Capture > Stop or the red square in the toolbar. Ctrl+E starts and stops a capture too, and Ctrl+R restarts it with the same settings.
Keep the first captures short, 30 seconds to a minute. A busy PC produces thousands of packets per minute, and a smaller file is easier to search through. You can always run another one.
Trick 3: Display filters turn chaos into answers
The long field above the packet list is the display filter bar. Type an expression there and press Enter (or click the arrow button on its right). Wireshark hides everything that doesn't match. Nothing is deleted: a display filter only changes what you see, and the capture stays complete.
The display filter bar sits right above the packet list. Shown here in an older Wireshark release.
The bar helps you while you type. Its background turns green when your expression is valid and red when it's incomplete or wrong. Protocol and field names are usually lowercase.
Good starter filters:
dnsshows only name lookups. You'll see every domain your PC asked for, including ones you never typed yourself.ip.addr == 192.168.0.1shows all traffic to or from one address. Swap in your router's IP or another device on your network.tcp.port == 443shows encrypted web traffic. Most sites use HTTPS today, so this is where your browsing lives.httpshows unencrypted web traffic. On a modern PC this list may be short, and that's good news.http.requestnarrows that down to the requests themselves.
Combine filters with and, or and not. For example, dns and ip.addr == 192.168.0.1 shows DNS traffic involving that one address. To remove a filter, click the clear button at the right edge of the bar.
You don't have to remember field names, either. Right-click a value in the packet list or the packet details and choose Apply as Filter, and Wireshark writes the expression for you. Prepare as Filter does the same but lets you edit it before applying. Conversation Filter shows all traffic between the two addresses of the selected packet.
Trick 4: Follow one conversation from start to finish
Single packets are fragments. Often you want the whole exchange between your PC and one server, reassembled the way the application saw it.
- Click any packet of the connection you're interested in.
- Choose Analyze > Follow > TCP Stream. Right-clicking the packet works too.
- A window opens with the stream content. Traffic from client to server is red, traffic from server to client is blue.
The Follow TCP Stream window, here on macOS. The Windows version has the same controls.
The dropdown at the bottom left switches between Entire conversation and each direction alone. Show and save data as changes the format, and Save as writes the stream to a file.
Watch the buttons when you close the window. Back closes the dialog and restores your previous display filter. Close keeps the stream filter active, which is handy when you want to keep working on just that connection.
For HTTPS connections, the stream content is gibberish, and that's correct: it's encrypted. Following a TCP stream is most revealing on plain protocols like HTTP or DNS over TCP. For an encrypted stream, the window still tells you how many packets and turns went each way.
If TCP Stream is grayed out or missing, the selected packet doesn't contain TCP. Pick a different packet, or try UDP Stream for DNS.
Trick 5: Save the capture properly
- Choose File > Save As.
- Pick a folder and a file name.
- Leave the format on pcapng, Wireshark's native format. It keeps extras such as packet comments that the older pcap format can't store.
- Click Save.
If you add no extension, Wireshark adds the right one for the chosen format. Want only the packets your filter shows? Use File > Export Specified Packets instead. That's the clean way to share a small, focused capture without the rest of your traffic.
Before you send a capture to anyone, remember what's in it: IP addresses, device names, the domains you visited and anything that crossed the network unencrypted. Share filtered exports, not your whole evening.
Our verdict
Wireshark is the right tool for curious beginners, home-lab tinkerers and anyone who wants to see why the network feels slow instead of guessing. You don't need to understand every protocol to get value from it. Do one thing today: capture one minute of traffic, type dns into the filter bar and look at which domains your PC contacts on its own.
Related on UpdateStar
- Wireshark on UpdateStar
- Wireshark alternatives, where Npcap is listed
- Wireshark 4.6.9 fixes 19 security vulnerabilities


