This is the multi-page printable view of this section. Click here to print.

Return to the regular view of this page.

Developers

Information for Developers.

This page is for developers looking to learn more about Navidrome. For information about contributing to Navidrome, see the Navidrome Contribution Guide.

1 - Development Environment

How to setup your local development environment

This is just a summary on how to get started. If you are stuck or have any questions, please join our Discord server and give us a shout on the #dev channel

Any IDE with good support for GoLang and JavaScript/Node can be used for Navidrome development. We suggest using Visual Studio Code, which has excellent support for both languages.

Using VSCode + Dev Container (Docker)

The project includes a VSCode Dev Container configuration for using with Docker. The Dev Container provides all dependencies out-of-the-box. If you prefer to install all dependencies yourself, or cannot/don’t want to install Docker for any reason, see the other sections below for step by step instructions for your OS.

Unix-based systems (Linux, macOS, BSD, …)

  1. Install GoLang 1.23+

  2. Install Node 20

  3. Install TagLib 2.0+

  4. Install pkg-config

  5. Clone the project from https://github.com/navidrome/navidrome

  6. Install development tools: make setup. This may take a while to complete

  7. Test installation: make build. This command should create a navidrome executable in the project’s folder

  8. Create a navidrome.toml config file in the project’s folder with (at least) the following options:

# Set your music folder, preferable a specific development music library with few songs,
# to make scan fast
MusicFolder = "/path/to/music/folder"

# Make logging more verbose
LogLevel = "debug"

# This option will always create an `admin` user with the specified password, so you don't
# have to create a user every time you delete your dev database
DevAutoCreateAdminPassword = "password"

# Move the data/DB folder out of the root. `./data` folder is ignored by git
DataFolder = "./data"

# If you are developing in macOS with its firewall enabled, uncomment the next line to avoid 
# having to accept incoming network connections every time the server restarts:
# Address = "localhost"

To start Navidrome in development mode, just run make dev. This will start both the backend and the frontend in “watch” mode, so any changes will automatically be reloaded. It will open Navidrome automatically in your browser, using the URL http://localhost:4533/

If it does not open a new window in your browser, check the output for any error messages.

For more useful make targets, run make help.

Building it locally

To build Navidrome locally, follow these steps:

  1. Make sure you have all the dependencies installed as mentioned in the previous sections.
  2. Open a terminal and navigate to the project’s folder.
  3. Run the command make build to build the whole project. This will create a navidrome binary in the project’s folder

Building with Docker

If you want to build Navidrome for a different platform than your own dev environment, use make docker-build and specify the OS/Platform as parameters. Example for Linux/ARM:

make docker-build PLATFORMS=linux/amd64,windows/amd64

To get a list of all available platforms, run make docker-platforms.

If you want to build a Docker image with your local changes, use make docker-image. The built image will be tagged locally as deluan/navidrome:develop. This can be overridden by setting the DOCKER_TAG variable. Use IMAGE_PLATFORMS to specify the platforms you want to build the image for. Example:

make docker-image IMAGE_PLATFORMS=linux/amd64,windows/amd64 DOCKER_TAG=mytag

Windows (using WSL)

Even though it is possible to setup a fully working Navidrome development environment in Windows, we currently don’t provide instructions for that (feel free to contribute to these docs if you successfully set it up).

The (arguably better) alternative is to set up the project using Visual Studio Code and WSL, which effectively lets you develop in a Linux environment while still using your Windows system.

Installing WSL

  1. Make sure your Windows 10 is updated.
  2. Go to Settings > Turn Windows feature on or off > Windows subsystem for Linux.
  3. Go to Microsoft Store and download and install any Linux distro you like. For maximum compatibility, we recommend Ubuntu.
  4. Open Downloaded Linux distro, add username and password and then update it using: sudo apt update && sudo apt upgrade -y.
  5. Install needed compilers for building Navidrome: sudo apt install gcc g++
  6. This will create an Linux terminal where you can execute any Linux commands.

