Lagsmith vs. Proxyman for throttling
Proxyman is a polished, modern HTTP debugging proxy for Mac. It can throttle, but through its proxy, and it needs a certificate to see HTTPS. Lagsmith focuses on network conditions: one app at a time, no proxy, no certificates.
| Proxyman | Lagsmith | |
|---|---|---|
| How it works | HTTP proxy: traffic is routed through Proxyman | Per-app network control, no proxy |
| Throttling | Throttles traffic going through the proxy | Throttles only the apps you choose |
| HTTPS | Install and trust Proxyman’s certificate to see HTTPS | Sees simulator requests with no certificate or proxy settings |
| Failures | Breakpoints, map local and scripting | Airplane Mode, refused connections, time-outs, dropped connections, outages that come and go, fail or mock one endpoint |
| Offline in the simulator | Not a device-like offline state | NWPathMonitor and SCNetworkReachability report no network |
| Physical devices | Yes, through the proxy | Mac apps and iOS Simulator apps |
When Proxyman is the better fit
For full HTTP debugging, scripting and inspecting traffic from physical devices, Proxyman is excellent. Lagsmith exports HAR files that open in Proxyman, so the two work well together.
When to use Lagsmith
- You want to throttle or break one app’s network while everything else stays fast.
- You want to skip installing certificates in each simulator.
- You need device-like offline behaviour in the simulator.
- You want UI tests or an AI agent to set network conditions.
See also Lagsmith vs. Network Link Conditioner and Lagsmith vs. Charles Proxy.
Slow down one app, not your whole Mac
Free to download, with a 14-day Pro trial. No account, no card. Requires macOS 13 Ventura or later.