Previa
中文 EN
Download

Previa

Share your in-progress local app for live preview and annotated feedback.

No deploy. Open the desktop app, copy a link, and anyone can see your local project in a browser — then leave markup feedback.

The installer for your system will be provided automatically

Install

If macOS blocks the first open

Previa ships as a standalone .dmg without Apple notarization. After a browser download, macOS may say the app is “damaged” or from an unidentified developer — the app is fine. Use any step below.

  1. Recommended: clear quarantine in Terminal

    Use this first if you see “damaged and can’t be opened.” Open Terminal, replace the path below with where Previa.app actually is on your Mac, then run:

    xattr -rd com.apple.quarantine /Applications/Previa.app
    • If you moved it to Applications: keep /Applications/Previa.app
    • If it is still in Downloads: use ~/Downloads/Previa.app
    • Anywhere else: in Finder, Option-click Previa.app → Copy … as Pathname, then paste that path over the end of the command

    The path must point at the .app itself (spaces are fine). After it succeeds, double-click to open.

  2. Open from the context menu

    In Finder, Control-click Previa (or two-finger click), choose Open, then Open again in the warning. This usually works for “unidentified developer.” For “damaged,” use the Terminal command above.

  3. Allow in System Settings

    Open System Settings → Privacy & Security, scroll to the blocked Previa notice, and click Open Anyway.

How it works

Client review in three steps

From your local port to their browser, peer-to-peer by default — with encrypted relay when the network blocks direct paths.

  1. Open the desktop app

    Launch Previa and pick the running local server (e.g. localhost:3000).

  2. Send the share link

    Create a room link in one click and send it to a client, designer, or teammate.

  3. They preview and annotate

    They open the link, see your real local page, box-select areas, and leave notes — screenshots and text return to your app.

Capabilities

Built for honest review

One less staging deploy. One more preview that matches what you actually run locally.

P2P tunnel

Assets travel over a WebRTC DataChannel. Content is not persisted on the server.

Annotated feedback

Guests box-select regions and comment; screenshots and notes return to the host, ready to export.

Zero-deploy preview

Share the running local dev server. Code changes show up immediately — no upload step.

Host-only login

Guests stay anonymous. The host signs in so rooms and quotas can be bound and timed.

Pricing

Scale with review intensity

Free covers the full share flow. Upgrade to Pro when reviews become continuous.

Free

Start here

  • 1 active share at a time
  • Up to 30 minutes per share
  • Public STUN · P2P first
  • Annotations and feedback export

Pro

For ongoing reviews

  • Up to 10 concurrent shares
  • Up to 8 hours per share
  • Cloudflare TURN and edge cache
  • More reliable cross-network paths

Upgrade monthly or yearly after signing in on desktop.

FAQ

FAQ

When preview feels slow, it is usually data moving through the tunnel — not a failed connection.

Why is the first open slower?

A cold visit pulls page assets through the tunnel into the guest browser. Larger payloads and more request waves mean longer waits. Re-entering the same room in the same browser is much faster.

How do I make guest preview smoother?

Prefer a lightweight review route or release build; help P2P succeed (same LAN, UDP allowed); avoid sharing the heaviest first screen.

What if Free limits are hit?

Free allows one active share for 30 minutes. For parallel or long reviews, upgrade to Pro inside the app.

Do guests need to install anything?

No. Guests open the link in any modern browser. Only the host needs the desktop app and a login.

It says the app is “damaged” after download. What now?

That is Gatekeeper blocking an unnotarized app — the file is not corrupt. Follow Install: run the xattr command, or try Open / Open Anyway. Download only the .dmg from the site; do not unpack .app.tar.gz (that is the auto-update package).

Guides

Find the page for your situation

Follow a review from connecting a local port to collecting feedback and verifying changes.

Send localhost to a client

Share localhost:3000 and troubleshoot ports, API requests, and browser connection issues.

Let clients mark up the page

Agree on a task, collect actionable annotations, verify changes, and export feedback with screenshots.

Review before you deploy

Complete a live review, check API and login dependencies, and decide when staging is needed.

Shorten client review to one copied link

Download Previa, pick a port, send the link. They open it and annotate.

Download desktop app