Make sure you are using WSL 2.0

Configuring Visual Studio Code

  1. Click on Extensions (present on leftmost column), install Remote Development extension and reload VSCode.
  2. Press F1, execute Remote-WSL: New Window. This will connect your installed Linux distro to VSCode.
  3. Now you can open a VSCode terminal and you’ll be able to run any Linux command.

Common Issues

  1. Because of this WSL issue you need to use your network IP address to be able to login to Navidrome in development mode. Otherwise you will get an Error: Unauthorized when logging in. You can see your network IP address after running make dev.

Now that you have a working instance of Linux running on your machine, follow the steps above for Unix-based system in the VSCode terminal. For more information on working with VSCode+WSL, check their documentation.

Troubleshooting

System limit for number of file watchers reached

If you encounter the Error: ENOSPC: System limit for number of file watchers reached, watch while running make dev on Linux systems, then your system is maxing out the number of files that can be “watched” for changes at one time.

To increase this limit, you can run the command echo fs.inotify.max_user_watches=524288 | sudo tee -a /etc/sysctl.conf && sudo sysctl -p, which adds the line fs.inotify.max_user_watches=524288 to /etc/sysctl.conf and reloads sysctl so the change takes effect. this allows inotify to watch more files and folders for changes at a time.

More information about this can be found here

2 - Creating New Themes

How to create and contribute with new themes

Themes in Navidrome are simple Material-UI themes. They are basic JS objects, that allow you to override almost every visual aspect of Navidrome’s UI.

Steps to create a new theme:

  1. Create a new JS file in the ui/src/themes folder that exports an object containing your theme. Create the theme based on the ReactAdmin/Material UI documentation below. See the existing themes for examples.
  2. Add a themeName property to your theme. This will be displayed in the theme selector
  3. Add your new theme to the ui/src/themes/index.js file
  4. Start the application, your new theme should now appear as an option in the theme selector

Before submitting a pull request to include your theme in Navidrome, please test your theme thoroughly and make sure it is formatted with the Prettier rules found in the project (ui/src/.prettierrc.js). Also, don’t forget to add lots of screenshots!

Resources for Material-UI theming

3 - Translations

Learn how you can contribute with translations for the UI

Translations are currently managed in POEditor. If you want to contribute new translations or help reviewing/proofreading any of the existing ones, please join our Discord server, channel #translations, for translation efforts coordination and to get further instructions.

Contributing with a Pull Request

Alternatively, you can submit a pull request with your proposed changes directly to our project in GitHub. This method requires you to have a GitHub account and some basic knowledge of Git.

If you choose to contribute translations via a pull request, most of the translation files are located in the resources/i18n directory. The English translation file is the only one located outside of this directory. It can be found in the ui/src/i18n/en.json.

Translation Status

Languages with at least 70% of the terms translated:

Language Code Progress Last Updated
Arabic ar 88.14% 2023-03-26
Basque eu 91.24% 2025-03-22
Bulgarian bg 89.18% 2023-11-17
Catalan ca 77.06% 2021-12-18
Chinese (simplified) zh-Hans 89.18% 2024-12-17
Chinese (traditional) zh-Hant 89.43% 2024-12-17
Czech cs 89.18% 2023-08-06
Dutch nl 89.43% 2024-10-01
English en 100.00% 2025-03-22
Finnish fi 99.48% 2025-03-08
French fr 100.00% 2025-03-22
Galician gl 99.23% 2025-02-23
German de 99.48% 2025-02-20
Greek el 100.00% 2025-03-26
Hungarian hu 99.48% 2025-03-07
Indonesian id 99.48% 2025-02-24
Italian it 78.35% 2025-03-24
Japanese ja 90.72% 2025-02-18
Korean ko 89.18% 2024-09-19
Norwegian no 77.06% 2022-11-20
Persian fa 74.23% 2024-05-09
Polish pl 100.00% 2025-03-25
Portuguese pt 100.00% 2025-03-22
Russian ru 100.00% 2025-03-26
Serbian sr 89.43% 2024-10-18
Slovenian sl 89.18% 2023-06-20
Spanish es 98.45% 2025-03-12
Swedish sv 90.72% 2024-12-21
Thai th 90.72% 2025-01-23
Turkish tr 100.00% 2025-03-25
Ukrainian uk 99.48% 2025-03-06
Yiddish yi 91.75% 2025-03-25

