Skip to content

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:3000
Start free:
or sign up with email

Every option is in the whk share docs. Using a framework? Jump to its guide.

Install and first run

  1. 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. 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. 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.

What each plan allows

Sharing comes with every plan; there is no separate subscription for it.

PlanShares at onceReserved namesSessionData a monthPasswords
Free1Random names only2 hours1 GBNo
Pro33No limit25 GBYes
Business1020No limit150 GBYes
Teams3 per member3 per seat, the team'sNo limit25 GB per memberYes
Team Business10 per member20 per seat, the team'sNo limit150 GB per memberYes

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 itself

Names 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.

Differencewhk sharewhk tunnel --live
ForPeople opening your site in a browserA webhook sender waiting for your app's answer
Commandwhk share 3000whk tunnel 3000 --live
Public addresshttps://<name>.sharehooks.cc, the whole porthttps://go.webhooks.cc/w/<slug>, a webhooks.cc endpoint
What is keptThe last requests while the share runs: method, path and statusEvery request and your app's response, in the dashboard, CLI, SDKs and MCP server
Answers passed onWeb pages up to 50 MB, with WebSocketsAPI answers up to 1 MB: JSON, XML, text or form data
Counts againstThe plan's shared data for the monthThe 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

Sharing localhost questions

Your first link in two minutes

Sign up free, install the CLI and run whk share with your port.

or sign up with email

No credit card