Native macOS & iOS · Swift + SwiftUI

Intercept, inspect & replay every request.

HTTrail is a native HTTPS debugging proxy and API client in one app. Inspect traffic you are authorized to test, capture locally or through your selected Mac, then compose or replay requests. You choose the capture route and export destinations.

Universal build for Apple Silicon & Intel · macOS 14+ · also coming to the App Store

Your capture destination No accounts, no telemetry macOS + iOS

Native, not Electron

Pure Swift + SwiftUI on a SwiftNIO core. It starts instantly, sips memory, and feels like a Mac app because it is one.

Capture where you choose

Run capture on your device or pair with a Mac you select. Remote mode sends traffic, captured flows, and diagnostics to that Mac. HTTrail does not automatically upload captures to the developer.

Yours to trust

The CA is generated locally. Pairing can send its certificate and private key to your selected Mac so it can decrypt your test traffic. Trust only your own authorized systems and remove trust when finished.

// Capabilities

A whole debugging toolkit in one window.

Two products, fused: a Charles-style intercepting proxy and a Hoppscotch-style API client, sharing one capture engine.

HTTPS MITM proxy

Answers CONNECT, terminates TLS with a freshly minted leaf cert, forwards to the real origin, and captures both directions — live-tested against real hosts.

On-device certificate authority

Generates a self-signed P-256 root (10-year, persisted) and mints per-host leaf certs on the fly. One-click install & trust on macOS.

Charles-style rules engine

Block, map local, map remote, rewrite request or response, throttle bandwidth, and set interactive breakpoints — pause a flow, edit the body, continue.

Deep flow inspector

Headers, raw and pretty-printed JSON bodies, live HTML preview, image preview, plus status, timing, and size for every captured flow.

Request composer

Methods, query params, headers, every body mode, GraphQL, and {{env}} variables — with Bearer, Basic, and API-key auth helpers built in.

Realtime clients

WebSocket, Server-Sent Events, Socket.IO (Engine.IO v4 handshake), and an MQTT 3.1.1 client — all over the same NIO core.

Import & export

Bring in cURL, OpenAPI 3, and Postman v2.1. Send out cURL, Swift, JavaScript, or Python — and export captured flows as HAR 1.2.

Pre-request & test scripts

Run JavaScript before and after a request through JavaScriptCore, with a familiar pm.* API for assertions and dynamic values.

SSL-proxying allowlist

Only decrypt the hosts you list. Everything else is blind-tunnelled untouched, so certificate-pinned apps keep working alongside your capture.

// Four steps

From zero to decrypted traffic.

1

Start the proxy

Hit the toolbar play button or ⌘P. HTTrail listens on 127.0.0.1:9090.

2

Trust the CA

One click installs & trusts the root CA on macOS — or install the .mobileconfig profile on iOS.

3

Capture

Toggle the system proxy and every request & response streams into the Capture tab in real time.

4

Compose & replay

Edit-and-resend any flow, copy it as cURL, or build a fresh request and hit Send (⌘↵).

// One core, two platforms

Built for Mac and iPhone.

The apps share a Swift core. Available features depend on platform and distribution: the direct macOS download supports CA and system-proxy tools; the sandboxed Mac App Store build does not provide HTTPS interception.

macOS

The direct download offers the full debugger and native system integration.

  • System-proxy toggle via networksetup
  • One-click CA install & trust into the System keychain
  • Reveal & export the root CA from Finder
  • Full inspector, composer, rules, and realtime clients

iOS

Capture this iPhone, or another device through your Mac.

  • On-device capture VPN via a Packet Tunnel extension
  • Capture keeps running while the app is backgrounded
  • Installs CA + proxy through a single .mobileconfig
  • Or point any device's proxy at your Mac — no dev account needed

Your traffic follows the route you choose.

HTTrail has no developer telemetry or account-based capture backend. Captures can contain tokens, cookies, and request bodies. They stay on the capture device or selected Mac until you delete or export them; proxying and replay also send requests to their destinations. Review what you share.