Capture & Inspect Traffic

Layout

The main window has three panes:

  • Traffic Panel (left) — hosts organized by category.
  • Flow List (center) — all captured HTTP requests.
  • Inspector (right) — details of the selected request/response.

Traffic Panel

Hosts are grouped into sections:

  • Pinned — hosts you pinned via right-click menu.
  • Devices — iOS Simulators, Android Emulators.
  • Apps — detected applications.
  • Hosts — all other hosts.

Click a host or section to filter the flow list.

Flow List

Each row shows: #, Method, Status, URL, Time. The list is virtualized for performance — thousands of flows render smoothly.

Filters

Click the filter bar above the flow list. Available filters:

Filter Options
Method GET, POST, PUT, DELETE, PATCH, HEAD, OPTIONS, etc.
Scheme HTTP, HTTPS
Status Success (2xx), Redirect (3xx), Client Error (4xx), Server Error (5xx), or a specific code
Host Contains or exact match
Path Contains or exact match

Use Quick search to search across all fields at once. Click Clear all to reset filters.

Context Menu

Right-click a flow to:

  • Pin Host — add the host to the Pinned section in the traffic panel.
  • Map Local — create a rewrite rule for this URL.
  • Bypass Host — add the host to the bypass list (skip HTTPS interception).

Inspector

Select a flow to open the inspector. Switch between Request and Response tabs.

Tabs

Request: Headers, Body, Auth, Raw, Summary. Response: Headers, Body, Raw, Summary.

Body Viewers

The body tab auto-selects the appropriate viewer based on content type:

  • JSON — syntax-highlighted, collapsible tree.
  • HTML — rendered view.
  • Image — preview with dimensions and file size.
  • Audio/Video — inline media player.
  • Text — plain text with syntax highlighting.
  • Binary — hex preview.

For large bodies, a Save to File button appears instead.

Export

From the inspector, you can copy headers, save the response body, or export the raw HTTP message.

Rewrite Rules (Map Local)

Open via Tools → Map Local (Cmd+Shift+M / Ctrl+Shift+M).

Rules let you replace HTTP responses with custom content. Each rule has:

  • Name — a label for the rule.
  • Domain pattern — wildcard matching (e.g., *.example.com).
  • Search pattern — regex to match the URL path (e.g., api/v1/(.*)).
  • Replacement — capture group replacement (e.g., api/v2/$1).
  • Response — custom status code, headers, and body (JSON, HTML, or plain text).
  • Enabled toggle — turn rules on/off without deleting them.

Rules are stored in encrypted local storage.