weblink

Control your desktop from a browser

Connect to the desktop app from a browser on your phone or computer to view the remote screen, use the mouse and keyboard, and transfer files. Weblink also provides chat, a local file library, voice and video calls, and screen sharing, with devices connected over WebRTC.

The Web app works without installing a native client. The desktop app reuses the same interface and application code, adding native screen capture, remote input, system clipboard access, and desktop window controls.

Get started

1. Open webl.ink or launch the desktop app.
2. Choose a display name and room ID, and optionally set a room password.
3. Join the same room from another device using the same password. Invite others with a room link or QR code.
4. Open room chat or a private conversation, send files, or enable your microphone, camera, or screen share.

To control a remote computer, run the desktop app there and request control from its participant or shared-display actions on another device. The host approves the request or uses a previously saved allow rule. A request can start display sharing after approval; window shares remain view-only.

Download the Windows x64 installer or portable ZIP from GitHub Releases. The installer sets up WebView2 when needed; the portable ZIP requires WebView2 120 or newer and its weblink-portable marker beside the executable. Development CI runs provide a weblink-windows-x64 executable artifact. See desktop setup and builds for prerequisites and source builds.

Web and desktop capabilities

The supported desktop target is Windows 10 22H2 / Windows 11 on x64 with WebView2 120 or newer. Native system audio and input features depend on OS capabilities. Browser media capture, clipboard access, notifications, and PWA integration depend on browser support and permissions; use HTTPS or localhost for browser capture.

Features

Conversations and rooms

• Private conversations and online room group chat with text, file attachments, forwarding, delivery status, and locally stored history.
• Conversation search, labels, and activity ordering, alongside recent-room selection with saved connection details.
• Per-client and per-room settings for remote-control requests, access to shared files, and automatic downloads.
• Message, control-request, speed-test, and completed-transfer notifications, with configurable previews and sound. Windows notifications support inline replies and request approval.

Device pairing and permissions

• Verify each device's identity before exchanging application data. First-use pairing is automatic after a valid signed proof; later connections must prove continuity with the saved device identity and pairing keys.
• If identity verification fails, application access is blocked and a warning opens the device's permission settings. Request re-pairing there and let the other device explicitly approve it through a notification.
• Manage receiving content, screen sharing, shared-file lists, remote control and automation separately for each device. Joining a room does not grant remote-control or Shell permission.
• Approve remote automation for the current connection, or save Always allow or Deny for its permission group. Normal reconnection preserves saved settings and verifies the device again before applying them.

Pairing belongs to the local browser or desktop profile. It is separate from MCP client tokens and is not shared through an account. See device pairing and content permissions.

File library and transfers

• Import files or folders through a picker or drag and drop, and send or forward files from chat or the library. Folders are packaged as ZIP archives.
• Track progress, pause, resume, retry, or cancel transfers, reusing cached chunks and already available content.
• Keep a content-deduplicated local library with explicit sharing controls and a shared file list available across rooms.
• Browse a connected member's shared files with search, sorting, previews, and batch downloads. Downloads enter the library and task list without adding chat messages.
• Room attachments are downloaded on request by default. Enable small-file automatic downloads per room with a shared size limit in Transfer settings.
• Choose browser storage or a real directory in File storage settings. Web defaults to IndexedDB; desktop defaults to a local directory. Supported browsers can mount a directory after permission is granted, and directory changes synchronize with the file library.
• Automatically migrate old IndexedDB files and resumable chunks with progress feedback. Old file databases are removed only after the new data is verified.
• Preview files with cached video thumbnails. Save IndexedDB files to your device, use Save As for directory files, or reveal a Windows file in Explorer.
• Save a batch to one destination directory, resolve name collisions with overwrite, skip or keep both, and apply a choice to all remaining conflicts. Imports and saves show progress and cancellation controls and continue when the file-cache dialog is closed.

Importing or receiving a file does not automatically share it. Newly sent files are shared automatically; sharing can be turned off in the library. Peers can browse only complete, shared content when their file-list permission allows it.

Changing the default storage affects new files; existing files, active transfers and recordings keep their original location. Unfinished directory files use a .part suffix and cannot be previewed or shared. If a browser rejects a filename, directory storage can add .weblink on disk while keeping the original name in Weblink and transfers. Browser directory access and batch saving depend on picker support and permission; reopening the page may require authorization again.

Meetings and screen sharing

