Export Spotify playlists to your self-hosted Navidrome music server

This project has been developed with the assistance of various Large Language Models (LLMs) for planning and writing code. All features and functionalities have been tested to meet the project's requirements and quality standards.

• ✨ Features
• 🚀 Quick Start
• 🎯 How It Works
• 📸 Screenshots
• ⚙️ Setup
• 📦 Deployment
• 💝 Donations
• 🛠️ Tech Stack
• 📚 Documentation
• 📝 License

• 🔗 Dual Integration – Connect Spotify & Navidrome simultaneously
• 🎯 Smart Matching – ISRC, fuzzy, and strict matching strategies
• 📊 Batch Export – Export multiple playlists at once
• 🔄 Differential Exporting – Sync only new tracks (single browser session)
• 📤 JSON Export – Export unmatched tracks as JSON
• ⚡ Real-time Progress – Live export tracking with match statistics
• 👁️ Export Preview – Review matches before committing

1. Connect – Login to Spotify and enter Navidrome credentials
2. Select – Browse and check playlists to export
3. Export – Review matches and start the transfer

Matching Strategy Chain:

1. ISRC → Exact match via unique recording code
2. Fuzzy → Similarity matching (80% threshold)
3. Strict → Normalized exact string match

Unmatched tracks can be exported as JSON for later addition to Navidrome.

Login	Dashboard	Export Progress
Connect to Spotify & Navidrome	Browse and select playlists	Real-time progress tracking

• Node.js 18.17+
• Spotify Developer account
• Running Navidrome instance

# Clone & install
git clone https://github.com/betsha1830/navispot.git
cd navispot
bun install

# Configure
cp .env.example .env.local
# Edit .env.local with your credentials

# Run
bun dev

Spotify Setup:

1. Create app at Spotify Developer Dashboard
2. Add one of the following as your Redirect URI. or to Redirect URIs. Spotify only allows the following loopback addresses: http://127.0.0.1:PORT or http://[::1]:PORT
3. localhost: http://127.0.0.1:3000/api/auth/callback
4. Remote host: https://your-domain.com/api/auth/callback
5. Copy Client ID & Secret to .env.local

docker compose up -d

Production Variables:

SPOTIFY_REDIRECT_URI=https://your-domain.com/api/auth/callback # localhost: http://127.0.0.1:3000/api/auth/callback
NEXT_PUBLIC_APP_URL=https://your-domain.com #localhost: http://127.0.0.1:3000

Update Spotify Dashboard with your production redirect URI.

If NaviSpot helps you migrate your music library, consider supporting development:

❤️ Support on Patreon

Your support helps maintain and improve this open-source project! 🙏

Found a bug or have a feature idea? We welcome your feedback!

Please open an issue and include:

• Error messages (screenshots or console logs)
• Spotify account type (Free or Premium)
• Navidrome setup (Local or Remote server)
• Browser you're using to access NaviSpot
• Steps to reproduce the issue
• Expected vs actual behavior

Please open an issue and include:

• Feature description – What you'd like to see
• Use case – Why this would be helpful
• Any examples from other apps (if applicable)

We appreciate detailed reports that help us improve NaviSpot for everyone!

• Framework: Next.js 16 (App Router)
• Language: TypeScript
• Styling: Tailwind CSS
• APIs: Spotify Web API, Navidrome Subsonic API

Feature docs available in docs/:

See full feature index for details.

We appreciate all contributions to NaviSpot!

Want to contribute? Check out our issue tracker for ways to help!

MIT License – Open Source

Copyright (c) 2026 NaviSpot

Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.