macOS desktop
Use the signed macOS build if you want the full desktop feature set, background audio, direct room controls, and server management tools.
Use this guide to install VoiceLink, connect to a server, and join your first room.
VoiceLink opens into a server-focused layout. You choose a server first, then review its rooms, room details, and available actions. Main and Community can both appear in the app, and federation can show matching rooms across more than one server.
Use the signed macOS build if you want the full desktop feature set, background audio, direct room controls, and server management tools.
Use the current TestFlight build if you are testing room join, chat, audio monitoring, or server switching on iOS.
Use the browser client when you need quick access from a device without a local install or when testing a server deployment.
Use the server installer path only when you are setting up or managing a VoiceLink server and its related admin services. Docker is supported for VPS and container hosts that already manage reverse proxy and storage volumes.
For container hosts, create a persistent data directory and run VoiceLink behind your existing HTTPS reverse proxy. Replace https://your-server.example with the public URL you will register in VoiceLink.
mkdir -p ~/voicelink-data
docker run -d \
--name voicelink-server \
--restart unless-stopped \
-p 3010:3010 \
-v "$HOME/voicelink-data:/app/data" \
-e VOICELINK_PUBLIC_URL="https://your-server.example" \
-e VOICELINK_HUB_URL="https://voicelink.dev" \
voicelink/server:1.0.0
If a published image is not available on your host yet, use the server tarball or ZIP package first, then build a local image from the extracted server directory.
Use Preview when you want to hear a short sample of room media before joining. The preview ends on its own after the short preview window.
Open room details when you need the room description, server source, visibility, access level, or the list of available actions before joining.
Join the room from the room row or details view. After joining, the room header and user list should update to reflect the active room.
After joining, move to the user list and message area to confirm users, bots, room chat, and system messages. If the room is configured to show chat, messages should appear above the message box.
Use the room menu or user actions to show audio controls only when needed. Volume, mute, monitoring, and media choices should remain available without forcing you out of the room.
VO-Space activates the selected control.If your first room join does not match this guide, send a bug report from Settings and include the build number, server name, room name, and the last action you took before the problem started.