Skip to content
Windows

WePROXA 3.0.0 now supports Windows and macOS. Windows installation is available from the Microsoft Store.

Frequently Asked Questions

WePROXA is a native macOS and Windows HTTP/HTTPS proxy debugger. It lets you capture, inspect, modify, and replay network traffic from apps on your computer.

Starting with WePROXA 3.0.0, WePROXA supports macOS 11.0+ (Big Sur and later) on Apple Silicon and Intel Macs, plus Windows 10 and Windows 11. The Windows build is installed from the Microsoft Store.

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

When a Pro license is active, SettingsLicense shows the details returned when the key was validated: the subscription (product and variant), the expiration date and time (or a note when none is scheduled), the customer email on the license, the activation usage (seats used out of the limit, or an unlimited indicator), and when the license was last validated. Use Revalidate to refresh these details against the license server, or Deactivate to release the activation on this machine.


Why does WePROXA need a certificate for HTTPS inspection?

Section titled “Why does WePROXA need a certificate for HTTPS inspection?”

To inspect HTTPS (encrypted) traffic, WePROXA needs a trusted local Certificate Authority. This is standard practice for proxy debugging tools. The certificate is generated locally and never leaves your machine. On macOS, see Certificate Trust. On Windows, see Windows HTTPS Certificate Setup.

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

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

Section titled “Can I activate my license or open settings from a link?”

Yes. WePROXA registers the weproxa:// URL scheme. Opening a weproxa:// link — for example from your browser after a purchase — can activate a license key or jump straight to a Settings section without hunting through the app. If activation from a link fails, WePROXA opens the License settings so you can see the error and retry.


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 a browser that uses system proxy settings, such as Safari on macOS or Edge/Chrome on Windows

The WePROXA CA certificate may not be trusted. On macOS, see Certificate Trust. On Windows, see Windows HTTPS Certificate Setup.

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.