4 - Subsonic API Compatibility

Are you a Subsonic client developer? Check out the API features supported by Navidrome

Supported Subsonic API endpoints

Navidrome is currently compatible with Subsonic API v1.16.1, with some exceptions.

OpenSubsonic extensions are being constantly added. For an up to date list of supported extensions, check here.

This is a (hopefully) up-to-date list of all Subsonic API endpoints implemented in Navidrome. Check the “Notes” column for limitations/missing behavior. Also keep in mind these differences between Navidrome and Subsonic:

  • Navidrome will not implement any video related functionality, it is focused on Music only
  • Right now, Navidrome only works with a single Music Library (Music Folder)
  • There are currently no plans to support browse-by-folder. Endpoints for this functionality (Ex: getIndexes, getMusicDirectory) returns a simulated directory tree, using the format: /Artist/Album/01 - Song.mp3.
  • Navidrome does not mark songs as played by calls to stream, only when scrobble is called with submission=true
  • IDs in Navidrome are always strings, normally MD5 hashes or UUIDs. This is important to mention because, even though the Subsonic API schema specifies IDs as strings, some clients insist in converting IDs to integers
System
ping
getLicense Always valid ;)
Browsing
getMusicFolders Hardcoded to just one, set with ND_MUSICFOLDER configuration
getIndexes Doesn’t support shortcuts, nor direct children
getMusicDirectory
getSong
getArtists
getArtist
getAlbum
getGenres
getArtistInfo Requires Last.fm and Spotify integration
getArtistInfo2 Requires Last.fm and Spotify integration
getAlbumInfo Requires Last.fm and Spotify integration
getAlbumInfo2 Requires Last.fm and Spotify integration
getTopSongs Requires Last.fm integration
getSimilarSongs Requires Last.fm integration
getSimilarSongs2 Requires Last.fm integration
Album/Songs Lists
getAlbumList
getAlbumList2
getStarred
getStarred2
getNowPlaying
getRandomSongs
getSongsByGenre
Searching
search2 Doesn’t support Lucene queries, only simple auto complete queries
search3 Doesn’t support Lucene queries, only simple auto complete queries
Playlists
getPlaylists username parameter is not implemented
getPlaylist
createPlaylist
updatePlaylist
deletePlaylist
Media Retrieval
stream
download Accepts ids for Songs, Albums, Artists and Playlists. Also accepts transcoding options similar to stream
getCoverArt
getLyrics Currently only works with embedded lyrics
getAvatar If Gravatar is enabled and the user has an email, returns a redirect to their Gravatar. Or else returns a placeholder
Media Annotation
star
unstar
setRating
scrobble
Bookmarks
getBookmarks
createBookmark
deleteBookmark
getPlayQueue current is a string id, not int as it shows in the official Subsonic API documentation
savePlayQueue
Sharing (if EnableSharing is true)
getShares
createShare
updateShare
deleteShare
Internet radio
getInternetRadioStations
createInternetRadioStation
updateInternetRadioStation
deleteInternetRadioStation
User Management
getUser Hardcoded all roles. Ignores username parameter, and returns the user identified in the authentication
getUsers Returns only the user identified in the authentication
Media library scanning
getScanStatus Also returns the extra fields lastScan and folderCount
startScan Accepts an extra fullScan boolean param, to force a full scan