Lavalink

Lavalink is a standalone audio sending node that lets Discord music bots stream audio without it passing through your bot's shards.

  • Media Applications
  • Media Servers
  • Tools & Utilities
Lavalink is a standalone audio sending node that lets Discord music bots stream audio without it passing through your bot's shards. Built on Lavaplayer and Koe, it handles audio processing and playback so your bot can focus on command handling. Used in production by popular bots including FredBoat, Dyno, and LewdBot.

Platform availability

Available on 1 of 10 platforms

  • Unraid
  • TrueNAS (not listed)
  • Umbrel (not listed)
  • ZimaOS (not listed)
  • Proxmox (not listed)
  • Helm (not listed)
  • Mac (not listed)
  • Windows (not listed)
  • Linux (not listed)
  • Any server (not listed)

Health score?A 0-100 score computed nightly from four factors: maintained (40%: recent commits and steady activity), popular (25%: GitHub stars, log scale), easy to install (20%: platforms, install notes, setup guides, Docker image) and light to run (15%: minimum RAM, ARM support). When the source code has been checked, a fifth factor, security check (20%: automated scan for committed secrets, unsafe desktop-app settings, known-vulnerable dependencies and project hygiene; any serious finding caps it at 20), is added. Factors without data are left out and the rest are rescaled.

72/100 Good

Maintained
73last commit 88 days ago
Popular
661,927 GitHub stars
Easy to install
351 install platform, install notes, Docker image
Light to run
95512 MB minimum RAM, runs on ARM
Security check
100no serious findings, CI, tests

Availability: platform listings confirmed today, links checked 53 days ago

GitHub stars
1,927
Open issues
13
Last commit
2026-08-25
Latest release
4.2.2
License
MIT
Activity
stale

Checked 21 days ago - source: GitHub (lavalink-devs/Lavalink)

Resources & Compatibility

Minimum requirements: 512 MB RAM. ARM (e.g. Raspberry Pi) is supported.

Checked 54 days ago - source: Docker Hub image tags and published docs

First-install notes

  • Set the node password and port correctly In your Lavalink client config, set authorization to the same password your Lavalink server uses, and point host and port (often localhost:2333) to where the server runs. Without a matching password or reachable port, your bot can’t connect and music won’t play. source
  • Forward Discord raw events to Lavalink Add a Discord.js raw event listener that calls sendRawData, and set sendToShard so voice updates are sent back to Lavalink. This keeps the bot and audio server in sync; without it, playback can fail or stop. source
  • Turn on debug events while testing During first setup, enable debug events in advancedOptions and log them temporarily. This helps you see connection problems or why tracks won’t start, and you can turn it off later to keep logs quiet. source
  • Unraid Setup Before deploying on Unraid, create the folder /mnt/user/appdata/Lavalink and upload your application.yml file into it. source

Fetched 44 days ago - each note links to its source

Alternatives

No alternatives collected yet.

Common questions

What settings must match between the bot's Lavalink client and the Lavalink server?

Set authorization to the same password used by the Lavalink server, and point host and port to where the server is running, often localhost:2333. If the password or reachable port is wrong, the bot cannot connect and music will not play.

Why should a Discord.js bot forward raw events to Lavalink?

Add a raw event listener that calls sendRawData and set sendToShard so voice updates are sent back to Lavalink. This keeps the bot and audio server in sync; without it, playback can fail or stop.

What debug setting is useful during the first Lavalink setup?

Enable debug events in advancedOptions and log them temporarily. This helps show connection problems or why tracks will not start, and the setting can be turned off later to keep logs quiet.

Which configuration areas commonly cause Lavalink errors?

Common issues involve configuring the Java environment, application.yml, and the network. A troubleshooting guide covers these common errors and fixes.

Answers sourced from tomato6966.github.io, tomato6966.github.io, visihost.in

Community

Collected 53 days ago - public community threads