Manual
NetPeek iOS Packet Capture Tool & Network Debugging Manual
Short, practical guides for each part of NetPeek — written for the phone you're debugging on. Step-by-step procedures live in the product documentation.
Product documentation
Procedures for iPhone: on-device capture, HTTPS inspection, rewrite DSL, scripts, replay, and MCP.
iPhone Packet Capture Tool
NetPeek is an on-device iPhone packet capture and network debugger that records HTTP/HTTPS through an on-device tunnel—no jailbreak. Capture and inspection stay on the phone by default. HTTPS plaintext needs you to install and trust a local CA and add hosts to the MITM list (see the HTTPS manual). Request data isn’t uploaded by NetPeek by default. Exports or MCP, once you turn it on, are how captures leave; crash and analytics sharing stays off.
HTTPS Inspection on iOS
To inspect HTTPS plaintext on iPhone you must manually install and fully trust the NetPeek on-device CA; only hosts on the MITM list are decrypted. The CA is generated on the device and is not uploaded by NetPeek; iOS cannot trust it automatically. After install and full trust, add the target host to the MITM list and send a new request.
Rewrite HTTP Traffic and Mock APIs on iOS
A NetPeek rewrite combines match conditions with actions, letting you edit headers, replace bodies, mock a response, block a request, redirect traffic, or return a local file without changing the app under test.
iOS Packet-Capture Scripts for Request and Response Automation
When a simple rewrite is not enough, NetPeek scripts can run JavaScript before requests, after responses, or on a schedule, while constants keep reusable environment URLs, tokens, and other values in one place.
Replay HTTP Requests on iOS
NetPeek can turn a captured request into a replay, let you edit its method, URL, headers, and body, then resend it. Frequently used requests can be saved as replay items for repeatable API checks.
NetPeek MCP
NetPeek MCP is off by default. After you enable it and provide a Bearer token, AI clients on the same Wi-Fi or USB can inspect captures. NetPeek does not upload captures—review the AI client’s privacy behavior.
NetPeek vs Desktop Charles Proxy: On-Device Tunnel or HTTP Proxy
This page compares NetPeek with desktop Charles Proxy’s HTTP-proxy workflow (phone pointed at a Mac)—not Charles for iOS’s on-device tunnel mode. Desktop Charles waits for apps to send traffic to a proxy; NetPeek takes over the network interface on the phone with an on-device tunnel, so it sees SDKs that ignore the system proxy. If you already debug on a Mac, Charles’s large desktop screen and mature proxy workflow remain strong.
Capture HTTPS Traffic on iPhone Without a Mac
To sniff HTTPS traffic from iPhone apps without a Mac, run the capture on the phone. NetPeek records traffic through an on-device tunnel, so the iPhone is the only device involved. Install and fully trust NetPeek's local CA, add the host you are debugging to the MITM list, and send the request again. Two limits apply: an app that pins its certificate still shows no plaintext, and QUIC traffic has to fall back to TCP first.