The $748.99 Plex pass and the library underneath
Plex tripled the lifetime pass to $748.99 and the forums spent four days arguing about Jellyfin. The louder question is the easy one. The harder one is sitting on the disk underneath either of them: what your library is actually on, and which vendor has leverage on it.
The new Plex lifetime pass costs $748.99. That is roughly triple the previous number, announced in the same week the company quietly retired several of the "forever" phrasings on its pricing page. The internet did what the internet does, and the bigger forums spent four days arguing about Jellyfin. The louder question (Plex or Jellyfin) is the easy one. The harder one is sitting on the disk underneath either of them.
What people actually mean when they say "migrate"
Installing Jellyfin is the smallest part of the move. A modern setup guide, an evening, a Docker compose file lifted from someone's GitHub. The community has done this work; you mostly copy it.
What costs you is everything that was not files. Watch progress across 600 episodes of something nobody else in the house is allowed to spoil. Playlists you built one slow weekend. The remote-access setup that lets your partner stream from her parents' house at Christmas. The kids' profiles. The metadata you fixed by hand for the foreign-language films that scrape badly. The shortcuts on the smart TV. The muscle memory of three other people in your household who learned this app and not the next one.
That is the actual exit cost, and it is also the reason Plex could price the lifetime pass at $748.99 with a straight face. Most of what holds you in is not the binary. It is the residue you accumulated inside the binary's database, and the household routines that grew around it. That residue is portable to the next vendor only if you set the system up that way from the start, which almost nobody does.
The library underneath does not care which app reads it
Whether the player on top is Plex, Jellyfin, Emby, Stremio, or the built-in "Movies and TV" app on the television, the layer underneath is the same. A pile of mkvs and mp4s, the home videos from 2009 in whatever codec the camcorder used, the ripped CDs from a marriage ago, a few audiobooks, possibly some comics. Files on a filesystem. None of them care which app is reading them this year.
The vulnerability is not the player. The player is a weekend of work to swap. The vulnerability is the storage decision the player encouraged you to make. If your media library lives inside an app's opaque database, or on a vendor NAS that wraps its own format around the drives, or in a cloud bucket where the scanner runs over your files looking for things it does not like, the player is not the part that has leverage on you. The storage is.
The healthier shape is the boring one. Plain files. A filesystem you can read on any computer. A backup that does not require running the application that wrote it. Each player you put on top of that pile is then disposable on the schedule of whatever pricing letter arrives next.
The household-media-archive question
For a household (not a homelab, not a YouTube-sized media operation), the real question is where the underlying files should live. The honest options are short.
Cloud storage works until it does not. Google Drive, iCloud, OneDrive will all hold a media library cheerfully, scan it less cheerfully, and reserve the right to classify a frame in a home video as a problem. The recent Manga artist whose Google account was banned for uploading backups of his own published artwork is the legible version of this risk. The pricing tier is also not yours; it can be renegotiated upward at any moment, which is the same shape Plex just demonstrated with a $748.99 price tag.
Vendor NAS boxes (Synology, QNAP, the rest) put the files on drives in your house, which is most of the way there, but they also put a vendor between you and the format on disk. The same quiet-renovation pattern that hit Bitwarden and Plex this year can hit a NAS vendor next year; the failure mode is the same shape, just with a smaller user base making the noise.
A small always-on machine reading plain files off a normal drive on a normal filesystem is the most boring option, and that is the point. ext4, a USB drive, a quiet ARM board: there is no vendor in the path between the file and the player. Swap the player out every two years and the library stays.
The honest tradeoffs
None of this argues for leaving Plex this weekend. If Plex still works in your household and the $748.99 number is not your problem, the rational move is to stay and to fix the storage question quietly underneath. The hard part is mostly the metadata and the watch state; some of that does not survive a switch and the right answer is to accept the loss rather than engineer around it.
For households that watch thirty hours of streaming a week, the friction of running anything at home will outweigh the savings on a library that is mostly streamed anyway. This post is not a recommendation to self-host the media stack. It is a framing of what the durable layer is and where the vendor leverage actually sits.
Pick the player you like this year. Make sure the files underneath are ones you could move to a different player next year. The next $748.99 lock-in event is going to happen on something; that is the game now. The cheapest answer is to put the durable thing (your files) on a layer the vendor cannot price.