Capture HTTP & HTTPS traffic
Launch an isolated Chrome or Brave window, connect a proxy-aware client, or choose an Android device. Keep your capture focused on the source you want to understand.
BrowserApplicationAndroidTerminal
WhiteToolkit by WhiteProxiesHTTP Debugger.
See what your
app is sending.
Capture HTTP & HTTPS traffic, inspect API requests, and find out why a response went wrong. Replay calls, mock responses, and debug browsers, applications, and Android in one local workspace.
Available for Windows, Mac Apple Silicon, and Mac Intel.
HTTP & HTTPSAPI inspectionRequest replayResponse mockingAndroid via ADBLocal MCP server
Your HTTP debugging toolkitFrom a failing request
From a failing request
to a clear explanation.
See the exchange between your app and its API. Change one thing, send it again, and inspect the result.
Inspect requests & responses
Search by URL and filter by method or status. Read headers, cookies, JSON, and decoded Protobuf bodies, or inspect captured WebSocket messages.
Example API sessionStatus
GET/api/products200POST/api/session401GET/api/account200Edit, replay & mock API calls
Send a captured request to the composer and change its method, headers, or body. Use an exact-URL response rule to reproduce a failure or test an edge case without changing your backend.
Edit requestSend againInspect response
Keep captures local
Sessions stay on your device. Export HAR or JSON when you need to share a reproducible example.
Local workspace
Built for the investigationDebug the traffic
Debug the traffic
behind the bug.
From API authentication to mobile requests, bring the details into a workspace you can search and inspect.
Debug REST API calls
Follow a request from URL and headers to status code and response body. Find the payload or parameter behind an unexpected result.
Investigate authentication
Inspect authorization headers, cookies, and redirect responses in your test sessions to track down failed logins and expired tokens.
Inspect Android traffic
Choose an ADB-connected device and set up the companion VPN. View HTTP and supported HTTPS requests in the same desktop workspace.
Bring capture context to AI
Ask questions in AI chat or enable the authenticated, read-only MCP server for a compatible AI client to explore captured requests.
Debug through your proxy
Keep local interception and add an upstream HTTP proxy, with optional credentials, to test requests through a different outbound IP.
Keep a reproducible session
Save captures on your device and export HAR or JSON. Share the requests and responses that explain the issue with your team.
How it worksA local proxy.
A local proxy.
A complete view of the request.
WhiteToolkit sits between a supported client and its destination so you can inspect the HTTP conversation.
- 01
Choose your source
Open an isolated browser from WhiteToolkit or point a test client at the local proxy. For Android, connect a device over ADB and choose it in the app.
- 02
Set up HTTPS trust
Isolated browsers are configured for capture. For other clients, export and trust the local CA. Android apps with certificate pinning need a compatible debug configuration.
- 03
Reproduce and inspect
Repeat the action that fails, find the request in View, and inspect its response. Replay it or mock a different result to narrow down the cause.
One workspace, including Android.
The Android 8+ companion routes device traffic to WhiteToolkit through a VPN connection. Use it with the desktop app and approve certificate trust for supported HTTPS traffic.
FAQHTTP debugging,
Talk to our teamHTTP debugging,
explained.
Capture, certificates, Android, and choosing the right workflow.
WhiteToolkit is a desktop HTTP debugger and interception proxy from WhiteProxies. Capture HTTP and supported HTTPS traffic, inspect API requests and responses, replay requests, mock responses, and save sessions locally. An Android companion connects a test device to the desktop workspace.
If you need a workspace for HTTP capture, HTTPS inspection, API request replay, and response mocking, WhiteToolkit covers those workflows. It also includes Android interception, an optional upstream proxy, and a local MCP server. Check the capture and certificate requirements for your client when choosing a debugging tool.
WhiteToolkit uses a local certificate authority to inspect supported HTTPS connections. Isolated Chrome and Brave sessions are configured automatically. Other test clients need to trust the exported CA. Applications that pin certificates or reject user-installed CAs need a compatible debug configuration.
Yes. Connect an Android 8+ device with USB debugging enabled, choose it from the desktop app, and install the companion through ADB. Approve the VPN connection on the device and install the local CA for supported HTTPS traffic. The companion needs the desktop app; it is not a standalone traffic inspector.
Open a captured request in the composer, change its URL, method, headers, or text body, and send it again. For response mocking, create a rule that matches an exact URL and optionally an HTTP method, then choose the response status, content type, and body.
Yes. Add an upstream HTTP proxy in Settings using host:port or host:port:user:pass. WhiteToolkit inspects the traffic locally and forwards it through your configured proxy. This lets you investigate requests using a separate outbound IP.
Enable the optional local MCP server to give a compatible AI client authenticated, read-only access to capture data. WhiteToolkit also has an AI chat workspace. Captures are stored locally; data you choose to send to an external AI provider is handled by that provider.
Published installers are listed in the downloads section for Windows, Mac Apple Silicon, and Mac Intel. Platforms without a published installer show Coming soon. Android capture also requires the desktop app and its companion APK.