Live HTTPS traffic inspection
See exactly what your app sends and receives, in real time, so issues are easier to find and explain.
Mac HTTPS Debugger · Free to try
Install ProxyHawk, point your app at the proxy, and immediately see live HTTPS traffic. Built for fast local debugging with no cloud dependency and a simple workflow your whole team can use.
1 app 1 proxy 0 cloud
macOS 13 or later · Free to try
No account needed 2-minute onboarding Traffic never leaves your Mac
Inside the app
Open captured requests, edit headers and body, import cURL, and hit Send in the same app. Fewer context switches means faster debugging.
Developer feedback
★★★★★
"Light and simple — exactly what I needed. Had it running and capturing traffic in under two minutes. Other tools feel bloated next to this."
★★★★★
"The onboarding is ridiculously easy. Installed the CA, pointed my app at the proxy, and I was seeing decrypted traffic immediately. Zero friction."
★★★★★
"The UI is genuinely beautiful. Every other proxy tool feels dated next to ProxyHawk. It fits right in on macOS — native feel all the way through."
Core features
See exactly what your app sends and receives, in real time, so issues are easier to find and explain.
Pin important hosts and patterns so you spend time on critical requests, not background noise.
Open captured calls, edit them, and resend right away without switching tools.
Pause matching requests or responses, inspect data, make changes, and continue with control.
Change or block live traffic to test failures, fallback behavior, and recovery paths before release.
Redirect calls to local files, staging services, or mock responses for predictable test runs.
Share captures, compare runs, and replay request batches to reproduce bugs and confirm fixes.
Turn captured HTTP calls into reusable API Client collections for regression testing and team handoff.
Automate request and response changes with scripts so repeated debugging tasks take seconds.
Simulate slow or unstable networks to catch timeout, retry, and loading-state issues early.
Documentation
Read these in order or jump straight to what you need.
Proxy CA, decrypt lists, and what certificate pinning means for debugging.
Pinned hosts, filters, search, Copy URL / cURL with full request context.
Collections, tabs, Send, import cURL—replay from the list or craft new calls.
Threat model, CA hygiene, sensitive data in captures, responsible use.
Short answers; details live in the docs.
Yes—for many Mac workflows. It is the same kind of tool: local HTTPS capture, SSL decrypt rules, traffic list, and export. ProxyHawk emphasizes Mac, privacy-first defaults, tight decrypt lists, and an in-app API Client next to the log. If you need deep legacy or non-Mac clients, Charles or others may still fit better.
Often no for solo debugging—collections and Send are in-app. Teams with collaboration in another client can still export cURL. See API Client.
Designed to stay on your Mac. Check your build for optional analytics or crash reporting in Security & privacy.
Pinning blocks MITM by design—you need debug builds or test hooks, same as any proxy debugger. See limitations.
Install the CA, point your app at the proxy, see live traffic. That's it. No account, no cloud, no complexity — just instant HTTPS visibility on your Mac.
macOS 13 or later · Free to try