Quickstart Guide

Turn a local folder into a controlled public share in less than 2 minutes. Local Bridge uses a single native binary, with no upload step, deployment workflow, or extra infrastructure to manage.

Select your operating system:

1. Download & Install

Local Bridge is distributed exclusively via Whop. Upon purchasing your Lifetime License, navigate to your Whop Dashboard.

  1. Go to your Whop Dashboard > Local Bridge.
  2. Click the Downloads tab.
  3. Download the binary for your platform:localbridge-windows-amd64.exe

Recommended: Use the built-in installer

Simply run the downloaded binary. On first launch, it will detect that it is not installed and offer to set itself up automatically:

# Double-click the downloaded .exe, or run from PowerShell:
> .\localbridge-windows-amd64.exe

Install now? [Y/n]: y
[OK] LocalBridge installed successfully
Installed to: %LOCALAPPDATA%\LocalBridge\localbridge.exe
Added to PATH: Yes

# Or install explicitly after the first launch
> localbridge install

Windows Note

If Windows SmartScreen shows a warning, click "More info" then "Run anyway". This is normal for unsigned executables. The binary installs to %LOCALAPPDATA%\LocalBridge\ and adds itself to your User PATH automatically. You may need to restart your terminal for the PATH change to take effect.

Verify the installation:

> localbridge --version
Local Bridge v1.0.6

2. Activate License

Before creating public shares, activate the CLI with your Whop license key.

> localbridge activate "YOUR_WHOP_LICENSE_KEY"

You can pass the key directly as shown above, or simply run localbridge activate without arguments to be prompted interactively. Your license key is available in the License tab on your Whop Dashboard. Once validated, the CLI securely stores your activation data with restricted file permissions.

3. Share Your First Folder

The simplest workflow is to point Local Bridge at a folder containing the files you want to publish as a controlled public share:

> cd .\my-project\dist
> localbridge --password "project-access" .

URL: https://random-words.trycloudflare.com

Anyone who visits the generated URL will see a browseable file listing. If you set a password, they must authenticate before browsing or downloading anything.

4. Run in Background (Daemon)

Need the share to stay online after you close your terminal? Add the --bg flag.

# Start a background share with a custom name
> localbridge --bg --name "release-share" .\my-project

# View all active background shares
> localbridge list

# Stop a specific share
> localbridge stop release-share