• Share a camera, microphone, and multiple screens with grid or featured layouts, pinning, fullscreen, picture-in-picture, and independent audio controls.
• Adjust resolution, frame rate, and bitrate during a session, and choose audio formats supported by the current device and runtime.
• On Windows, select displays or windows with previews, use DXGI or Windows Graphics Capture, and choose available software encoders or H.264/HEVC hardware encoding. High-refresh options follow connected displays.
• Supported Windows hardware encoders receive GPU textures without a CPU frame round trip. Automatic selection prefers the capture GPU's encoder, while unsupported paths retain the memory-input fallback. Software and hardware encoders share variable-frame-rate scheduling for static screens.
• On compatible NVIDIA devices, prefer native NVENC for H.264/HEVC, with Media Foundation fallback if it is unavailable or fails. Intel and AMD use their available Media Foundation encoders. Statistics identify the active encoder.
• Compatible viewers share native encoders, with keyframe delivery for viewers joining an active stream. Receiver decode failures can trigger another supported codec, and Media Foundation output changes are renegotiated.
• Local preview reuses readback buffers and follows new-frame notifications. Hiding it pauses local presentation while remote streaming continues.
• Inspect stream statistics, ICE routes and connection state, and run peer throughput tests from the application.

HEVC requires a compatible hardware encoder and a receiver with H.265 support in WebRTC. Native screen streams currently use 8-bit SDR YUV 4:2:0. Capture and codec availability are reported by the application; see native media details.

Recording

• Record one selected local or remote camera or shared screen, with only that source's associated audio. Start from its video menu; pause, resume or stop and save from the header status.
• Pause and resume into one file. Closing a menu or the file-cache dialog does not stop recording; source removal or leaving the meeting finishes the recording.
• Save continuously to the storage selected at the start. An unfinished entry remains in the file library until the recording is finalized with duration and seek metadata. A completion notification can open Web preview or the desktop system player, using the shared foreground/background notification settings.
• Reuse supported encoded video and audio from the existing stream to avoid encoding them again. Web and desktop share this path, with MediaRecorder and native audio fallbacks when reuse is unavailable. Bounded recording queues keep slow storage from blocking normal stream delivery.
• Choose Automatic, MKV or MP4 in settings. Automatic uses MP4 for H.264/H.265 and MKV for other supported video codecs. Reused G.722, PCMU or PCMA audio also uses MKV to preserve the original audio.

Recording availability depends on browser APIs and the source's codecs. External players must support the codecs inside the chosen container. Browser directories may need additional time to finalize a recording; unfinished recordings are not guaranteed to be playable or recoverable after a crash or forced shutdown.

Remote control and clipboard

• Control a shared Windows display with a mouse and keyboard, including cursor appearance synchronization and configurable input-release and host emergency shortcuts.
• Use mobile trackpad gestures or direct multi-touch, soft-keyboard and IME input, configurable sampling, and optional keyboard visibility following remote text focus.
• Enable remote clipboard synchronization for text, rich text, images, and files. Copied files can go to the local clipboard or file library, depending on client capabilities; folders are transferred as ZIP archives.
• Enable file drag-and-drop onto the remote screen to copy local files into compatible Windows applications. This copies files into the remote computer; dragging files out into the controller's operating system is not supported.

Clipboard synchronization and remote file drop are off by default and require an active control grant. Their file transfers share a per-operation size limit of 64 MiB by default, configurable from 1 to 512 MiB. Hosts can approve or decline requests, remember a client's permission, and revoke control locally. See remote-control behavior.

AI automation with MCP and WebMCP

Connect an MCP client to a Windows desktop to inspect screens and accessibility trees, control keyboard and mouse input, manage screen sharing, run Shell jobs, and read diagnostics. Calls can target that desktop or a directly connected, paired desktop; each destination enforces its own permissions.

1. On the desktop providing the MCP endpoint, open Settings → Automation, enable MCP, and create a Local MCP token for the client.
2. Copy the URL and Authorization header from the token creation dialog into the MCP client. The default endpoint is http://127.0.0.1:32100/mcp.
3. Enable automation on each desktop that may be operated. A desktop used only to discover and forward calls can keep its own automation switch off.
4. For remote control, join the same room, complete device pairing, and approve the requested automation group on the target. devices.list supplies the peer IDs used by the tools.

The two switches are independent and default to off. A supporting browser has only the MCP switch for WebMCP registration; it can control connected desktops but cannot execute local OS input or Shell commands. WebMCP is unavailable in browsers that do not provide document.modelContext.

