A self-hosted media server turns the machine that holds your films and shows into the source for every screen in the house. The files stay on hardware you own. The server’s job is to organise them, match the metadata, and give each client the playback path that suits it.
Storage, catalogue and playback are separate jobs
Your folders and disks are still the storage layer, exactly as they are, and Quven scans the folders you choose, builds a catalogue from what it finds, and can keep several physical versions under one logical title. Ordinary library use won’t rename, move or replace anything. The media stays where it is, under the name you gave it.
When you press play, the client and the server settle on one of three routes: send the original file, remux it into a container the client accepts, or transcode the video, the audio or the subtitles. Because those decisions are separate from the catalogue, a well-supported native client can keep more of the source and ask less of the server.
What you need before installing
How much machine do you need? Start with a Windows, macOS or Linux machine that’ll stay reachable for as long as you’re watching. Direct play asks very little of a processor. Simultaneous transcodes and HDR-to-SDR conversion are where extra processor or GPU headroom starts to pay for itself. You don’t especially need a fast disk, though, since reliable read access to the library counts for more than putting every file on the fastest one you own. Read the current requirements and check release availability before you buy anything.
Local-first does not mean isolated
Quven Account carries your identity, the list of linked servers, and the profile data you’d miss if it vanished: watchlists, ratings, reviews, resume points. And your media files and library folders stay on your server. Remote playback can run over networking you manage yourself, or over the optional managed relay when direct inbound access isn’t practical.
The useful test. A self-hosted system should still be a fast local media server on the day you decide you’d rather not pay for managed remote infrastructure. That’s why the free home tier includes local playback, the native clients and remote access you set up yourself.
Frequently asked questions
Do I need a NAS to run a self-hosted media server?
No. Any machine that stays on and can read your library will do, and a small desktop or mini PC will often beat an entry-level NAS at the one job that matters here, which is transcoding when a client can’t play the file directly. A NAS is good at storage and redundancy; playback is a different job.
Does a self-hosted media server work without an internet connection?
But playback does. Quven Account is required the first time a client signs in, and after that the client’ll keep working offline for seven days, with everything on the local network playing as usual throughout. Metadata matching and the managed relay are the two parts that genuinely need the connection.
How much disk space does a film library need?
A compressed 1080p encode runs a few gigabytes. A 1080p remux is typically eight to twenty, and a 4K remux forty to eighty. Plan the archive around the versions you actually keep, because one title can hold several, and it’s the largest one that’ll set the tone.
Is a self-hosted media server free?
Quven is free for home use. That covers local playback and direct play, hardware transcoding, the native clients, subtitles and burn-in, and any remote access you set up yourself. Nine things are free for good, and the plans page lists all nine, so you can check them yourself and needn’t take our word for it, while what you pay for is the managed relay, AI subtitle translation, and two desktop tools that same page marks.