Proxyman
Proxyman is a debugging proxy for capturing, inspecting and replaying HTTP and HTTPS traffic, with breakpoints, Map Local, scripts, mobile capture and clients for multiple platforms.
What Proxyman provides
Proxyman captures and explains HTTP or HTTPS flows from desktop and mobile test clients. Breakpoints, Map Local and scripts help reproduce API behavior, while system proxy settings and certificate trust determine which flows are visible.
Platform versions and privacy
Proxyman maintains separate release lines for macOS and Windows/Linux, so version numbers should be compared within the same platform. Captures can contain cookies, tokens and personal data; redact them before sharing and review optional analytics or cloud features.
Maintenance note
This page reviews Proxyman macOS 6.14.0 and Windows/Linux 3.16.1 for desktop and mobile debugging, including SSL inspection, certificates, Map Local and proxy restoration. Content review date: 2026-08-23.
Save to your cloud drive
Open the cloud drive to get the file directly, or save it for convenient access on another device.
Quark Cloud Drive
RecommendedSave Proxyman to this cloud drive
Baidu Netdisk
Save Proxyman to this cloud drive
Proxyman first HTTPS debugging guide
Install the matching desktop client, record the original proxy state, trust a temporary test certificate and inspect one controlled HTTPS request.
Before you start
- Match the client and architecture; macOS and Windows/Linux use different release lines.
- Use only devices, accounts and interfaces that belong to the test environment or are approved for debugging.
- Prepare a test site with no sensitive data and confirm permission to install a local root certificate.
Installation steps
- 01
Install and record the original proxy
Install the platform client, note system proxy and VPN settings, and confirm that the original state can be restored after the test.
- 02
Install the local test certificate
Generate and trust the certificate only in a disposable test profile, then enable SSL Proxying for the selected test domain.
- 03
Capture one controlled request
Start capture, send a harmless request from the test client, inspect headers and body, and stop capture after the result is recorded.
Quick start
- 01
Use filters and Map Local carefully
Start with a narrow domain filter, map one response to a local fixture and verify that the request is restored after the rule is removed.
- 02
Test mobile traffic separately
Configure the mobile device to use the desktop proxy, install the temporary certificate in the test profile and remove it after the session.
- 03
Redact and export evidence
Remove cookies, authorization values and personal data before saving a capture or sharing it with a team.
Usage tips
- SSL inspection requires proxy routing and certificate trust; certificate-pinned apps may require an approved debug build.
- Capture certificates grant broad visibility into a test device. Remove them and restore the proxy when the work ends.
- License activation, optional analytics and crash reports may use the network; review the selected settings before a private test.
Troubleshooting and uninstall
Why is HTTPS content not visible?
Check the active proxy, selected domain, certificate trust and SSL Proxying rule, then test a simple domain before changing several settings.
Why did another app lose network access after testing?
Stop the proxy and restore the original system proxy, VPN and certificate settings. Confirm the clean state with a normal browser request.
- Restore proxy and certificate stateStop capture, disable SSL Proxying, remove the temporary certificate and restore the recorded system and mobile proxy settings.
- Remove the client and capturesUninstall the client through the operating system and delete captures or logs after retaining only the redacted evidence required for the project.
Frequently asked questions
Can Proxyman see every HTTPS response?
The device must route traffic through the proxy, the domain must be selected for SSL Proxying and the client must trust the local certificate. Certificate pinning can still block inspection.
Does Proxyman upload captured traffic?
Desktop capture data and the generated certificate are kept on the device by default, while license activation and optional analytics or crash reports may use the network.
Why do macOS and Windows/Linux versions use different numbers?
They are maintained as separate release lines. Compare versions within the same platform rather than treating a larger number as universally newer.