KitJade
Network & CybersecurityRuns in your browserNew

PCAP Analyzer

A browser packet workspace with filters, protocol trees, TLS decryption and an analysis report.

Use the PCAP Analyzer tool

Runs in your browserUpdated Report a problem

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

  1. 1Capture traffic with tcpdump, tshark or your firewall, then stop the capture cleanly.
  2. 2Drop the .pcap or .pcapng file above, or click to browse. The file stays on your device.
  3. 3Use the display-filter bar to narrow the packet list. Invalid expressions show an error instead of hiding traffic.
  4. 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.
  5. 5To read TLS, add a key log file from the optional TLS decryption panel; decrypted records appear in the tree and the report.
  6. 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?
Add a key log file in the SSLKEYLOGFILE text format. The tool matches client randoms, derives keys with Web Crypto and decrypts TLS 1.2 and TLS 1.3 AES-GCM records locally. ChaCha20-Poly1305, CBC and CCM suites are reported as unsupported rather than guessed, and the key log is never uploaded.
Is this a full desktop protocol analyser?
No. It covers packet browsing, display filters, a protocol tree, hex highlighting, Follow TCP stream, fragment reassembly, 802.11 decoding, key-log TLS decryption, colour rules and an analysis report. Live capture, Lua dissectors and deep protocol coverage are outside its scope.
Is my capture uploaded anywhere?
No. The file is read locally, parsed in this tab and discarded when the page is closed. There is no upload request, and any key log you add is handled the same way.
Which filter syntax is supported?
Fields such as tcp.port, ip.addr (with CIDR), tcp.flags.reset, http.host, dns.qry.name and tls.handshake.extensions_server_name, with ==, !=, <, >, contains, matches, &&, ||, ! and parentheses. The shortcuts ip:, port: and proto:, plus bare text search, still work.
What does Follow TCP stream show?
Every captured payload in that TCP conversation, ordered by sequence number, grouped by direction and marked with an arrow. It does not merge retransmissions; decrypted TLS appears separately in the protocol tree when a key log is loaded.
What is in the analysis output?
A plain-text report with capture details, packet rate and throughput, protocol mix, top talkers, conversations, application inventory, fragment reassembly counts, optional TLS decryption results, findings such as cleartext HTTP or unanswered SYNs, and recommended next steps. Copy it or download it as a .txt file.
Which capture formats and link types are supported?
Classic pcap in either byte order with microsecond or nanosecond timestamps, and pcapng section, interface and packet blocks. Ethernet with 802.1Q/QinQ, raw IPv4/IPv6 with fragment reassembly, 802.11 with radiotap, BSD loopback and Linux cooked capture are dissected; other link types are listed without a decode.
How large a file can it read?
Up to 60 MB, decoding the first 200,000 packets to keep the page responsive. Filter or trim larger captures with your capture tool before opening them here.
All tools