PCAP File Analyzer

Open a packet capture and see what happened on the wire. The analyzer reads .pcap and .pcapng files in your browser, draws the packet flow, decodes every layer of any packet, and lists conversations, DNS lookups, HTTP requests, TLS handshakes and red flags.

Analyzer Networking Updated Oct 6, 2026
Learn how this works
How to Use
  1. Drop a .pcap, .pcapng or .cap file on the box, or press Open a capture. A .pcap.gz is unzipped for you. Nothing is uploaded.
  2. Or pick a sample: a web page load, TLS 1.3 over IPv6, ping and traceroute, red flags, or a file that was cut off.
  3. Read the packet-flow diagram: one arrow per packet between the hosts, oldest at the top. Click an arrow, or any table row, to decode that packet layer by layer in Show Work and the Hex tab.
  4. Use the tabs (Overview, Packets, Conversations, DNS, HTTP, TLS, Threats, Hex). Type in a tab’s filter box, such as an address, :443, dns or a domain, to narrow it.
  5. Export the rows you see as CSV or JSON, or copy them as a Wireshark display filter to carry on in Wireshark.

PCAP File Analyzer

Capture
Drop a .pcap or .pcapng file here
or click to browse · .cap and .pcap.gz work too · read in your browser, never uploaded
Sample captures
Packet flow
Reading the sample capture…
Packets
—
Duration
—
Bytes on the wire
—
Conversations
—

Worked Example

Loading a web page (the default sample). A laptop at 192.168.1.20 asks its router 192.168.1.1 for the address of example.com. The DNS query leaves 0.655 ms into the capture and the answer, A 203.0.113.80 with a TTL of 3,600 s, arrives at 14.873 ms: the lookup took 14.873 − 0.655 = 14.218 ms. The SYN goes out at 15.402 ms and the SYN-ACK returns at 38.117 ms, so one round trip to the server is 38.117 − 15.402 = 22.715 ms. The 75-byte GET / HTTP/1.1 leaves at 38.391 ms and HTTP/1.1 200 OK comes back at 62.540 ms, 24.149 ms later. The server’s acknowledgement of the GET says Ack=76: the client started at relative sequence 1 and sent 75 bytes. (The addresses come from the documentation ranges of RFC 5737; the sample was built for this page and every checksum in it is valid.)

Reading a TLS 1.3 Client Hello (TLS sample). Packet 6 carries the Client Hello. It offers 16 cipher-suite values (one of them a GREASE placeholder), the server name www.example.com and ALPN h2 and http/1.1, and its supported_versions extension lists TLS 1.3 and 1.2 while the old version field still says TLS 1.2 (0x0303 = 771). Dropping the GREASE values (RFC 8701) gives the JA3 string 771,4865-4866-…,0-23-65281-10-11-35-16-5-13-18-51-45-43-27,29-23-24,0, whose MD5 is 7f805430de1e7d98b1de033adb58cf46. Packet 7, the Server Hello, picks TLS 1.3 and TLS_AES_128_GCM_SHA256; everything after it is encrypted.

The common mistake: reading the frame length as the data. Packet 7 of the web sample is 60 bytes on the wire, but it carries 0 bytes of data, not 60 or 6. Ethernet (14) + IPv4 (20) + TCP (20) is only 54 bytes, and the IPv4 total-length field says the packet ends after 40 bytes of IP; the last 6 bytes are padding, because an Ethernet frame is never shorter than 60 bytes plus its 4-byte check sequence. The data length is IPv4 total length − IP header − TCP header = 40 − 20 − 20 = 0, which is the Len=0 in the packet list.

Show Work

How the selected packet was read: the file header, the packet’s record header, then every layer from the outside in, with what each field means. Click another packet to decode it.

Reading the sample capture…

Formulas and Header Layouts

