What Are Plugins?
Plugins extend Lavalink’s core functionality by providing:- Custom Audio Sources - Support for additional streaming platforms (Spotify, Apple Music, Deezer, etc.)
- Audio Filters - Advanced audio processing and effects
- API Extensions - New REST endpoints and WebSocket handlers
- Utility Features - Lyrics, sponsor segment skipping, search enhancements, and more
How Plugins Work
Automatic Download
Plugins can be automatically downloaded by configuring them in your
application.yml filePlugin Architecture
Plugins are built using the Lavalink Plugin API and Spring Boot framework.Plugin Capabilities
Audio Source Managers
Add support for new streaming platforms and audio sources
Media Container Probes
Support for additional media container formats
REST Endpoints
Create custom API endpoints for your specific needs
Request Interceptors
Modify or intercept existing REST endpoint behavior
Audio Info Modifiers
Customize track and playlist JSON data
Type-Safe Configuration
Define custom configuration properties in application.yml
Plugin Configuration Methods
There are two ways to use plugins with Lavalink:1. Manual Installation
Place plugin.jar files directly in the plugins directory:
You may need to create the
plugins directory manually if it doesn’t exist.2. Automatic Download (Recommended)
Configure plugins in yourapplication.yml to download them automatically:
- No manual file management
- Version control through configuration
- Easy updates and deployment
- Custom repository support
Default Repositories
By default, Lavalink uses the official Maven repository:- Releases:
https://maven.lavalink.dev/releases - Snapshots:
https://maven.lavalink.dev/snapshots
Plugin Directory Configuration
Customize where Lavalink saves and loads plugins:Next Steps
Using Plugins
Learn how to install and configure plugins
Available Plugins
Browse the list of available plugins
Developing Plugins
Create your own custom plugin