The files are on a machine in the other room
Playing your own collection on a phone is two pieces of software, not one. Something on a computer or a network drive keeps the files, reads their names and works out what they are. Something on the phone asks for them and plays them. Almost every problem people hit is a disagreement between those two halves: a format the phone cannot decode, a network share the phone cannot see, or a server quietly converting a file in the background and heating up a laptop to do it.
Which half does what
| The job | Where it happens | What goes wrong |
|---|---|---|
| Keeping the files | A computer, a network drive, a spare machine | It sleeps, and the phone finds nothing |
| Naming and artwork | The server software | Odd filenames match the wrong film |
| Deciding the format | The server, on request | It converts on the fly and the machine roars |
| Playing it | The app on the phone | An audio track the phone cannot decode |
| Getting there from outside | The network, not the app | It works at home and nowhere else |
| Keeping your place | The server, if you let it | Two apps track progress separately |
Advertisement
The apps on the phone
Plex. The easiest of the big three to get working, with the best artwork and the best remote access, because it brokers the connection for you. Some features are held behind its paid tier, and it has grown a lot of content you did not ask for.
Plexamp. The music half of the same server, built by people who clearly care about music. Gapless playback, offline downloads and a far better queue than the main app.
Jellyfin. Free throughout, no account with anybody, no upsell. Remote access is your problem rather than the project's, which is the honest trade for the rest of it.
Emby. Sits between the two: more polished than one, more commercial than the other, with strong live TV and recording support if you have a tuner.
Kodi. Not a client for a server at all, but a media centre running on the phone itself, reading straight from a network share. Heavier to set up and answerable to nobody.
Yatse. A remote control for a Kodi box on the television, so the phone becomes the handset. Also sends a video from the phone to the box in one tap.
VLC. Browses network shares directly and plays essentially anything you point it at. The right first test when another app refuses a file: if this plays it, the problem is the other app.
MX Player. Better gesture controls and subtitle handling than most, and it opens network streams as well as local files. Advertising supported in this build.
Nova. Built specifically for a library on a network share, with proper handling of audio passthrough to an amplifier. The specialist choice for a home cinema rather than a phone screen.
Symfonium. A paid music client that talks to Plex, Jellyfin, Emby and Subsonic servers at once. If music is the point rather than film, this is the app to try first.
DSub. The long-standing client for a Subsonic-style music server, still working, still small, and it caches offline properly.
Audiobookshelf. For a self-hosted audiobook and podcast library, with sleep timers and position sync that survives switching devices mid-chapter.
BubbleUPnP. The translator of this list. It bridges older DLNA devices, a media server and a casting target, and it rescues setups where nothing else will talk to the television.
LocalCast. Pushes a file from the phone or a network share to a television, which is a different job from browsing a library and the one people usually want in a hurry.
Solid Explorer. Mounts a network share as a folder, so copying a film onto the phone before a flight is an ordinary file operation rather than an app feature.
DS video. If the collection lives on a Synology drive, this is the client that already knows about it and needs no extra server software.
Tailscale. The modern answer to reaching your own machines from outside without opening a port on the router. Install it on the phone and the server and they behave as if they share a network.
WireGuard. The same result configured by hand, if you would rather run the tunnel yourself. More work, no third party involved.
Getting it working the first time
- Get it playing on the home network before anything else Remote access, transcoding settings and apps on the television are all later problems. One film, one phone, same WiFi.
- Name the files the way the server expects Most scanning failures are a filename the server cannot parse. Film name and year in the folder name fixes the great majority of wrong artwork.
- Stop the machine going to sleep A server that suspends after ten minutes works perfectly while you are testing and never afterwards. This is the single most common cause of it working on Saturday and not on Sunday.
- Check whether it is converting Every server has a screen that shows whether a stream is direct or being re-encoded. If it is converting for a phone sitting on the same WiFi, change the player before you change anything else.
- Set up remote access last, and deliberately A brokered connection through the server's own service, or a private tunnel of your own. Forwarding a port straight to a media server is the arrangement to avoid.
- Download, do not stream, anything you will watch on a train Every client on this list can keep a copy on the phone. Doing it the night before costs nothing and removes the whole problem.
Out of the house, and on somebody else's television
Away from home, two things change. The connection is slower and less predictable, so the server will usually reduce quality to keep the stream alive, and that is the setting worth finding before a long journey rather than during one. And the phone is now doing the decoding on battery, which is fine for an hour and noticeable over three.
- Music, at any quality worth having
- A film downloaded the night before
- Anything the phone can decode directly
- A tunnel back to your own network
- Large high-bitrate video over mobile data
- Live conversion on a laptop that has gone to sleep
- Casting to a hotel television on its guest network
- Anything that assumes the server is reachable and it is not
Get one film playing on your own WiFi, stop the machine sleeping, then pick the player that avoids conversion. Remote access is the last step, not the first.
Frequently asked questions
Do I need a network drive, or will an old laptop do?
An old laptop is a perfectly good start, with two caveats: stop it sleeping, and expect noise if it ends up converting video. A dedicated drive is quieter and uses less power, not faster.
Why does the same film play on the television and stutter on the phone?
Almost always the audio track rather than the picture. A surround format the television handles natively may force the server to re-encode for a phone, and that conversion is where the stutter comes from.
Is any of this a substitute for a streaming subscription?
Only for things you already own. It plays your own files reliably and does nothing whatever about this week's new releases, which is worth being clear about before building it.
Can several people watch at once?
Yes, and the limit is the machine doing the work rather than the network. Two direct streams are nothing; two simultaneous conversions will flatten a modest laptop.
Read next
Nothing has infected your phone. Something you installed has permission, and the fix is a list in settings.
A phone will happily run a keyboard, a mouse and a memory stick. It will not power a desktop hard drive.
Hard and fast are different things. Almost every game confuses them, and these do not.