• Screenshots return PNG image content, fitting within 1024 × 1024 by default. Use a window or rectangle crop for detail, or request up to 2048 pixels per axis. Pointer coordinates always use the physical desktop coordinate system.
• Keyboard input targets the foreground window by default. Optional window binding ends the input lease when that window loses focus or closes. Moving Weblink itself into the background keeps the automation session active.
• Shell jobs support stdin, EOF, output cursors and target-specific signals, with up to ten concurrent jobs per device. Windows prefers PowerShell 7 (pwsh), falls back to Windows PowerShell when absent, and defaults to UTF-8. Jobs use pipes rather than a PTY and run with the app account's privileges.
• Active AI control uses a sparkle pointer in the header and matching screen labels. The host's configured emergency-stop shortcut also stops automation. MCP token expiry remains independent of remote session approvals.

See automation setup, tools and permissions for a connection example, tool arguments and execution limits.

Connections and local data

flowchart LR
    A[Client A] -->|Join room / SDP / ICE| S[Signaling]
    B[Client B] -->|Join room / SDP / ICE| S

    A <-->|WebRTC Data / Media| B

Both browser and desktop clients use WebSocket signaling for room membership, peer discovery, and WebRTC negotiation. Messages, files, remote input, and media use WebRTC channels. When a direct route is unavailable, TURN can relay the encrypted traffic.

Room passwords protect signaling payloads during negotiation. Display names and avatars are exchanged over WebRTC rather than published in signaling presence. The signaling service does not store chat history or files.

Room messages reach currently connected members; there is no server-side offline message delivery. History, file metadata and preferences stay in the local browser or desktop WebView profile. File contents live in IndexedDB or the selected local directories. Browser and desktop profiles are separate and are not automatically synchronized. Access to a peer's shared files requires that peer to be connected.

Settings and desktop MCP token hashes/listener configuration use localStorage; device identity, pairing keys and chat data use the profile's IndexedDB storage. Clearing profile storage removes that profile's identity and saved configuration. Local desktop development uses a separate WebView profile from built applications; development builds and stable builds share the existing built-app profile.

Shared code and versions

The SolidJS + TypeScript application lives in apps/web. The Tauri app in apps/desktop builds that same frontend with a desktop adapter, shared contracts in packages/platform, and native capture/input implementations in crates.

Web and desktop use one application version from apps/web/package.json. About, copied version information, build metadata, and desktop installers all use this version. Stable Windows builds offer manual update checks in Settings → About and optional automatic checks at startup and hourly. Installed builds support signed, user-confirmed updates; portable builds link to the matching ZIP for manual replacement. Checks never download or install automatically.

Self-hosting

Host the static Web build or use the included Docker setup, then configure a WebSocket signaling backend:

• weblink-ws-worker: Cloudflare Workers + Durable Objects, used by the public service.
• weblink-ws-server: Bun server for self-hosting and LAN use.

Configure STUN/TURN for your network as needed. Signaling servers must support the v2 join acknowledgment. See deployment for hosting, environment variables, managed TURN credentials, and LAN HTTP behavior.

Development

Use the Bun version pinned in root package.json (currently 1.4.2). Clone the repository with its signaling submodules:

git clone --recurse-submodules https://github.com/99percentpeople/weblink.git
cd weblink
bun install --frozen-lockfile
cp .env.example .env
bun dev

This starts the Web app and local Bun signaling. Configure ports and the local signaling URL in .env. For an existing checkout, initialize submodules with git submodule update --init --recursive before installing dependencies.

For desktop development, install the Windows prerequisites in desktop development. If bun dev is already running, reuse its signaling server; otherwise, start local signaling in one terminal:

bun --env-file=.env run dev:server

Then start the desktop app in another terminal:

bun --env-file=.env run dev:desktop

Common checks and builds, also from the repository root:

bun run lint
bun run test:unit
bun run test:integration
bun run build
bun run check:desktop
bun run build:desktop --bundles nsis

The NSIS installer build runs on Windows. See workspace development for the repository layout and testing for focused checks.

Learn more

• Documentation
• Architecture
• Desktop behavior and development
• Device pairing and permissions
• MCP and WebMCP automation
• P2P protocol
• File-transfer protocol
• Deployment
• Changelog
• Media dependency notices: Mediabunny and NVENC interface