Skip to content

Recordings

A recording is traffic saved to a file. zhttp writes four formats:

Format Keeps
.zhttp Everything zhttp captured: requests and responses, timing, TLS handshakes and fingerprints, the app each connection came from with its icon, and connections with no request, such as a failed handshake
.har HAR 1.3: requests, responses and timing. Bodies are written decoded, as text, or as base64 when they aren’t text.
Postman Collection v2.1 One request per exchange, oldest first, each with its response saved as an example. Bodies are written decoded. A body that isn’t text is left out, and the request keeps its headers.
OpenAPI 3.1 The API the requests were made to: one path per endpoint, with IDs, UUIDs, dates and tokens in the path made into parameters, the query parameters, and the schemas of JSON and form bodies by status. No captured values are written, only their shapes.

The comments you left on requests go with them: in a HAR, a request’s comment is its entry’s comment, and in a Postman collection it’s the request’s description. In a HAR, why a request ended without a response is its entry’s _error.

  • Some requests: select them in the list (Ctrl-click or Shift-click), right-click › Export…
  • A host or folder: right-click it in Structure › Export… This saves everything under it, whatever the search shows.
  • Everything: right-click All requests in Structure › Export…

Pick zhttp recording, HAR 1.3, Postman Collection v2.1 or OpenAPI 3.1 as the file type. The suggested name is the session’s name, or its port, and the time, for example iphone 2026-11-10 1430.zhttp. Once it’s saved, a message names the file, and Show in folder opens its folder.

Postman opens both with Import.

Any of these:

  • the Open a recording button near the right end of the top bar, beside Settings;
  • drag files onto the window.

Each file opens in its own tab, named after the file and marked with a file icon. You can search it, inspect it and export from it like a live session. It has no port, so there’s nothing to pause, and none of the session row’s buttons: no block and allow lists, network conditions, upstream proxy, SSL proxying or system proxy.

zhttp opens:

File From
.zhttp zhttp
.har Any tool that writes HAR, of any version. Each entry’s comment shows as the request’s comment.
.chls Charles session
.chlsj Charles JSON session
.chlz Charles zipped session
.powc powhttp session

zhttp tells the format from the file’s contents, so a renamed file still opens.

A Charles session opens with its requests, responses, timing, HTTP/2, CONNECT tunnels, refused and unfinished requests, and WebSocket messages. TLS handshakes and fingerprints don’t come across.

  • When Charles kept a WebSocket as raw frames, it didn’t record when each one was sent. The messages open in order for each side, all at the time the exchange ended.
  • Charles 5.0 writes .chlsj and .chlz files that mark compressed bodies wrongly, so a gzipped or zstd body from those files may show a decode error. .chls files from any version, and .chlsj and .chlz files from Charles 5.2 and later, open exactly.

A powhttp session opens with its requests and responses, headers in the order sent, bodies, timing, HTTP/1.1 and HTTP/2 connections, the client’s and the server’s addresses, the TLS version and cipher, and the program each request came from. TLS handshakes and fingerprints don’t come across, and neither do program icons.

If a session holds something zhttp can’t read yet, it won’t open, and the error says which entry.

Recording tabs aren’t reopened when zhttp restarts. Open the file again.