Ngrok vs Cloudflare Tunnel: Which One Should You Use?

You have something running on localhost and you need other people to see it. Two names come up immediately: ngrok and Cloudflare Tunnel. Both solve the same problem, both are free to start with, and they make almost opposite trade-offs. This is the practical comparison, including the question people ask right after this one, which is whether Vercel does the same thing (it does not, and the difference matters), and the case where the honest answer is that you should not be using a tunnel at all.

What a tunnel actually does

Both tools work the same way underneath. A small program on your machine opens an outbound connection to the provider's network. The provider gives you a public HTTPS URL, and traffic to that URL is relayed through the open connection to the port your local server listens on. No router configuration, no port forwarding, no public IP needed.

The defining property of every tunnel: your machine is the server. Close the laptop, kill the process, lose the Wi-Fi, and the public URL dies with it. That is fine for a demo and fatal for anything you wanted to leave online. Keep that in mind for the last section.

Ngrok: fastest from zero to URL

Ngrok's pitch is speed of first success. You install one binary, run ngrok http 3000, and a public HTTPS URL appears in your terminal before you have finished reading the output. Nothing else on this page beats that.

The free tier's trade-offs show up when you share the link:

• The URL is random and temporary by default. Restart ngrok and you get a new one, which means re-sending the link to everyone who had the old one. You can claim one static ngrok domain for free, which softens this considerably.
• Visitors see an interstitial warning page on the free tier before they reach your site. For a client demo, that first impression is not yours, it is ngrok's.
• Custom domains and higher limits are paid. Reasonable for professional use, but the bill exists.

Where ngrok shines: one-off demos, webhook development (its request inspector is genuinely excellent, you can replay incoming webhooks against your local code), and situations where the person running it has no domain and no patience for setup.

Cloudflare Tunnel: more setup, more permanence

Cloudflare Tunnel (the cloudflared daemon, formerly Argo Tunnel) assumes you already have a domain and that its DNS is managed by Cloudflare. That is the toll gate: if your domain is not on Cloudflare, moving it there is the real setup cost, not installing the software.

Past that gate, the deal is better than ngrok's in almost every direction:

• It is free without an interstitial, including on your own domain. demo.yourdomain.com pointing at your laptop costs nothing.
• Named tunnels are persistent. The hostname survives restarts; the URL you shared on Monday still works on Friday, as long as your machine is up.
• It plugs into Cloudflare Access if you want the shared URL behind a login, which is the sane way to demo something semi-confidential.

Where it loses: first-run friction. Between authenticating cloudflared, creating the tunnel, and wiring the DNS route, the first URL takes fifteen minutes instead of fifteen seconds. It is also less pleasant for webhook debugging, because there is no built-in request inspector.

The short version

Rule of thumb: ngrok for minutes, Cloudflare Tunnel for weeks. A webhook session or a one-time screen-share demo is ngrok territory. A staging URL on your own domain that a client will click all week is Cloudflare Tunnel territory, if your machine genuinely stays on.

Where does Vercel fit? (It is not a tunnel)

"Ngrok vs Vercel" is a common comparison, and it is comparing a courier with a warehouse. Ngrok exposes your running machine; Vercel takes a copy of your code, builds it, and serves the result from its own servers. There is no "Vercel tunnel": the closest things are vercel dev, which runs locally like any dev server, and preview deployments, which are real hosted copies of your project, not views into your laptop.

That distinction is the actual decision point. If people need to see software that is running on your machine right now, mid-development, that is a tunnel job. If people need to see the site or app itself, deploying a copy is strictly better: the URL survives your laptop, and nobody's traffic depends on your Wi-Fi. The full breakdown of tunnels versus deploy platforms, including Netlify and the EU angle, lives in our localhost hosting comparison.

When neither is the right answer

Here is the pattern we see constantly: someone builds a site, often with an AI tool, previews it on localhost, and reaches for a tunnel to "put it online". For a website, that is the wrong tool twice over. The tunnel URL dies with the laptop, and the laptop was never meant to be a web server.

A static site, which is what AI tools produce in most cases, does not need your machine at all. Deploying the built files to real hosting takes about as long as installing ngrok, and the result is permanent: a stable HTTPS URL, optionally your own domain, served from infrastructure that does not sleep. If that is the situation you are actually in, skip the tunnel debate entirely and read how to put localhost on a live URL, which covers the drag-and-drop deploy path on EU hosting.

Tunnels are for showing people your machine. Hosting is for giving your site a life of its own. Most "how do I share localhost" questions are secretly the second thing.