Comparison · Updated November 2026
ngrok vs Webhook.site
ngrok carries a request to your local server. Webhook.site shows you the request: it hands you a URL and lists everything sent there. Which one to reach for when a provider asks for a webhook URL depends mostly on whether you have a handler to send it to yet.
What each one is for
ngrok
ngrok gives a local port a public URL. The free plan comes with one assigned ngrok-free.app domain that stays the same when you restart the agent, HTTP endpoints, and TCP once a card is verified. The sender talks to your app through the tunnel, so it gets your app's own response, and the agent has to be running when the request arrives. Requests show in the local inspector at localhost:4040 and in the dashboard's Traffic Inspector, where they can be replayed.
Webhook.site
Webhook.site gives you a unique URL, an email address and a DNS name the moment you open it, with no signup, and shows everything sent to them in the browser. A free URL expires after 1 week and stops at 50 requests. Its CLI, whcli forward, passes requests on to localhost and can return your server's response to the caller. Paid accounts add Custom Actions (workflows that run on each request), schedules and URLs that do not expire.
Features and pricing
| Feature | ngrok | Webhook.site |
|---|---|---|
| What it is | A tunnel from a public URL to a local port | A hosted URL that captures and shows requests |
| Needs a local server | Yes | No, the URL answers on its own |
| Account | Yes, free signup | None for a free URL |
| Forward to localhost | ngrok http 3000 | whcli forward |
| Who answers the sender | Your local app, through the tunnel | Webhook.site, or your server's response when whcli forwards it |
| Request history | Traffic Inspector: 24 hours on Free, 72 hours on paid plans | 50 requests on a free URL; 1,000 to 100,000 per URL on paid plans |
| Free plan | One assigned domain, 1 GB of data and 20,000 HTTP requests a month | URLs expire after 1 week and take 50 requests |
| Paid plans | Free; Hobbyist $10/mo; Pay-as-you-go $20/mo plus usage | Basic $9/mo, Pro $19/mo, Enterprise $69/mo |
| Email capture | No | Yes, an address for every URL |
| Acting on a request | Traffic Policy rules at the endpoint | Custom Actions, on paid plans |
| Your own domain | Pay-as-you-go | Enterprise |
| Protocols | HTTP, TCP, and TLS on Pay-as-you-go | HTTP requests, email and DNS lookups |
| Team members | 3 included on Pay-as-you-go, then $5 per user | Enterprise, 10 included |
ngrok as listed on ngrok.com/pricing and in its docs, Webhook.site as listed on webhook.site/pricing and docs.webhook.site, in November 2026; "not documented" means we did not find it there. Check their pricing before you buy.
When to pick which
Pick ngrok when
- You already have a handler and want real requests to reach it
- The sender needs your app's response
- You are sharing a website or a TCP service, not only webhooks
- You want the address to stay the same on a free plan
Pick Webhook.site when
- You want to see what a provider sends before writing any code
- Nothing is running locally yet
- You need an email address or a DNS name that records what reaches it
- You want to transform or forward requests without a server of your own, on a paid plan
Where webhooks.cc fits
webhooks.cc does both halves in one tool. An endpoint is a hosted URL like Webhook.site's: it captures every request, and email at its own address, and keeps them with no tunnel running. whk tunnel then forwards them to localhost the way ngrok would, whk tunnel --live returns your app's answer to the sender, and whk share puts a local site at a public link.
On top of that it has SDKs that wait for a webhook and assert on it in CI, signature checks for more than 30 providers, and an MCP server. The free plan takes 50 requests a day and keeps them for 7 days.
webhooks.cc vs ngrok · webhooks.cc vs Webhook.site · CLI tunnel · Share localhost
Try it yourself
Frequently asked questions
ngrok vs Webhook.site for receiving webhooks on localhost?
ngrok forwards traffic to your local port and shows it in an inspector at localhost:4040 while the agent runs. Webhook.site captures requests on a hosted URL and shows them in the browser; getting them to localhost takes its CLI, whcli forward. Pick ngrok when you have a handler to test, and Webhook.site when you first want to see what the provider sends.
Is Webhook.site an alternative to ngrok?
For webhooks, partly: whcli forward sends requests from a Webhook.site URL to localhost and can return your server's response. It is not a general tunnel, so it does not share a local website or a TCP service the way ngrok does.
Do I need an account for ngrok or Webhook.site?
Webhook.site gives you a URL without signing up; that URL expires after 1 week and takes 50 requests. ngrok's free plan is an account plan: the assigned domain is tied to your account.
Which keeps webhook history longer?
ngrok's Traffic Inspector keeps traffic for 24 hours on the free plan and 72 hours on Hobbyist and Pay-as-you-go (metadata by default; bodies only with Full Capture turned on). Webhook.site keeps the most recent requests per URL: 50 on a free URL, and 1,000, 10,000 or 100,000 on Basic, Pro and Enterprise. Figures from each site in November 2026.
See also: ngrok vs Hookdeck · Hookdeck vs Webhook.site · ngrok vs LocalTunnel · ngrok vs Cloudflare Tunnel · Webhook.site vs RequestBin · All comparisons
Start testing webhooks in under a minute
Sign up with one click. No credit card, no setup wizard, no trial limits on core features.