Skip to content

Comparison · Updated November 2026

ngrok vs Cloudflare Tunnel

Both connect a local service to the internet over an outbound connection, with nothing to open in a firewall. ngrok is built around a developer's machine: one command, an assigned domain and a request inspector. Cloudflare Tunnel is built around Cloudflare's network: cloudflared connects a server to your own domain there, with a no-account Quick Tunnel for testing.

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.

Cloudflare Tunnel

Cloudflare Tunnel runs cloudflared next to your service and maps hostnames on a domain you keep on Cloudflare to local addresses, with Cloudflare's CDN, WAF and DDoS protection in front. Cloudflare lists it as available on all plans, and cloudflared is open source under Apache 2.0. For a quick test, cloudflared tunnel --url http://localhost:8080 opens a Quick Tunnel on a random trycloudflare.com address with no account. Cloudflare says Quick Tunnels are for testing and development: no uptime guarantee, at most 200 requests in flight, and no Server-Sent Events.

Features and pricing

FeaturengrokCloudflare Tunnel
Quick startngrok http 8080cloudflared tunnel --url http://localhost:8080
Account for a quick linkYes, free signupNo (Quick Tunnel)
Free addressOne assigned ngrok-free.app domain, the same after a restartA random trycloudflare.com name, new for every Quick Tunnel
Stable addressThe assigned domain; your own domain on Pay-as-you-goYour own domain on Cloudflare
PriceFree; Hobbyist $10/mo; Pay-as-you-go $20/mo plus usageListed as available on all Cloudflare plans; Quick Tunnels need no account
Limits on the free route1 GB of data and 20,000 HTTP requests a month, up to 3 endpointsQuick Tunnels: 200 requests in flight, no Server-Sent Events, no uptime guarantee
Request inspector and replayYes: localhost:4040 and the Traffic InspectorNot documented for Tunnel
ProtocolsHTTP; TCP with card verification on Free; TLS on Pay-as-you-goHTTP on Quick Tunnels; TCP, SSH and RDP on a tunnel, with cloudflared on the client too
Restricting who gets inOAuth, SAML or OIDC sign-in through Traffic PolicyEmail one-time PIN on Quick Tunnels, for browser visitors only; Cloudflare Access on a tunnel
In front of your servicengrok's gateway: Traffic Policy and endpoint poolingCloudflare's CDN, WAF and DDoS protection

ngrok as listed on ngrok.com/pricing and in its docs, Cloudflare Tunnel as described on developers.cloudflare.com/tunnel, 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 want a fixed address without owning a domain
  • You are debugging webhooks and want to inspect and replay requests
  • You want one command on a laptop, with no DNS to move
  • You need sign-in rules (OAuth, SAML or OIDC) on a development link

Pick Cloudflare Tunnel when

  • Your domain is already on Cloudflare
  • The service should stay up: a server, a home lab, production
  • You want a link right now with no account
  • You need SSH or RDP, or Cloudflare's WAF in front

Where webhooks.cc fits

Neither tunnel is a place where webhooks wait for you. A webhooks.cc endpoint has a fixed URL that captures every webhook and keeps it (7 days on Free, 31 on Pro), and whk tunnel forwards each one to localhost; with --live the sender gets your local app's answer, as it would through a tunnel.

For a quick link to a local site, whk share needs no domain: a random name ending in -free for 2 hours at a time on Free, and reserved names with passwords on Pro at $8 a month. It serves web pages only. For TCP, SSH, or a service that should stay up on your own domain, ngrok and Cloudflare Tunnel are the right tools.

webhooks.cc vs ngrok · webhooks.cc vs Cloudflare Tunnel · Share localhost

Try it yourself

or try without an account

Frequently asked questions

ngrok vs Cloudflare Tunnel: which is better for local development?

ngrok is the shorter path on a laptop: one command gives an address that stays the same, with an inspector for the requests. Cloudflare Tunnel fits when your domain is already on Cloudflare and you want the service on a hostname of your own; its Quick Tunnel covers a one-off link with no account, on an address that changes every time.

Is Cloudflare Tunnel free?

Cloudflare's docs list Cloudflare Tunnel as available on all plans, and a Quick Tunnel needs no account at all. Publishing an application on a tunnel needs a Cloudflare account and a domain on Cloudflare.

What are the limits of a Cloudflare Quick Tunnel?

Per Cloudflare's docs: no uptime guarantee, up to 200 requests in flight (more get a 429), no Server-Sent Events, and a hostname that changes each time you create one. They are meant for testing and development.

Can I receive webhooks through Cloudflare Tunnel?

Yes, a tunnel passes HTTP requests to your local service. A Quick Tunnel's hostname changes each time, so the URL you gave the provider has to be updated; a hostname on your own domain stays. Cloudflare's Tunnel docs describe no request inspector or replay, so what arrived is whatever your app logged.

See also: ngrok vs Hookdeck · ngrok vs Webhook.site · ngrok vs LocalTunnel · 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.

or try without an account