What Is Universal Media Server and How Does It Stream Media to Your Devices?
Updated
Universal Media Server (UMS) is a free DLNA, UPnP, and HTTP/S media server for Windows, macOS, and Linux. You point it at the media you already have, and it makes that media playable on TVs, game consoles, phones, computers, audio receivers, and other DLNA/UPnP renderers on your network. It fits best when your files are spread across folders or drives and your playback devices don't all support the same formats — UMS handles the conversion when a device can't play a file natively.
The core workflow
UMS works as a bridge between where your files live and where you want to watch or listen.
- Install UMS on the computer that holds your media, or on a machine that can reach it. The project offers direct downloads plus package managers including Chocolatey, Homebrew, AppImage, and Docker.
- Point UMS at your media folders. Once configured, the server exposes those folders to devices on your network.
- Browse from a renderer or a browser. On a TV, console, or audio device, open the DLNA/UPnP source list and pick UMS. Alternatively, connect from any web browser on any device to use the web interface, play directly in the browser, or send playback to a device.
- Play. UMS passes the file through untouched if the device supports it; otherwise it transcodes to suit your network, device, and language preferences.
One practical detail from the project: you get access to your media instantly, without waiting for a library scan to finish. Scanning still runs in the background to enable extra features, but it doesn't block playback.
How transcoding decides what you see
The format question is where most media-server setups fail, so it's worth understanding the mechanism. UMS is powered by FFmpeg, MediaInfo, MEncoder, tsMuxeR, AviSynth, VLC, and other tools. MediaInfo inspects each file, and when a renderer reports it can't handle the container, codec, or bitrate, UMS converts the stream on the fly with FFmpeg and related tools.
A concrete example: you have a folder of MKV files with subtitles, and an older TV that only plays MP4 with simple audio. Rather than converting the whole library by hand, you browse the folder from the TV, and UMS transcodes each file as you play it. The same library still plays untouched on a phone or computer that supports the original format.
The trade-off is CPU load: transcoding is real-time work, so a low-power server machine may struggle with high-bitrate video. Direct play avoids that cost entirely.
Supported devices and platforms
| Category | What UMS supports |
|---|---|
| Server OS | Windows, Linux, macOS |
| Renderers | TVs, audio devices, gaming consoles, computers, smartphones, and more via UPnP or DLNA |
| Access method | DLNA/UPnP renderers, or any web browser on any device |
| Physical media | Direct access to disc drives and disc images |
| Online media | YouTube channels, online radio, podcasts, and RSS feeds, viewable from connected devices |
The project describes its renderer support as the largest range of media renderers, with regular improvements.
Features beyond basic streaming
- Dynamic metadata. UMS looks up metadata for your media and integrates with TMDB, Discogs, and MusicBrainz to show cover art and details, and to sync likes/dislikes. You can filter videos by actor, director, genre, or year, and music by artist, genre, or year.
- Web interface. A feature-rich browser view with dynamic pages for every media file, usable from any device on your network.
- Privacy posture. The project states it does not track actions you take in the program, and that external requests are made over secure connections.
Setup considerations before you commit
- Network scope. The project describes your server as being as secure as your home network. Treat UMS as a LAN tool; exposing it beyond your home network changes the security picture and isn't described as a supported use case.
- Where you run it. Because transcoding is CPU-intensive, the machine hosting UMS matters more than the client devices. A always-on desktop or a Docker host on a capable machine is a safer bet than a low-power box if much of your library needs conversion.
- Metadata needs internet access. Cover art and lookups depend on external services, so a fully offline setup will show less rich browsing.
- Online sources are optional. YouTube channels, radio, podcasts, and RSS are add-ons; the core function is streaming your own files.
If your goal is simply to get local video, music, and photos onto whatever screen is in the room — without converting files by hand — UMS is a reasonable fit, especially on a mixed-device household. If you need remote access outside your home network or heavy transcoding on minimal hardware, check those constraints first.