DLNA, built on UPnP discovery, lets a media server advertise itself on your network so that any player can find it without configuration. Switch it on in the NAS settings, open the player, and the library appears. For a VR collection it is the easiest route and not the best one.
In short
- Supported by: Pigasus, SKYBOX, HereSphere, Moon VR Player, 4XVR and DeoVR.
- Not supported by: PLAY'A and Prism VR, which name no network protocols.
- Advantage: no address, no credentials, no setup.
- Drawbacks: file names can be hidden or rewritten, and some servers transcode.
Why it is the easy option
Discovery. A DLNA server broadcasts its presence, so the player lists it without you typing anything. On a network with one NAS and one headset that is a thirty-second setup, and it is why most consumer storage ships with DLNA enabled by default.
It is also the only network protocol DeoVR supports, which matters because DeoVR is free and on every headset. If you want network playback without paying for a player, DLNA is the route.
The two problems
First, names. A DLNA server presents a catalogue rather than a folder, and many of them clean up titles or hide extensions. VR players read projection, stereo and lens tags out of the file name, so a server that tidies names is removing the information the player needs. The symptom is a library that plays with the wrong projection on every file.
Second, transcoding. Some servers re-encode on the fly for compatibility, which at 8K is usually beyond the hardware and produces a worse picture than the original, assuming it plays at all. Turn transcoding off for the VR folder if the server allows it.
When to use it anyway
When the player you want only speaks DLNA, which means DeoVR. When the files are smaller, 4K or 6K, where transcoding risk is lower and names matter less because the projection is obvious. And when you simply want it working in a minute rather than configuring a share.
For a serious 8K library, SMB is the better protocol, and the five players that support DLNA also support it.
What it needs from the network
The same as any other route: sustained bandwidth to the headset. The one published estimate in this market puts 8K at roughly 120 Mbps, so a wired server and a clean 6 GHz wireless link are what make it comfortable. DLNA adds no overhead of its own worth worrying about.
More routes are in the streaming section, and the glossary entry is the short definition.
Which servers behave well
The variable is the server software rather than the hardware. A server that exposes the original file names and does not transcode is perfectly good for VR; one that builds a tidy media catalogue with cover art and cleaned-up titles is working against you. Most NAS operating systems let you choose, and some let you disable transcoding per folder.
If you cannot tell which yours is doing, the test takes a minute: play one file whose name you know contains a projection tag, and see whether the player picks the projection up automatically. If it does, the names are reaching it.
Which VR players support DLNA?
Pigasus, SKYBOX, HereSphere, Moon VR Player, 4XVR and DeoVR. PLAY'A and Prism VR name no network protocols.
Why is the projection wrong on every file?
The DLNA server is probably renaming or hiding them, and the tags live in the file name. Use SMB instead.
Should I turn off transcoding?
For VR, yes. Re-encoding an 8K file on a NAS rarely ends well and the original is what you want.
Is DLNA slower than SMB?
Not meaningfully for file transfer. The differences that matter are naming and transcoding.