Nothing breaks halfway
HTTPS is decrypted only after Proxly confirms the device trusts its certificate, by fetching https://proxly.cert/check through the proxy. Until then it passes through untouched.
HTTPS debugging proxy for iPhone and iPad
Proxly captures traffic from every app on your iPhone or iPad, decrypts HTTPS with a certificate made on the device, and lets you mock, rewrite, block or pause any request with rules. No Mac, no cables.
Capture
Start the proxy and use any app. Requests are grouped by site, so api.example.com and cdn.example.com sit together under example.com. A site spread over several hosts opens into a row per host, so one subdomain can be looked at on its own.
POST, 404 or part of a path.Tap the filter chips on the screen.
Inspect
Open any request for its overview, headers, query parameters, cookies, timing and body. Bodies compressed with gzip, deflate or Brotli are decoded before you see them.
users[1].tags[0].HTTPS
Proxly creates its own certificate authority on your iPhone. When an app connects, it reads the TLS ClientHello and makes a certificate for exactly the server name the app asked for, signed by that authority.
The tunnel only installs proxy settings, so iOS sends HTTP and HTTPS to the engine running inside Proxly’s extension. Plain HTTP is parsed directly.
TLS for a host you decrypt is terminated with a certificate made on the fly for the name the client asked for. Everything else is relayed untouched and shown as an encrypted tunnel.
The app sees each response byte as the server sends it, with backpressure both ways, so live event streams and long downloads work as they should. A body is held only when a rule needs it.
Proxly checks the upstream certificate itself. You can skip that for development servers you list, and the proxy card warns you while any are listed.
HTTPS is decrypted only after Proxly confirms the device trusts its certificate, by fetching https://proxly.cert/check through the proxy. Until then it passes through untouched.
All hosts except excluded ones, only hosts you list, or none. Changes apply from the next connection.
Apps that pin their certificates show up as Certificate not trusted. One tap on Stop decrypting and that host is relayed as is.
On by default: iCloud, the App Store, other Apple services and any hosts you add pass straight through. No decryption, no history, no rules.
Rules
Rules act on requests as they pass through the proxy. Start from a template, build one from scratch, or touch and hold any captured request. The rule comes prefilled with what was actually sent and received.
Answer with inline text or a file, with your own status and headers. The request never reaches the server. This is how you mock.
Send requests to another server without the app knowing. $1, $2… insert what the pattern captured.
Reply with a 301, 302, 307 or 308, and the app follows it itself.
Edit the body, status and headers in a simple form. Advanced steps change URLs and query parameters, replace text by regex, or set JSON values by key path.
Respond with a status code, or drop the connection as if the network failed.
Pause the request, the response or both. Edit it, then continue or abort.
Add delay and limit download speed per rule, to test loading states and timeouts.
Every rule has a URL pattern (wildcard, regular expression, contains or exact), optional methods, and conditions on request and response headers, query parameters, bodies, host, path or response status. Match all of them, or any.
https://api.example.com/*/login(analytics|tracking|doubleclick|adservice)data.items[0].nameTest a URL right in the editor, or open Test rules to see which rules match a request and what the whole set would do with it.
All rules match against the original request, so the order you list them in never changes what a pattern sees.
Rules are grouped by type, reordered with a drag, duplicated with a swipe, and turned off together when you want to see the real thing. Import and export them as JSON, and Map Local files travel with them.
An imported Map Local rule can only name a file inside Proxly’s own Map Local folder; anything pointing elsewhere is refused.
Breakpoints
A breakpoint rule holds matching traffic until you decide. Change the method, URL, headers, body or status code, then continue with your changes, continue unchanged, or abort.
Try +1 min on the screen.
Dynamic Island
Once a rule has changed traffic, a Live Activity counts how many times rules did so. When one fires, the island expands with the rule’s name and the request’s method, host and path, but never its query string.
Toolkit
Presets modelled on Apple’s Network Link Conditioner profiles, or your own latency, download and upload speed and packet loss. They apply to all traffic, on top of any Latency rules.
Any request becomes a cURL command you can paste into a terminal. Export one flow or the filtered list (up to 500) as HAR.
curl -X POST 'https://api.example.com/v1/login' \
-H 'Content-Type: application/json' \
--data-raw '{"email":"nino@example.com"}'
Replay any request, or edit it and send it again. Replays go through your rules and land in the history.
Frames in both directions are captured and searchable.
{"type":"subscribe","channel":"prices"}{"type":"price","symbol":"GEL","value":2.71}⟨ping⟩{"type":"price","symbol":"GEL","value":2.72}A development server with its own certificate? Skip certificate checks for listed hosts only, such as *.dev.example.com. The proxy card warns while any are listed.
Keep the last 500 to 5,000 requests, store bodies up to 4 MB, pause recording, and send hosts like *.local straight past the proxy.
iPad
Domains, requests and the inspector sit in three columns, so you move through traffic without losing your place.
Privacy
A debugging proxy sees everything, so Proxly is built to keep everything where it is.
The local VPN sends your apps’ traffic to Proxly on the same device. The proxy runs there, and so do your rules.
Proxly’s privacy manifest declares no tracking and no collected data.
Captured traffic and paused requests are excluded from iCloud and computer backups.
The root certificate’s private key lives in the Keychain, on this device only. It’s never synced or restored from a backup, and you can replace it any time.
Setup
The setup guide walks you through both, and Proxly checks each one for you. A step ticks itself off only once it can verify it.
Choose Set up later and nothing breaks: until the certificate is trusted, HTTPS simply passes through. The guide is always in Settings.
A local VPN sends your apps’ traffic to Proxly on this device. Nothing leaves it. iOS asks you to allow it and enter your passcode; the step completes when the proxy is actually running.
FAQ
No. Proxly’s “VPN” is a local packet tunnel that routes no packets: it only sets the device’s HTTP and HTTPS proxy to an engine running inside Proxly’s own extension, on the same device. Requests then go straight to the servers they were meant for.
To read HTTPS, Proxly has to present a certificate apps accept. It creates its own root certificate on your device; once you install and fully trust it, Proxly can sign a certificate for each host on the fly. Until Proxly has confirmed that trust, it doesn’t decrypt anything, and HTTPS passes through untouched.
That app most likely pins its certificates, so it will never accept Proxly’s. Open the request and tap Stop decrypting: from the next connection, that host is relayed as an encrypted tunnel and the app works normally. The same failure is reported at most once per host every 30 seconds.
No. Apple services check their own certificates, so Hide system traffic is on by default: iCloud, the App Store and other Apple services pass straight through. They aren’t decrypted, recorded or changed by rules. You can add your own hosts to that list too.
Not today. Proxly offers only HTTP/1.1 when it decrypts, and most clients fall back to it through the proxy. Clients that speak only HTTP/2, such as gRPC, are relayed without decryption so they keep working. They appear as encrypted tunnels.
They reach the app in full; only the first part is kept for inspection. The capture limit is 2 MB by default and 4 MB at most, because iOS ends a network extension that uses too much memory. If a rule needs a body larger than the limit, header, status and URL changes still apply, but body rewrites and breakpoints are skipped for it.
When the timeout runs out, the request continues unchanged. If Proxly is in the background you get a notification with Continue and Abort buttons, and if the requesting app gives up first, the breakpoint is withdrawn.
Yes. Add the host, or a pattern like *.dev.example.com, under Skip certificate checks. Only listed hosts skip the check, because every app trusts the Proxly certificate and couldn’t spot an impostor on them. The proxy card warns you while any are listed.
Yes. Export a single request or the whole filtered list (up to 500) as a HAR file, which browsers’ developer tools and other proxies can open, or copy any request as a cURL command. Rules export as JSON, with their Map Local files included.
iPhone and iPad running iOS 17 or later. On iPad, domains, requests and the inspector sit side by side.
Proxly for iPhone and iPad. Requires iOS 17 or later.