DevPeek

Capture · Mobile web debug · Collaborate

DevPeek

H5 bugs that only show on a real phone? DevPeek is built for joint debugging—not just watching traffic.

Param encrypt/decrypt, visual Mock, and response-body search; self-built debug panels mirror mobile web over the proxy on your desktop.

Core features free forever on desktop—no subscription. See pricing for Pro and Team.

Getting startedWindows only for now · install guide

Watch first: debugging mobile web pages

Prerequisites: the phone points at DevPeek’s proxy with SSL trust and decrypt scope set. Then open Debug, pick the phone in the top client tab, refresh the target page to auto-connect and mirror, and use DevPeek’s built-in debug panels—not browser DevTools.

Demo

Mobile web page debugging over the proxy

After the phone browses through the proxy: pick the client tab in Debug, refresh the page to auto-connect and mirror, and use DevPeek’s built-in debug panels.

Read the mobile web debugging guide →

What you can do

More than plain capture: encrypt/decrypt, Mock, and search wired into the workflow; mobile web uses self-built debug panels on your desktop.

  • Capture

    Not just traffic—encrypt/decrypt, Mock, and search feel different

    • Separate tabs per phone, browser, or test app; decrypted HTTPS headers and bodies in detail.
    • Param encrypt/decrypt: once transform rules are set, details, Mock, and Debug API default to plaintext—DevPeek encrypts on send. Mock and debug match on plaintext without one-off decode scripts.
    • Visual Mock: pick URL/param traits from a request, configure intercept and rewrite in a guided UI; carry params forward to simplify the next rule.
    • Powerful search: keywords hit URL, method, and Host—and optionally response bodies; regex and case options to find needles in long lists.

  • Mobile web debug

    Self-built debug panels mirroring phone web over the proxy

    • For HTML through DevPeek’s proxy: the phone must use the proxy, trust the root CA, and the host must be in SSL decrypt scope.
    • When prerequisites are met, pick the phone client tab in Debug and refresh the page to auto-connect; DevPeek’s built-in debug panels below—not browser DevTools—for DOM, scripts, and network.
    • Throttling presets; optional session recording. PC browser work can use the Chromium extension import.
    • Switch between Capture and Debug in one app—trace APIs and the page on the same phone without tool hopping.

  • Collaborate

    Find teammates on the LAN, share in one gesture

    • Discover other DevPeek users on the LAN with less file shuffling and timestamp wrangling.
    • Send captures or debug recordings to colleagues for joint debugging—scrub secrets before sharing.

Your first session

  1. 1

    Point the phone at DevPeek’s proxy

    Install DevPeek on Windows and note the listen port; set the phone’s Wi‑Fi proxy to your PC’s LAN IP and port (local browser can use system proxy).

  2. 2

    Trust the CA on mobile and set SSL decrypt

    Install and fully trust the DevPeek root CA on the phone (iOS also needs Certificate Trust Settings); add target hosts to SSL decrypt scope—you should see decrypted HTTPS and HTML responses in Capture.

  3. 3

    Mirror mobile pages in the Debug tab

    Open Debug, pick the phone in the top client tab, and refresh the target page in the phone browser. When injectable HTML is available, DevPeek auto-connects and shows the mirror plus built-in debug panels. If it stays on “Waiting for device connection”, fix proxy and SSL setup first.