Spotifie runs on a single local Node server that serves the interface, indexes the music on this machine and speaks to the shared catalogue. Two sources of music sit side by side in one library: albums an administrator has published for everyone, and the audio found on this device. Both play through the same player, with the same controls, under stable identifiers that never expose a filesystem path to the browser.
Explore
Powerful Features
Published Catalogue
Albums an administrator publishes are available to everyone who opens Spotifie, including guests who have not signed in. Artwork and audio resolve through short-lived signed links that are requested when needed and never stored.
Local Music Discovery
Spotifie searches the folders music normally lives in — Music, Downloads, Desktop and Documents — reading tags and artwork into a local index. Everything it finds appears as one Local Music collection. After the first pass it only looks at what has changed, recognising unchanged files by path, size and modified time.
Your Own Collections
Build albums of your own from anything in the library, import audio straight from your device, and keep a Liked Songs collection. A published album can be renamed, re-covered or re-described for you alone — the shared record is never touched, and your version stays on this device.
A Complete Player
Play and pause, previous and next, a seek bar you can drag or reach with the keyboard, volume, shuffle that walks a collection once through, and repeat off, all or one. An expanded Now Playing view opens over the page without interrupting the sound, and where the browser supports it the system's own media controls work too.
Dark & Light, Every Screen
A full light theme alongside the dark one, with contrast checked across both, and a layout built for a phone, a tablet and a desktop rather than scaled down from one of them. Your choice of theme is remembered on this device.
Search, Resume and Backup
Search across everything in the library by album or song. Spotifie remembers where you stopped in each track and starts you there next time. Your collections and preferences can be exported and restored — the file carries what you organised, never the audio itself.
Learn
How It Works
Two libraries, one player. Spotifie runs from a single Node server on your own machine. That one process serves the interface, indexes the music already on the device, and reads the catalogue an administrator has published for everyone. Anyone can listen as a guest; signing in adds a profile and keeps your collections and listening positions with your account.
1. Start Spotifie
Start the local server and open it in any modern browser. One process serves the pages, the library API and the audio — on a desktop, a tablet or a phone.
2. Browse the Published Catalogue
Albums an administrator has published are there the moment the page loads, for signed-in listeners and guests alike. Search reaches any album or song across the whole library.
3. Let Spotifie Find Your Music
The first run walks the folders music usually lives in and builds a local index of what it finds. Everything on the device appears as one Local Music collection, listed first. Later runs only look at what changed.
4. Make the Library Yours
Group tracks into albums of your own, import audio straight from the device, keep a Liked Songs collection, and rename or re-cover a published album for yourself without touching the shared copy.
5. Play It, and Pick Up Where You Stopped
One player throughout: shuffle, repeat, seek, volume and an expanded Now Playing view. Spotifie remembers your position in each track, and your collections can be exported and restored at any time.
2
Music Sources
0
Audio Files Uploaded
Local
Index and Playback
Guest
Listening Supported
Your Data
Privacy & Data
Your music stays where it already is. The audio on your device is read where it already sits and played on the device. It is never uploaded to Supabase or anywhere else. Supabase holds your account and serves the catalogue an administrator has published for everyone; Cloudflare hosts the website itself. Your own music and your account stay separate, and deleting one never touches the other.
Local Audio Stays Local
In the Android app you choose one folder with Android's own folder picker, and Spotifie reads the audio inside it. It asks for no storage permission beyond that folder, and never uploads, copies, moves or deletes a file. In a browser, the same is true of the folder you hand it. Only the identifier, tag data and artwork needed to draw the library ever reach the page — the filesystem path never does, and the audio itself is never sent to Supabase.
The Published Catalogue
Album and track descriptions come from Supabase, and published music is streamed over short-lived signed links — so playing a published song needs a connection. To open quickly and to work offline, Spotifie keeps a copy of the catalogue's descriptions and artwork on your device. No published audio is ever downloaded for offline use. Where Spotifie runs beside a helper on your own machine, that helper searches only the music locations it has been configured for, and logs folder names on that machine alone.
Account and Session
Signing in is optional — guests can listen to the published catalogue and to this device's music. If you do sign in, Supabase handles authentication, and the account holds your email address, the display name you choose, and the dates it was created and updated. Your password is handled by Supabase and kept only as a hash; Spotifie never sees it. The session is kept on your device. Spotifie sets no cookies of its own and loads no analytics, advertising or tracking scripts, uses no advertising identifier, and asks for no location, camera, microphone or contacts access.
What Is Kept, and Clearing It
Your playlists, liked songs, listening history, the position you reached in each track, your theme and your player settings are kept on the device you used them on — not in your account, and never in Supabase. The music index and artwork cache live there too. All of it is rebuildable: clear the app's or the site's data and Spotifie starts over.
Deleting Your Account
You can delete your Spotifie account whenever you like: from inside the app, under your profile, or from the account deletion page — which works whether or not you still have Spotifie installed. Deleting an account removes the account itself, the profile held for it, and any administrator rights it had. It does not delete the music on your device. Your files and the folder you chose stay exactly as they are, and anything kept on the device — playlists, liked songs, history — is removed by clearing the app's data, not by deleting the account.
Legal
Terms of Use
Plain terms for a player you run yourself. Spotifie brings together a catalogue published by an administrator and the music already on your own device. By installing or using the application, you agree to the terms below.
Acceptable Use
Use Spotifie to listen to music you are entitled to listen to. Do not attempt to bypass sign-in or the administrator checks, interfere with the local server or the catalogue service, extract or redistribute catalogue media, or use the application to store or distribute unlawful material.
Your Account
Signing in is optional, but if you create an account you are responsible for it and for keeping its credentials to yourself. Administrative access is limited to accounts that have been granted it; do not attempt to obtain it by other means. Tell whoever operates your installation if you believe an account has been misused.
Your Own Music
Spotifie indexes and plays files that are already on your device. Those files remain yours and remain your responsibility: you must hold the rights or permission needed to store and play them. Spotifie does not upload them, does not verify where they came from, and grants you no rights over them.
The Published Catalogue
Albums published by an administrator are provided for listening inside the application. Rights in that content stay with whoever holds them. Downloading, re-hosting or redistributing it, or building a separate service on top of it, is not permitted. An administrator is responsible for having the right to publish whatever they add.
Availability and Local Limits
Spotifie runs on the machine you start it on. It is available while that server is running, and the device library reflects only what that machine can reach. Sign-in and the published catalogue depend on Supabase and on your network connection, neither of which this project controls. Features may change or be withdrawn as the application develops, and no particular level of availability is promised.
Intellectual Property and Warranty
Spotifie is an independent project. It is not affiliated with, endorsed by or connected to Spotify AB, and the Spotify name and logo are trademarks of Spotify AB. The application is provided as is, without warranty of any kind, and is used at your own discretion and risk.
Inclusive
Accessibility
Music is for everyone. Accessibility is part of how the interface is built rather than something added at the end, and it is checked again as the application changes. What follows describes what is in place today. It is a statement of practice, not a claim of formal WCAG conformance, and the work continues.
Keyboard Navigation
Every control can be reached and used from the keyboard. Buttons and links are real buttons and links, volume is a native range input, the seek bar is a focusable slider that answers the arrow keys along with Home and End, and menus, dialogs and the library drawer close with Escape.
Labels and Semantics
Icon-only controls carry accessible names, menus and dialogs carry the roles that describe them, and live regions announce scan results and status messages. Each page keeps a sensible heading order and landmark structure for screen readers to follow.
Visible Focus and Contrast
Focus is never invisible: a distinct focus indicator is drawn on controls across the player, header, library and album pages. Both themes are built from semantic colour tokens, with text, icons and control states checked for contrast in light and dark alike.
Scale, Touch and Motion
Layouts and text scale from a large monitor down to a phone, with touch targets sized for a finger rather than a cursor, and hover effects kept to devices that actually hover. When the system asks for reduced motion, animations and transitions are turned off.