Inside Wireshark
1 / 1Wireshark packet capture and protocol analysis workspace
Wireshark on Windows: installing it and reading your first capture
Wireshark records the traffic passing through a network interface and shows you every packet, decoded into the protocols it carries. Network engineers use it to find out why a connection drops, developers use it to see what their app actually sends, and students use it to learn how networks work. It is free and open source, and its command-line companion, TShark, does the same job in scripts.
Which Wireshark download?
The download page offers three Windows packages for the current stable release:
- x64 installer for ordinary Intel and AMD PCs.
- Arm64 installer for Windows on Arm.
- x64 PortableApps package, which runs from a folder or USB drive.
Wireshark for Windows is 64-bit only. According to the user's guide it supports the Windows versions still within Microsoft's extended support, which currently means Windows 10 and 11 and recent Windows Server releases. The last branch for 32-bit Windows was a much older one.
Npcap: the part that actually captures
Wireshark itself only displays traffic. Capturing it live requires Npcap, a packet capture driver, and every Windows package ships with it. Let the installer add it. You do not need Npcap simply to open a capture file someone sent you.
Your first capture
- Start Wireshark. The welcome screen lists your network interfaces with a small live graph next to each. Pick the one that is busy: usually Wi-Fi or Ethernet.
- Double-click it. Packets start scrolling immediately.
- Do the thing you want to examine, such as loading a page or starting the app that fails, then press the red square to stop.
You will have thousands of lines. The display filter bar above them is how you find what matters:
dnsshows name lookups.ip.addr == 192.168.1.20shows traffic to or from one device.tcp.port == 443shows connections on one port.httpshows unencrypted web traffic.
The bar turns green when the filter is valid. Display filters only hide packets; nothing is deleted.
Three tools worth knowing early
- Follow stream. Right-click a packet and choose Follow, then TCP Stream. Wireshark reassembles the whole conversation in one window.
- Statistics, Conversations. Shows who talked to whom and how much. A quick way to spot the device that is flooding the network.
- Statistics, Protocol Hierarchy. A breakdown of the protocols in the capture.
Save a capture with File, Save As. The default .pcapng format keeps comments and interface details; other tools open it too.
What Wireshark will not show you
Most web traffic is encrypted. Wireshark sees that a connection to a server happened, how large it was and when, but not what was inside it. For your own browser you can let Wireshark decrypt sessions with a key log file; for anyone else's traffic, you cannot and should not.
Capture filters, set before you start, use a different syntax from display filters. Most people never need them; filter after capturing instead.
Finally, the legal point: capture only on networks you own or are explicitly allowed to analyse. Recording other people's traffic without permission is illegal in many places.
Common questions
Is Wireshark free?
Yes. It is free, open-source software with no paid edition.
Why are no interfaces listed?
Usually Npcap is missing or failed to install. Run the Wireshark installer again and make sure the Npcap step completes.
Can Wireshark show passwords?
Only those sent unencrypted, which is exactly why plain protocols are a bad idea. Encrypted logins, such as HTTPS, stay unreadable.
Is there a 32-bit Wireshark?
Not any more. Current releases are 64-bit only on Windows.
- Best for
- Finding out what is really happening on a network connection when an app, device or service misbehaves.
- Good to know
- Capture only networks you are allowed to inspect; encrypted traffic such as HTTPS stays unreadable without keys.
Related network tools
Nmap maps the hosts and ports on a network before you start capturing. More tools are in our browsers and internet category.