Quven vs Plex and Jellyfin: the media server that puts your files first

This is a comparison for people who already have a library: remuxes, two cuts of the same film, an HDR master, an audio track the television refuses to play, filenames no scraper has ever parsed. Which server has the nicer logo doesn’t come into it. What matters is which one copes with that library on the evening you sit down to watch something.

Where each one is the right answer

	Best when	The trade
Plex	You want the largest client ecosystem and are happy inside it	The product has interests beyond your own files
Jellyfin	You want free software you can read, patch and host forever	You are the integrator, and the polish is your job
Quven	Your own collection is the product and playback fidelity decides everything	Closed source, and the managed conveniences are paid

All three positions are reasonable. Do you want to read the server’s code and patch it yourself? Then Jellyfin is the right choice, and you probably know that already. The rest of this article is for the other two columns.

The file comes before the storefront

Quven runs on your own hardware and reads the folders you point it at. It doesn’t rename files, it doesn’t move them, and it doesn’t scan on a schedule you didn’t set. A scan runs when you press the button.

When you press play, the server tries the cheapest route first. If the client can open the file as it is, the file goes out as it is. If the only problem is the container, the server repackages the streams and leaves the picture and the sound alone. A full transcode happens when the device can’t decode what’s on disk, and if that’s happening often it’s worth understanding why before you blame the server.

The difference becomes visible once a library grows past MP4 files. A lossless audio track reaches a native player as it was mastered. An HDR film on an SDR screen is tone-mapped with a Hable curve, so the highlights survive where a plain clamp would flatten them. A styled ASS subtitle stays styled. Those are the three cases that, in our experience, decide whether an evening’s viewing goes smoothly, and none of them shows up in a feature table.

Matching that asks instead of guessing

A personal library is full of truncated titles, missing years, release-group names and two films from different decades that happen to share a word. Quven matches against TMDb, TVDB, OMDb, AniDB with deterministic rules first. When it isn’t sure, it asks you: the doubtful titles go into a review inbox, and clearing a library’s worth of them will usually take one sitting.

AI gets involved only after the rules have given up, for two candidates that score the same, a query that came back empty, or a filename with nothing usable in it. You can use the managed version on a paid plan, bring your own key, or switch it off and never see it. In every case it proposes a match and waits for you to confirm it; nothing is written to the catalogue until you do.

Subtitles are where the engineering went

A media server that gives up on a Blu-ray’s subtitles isn’t ready for a living room. If a file has no subtitle at all, Quven can write one from the dialogue, on your own machine, and the audio never leaves it. If the subtitle is a bitmap track, the PGS, VobSub or DVB kind, the server reads it into ordinary text you can search and restyle, and the film keeps playing untouched. Both of those are free.

The paid line is further along. Correcting a track in the cue editor and translating one into another language are both Max features, and translation sends the finished text only. Your audio stays where it is.

Remote access without a router lecture

You can reach your library from outside on your own terms, with a port forward, a reverse proxy, Tailscale, or whatever you already run at home. That route is free and will stay free. The managed relay exists for people stuck behind carrier-grade NAT, or who would sooner not open the router at all, and it comes with a trust boundary you should read about before you switch it on.

What is actually next

Desktop, the hosted web client, iPhone, iPad, Android phones and tablets, and Android TV are all shipping today. Fire TV and the Samsung, LG and Hisense televisions come next, then Apple TV after launch, and music libraries should follow. Subtitle generation, bitmap recognition and translation have already shipped, so if you read something earlier in the summer that called them almost ready, it’s out of date.

Frequently asked questions

Is Quven open source like Jellyfin?

No. Quven is closed source. It’s free for home use, but you can’t read the server or patch it, and if that matters to you then Jellyfin is the better choice. That’s true even though we’re the ones building Quven.

Can I move my watch history from Plex or Jellyfin?

Yes. Quven reads the existing Plex or Jellyfin database directly and brings over what’s been watched and which playlists exist. Titles are matched by catalogue identity, so a library you’ve already reorganised should still line up. The old server is only read, never modified.

Does Quven transcode less than Plex or Jellyfin?

That depends on your clients far more than on the server. Any of the three will play a file directly if the client can decode it. The difference shows up in the cases where it can’t: how much fidelity survives, which is where the native clients and the subtitle work make the difference.

What does Quven cost?

Local playback, the native clients, hardware transcoding, subtitle generation and bitmap recognition, and remote access you configure yourself are all free, with no ads and no limit on simultaneous streams. The managed relay is Pro. The cue editor and AI subtitle translation are Max.