You turned the DLNA server on, pointed the television at the network, and waited for the folder to appear. It did not. Or worse, it did appear — the folder, the subfolder, the file name with the year in it — and the moment you pressed play the TV flashed "file not supported" and dropped back to the source menu. Either way you are now searching for "DLNA not working Mac", which is where almost everyone lands after twenty minutes of unplugging things. The good news is that DLNA failures are not mysterious. They are boring, and they are countable: the Mac and the TV either can reach each other, or they cannot; the TV either receives the Mac's announcement, or it does not; the file is either something the television's own decoder accepts, or it is not. Four layers, four different symptoms, four different fixes. This guide walks the layers in order, with the checks that actually tell you which one broke, an honest look at where DLNA is the wrong tool on macOS, and the step-by-step checklist that gets a video onto the screen when the protocol refuses to cooperate.
What "DLNA Not Working" Really Means on a Mac
DLNA is not one thing. It is a family of agreements that lets a device holding media (a server) describe what it has to a device that can display it (a renderer). On a Mac setup the server is usually the Mac, running a media server that indexes a folder and announces it on the local network. The renderer is the television, the streaming stick, the console, or the set-top box. Between those two ends there are four independent jobs that all have to succeed before you see a picture, and each one fails in its own recognisable way.
Reachability is the simplest: both devices need an IP address on the same local network segment. If the Mac is on the office VLAN and the TV is on the guest network, no amount of DLNA configuration will help, because the packets have nowhere to go. Discovery is the next step: the server announces itself with multicast packets, the renderer listens for them and occasionally asks again. Multicast is the fragile part of every home network — switches filter it, access points drop it, and mesh systems sometimes treat it as noise. Negotiation happens after discovery, when the TV asks for a file and the two sides compare notes about formats. Decoding is the last step and the least forgiving: in a DLNA push, the television decodes the file itself, and televisions are far pickier than a Mac.
That is why two people with the same Mac and the same television can have completely different experiences. One has a flat network, an access point that passes multicast, and a library of H.264 MP4 files that the TV's decoder was built for. The other has a mesh node in bridge mode with client isolation switched on and a folder full of HEVC in MKV with PGS subtitles, which is a combination no DLNA renderer in a living room is going to open. Same protocol, same app, opposite outcome.
| What you see | Layer that failed | First check |
|---|---|---|
| TV source list shows no media server at all | Reachability or discovery | Are the Mac and TV on the same subnet, with client isolation off? |
| Server appears, then vanishes after a minute | Discovery — multicast or sleep | Is the Mac going to sleep, or is the access point filtering multicast? |
| Folder and file names appear but thumbnails are blank | Negotiation — metadata | Does the server expose thumbnails, and is the TV reading the right profile? |
| "File format not supported" on play | Decoding — renderer limits | Is the file HEVC, MKV, or carrying subtitles the TV cannot render? |
| Picture starts, then freezes or stutters | Throughput or decode speed | Is the TV on Wi-Fi at the edge of coverage while the Mac streams a high-bitrate file? |
| Video plays but there is no sound | Audio codec in the renderer | Is the audio AC3, DTS, or FLAC inside an MKV the TV expects to be plain stereo? |
Find your row. That is the layer to work on, and the rest of this guide is organised around those rows. The single biggest time-saver in DLNA troubleshooting is refusing to change settings at random: if the TV cannot see the server, format support is irrelevant; if the TV sees the server and rejects the file, network settings are irrelevant.
The core idea: know which layer you are in
Discovery problems look like "nothing is there". Negotiation and decode problems look like "there it is, and it will not play". Those two sentences describe almost every DLNA failure on a Mac, and they have nothing to do with each other.
Layer 1: Network Reachability Between Mac and TV
Start with the least glamorous question: can these two devices see each other at all? Open System Settings on the Mac, go to Network, and note the address of the active connection — four groups of numbers separated by dots. Then open the television's network status screen, which is usually under Settings, Network, or About, and note its address. The first three groups should be identical on both devices. If the third group differs, the two are on different subnets and DLNA discovery will never cross that boundary on its own.
Different subnets usually mean one of four things. The television is on a guest Wi-Fi network, which is deliberately isolated from the main one. The router has a separate network for IoT devices, and the TV was sorted into it. The Mac is connected to a VPN, so its traffic is leaving through a tunnel instead of the local network. Or the home has two routers — the ISP box plus a mesh system — and the two devices landed on different ones. Any of these produces the identical symptom: an empty source list on the TV and a working internet connection on both devices, which is exactly why people conclude that DLNA itself is broken.
Client isolation is the other common blocker and it is invisible unless you look for it. Many routers and nearly all guest networks enable a setting called AP isolation, client isolation, or "block LAN traffic", which stops wireless clients from talking to each other even when they share a subnet. The Mac can browse the web, the TV can stream Netflix, and the two cannot exchange a single packet. On a mesh system the setting sometimes appears per node rather than per network, so a device connected to the satellite is isolated while one connected to the base station is not — which explains the maddening case where DLNA works in one room and not another.
The macOS side has its own gate. Recent versions of macOS ask whether an app may access the local network, and if you dismissed that prompt the first time it appeared, the app can be silently blocked from multicast and from connections to other devices on the LAN. Look under Privacy and Security, then Local Network, and confirm the media server or player you are using is switched on there. The application firewall is a second gate: if it is enabled, incoming connections have to be allowed for that app, otherwise the TV's request for a file is refused at the Mac. Both settings are one toggle away, both are easy to forget, and both produce a server that looks alive on the Mac and invisible to the television.
A quick way to separate "network" from "everything else" is to test reachability directly. With the TV's IP address in hand, use Network Utility or a terminal ping from the Mac. A reply means the two devices are on speaking terms and the problem lives further up the stack. No reply means you are wasting your time on DLNA settings — fix the network first, whether that is the guest network, the VPN, or the isolation toggle. Our Mac-to-TV casting guide covers the network prerequisites for AirPlay, Chromecast, and DLNA in one place if you want the broader picture.
Layer 2: Why the TV Never Discovers the Mac's DLNA Server
If the two devices can ping each other, the next job is discovery, and this is where most "DLNA not working on Mac" cases actually live. A DLNA server does not wait to be asked; it announces itself by sending multicast packets to a reserved group address, and it answers search requests from renderers the same way. Multicast is efficient — one packet reaches every interested device — and it is also the first thing a network does badly. Access points drop multicast to save airtime. Switches with IGMP snooping enabled may prune the group if no device has explicitly joined it. Mesh systems sometimes forward multicast only between the base and the nodes, not between two clients on the same node.
Before you blame the network, confirm the server is actually running. Open the player or server app on the Mac and check that the DLNA media server is switched on and that at least one folder is shared. A server with no shared folder will announce itself and then show an empty tree, which looks like a discovery failure from the sofa but is really a configuration one. Then check the renderer side: most televisions cache their source list and only refresh it when they are powered on from standby, or when you explicitly refresh the input list. If you started the server after the TV was already on, the TV may simply not have looked again.
The single most effective trick in this situation is a cold restart of the renderer. Not standby — unplug the television for thirty seconds, or use the full power-off option in its menu, then let it boot with the Mac's server already running. Discovery happens in the first moments after boot, and a renderer that scanned an empty network at 7pm will happily keep showing an empty list at 9pm. Alongside that, restart the server itself so it re-announces on the network, and if the Mac is on Wi-Fi while the TV is on Ethernet, try the reverse: the asymmetry itself is a useful diagnostic, because a wired path that works tells you the wireless path is filtering multicast.
Firewalls deserve one more mention here because they cause a partial failure that is easy to misread. A blocked server often still appears in the TV's list — the announcement is a single outbound packet, and outbound traffic is rarely filtered — but every attempt to browse or play fails, because those are inbound connections to the Mac. So "it shows up but nothing happens when I open it" is not a discovery problem at all; it is an inbound firewall problem. Allow the app through the macOS firewall, confirm the Local Network permission is granted, and try again before you touch anything else.
Finally, sleep. A Mac that goes to sleep stops answering, and the server disappears from the TV mid-browse. In System Settings, under Battery or Energy Saver, enable the option that prevents automatic sleeping when the display is off, at least while you are watching. This is the cause behind the classic "DLNA worked yesterday and stopped today" report: nothing changed except that yesterday you were using the Mac while the film played, and today you walked away from it.
Layer 3: The TV Sees the File but Refuses to Play It on Mac Setups
Now the harder truth. When the server is visible, the folders open, and the file still will not play, the network is fine and the problem is the model DLNA uses. In a classic DLNA push, the server does not send a picture — it sends a URL pointing at the original file, and the renderer fetches and decodes it with its own hardware. The television is the player. Its decoder is a fixed-function chip built to a short list of formats, and that list is much shorter than the list of files on your Mac.
What televisions accept varies by model and year, but the pattern is consistent. H.264 in an MP4 container is close to universal. MPEG-2 in a transport stream is common on older sets. HEVC support exists on newer televisions but is often restricted to particular containers or particular profiles. Matroska — MKV — is where things fall apart: some sets open it, many do not, and the ones that do frequently handle only a subset of what an MKV can contain. Add a subtitle track in PGS or ASS and the renderer may reject the file outright, or play it silently without captions. Add AC3, DTS, or FLAC audio and you get the notorious "video plays, no sound" result, because the picture codec was supported and the audio codec was not.
This is also where server-side profiles matter. A DLNA server describes each file with a profile string and a MIME type, and the renderer decides from that description whether it can cope. Servers that over-claim — declaring every file as generic video — cause renderers to attempt playback and fail mid-stream, which is why you sometimes see ten seconds of video before the TV gives up. Servers that under-claim cause files to be greyed out in the list even when the TV could have played them. Neither behaviour is a bug you can fix from the sofa; it is the inherent fragility of two devices negotiating over a format vocabulary that was never designed to describe modern files.
The practical conclusion is worth stating plainly, because it saves people hours: DLNA playback quality is capped by the television, not by the Mac. No setting on the Mac makes a set-top decoder accept a file it was never built for. You can convert the file, you can pick a different file, or you can change who decodes — and the third option is the one that keeps your library intact. When the Mac decodes and sends a finished picture, the television stops being a player and becomes a screen, and its format list stops mattering entirely. That is the difference our DLNA media server guide describes from the serving side, and it is the pivot this whole troubleshooting exercise eventually reaches.
DLNA vs AirPlay vs Chromecast on a Mac: Which Path Survives
Once you understand that the four layers exist, the choice of transport stops being a brand preference and becomes a question of which layers you want to depend on. DLNA depends on all four. AirPlay and Chromecast depend on reachability and discovery, and then skip negotiation and decoding by sending a picture the Mac has already decoded. Playing on the Mac itself with an HDMI cable depends on nothing but the cable.
| Path from Mac to TV | Who decodes the file | Format ceiling | Subtitles | Discovery fragility |
|---|---|---|---|---|
| DLNA push from a Mac media server | The television | The TV's supported list — often narrow for MKV and HEVC | Only what the renderer supports; PGS and ASS often ignored | High — depends on multicast and renderer caching |
| AirPlay from a Mac | The Mac | Whatever the Mac player can open | Rendered by the Mac, so styled captions travel with the picture | Medium — Bonjour based, needs Apple TV or an AirPlay-capable set |
| Chromecast from a Mac | The Mac, for local files sent as a stream | Whatever the Mac player can open | Rendered by the Mac | Medium — needs the Cast device on the same network |
| Play on the Mac, cable to the TV | The Mac | Whatever the Mac player can open | Rendered by the Mac | None — a cable does not need discovery |
Read the second column carefully, because it explains every symptom in this guide. When the Mac decodes, the television's format list is irrelevant, the container is irrelevant, the audio codec is irrelevant, and the subtitle format is irrelevant. What remains is bandwidth: a 4K stream needs a healthy link, and Wi-Fi at the far end of a house may not deliver it. That is a throughput problem with a throughput fix — move a mesh node, use Ethernet, or drop the cast resolution — not a protocol problem.
AirPlay and Chromecast also remove the subtitle layer that DLNA handles so badly. In a push, subtitles are the renderer's problem: the television has to parse the caption format inside the file, and many sets simply ignore anything that is not a basic text track. When the Mac renders the frame, the captions are already part of the picture, so the font, size, colour, and position you set in the player are the ones that appear on the television. If subtitles matter to what you are watching, that difference alone usually decides the transport.
DLNA still has a legitimate role, and it is worth being fair to it. It is the only one of these paths that works with a renderer you did not have to think about — a television from a brand with no AirPlay support, a console, an old streamer, a receiver with a network input. It also lets one library serve several rooms without a Mac in each one, which is why the protocol survives despite its fragility. The realistic position is: use DLNA when the file matches what the renderer accepts, and stop using it the moment the file does not.
A Step-by-Step DLNA Fix Checklist for Mac
Here is the sequence that resolves the overwhelming majority of cases, ordered so that each step rules out a layer before the next one is attempted. Work down the list, and stop as soon as the picture appears.
-
Confirm the Mac and the TV share a subnet
Compare the IP addresses under System Settings, Network, and in the television's network status screen. The first three groups of numbers must match. If they do not, move one device to the other network — guest networks and IoT networks are the usual culprits — and turn off any VPN on the Mac while you test.
-
Turn off client isolation and check the firewall
In the router's wireless settings, disable AP isolation or client isolation for the main network. On the Mac, open System Settings, Privacy and Security, Local Network, and make sure the media server or player is allowed; then check the application firewall and allow incoming connections for the same app. These two toggles explain most "visible but unusable" reports.
-
Restart the server, then cold-boot the TV
Stop and start the DLNA media server on the Mac so it re-announces, then remove power from the television for thirty seconds rather than putting it in standby. Renderers scan for servers at boot, and a set that has been on since morning is often showing a stale source list.
-
Switch on the setting that stops the Mac from sleeping
Under Battery or Energy Saver, enable the option to prevent automatic sleep when the display is off. A sleeping Mac stops answering mid-browse, which is the usual reason a server that worked last night is gone tonight. Keeping the Mac awake for the length of a film costs very little.
-
Test with a file the television is certain to accept
Play an H.264 MP4 with stereo AAC audio. If that works, discovery and negotiation are healthy and the failures you saw were decode failures. If it does not work, go back to step one — do not start converting files to solve a network problem.
-
Match the file to the renderer, or change the renderer
If MP4 plays and MKV does not, the television's decoder is the limit. Either keep a compatible copy for the living room, or stop pushing bits and let the Mac decode: open the file in a Mac player and cast the picture over AirPlay or Chromecast, where the container and codec no longer matter.
-
Check the audio track separately from the video
Picture with no sound means the video codec was accepted and the audio codec was not. Look for a stereo AAC track in the file's audio menu and select it; if the only tracks are AC3, DTS, or FLAC, that is your answer, and again the Mac-side decode path avoids it entirely.
-
Give the Mac a stable address and a stable name
Reserve its IP address in the router's DHCP table so the server does not change identity overnight, and keep the server's display name short and without symbols. Some renderers cache a server by name and address together, and a changed address looks like a disappeared server.
Run the list once and note where it stops. That stopping point is the layer that failed, and it is the only thing worth fixing next time — because the second failure on the same network is almost always the same failure. If you get all the way to step six with a file the TV will not touch, you have not failed at DLNA; you have simply reached the edge of what a television decoder was designed to do, and the answer is a different transport rather than more configuration.
Keeping a Mac DLNA Server Discoverable Over Time
Fixing DLNA once is a fifteen-minute job. Keeping it working for a year takes three small habits, and they are the difference between a library you trust and one you stop opening. The first is a reserved address: routers hand out addresses by lease, and a Mac whose address ended in one number last month can end in another this month, at which point a renderer holding the old address shows a dead entry. Reserve the address in the DHCP table, or set a static one outside the pool, and the problem stops recurring.
The second habit is a library that a renderer can parse quickly. DLNA browsing is a directory walk over HTTP, one request per folder, and a flat folder of nine hundred files with long names makes a television's sluggish browser feel broken. Group by series or by year, keep the folder depth shallow, and avoid characters that some renderers mangle in URLs — ampersands, question marks, and emoji are the usual offenders. Renaming a file so it sorts predictably also fixes the "the episode I want is not in the list" complaint, which is almost always a paging limit rather than a missing file.
The third habit is knowing which files your renderer accepts and keeping one copy in that shape for the living room. If the television handles H.264 MP4, keep the films you watch on the big screen in that form and leave the HEVC archive for the Mac. It is a small amount of housekeeping that removes an entire category of failure. For the files that will never fit, the Mac-side decode path stays available: open the original in Total Video Player for Mac, which reads MP4, MKV, MOV, AVI, M4V, MPEG, WMV, FLV, WebM, MTS, M2TS, and TS, decodes 4K UHD in hardware on Apple Silicon, and casts the finished picture over AirPlay, Chromecast, or DLNA when a renderer will take a stream. The server side and the player side are described together in our DLNA media server guide.
It also helps to remember that DLNA is a local-network protocol with no cloud component. Nothing about it depends on an account, a sign-in, or an internet connection, and nothing about it is improved by one. If the internet is down and both devices are on the same subnet, DLNA still works — which is a genuinely useful property, and one of the reasons it is worth ten minutes of setup rather than a shrug.
Stop Fighting DLNA on Mac — Play the File the Direct Way
There is a point in every DLNA troubleshooting session where the honest answer stops being "change another setting" and becomes "this file is not going to play on that television". The set decoder accepts a short list, the file is outside it, and no amount of firewall toggling changes the silicon in the TV. Recognising that moment is the actual skill here: it turns an evening of frustration into a thirty-second decision about which transport to use.
The alternative is to keep the Mac in charge of the picture. Open the file in a player that handles the containers and codecs the television refuses — 4K UHD H.264 and H.265 decoded in hardware on Apple Silicon, MKV and AVI and MTS and WebM opened directly, subtitles loaded from a separate file and styled to be readable — and then send the decoded frame to the screen over AirPlay, Chromecast, or DLNA. The television stops negotiating formats because it is no longer being asked to decode anything. The subtitles arrive as part of the image, so the caption format that the renderer would have ignored is simply there, in the font and size you chose. Dual subtitle tracks work the same way, which matters if you are watching with a translation.
What you keep is the rest of the playback toolkit, and it is the reason the setup is worth more than a one-off fix. Playlists queue a whole season instead of one episode at a time. Playback speed up to 10x and slow motion cover lectures, interviews, and match footage. A-B loop repeats a passage without touching the file. Rotate and mirror fix footage that arrived sideways. Screenshot captures a frame you want to keep. Network playback over SMB, NFS, SFTP, FTP, and WebDAV means the file can stay on the NAS and never be copied to the desktop at all — the same library the DLNA server was pointing at, opened directly. If the Pro edition fits your workflow better, the Total Video Player Pro for Mac page lays out the two feature sets side by side.
The positioning is the whole argument in one line: play locally, stream from your network, cast to the big screen. DLNA is one way to attempt the third part, and when it works it is elegant. When it does not — and the reason this page exists is that it often does not — a Mac that decodes the file itself and sends a finished picture is the path that does not care what year your television was built. Our NAS video player guide takes the same idea to a network library, and the casting guide covers the three transports in detail. Start with the checklist above, find your layer, and if the answer turns out to be "the TV will not decode this", stop configuring and let the Mac do the work.
Frequently Asked Questions About DLNA on Mac
Why does my Mac not show up on my TV for DLNA?
The usual cause is that the two devices cannot exchange multicast packets, even though both have working internet. Check that they share the same subnet by comparing IP addresses, turn off client isolation or AP isolation on the router, and confirm the player or media server is allowed under Privacy and Security, Local Network, on the Mac. Then restart the server and cold-boot the television, because most renderers scan for servers only at power-on. If the Mac is on a VPN or a guest network, that alone is enough to hide it.
Why does my TV list the server but say the file format is not supported?
Because DLNA pushes the original file and the television decodes it with its own fixed-function hardware. When the container, video codec, or audio codec is outside the set's supported list, the renderer rejects the file after the server has already offered it. HEVC inside MKV, PGS or ASS subtitles, and AC3 or DTS audio are the most common triggers. Confirming with a plain H.264 MP4 tells you whether the problem is the file or the network.
Does macOS block DLNA by default?
Not by design, but two macOS features can stop it in practice. Recent versions ask whether an app may access the local network, and a dismissed prompt leaves the app unable to send or receive local traffic. The application firewall, if enabled, also blocks incoming connections until you allow the app. Both are visible in System Settings, and both produce a server that appears healthy on the Mac and invisible to the television.
Can Total Video Player for Mac act as a DLNA server?
Yes. It includes a built-in DLNA Media Server that shares a folder on your Mac with DLNA-capable televisions and other renderers on the same network, alongside its role as a player. The server is the serving half of the story; the player is the half that matters when a renderer refuses a file, because it decodes the video on the Mac and casts the finished picture over AirPlay, Chromecast, or DLNA instead of handing the file to the TV.
What is the fastest fix when DLNA stops working on Mac?
Cold-boot the television with the Mac's server already running. It takes thirty seconds and resolves a large share of cases, because renderers cache their source list and only rescan at power-on. If that does not do it, check whether the Mac went to sleep and whether its IP address changed; both make a working server look like a vanished one, and both are fixed in the same settings panel.
Why did DLNA work yesterday and stop working today?
Three changes account for most of these reports. The Mac slept or shut its lid, so the server stopped answering. The router issued a different IP address after a lease expired, so the renderer's cached entry went stale. Or a mesh node rebooted and came back with client isolation or a different multicast setting. None of these involve DLNA itself; they are all about the server disappearing from the network's point of view.
Is AirPlay better than DLNA for playing local video from a Mac?
For files a television cannot decode, yes, because the Mac renders the picture and the television only displays it, so containers, codecs, and subtitle formats stop mattering. DLNA remains useful when the renderer is not AirPlay-capable or when one library has to serve several rooms without a Mac in each. A practical rule is to use DLNA for files that match the renderer and switch to AirPlay or Chromecast the moment one does not.
Do subtitles work over DLNA from a Mac?
Only if the renderer supports the subtitle format inside the file. Many televisions ignore PGS and ASS entirely and handle basic text tracks inconsistently, which is why films with styled subtitles often play without captions over DLNA. When the Mac casts a decoded picture instead, the subtitles are drawn into the image with the font, size, and colour you selected, so they always appear, and dual subtitle tracks can be shown together.
Get the Video on the Screen of Your Mac Setup
DLNA failing on a Mac is rarely one bug. It is a stack of four agreements, and the symptom tells you which one broke: an empty source list means reachability or discovery, a listed file that will not open means negotiation or decode, and a stutter means throughput. Work the layers in order, cold-boot the renderer, keep the Mac awake and its address stable, and most setups come back to life in a few minutes.
For the files that never come back to life — the MKV with PGS subtitles, the HEVC clip the television was never built for, the AC3 track that plays as silence — the fix is not another protocol setting. It is to stop asking the television to be a computer. Let the Mac decode the file it already understands, and send the picture to the screen. Same library, same sofa, no negotiation.
Play It on the Mac and Cast the Picture
Total Video Player for Mac opens MP4, MKV, MOV, AVI, M4V, MPEG, WMV, FLV, WebM, MTS, M2TS, and TS, decodes 4K UHD in hardware on Apple Silicon, plays from SMB, NFS, SFTP, FTP, and WebDAV, runs a DLNA Media Server, and casts over AirPlay, Chromecast, and DLNA — with dual subtitles, subtitle styling, playlists, 10x speed, A-B loop, rotate and mirror, and screenshot capture.