pcap file header
magic 4 + version 2.4 (2 + 2) + reserved 8 + snaplen 4 + link type 4 = 24 bytes
The low 16 bits of the last field are the link-layer type; the top bits can give a frame-check-sequence length (pcap-savefile(5)).
pcap record header
seconds 4 + µs or ns 4 + captured length 4 + original length 4 = 16 bytes
Captured < original when the snapshot length cut the packet.
pcapng block
type 4 + total length 4 + body (padded to 4) + total length 4
The length is written at both ends so a reader can check it and walk backwards.
pcapng timestamp
seconds = (high × 232 + low) ÷ 10if_tsresol + if_tsoffset
if_tsresol defaults to 6 (microseconds); with its top bit set it is a power of 2 instead.
TCP data length
Len = IPv4 total length − IHL × 4 − data offset × 4
40 − 20 − 20 = 0 for a bare ACK; bytes after the IPv4 total length are link padding.
Relative sequence numbers
relative = (seq − first seq from that side) mod 232; next Ack = Seq + Len (+1 for SYN or FIN)
GET with Seq=1 and Len=75 is acknowledged with Ack=76.
Internet checksum
one’s-complement sum of 16-bit words = 0xFFFF when correct
RFC 1071; TCP and UDP add a pseudo-header of the addresses, protocol and length.
JA3 fingerprint
MD5("version,ciphers,extensions,groups,point formats")
Decimal values joined with “-”, GREASE values removed (Salesforce JA3).

Where Packet Captures Come From

In the late 1980s Van Jacobson, Steve McCanne and others in the Network Research Group at Lawrence Berkeley National Laboratory wrote tcpdump to capture and dissect network traffic; its capture and file code later became the libpcap library, and its file layout is the classic pcap format (IETF draft-ietf-opsawg-pcap, which documents version 2.4). McCanne and Jacobson described the kernel filter underneath it in “The BSD Packet Filter” at the USENIX Winter 1993 conference.

Gerald Combs began Ethereal in late 1997 and released version 0.2.0 in July 1998; the project was renamed Wireshark in 2006 and reached 1.0 in 2008 (Wireshark User’s Guide). pcap can hold only one link-layer type and its header differs from everything after it, so files cannot simply be joined. The pcapng format (draft-ietf-opsawg-pcapng) replaces it with self-describing blocks, several interfaces per file, comments and other timestamp resolutions, and Wireshark 1.8 and later save pcapng by default. The link-layer type numbers both formats use are kept by tcpdump.org.

About This Analyzer

Reference: Common Port Numbers.

The PCAP File Analyzer opens classic pcap files in either byte order with microsecond or nanosecond timestamps, and pcapng files with any number of interfaces, comments, name-resolution and statistics blocks. It draws the packet flow, lists every packet, conversation, DNS lookup, HTTP request and TLS handshake, flags clear-text passwords and other red flags, shows any packet in hex, and explains each header field of the packet you pick. It reads only the first TCP segment of an HTTP message (it does not reassemble bodies), puts a split Client Hello back together, and does not decrypt TLS.

It is for IT staff triaging a capture without Wireshark to hand, CCNA and Network+ students learning what is inside a packet, and anyone who should not upload a capture of their own network to a website. The file never leaves your browser.

Sources: pcap-savefile(5), tcpdump.org link-layer header types, draft-ietf-opsawg-pcap and draft-ietf-opsawg-pcapng; RFC 791, 8200, 826, 792, 4443, 9293, 768, 1035, 6762, 9112, 7617, 8446, 6066, 7301, 8701 and 1071 at rfc-editor.org; the IANA registries for protocol numbers, ICMP and ICMPv6 types, DNS record types and response codes, TLS cipher suites, extensions and groups, EtherTypes and service names; Salesforce JA3; and the Wireshark display filter reference for the copied filters.

Related tools: DNS Lookup, Traceroute, and User Agent Parser.

Frequently Asked Questions

Is my capture uploaded anywhere?

No. The file is read in your browser in 4 MB slices and parsed in bursts of about 12 ms, so even a large file never freezes the page and nothing leaves your computer. Packet bytes are not kept in memory: when you click a packet, its bytes are read again from the file on your disk.

