Suggestions appear as you type. Use the up and down arrows to choose one and Enter to open it.

This page's audience our own tag's counts — open to see them
–Visits
–Page views
–Clicks to vendors
–Time on page
–Reading now
Clicks to vendors, by tool
  • –
Top countries
  • –
Devices
  • –

– · visits, page views and clicks counted by our own tag, which counts more than our checked analytics; every figure rounded down · how we count

Whistle review

Free#7 of 27 in Web Debugging Proxies

A flexible open-source proxy for inspecting, replaying, and mocking network traffic.

8.6/10Editor score
Whistle8.6 Visit Whistle

Reviewed by iTechGuides Editors · Editorial team · Updated Oct 2026

Whistle is an open-source network debugging proxy for developers and technical teams working across desktop, browser, and command-line environments. It captures and modifies HTTP, HTTPS, HTTP/2, WebSocket, and TCP traffic, while also supporting HTTP, HTTPS, SOCKS, and reverse proxy modes. Its feature set covers request and response editing, replay, redirection, response mocking, WebSocket and TCP frame control, and remote DOM inspection through Weinre and Log.

Whistle uses an open-source model and is distributed under the MIT license. A desktop client is available for macOS, Windows, and Linux, while the command-line version supports headless Linux servers and other environments. This makes it a practical fit for teams that need the same proxy-oriented debugging approach across local development and server-side workflows. Plugins can extend protocol and interface capabilities, giving teams a way to adapt the tool beyond its built-in behavior.

Its strongest area is the depth of traffic handling: rules can modify requests and responses, the Network interface supports replay and editing, Composer constructs custom HTTP requests, and local files or inline content can provide mocked API responses. WebSocket and TCP frames can also be inspected and controlled. Teams choosing Whistle should value flexible proxy modes and open-source extensibility. Teams that specifically need a verified breakpoint-rule workflow or broader application observability should choose a tool focused on those capabilities instead.

Whistle pros and cons

  • Where it wins
    • Captures and modifies HTTP, HTTPS, HTTP/2, WebSocket, and TCP traffic
    • Supports proxy modes, replay, custom requests, and response mocking
    • Runs across macOS, Windows, Linux, and headless environments
  • Where it doesn't
    • Dedicated breakpoint rules are not established as a feature
    • Its workflow centers on proxy traffic rather than general app observability
    • Protocol and interface expansion relies on plugins

Whistle fact sheet, pricing and score →

Advertiser disclosure: iTechGuides is reader-supported. Vendors can pay for top positions in our rankings and for a place on other products' pages, and we may earn a commission when you click some links. Bought places stand at the number bought; this page and our disclosure say so. Paying vendors may get a fuller, more detailed review from our editors, and that review can change their score. How we rank.

Last updated · How we research and update