Side by side
| RequestFox | Hoppscotch | |
|---|---|---|
| Where it runs | A side panel in Chrome, a sidebar in Firefox | Web, Mac, Windows, Linux and CLI; the web app needs no install [1] |
| Self-hosting | Nothing to host: there is no server | Host it on your own server for your team [1] |
| Calls your web app makes | Recorded as you click, with problems flagged | You build the requests |
| CORS from the web app | Sends through the page while recording, or from the extension itself | An interceptor: the Hoppscotch Agent, a proxy or the browser extension [2] |
| Realtime clients | WebSocket and Socket.IO client; WebSocket, Socket.IO and SSE captured, with live rows for fetch, XMLHttpRequest and EventSource streams | WebSocket, SSE, Socket.IO and MQTT [3] |
| Source | Free; MIT licence, repository not public | Source code open and auditable [1] |
Where Hoppscotch is stronger
- Open source, and you can self-host it for a team [1].
- An MQTT client [3]. RequestFox has none.
- Runs on the web with no install at all [1].
Where RequestFox is different
- It records what your app really sends and flags the problems, tied to your click.
- Mock and fault rules change the answers your app receives.
- History keeps every session to compare runs, and exports evidence for bug reports.
Sockets and streams in the browser
While recording, RequestFox lists the page's own WebSocket frames and server-sent events next to its other calls, and reads Socket.IO frames as events with their arguments. Its WebSocket client connects to any ws:// or wss:// server, with a Socket.IO mode, and keeps messages you save.
Sources
- Hoppscotch Docs, "Introduction to Hoppscotch". Checked 1 November 2026. docs.hoppscotch.io
- Hoppscotch Docs, "Interceptor". Checked 1 November 2026. docs.hoppscotch.io
- Hoppscotch Docs, "Realtime API Testing". Checked 1 November 2026. docs.hoppscotch.io
Something here out of date? Tell us at the address in the privacy policy and we will fix it.