What is the difference between pcap and pcapng?

A classic pcap file is a 24-byte header (magic number a1 b2 c3 d4 for microsecond or a1 b2 3c 4d for nanosecond timestamps, in either byte order, then version 2.4, snapshot length and one link-layer type) followed by a 16-byte header before every packet. pcapng is built from blocks, each starting with a type and a length: a Section Header (0x0A0D0D0A), Interface Descriptions and Enhanced Packet Blocks. It can hold several interfaces, comments and other timestamp resolutions. Wireshark 1.8 and later save pcapng by default.

Which protocols does it decode?

Ethernet with 802.1Q/802.1ad VLAN tags, Linux cooked captures (v1 and v2), BSD loopback and raw IP; ARP (RFC 826), IPv4 (RFC 791), IPv6 with extension headers (RFC 8200), ICMP (RFC 792), ICMPv6 (RFC 4443), TCP (RFC 9293), UDP (RFC 768), DNS and mDNS (RFC 1035), HTTP/1.x request and status lines (RFC 9112) and TLS records with Client and Server Hello (RFC 8446). Anything else, such as QUIC, SMB or DHCP, is listed by port and protocol number; open those in Wireshark for a full decode.

If HTTPS is encrypted, how can it show the website name?

The browser names the site in the server_name (SNI) extension of its Client Hello (RFC 6066), which is sent before encryption starts. In the TLS sample that is www.example.com, offered with ALPN h2 and http/1.1, and the server picks TLS 1.3 with TLS_AES_128_GCM_SHA256. The page also gives the JA3 fingerprint of each Client Hello, 7f805430de1e7d98b1de033adb58cf46 for the sample, which identifies the client software rather than the user.

How large a file can it open, and what about broken ones?

The packet list keeps the first 250,000 packets, while packet, byte, protocol, talker and conversation totals cover every packet; the DNS, HTTP and TLS tables hold 50,000 rows each and draw 5,000 at a time. A damaged or cut-off file is read up to the damage and the page says where it stopped: the cut-off sample shows 13 packets and reports that packet 14 promises 60 bytes but only 20 are left.

How do I use the PCAP File Analyzer?

Just type your numbers. The answer shows up right away — there is no button to press. Change anything and it updates by itself.

Does it cost anything or need an account?

No. The tool is completely free, there is no account to create, and it keeps working offline after the page first loads.

Is anything I type uploaded?

No. The tool works entirely on your device, so the values you enter never leave your browser.

Common Use Cases

Why is this page slow?

In the web sample the DNS answer takes 14.2 ms, the server returns the SYN-ACK 22.7 ms after the SYN, and the 200 OK arrives 24.1 ms after GET /. Each gap points at a different culprit: the resolver, the network path or the server.

CCNA and Network+ study

Watch the three-way handshake with relative numbers: SYN Seq=0, SYN-ACK Seq=0 Ack=1, ACK Seq=1 Ack=1. The 75-byte GET moves the server’s Ack to 76, and Show Work names every header field.

Which sites does a device contact?

The TLS tab lists each server name (SNI), the ALPN offered and the version the server chose: www.example.com, h2, TLS 1.3 in the TLS sample, even though the content itself is encrypted.

Incident triage

The red-flags sample shows 6 findings: an HTTP Basic password for user alice, a password in the URL, 2 random-looking names, 2 NXDOMAIN answers and a Client Hello whose server name is the IP address 203.0.113.9.

Seeing traceroute work

A probe sent with TTL 1 to UDP port 33434 comes back 0.924 ms later as ICMP Time Exceeded from the first router, 192.168.1.1, which quotes the probe’s ports.

Handing over to Wireshark

Filter a tab, then copy its rows as a display filter such as dns.qry.name == "example.com" or tcp.port == 443 || udp.port == 443 and paste it into Wireshark.

Last updated: