Skip to content

Frequently Asked Questions

Weproxa is a native macOS HTTP/HTTPS proxy debugger. It lets you capture, inspect, modify, and replay network traffic from any app on your Mac.

Currently, Weproxa is available for macOS 11.0+ (Big Sur and later) on both Apple Silicon and Intel Macs.

Weproxa offers a free tier with core features. Advanced features are available with a Pro license. See Pricing for details.


Why does Weproxa need to install a certificate?

Section titled “Why does Weproxa need to install a certificate?”

To inspect HTTPS (encrypted) traffic, Weproxa needs to generate and trust a local Certificate Authority. This is standard practice for proxy debugging tools. The certificate is generated locally and never leaves your machine. See Certificate Trust.

Click the network icon in the toolbar. Weproxa will configure your Mac’s system proxy settings automatically. When you stop the proxy or quit the app, the settings are restored.

Most apps that respect macOS system proxy settings will work automatically. Some apps (like those using custom proxy configurations or certificate pinning) may need additional setup.


Yes. Weproxa runs entirely on your local machine. No traffic data is ever sent to external servers. The CA certificate and private key are stored locally in the app’s data directory.

Yes, when the Weproxa CA certificate is trusted. This is a standard man-in-the-middle (MITM) technique used by all proxy debugging tools.

Apps with certificate pinning will reject Weproxa’s generated certificates. This is by design — it’s a security feature of those apps.


  1. Make sure the proxy is running (green indicator in toolbar)
  2. Check that the system proxy is enabled
  3. Try opening a website in Safari — it uses system proxy settings

The Weproxa CA certificate may not be trusted. See Certificate Trust for setup instructions.

Weproxa keeps up to 10,000 requests in memory. Use the Clear button in the toolbar to remove old requests, or use filters to focus on relevant traffic.