Share localhost with a client

Prepare a working local page

Suppose your dev server runs at http://localhost:3000 and you want feedback on /pricing. Open http://localhost:3000/pricing on your own machine first. Check images and interactions before sharing. A share link does not start a stopped project or repair a failing server.

localhost and 127.0.0.1 refer to the visitor’s own computer. Sending that address sends clients to their machine. A LAN address also usually cannot be reached directly from another city.

Share the running port

1. Start your project and note its actual port. This example uses 3000; use the port shown in your startup log.
2. Open the Previa desktop app, sign in, and enter 3000 or the local address you have verified in the port or address field.
3. Select “Start sharing” and copy the generated share link. Send that link, rather than the original localhost URL.
4. Ask the client to open it in Chrome or Safari. Guests do not need an account or the desktop app.
5. Have them navigate to the review page and test a button or a second page. After a code change, ask them to reload and check the result again.

Troubleshoot in this order

• The local page fails too: fix the dev server first. Check for a changed port or a stopped process.
• A previously working link fails: check whether sharing ended or the host computer went to sleep. Start a new share and send the current link when needed.
• An in-app browser fails: copy the link into a system browser. The preview needs Service Worker support.
• The page loads but API calls or images fail: inspect the network panel for hardcoded localhost URLs. A visitor’s localhost is not your machine. Prefer relative resource paths through the same dev server, configuring its development proxy as needed.
• The first load is slow: verify the connection with a lighter page, then check large images and assets. Transfer time depends on both networks.

Before and after the session

Use demo accounts and test data. Keep secrets, internal admin screens, and real customer records out of the demo. Keep the host computer awake and the dev server running. Free sessions last up to 30 minutes, so plan longer reviews ahead of time.

Select “Stop sharing” when finished and keep the feedback you need to act on. Temporary sharing depends on your computer staying online. Deploy normally when a site must be available all day.

Temporary link versus public URL

A Previa link is an entry point for the current review, not a deployment address for search engines or permanent public access. It stops when your computer, local server, or sharing session stops. A public URL should be served continuously by a stable hosting environment.

• Use a temporary share: a client needs to see the page you are editing now, click it, and leave feedback.
• Use staging: several people need to review one fixed version at different times.
• Deploy: the page must stay public, appear in search, or use production domains and callbacks.