PCAP Analyzer
A browser packet workspace with filters, protocol trees, TLS decryption and an analysis report.
Use the PCAP Analyzer tool
What this pcap analyzer does
PCAP Analyzer opens a classic pcap or pcapng file into a three-pane workspace. The packet list is colourised by protocol and traffic type, the middle pane is a collapsible protocol tree with the byte range of every field, and the right pane is a hex dump that highlights the bytes behind whichever field you click. A display-filter bar accepts expressions such as tcp.port == 443, ip.addr == 10.0.0.0/24 or tcp.flags.reset == 1, alongside the older ip:, port: and proto: shortcuts.
Beyond the packet list, the tool builds endpoint, conversation, DNS, HTTP, TLS and DHCP tables, reassembles fragmented IPv4 and IPv6 datagrams, decodes 802.11 and radiotap frames down to SSID and BSSID, lists both sides of a TCP conversation with Follow TCP stream, and writes a plain-text analysis report with traffic rates, protocol mix, findings and recommended next steps. Everything runs in this tab: the file is read with the File API, parsed in JavaScript and never uploaded.
For encrypted traffic it accepts a key log in the SSLKEYLOGFILE text format and decrypts TLS 1.2 and TLS 1.3 records with AES-GCM suites using Web Crypto. The key log is read from your disk, used in memory and never sent anywhere. There is no live capture, no Lua dissector support and no TCP stream rebuilding for file extraction; what it offers is a private first pass over a capture from any machine with a browser, plus exports you can paste into a ticket.
Why use it
- Triage a capture without installing anything, and without handing internal traffic to a third-party service.
- Filter with expressions such as http.request.method == "GET" or dns.qry.name contains "example".
- Rebuild fragmented datagrams, decode 802.11 frames and see exactly which bytes make up a field.
- Decrypt TLS records locally when you already hold the session keys, then follow the HTTP inside them.
- Get a written analysis output with findings and next steps that can be copied or downloaded.
How to use it
- 1Capture traffic with tcpdump, tshark or your firewall, then stop the capture cleanly.
- 2Drop the .pcap or .pcapng file above, or click to browse. The file stays on your device.
- 3Use the display-filter bar to narrow the packet list. Invalid expressions show an error instead of hiding traffic.
- 4Select a packet to inspect the protocol tree and hex view, click a field to highlight its bytes, and use Follow TCP stream where relevant.
- 5To read TLS, add a key log file from the optional TLS decryption panel; decrypted records appear in the tree and the report.
- 6Open the Analysis tab to read, copy or download the generated report, or export the filtered packet list as CSV and the summary as JSON.
Worked examples
Hunting a suspect connection
Input
A capture of a workstation session; filter ip.addr == 10.0.0.42 && tcp.port == 443
Output
The list narrows to that host's TLS flows. Selecting one shows the SNI in the protocol tree and the matching bytes in the hex pane.
Reading a session you own the keys for
Input
A localhost TLS capture plus an SSLKEYLOGFILE written by your browser
Output
The session table matches the client random, records are decrypted in the tree, and the report lists the decrypted HTTP hosts and record counts.
Checking for cleartext credentials
Input
A capture that includes HTTP POST requests
Output
The analysis report raises an alert for HTTP Basic credentials, while the packet tree shows the Authorization header with its value redacted.
Explaining a refused connection
Input
Filter tcp.flags.reset == 1
Output
Only reset packets remain, and the analysis report names the busiest conversation and the reset count.
Common mistakes
- Expecting HTTPS payloads to be readable without keys. TLS payloads stay encrypted unless you supply a matching key log and the suite is AES-GCM.
- Assuming every fragment can be rebuilt. Reassembly needs the first fragment and the last one; a capture that starts mid-datagram is reported as incomplete.
- Treating Follow TCP stream as full reassembly. Payloads are ordered by sequence number, but retransmissions are not merged and files are not rebuilt.
- Assuming a missing SNI means no TLS. Resumed TLS 1.3 sessions, Encrypted Client Hello and QUIC hide it.
- Capturing with a tiny snaplen, then wondering why payload fields and HTTP headers are missing.
Frequently asked questions
How does TLS decryption work?
Is this a full desktop protocol analyser?
Is my capture uploaded anywhere?
Which filter syntax is supported?
What does Follow TCP stream show?
What is in the analysis output?
Which capture formats and link types are supported?
How large a file can it read?
Related tools
All toolsHTTP Header Checker
Response headers plus a practical security-header audit.
TLS Configuration Checker
Check HTTPS redirects and HSTS headers.
DNS Lookup
Query DNS records over DoH with multiple record types.
IP Blacklist Checker
Check an IP against common DNSBL zones.