Share localhost at a public URL
One command puts the site running on your machine at an HTTPS link, so a client, a teammate or your phone can open it while you keep editing. Nothing is opened on your machine, and it is free to start.
$ whk share 3000
● Sharing
Link: https://sample-preview-1234.sharehooks.cc
Forwarding to: localhost:3000Every option is in the whk share docs. Using a framework? Jump to its guide.
Install and first run
- 1
Install the CLI
One line on macOS and Linux. The installation page has Windows binaries and the other ways to install.
curl -fsSL https://webhooks.cc/install.sh | sh - 2
Log in once
Opens your browser to confirm a code. Sharing needs an account with a confirmed email address; a free one will do.
whk auth login - 3
Start your dev server, then share its port
The CLI prints the link and draws it as a QR code for your phone. Press Ctrl-C to stop sharing. If your connection drops, the CLI reconnects and the link stays the same.
whk share 3000
The target is a port on this machine: 3000, localhost:3000 or 127.0.0.1:3000. Other ways to install are on the installation page.
What your dev server sees
Visitors' requests travel down one outbound connection from the CLI to your port, and the answers go back the same way. On the way in, the link makes each request look local, which is why most dev servers need no setup at all.
Host is localhost
Your server gets Host: localhost:3000, as if you had opened it yourself, so a dev server's host check has nothing to refuse. The public name travels in X-Forwarded-Host, with X-Forwarded-Proto: https and the visitor's address in X-Forwarded-For.
WebSockets and streams pass
Hot reload sockets, your own WebSockets and server-sent events go through the same link. A socket's Origin is sent as your local origin, which is what dev servers expect from their own pages.
Redirects come back to the link
A redirect your app sends to http://localhost:3000/... is rewritten to the public address, so a login flow does not strand a visitor on their own localhost.
Cookies stay on the link
Cookies your app sets without a Domain work as usual. One set for another domain (Domain=localhost, for one) is dropped, since the visitor's browser is on the sharehooks.cc name.
- Web pages only: HTML, CSS, JavaScript, JSON, XML, images, fonts, WebAssembly and text
- No videos, audio, documents, archives or downloads; no response over 50 MB
- Plain HTTP on the local port; a local HTTPS server is refused
- 50 requests a second per share, with room for a page load's burst of a few hundred
Framework guides
The port to share, whether hot reload comes along, and the one setting a framework may still want when its pages are opened from a public name: a trusted origin for forms, a trusted proxy for links and cookies.
JavaScript
Next.js
whk share 3000Nothing to add: pages, Fast Refresh and Server Actions work as they are. Watch for redirects built from request.url in route handlers.
Vite
whk share 5173React, Vue and Svelte templates alike. Nothing to add: server.allowedHosts is checked against Host, and HMR dials the page's own address.
Nuxt
whk share 3000Nothing to add: HMR shares the dev server's port. Server-side useRequestURL() says localhost until you opt into the forwarded host.
SvelteKit
whk share 5173Nothing to add in dev: the CSRF origin check only runs in production builds. Sharing npm run preview needs paths.origin.
Astro
whk share 4321Nothing to add for pages and HMR. security.allowedDomains makes Astro.url the public address and settles form posts from non-browser clients.
Angular
whk share 4200Nothing to add: ng serve checks Host, which arrives as localhost, and live reload shares the port. SSR apps log a proxy header notice.
Express
whk share 3000No host check to pass. Set trust proxy to loopback so req.protocol, req.hostname, req.ip and secure cookies follow the link.
webpack-dev-server
whk share 8080No Invalid Host header: the host check sees localhost. Set client.webSocketURL so hot reload uses the link's port.
Python, Ruby, PHP and Elixir
Ruby on Rails
whk share 3000Add the preview to config.hosts: Rails checks X-Forwarded-Host as well as Host, and answers Blocked hosts without it.
Laravel
whk share 8000Trust the proxy so links and assets use the public name, and build your assets: the Vite dev server is a second port.
Django
whk share 8000ALLOWED_HOSTS passes as it is. Forms need the preview in CSRF_TRUSTED_ORIGINS, or POSTs fail with Origin checking failed.
Flask
whk share 5000No setting needed to load pages. ProxyFix makes external URLs use the public name, and the debugger's console is kept from visitors.
FastAPI
whk share 8000No host setting. Start it with --no-proxy-headers so redirects come back to the link, and link with paths rather than url_for's full URLs.
Phoenix
whk share 4000Nothing to add for pages, LiveView or live reload: sockets share the port, and their Origin arrives as localhost.
What each plan allows
Sharing comes with every plan; there is no separate subscription for it.
| Plan | Shares at once | Reserved names | Session | Data a month | Passwords |
|---|---|---|---|---|---|
| Free | 1 | Random names only | 2 hours | 1 GB | No |
| Pro | 3 | 3 | No limit | 25 GB | Yes |
| Business | 10 | 20 | No limit | 150 GB | Yes |
| Teams | 3 per member | 3 per seat, the team's | No limit | 25 GB per member | Yes |
| Team Business | 10 per member | 20 per seat, the team's | No limit | 150 GB per member | Yes |
Data is what passes through your shares both ways, counted per calendar month. A Free link has a random name ending in -free and shows visitors a short notice page first, once a week per browser; paid links show it only during the plan's first 7 days. Your limits are the best of your own plan and any subscribed team you belong to. Prices and the rest of each plan are on the pricing page; the full limits are in plans and limits.
Reserved names and passwords
On Pro, Business and team plans, reserve a name once and share under it as often as you like, so the link you sent last week still works. A password puts a page in front of the site; a visitor who gets it right is remembered for 7 days.
whk names reserve acme # keep acme.sharehooks.cc
whk share 3000 --name acme # the same link every time
whk share 3000 --password # ask visitors for a password
whk names password acme # or put one on the name itselfNames use lowercase letters, digits and hyphens. A name reserved inside a team belongs to the team, and every member can share under it. See names and passwords in the docs.
whk share or whk tunnel --live
Both reach a port on your machine from the internet, for different callers. A share serves your site to people. A live tunnel answers a webhook sender, such as a Slack slash command or Twilio, with your local app's response, and keeps the request.
| Difference | whk share | whk tunnel --live |
|---|---|---|
| For | People opening your site in a browser | A webhook sender waiting for your app's answer |
| Command | whk share 3000 | whk tunnel 3000 --live |
| Public address | https://<name>.sharehooks.cc, the whole port | https://go.webhooks.cc/w/<slug>, a webhooks.cc endpoint |
| What is kept | The last requests while the share runs: method, path and status | Every request and your app's response, in the dashboard, CLI, SDKs and MCP server |
| Answers passed on | Web pages up to 50 MB, with WebSockets | API answers up to 1 MB: JSON, XML, text or form data |
| Counts against | The plan's shared data for the month | The plan's request quota |
A plain whk tunnel 3000 answers the sender at once and then replays each webhook to your port; see the tunnel docs.
Compared with other tunnels
webhooks.cc vs ngrok
Free and paid links side by side: names, data, the browser notice, passwords, and where ngrok's TCP tunnels and own domains still win.
Read the comparisonwebhooks.cc vs LocalTunnel
The free open-source tunnel next to a maintained one with request history, replay and stable URLs.
Read the comparisonSharing localhost questions
Install the whk CLI, run whk auth login once, start your dev server and run whk share with its port, such as whk share 3000. The CLI prints an HTTPS link on sharehooks.cc that sends every visitor to your local port until you press Ctrl-C.
Yes. Sharing is on every webhooks.cc plan, Free included: 1 share at a time, 2 hours per session and 1 GB of data a month. A free link gets a random name ending in -free and shows visitors a short notice page once a week per browser. There is no separate subscription for sharing.
Those come from dev servers that refuse a Host they do not know, which is what most tunnels send. whk share sends your server Host: localhost with its port and carries the public name in X-Forwarded-Host, so webpack-dev-server, Vite and others see their own address. Frameworks that read X-Forwarded-Host or compare a form's Origin still need one setting; the framework guides name it.
Yes, when the dev server's reload socket uses the same port as the page, which is the default in Next.js, Nuxt, Vite, SvelteKit, Astro and Angular. WebSockets pass through the link, so a page someone has open updates as you edit. A share is one port: a dev server that serves assets or its reload socket from a second port needs that changed, and the framework guides say where.
On Pro, Business and team plans. Reserve a name with whk names reserve acme and share with whk share 3000 --name acme; the link is acme.sharehooks.cc every time. Pro keeps 3 names and Business 20. Free shares get a new random name each session.
For showing a local web app to someone, yes: one command, an HTTPS link, WebSockets and hot reload, with reserved names and passwords on paid plans. It is not a general tunnel: it carries web pages over HTTP, with no TCP tunnels, no domains of your own, and no downloads or video. The ngrok comparison lists both side by side.
Use whk tunnel for that instead. It gives the provider a webhooks.cc endpoint URL that stays the same, keeps every request so you can inspect and replay it, and forwards it to your local port; with --live the provider gets your local app's own answer.
Anyone with the link can use the site while the share runs, so share what you would show. Nothing is opened on your machine: the CLI makes one outbound connection and only the port you named is reachable. On paid plans a password keeps strangers out, and whk shares stop ends a share from another terminal. Debug consoles that run code, such as Werkzeug's, are refused by the link.
Your first link in two minutes
Sign up free, install the CLI and run whk share with your port.
No credit card