This is the most annoying failure in the whole casting family, because nothing looks broken. The Mac found the television. You clicked it. The TV came out of standby, its little "AirPlay" badge appeared in the corner, and then a rectangle of nothing. Sometimes the audio plays perfectly while the screen stays black, which is almost insulting. No error, no dialog, no spinning wheel — just a black panel where your film should be. The instinct is to blame the network, restart the router, and start reading about ports. That instinct is usually wrong. An AirPlay black screen means the connection already worked, and the fault is further down: in which mode the session opened, in what the content allows, in whether the Mac's encoder ever produced a frame, or in whether the receiver ever decoded one. Four causes, four different fingerprints, four different fixes. This guide walks them in order, with the checks that tell you which one you are looking at, and the one workaround that sidesteps all four.
What an AirPlay Black Screen Really Means on a Mac
AirPlay is two mechanisms wearing one name. The first is a session: the Mac and the receiver find each other over the local network, agree on a format, and establish a channel. The second is a stream: actual pixels travelling from the Mac to the receiver, at a bitrate the link can carry. A black screen is what you get when the first mechanism succeeds and the second does not. That distinction matters enormously, because it rules out everything people normally troubleshoot. Discovery is fine. Passwords are fine. The two devices can see each other. If they could not, you would have no device in the list at all, and that is a completely different page.
It also matters that "AirPlay" covers three different things on macOS, and they fail in unrelated ways. Screen mirroring captures your entire display, encodes it continuously, and sends it as a live video feed. Video handoff is what a player app does when you press its own AirPlay button: the app hands one video to the receiver, which plays it as a single item. And audio routing makes the receiver a sound output device for the whole Mac — no picture involved at all. Two of those three can produce a black television, and one of them produces a black television on purpose because there was never any video to show.
Then there is the question of who is responsible for the image. In mirroring, the Mac encodes and the receiver decodes a continuous feed it cannot inspect or renegotiate. In video handoff, the receiver is asked to play a specific stream with specific properties. Those two paths have almost nothing in common when they break, which is why a fix that rescues one does nothing for the other. Before you change a single setting, work out which path you are on. The table below maps the symptom to the cause.
| What you actually see | What it means | Where to look first |
|---|---|---|
| Sound plays on the TV, screen stays black, no mirrored desktop | The receiver was opened as an audio device, not a display | Check One — the sound output list |
| Mirrored desktop appears, but one rectangle inside it is black | Protected content suppressing its own picture | Check Two — copy protection |
| Connected for a moment, maybe a flash of desktop, then black | The display encoder stalled or lost its source frame | Check Three — resolution and display path |
| Session stays "connected" indefinitely with nothing on screen | The receiver accepted the handshake and never decoded | Check Four — input, wake state, receiver |
| Black only for one particular file, other files cast fine | Not AirPlay at all — the receiver refused the stream's format | Cast the file from a player instead of mirroring |
Read that table twice, because most people are in the first or the last row and spend their evening on the wrong one. A black screen with working audio is almost never a video problem; a black screen on a single file and nothing else is almost never an AirPlay problem. Once you have picked your row, the rest of this page is short.
Check One: Is Your Mac Sending Audio Instead of Video?
Start here because it is the single most common cause, and because it is the only one where your Mac is behaving exactly as designed. macOS treats an AirPlay receiver as an output device in the sound settings, completely independently of the Screen Mirroring menu. If you selected the receiver there — or if some app did it for you — the Mac opens an audio-only session. The television wakes, shows a now-playing card with the track or the app name, and plays sound. Your desktop never leaves the Mac. There is no picture to be black; there is simply no picture.
The tell is easy once you know it. Open Control Center and look at Screen Mirroring: it will not show an active display, because none was ever requested. Then look at the sound section of the same panel: the receiver is ticked as the output. In the menu bar, the AirPlay icon is the audio variant rather than the display variant. On the television, you see a music or media card instead of a mirror of your desktop. Every one of those signals says the same thing — the video path was never opened.
The fix is to end the audio route and start a display session instead. In Control Center, open Screen Mirroring and pick the receiver from the display list rather than from the sound list. If the Mac keeps reverting, the cause is usually that something switched the output on your behalf: a conferencing app that grabbed the receiver when it started, a media player that set it as its preferred output, or the simple fact that macOS remembers the last output device and re-applies it when the receiver reappears. Switching the sound back to the Mac's speakers before you mirror is a reliable way to stop the two from fighting.
There is a second layer to this that catches people who are already doing the right thing. Many player apps have their own AirPlay button inside the window, and that button is not the same control as the system Screen Mirroring menu. The in-app button performs a video handoff: the app sends one item and the receiver plays it as a single stream. The menu bar control mirrors the whole display. If you press the system control when you meant the app's button, you mirror a window that contains a video, which is a heavier and more fragile arrangement — and if the app in question refuses to be captured, you get the black rectangle described in the next check. Match the button to the job: in-app button for a file you are watching, system mirroring for a desktop you want to show.
Check Two: Why Protected Video Blacks Out on a Mac
AirPlay honours the copy-protection flags that content carries. When a stream is marked as protected and the receiver cannot verify an end-to-end protected path, the correct behaviour is to suppress the picture entirely rather than show it degraded or partially scrambled. This is why you get black instead of an error message: silence is the feature. A polite dialog saying "this content cannot be mirrored" would be more useful, but it would also tell anyone probing the system exactly where the boundary is, so the industry's habit is to show nothing at all.
What trips this is commercial material: a film playing in a browser streaming service, a rented title, a purchased movie opened in the system television app, some subscription apps. What does not trip it is your own material — camera footage, phone clips, exports from an editor, screen recordings you made yourself, home video, anything that left a tool on your own machine without a protection flag attached. This is worth stating plainly because it is the fastest way to rule the check out: if the file is yours, and it plays on the Mac, copy protection is not your black screen.
The fingerprint is distinctive. Mirror your desktop with a protected video playing and you will see your wallpaper, your windows, your dock — and a black rectangle exactly where the video was, with the player's own controls sometimes still drawn on top of it. The frame is blanked; the app's chrome is not. If your entire screen is black including the menu bar, you are not in this check, and you should be looking at the encoder instead.
There is no setting that turns this off, and there is no reason to look for one. What you can do is change the path. Supported apps can request a protected handoff through their own AirPlay control, which negotiates the protected route properly instead of trying to capture a protected window — that is why the in-app button sometimes works where mirroring produces a black square. For everything else, the practical answer is that protected material wants to be played by a receiver that is licensed for it, and unprotected files — the ones this whole cluster of guides is about — want a Mac that decodes them and sends the result. Those are different jobs, and the second one never blacks out.
Check Three: The Mac's Screen Encoder Never Started
Screen mirroring is a live encode. The Mac captures the display, compresses every frame, and pushes it out continuously for as long as the session lasts. That pipeline has a startup sequence, and if it never produces a first frame, the receiver sits there holding a valid session with nothing to display. The user-visible result is a black screen that is genuinely connected. It is the most misleading of the four, because the Mac believes it is mirroring and the television believes it is receiving.
The triggers are all about the display, not the network. A scaled resolution that the encoder cannot accept cleanly is the classic one: macOS offers a long list of "more space" and "larger text" modes for Retina panels, and some of those intermediate modes are rendered by the window server in a way that a live capture handles badly. A refresh rate that does not match what the receiver will accept is another. So is starting a mirroring session while the display is still settling from a change — plugging in a monitor and mirroring within the same second is a reliable way to get black. Docks and external GPUs that drive a panel through a display-link style driver add a third path the capture layer does not always follow. Running on battery in a low-power state can throttle the encoder enough that the first frame misses its deadline, and clamshell mode with the lid shut removes the display the capture was reading from.
The fingerprint here is motion. You get a connected state, sometimes a brief flash of your desktop, then black — and disconnecting and reconnecting repeats the flash-then-black cycle identically. That repetition is the giveaway: a receiver problem tends to be stable, while an encoder problem tends to fail at exactly the same point every attempt. If the Mac's own screen goes dark at the same moment, that is a further hint that the display is being handed over and the encoder is running; the fault is then on the receiving end, which is Check Four.
The fixes are boring and effective. Set the display to its default scaled resolution — the option macOS labels as default for the display — rather than an in-between mode, and pick a standard refresh rate. Connect the mirroring session a few seconds after any display change has finished. Take the dock and the external GPU out of the path and test with the built-in display alone; if that works, you have found the culprit and can reintroduce hardware one piece at a time. Turn off the low-power setting while you test. Quit any app that is already encoding video, because the hardware encoder is a shared resource and a background export will win the race more often than you would expect.
One more variation belongs here. If mirroring works fine for a static desktop but goes black the moment you play a video in a window, the encoder is fine and the trouble is one layer up — either protection, as in Check Two, or the capture of a window that the system will not share. Dragging the video into a plain window, or using the app's own AirPlay button instead of mirroring, resolves both.
Check Four: The Receiver Accepts the Mac but Shows Nothing
The last place to look is the far end, and it is where a surprising number of cases actually live. The receiver completed the handshake, so it is awake and on the network, but it is not putting your picture on the panel. The most mundane version is an input mismatch: the television switched itself to the AirPlay splash, and then something — a set-top box waking up, a console, a scheduled app — pulled the panel back to a different input while the AirPlay session stayed alive in the background. The session is real. The picture is being shown to nobody.
Next is a receiver that fell asleep or invoked its own screensaver mid-session. Apple TV units do this if the attached display reports no activity, and some televisions with built-in AirPlay treat a static mirrored desktop as a still image and dim or blank after a while. Cold-booting the receiver with the Mac's session already ended is the fastest test: pull the power, let it come back, then connect fresh. This resolves a large share of "it connects and shows nothing" reports because it clears the receiver's cached session state, which can otherwise believe a stream is still running when it is not.
Third is the receiver implementation itself. Apple's own hardware handles a mirrored Mac display as a documented, well-trodden path. Third-party televisions that advertise AirPlay support implement that path themselves, and their behaviour when the stream's properties are unusual — a very high resolution, an odd frame rate, a wide colour profile — can be to show a black panel rather than fall back. If the same Mac mirrors perfectly to one receiver and shows black on another, you have your answer, and no amount of Mac-side configuration will change it. Update the television's firmware, drop the mirrored resolution a step, and if neither helps, stop mirroring to that set.
Fourth, and distinct from the discovery problems covered elsewhere in this cluster, is the media path rather than the control path. The handshake is a small amount of unicast traffic that gets through almost anything. The video is a sustained high-bitrate flow that does not. A Mac on the edge of Wi-Fi coverage, a mesh node that roams mid-session, a VPN client that captures all traffic, or a receiver on wired Ethernet while the Mac is on a distant access point can all produce a session that never dies and a picture that never arrives. The tell is that the black screen comes with stuttering audio or a picture that occasionally appears for a second. Move the Mac closer, put both devices on the same band, disable the VPN, and test again before you blame the receiver.
How to Fix an AirPlay Black Screen on Mac, Step by Step
Work these in order and stop at the first one that changes the symptom. The order is deliberate: it goes from the cheapest check to the most invasive, and each step eliminates one of the four causes above so that later steps are not guesses.
-
Identify which mode is actually open
Open Control Center and look at both lists. If Screen Mirroring shows no active display but the sound output is set to the receiver, you are in Check One and the fix is one click. If Screen Mirroring shows the receiver as connected, write down what the television is displaying, then move on.
-
End the session completely before retrying
Disconnect from the Screen Mirroring menu, wait five seconds, then reconnect. A session that is torn down and rebuilt tells you whether the failure is repeatable at the same point. Flash then black every time is an encoder problem; connected with nothing at all is a receiver problem.
-
Check the receiver's input and wake state
Confirm the television is on the input that AirPlay uses, not on a set-top box or a console. Wake the receiver with its own remote rather than relying on the AirPlay request to do it, then reconnect. If the picture appears, the problem was the receiver's power state, not the Mac.
-
Set the Mac's display to its default resolution
In Displays, choose the mode macOS marks as default for the display rather than an intermediate scaled option, and select a standard refresh rate. Reconnect and test. This clears the largest single category of encoder stalls.
-
Remove the dock, the external GPU, and low-power mode from the path
Test with the built-in display only, on power, with the battery-saving mode off. If mirroring works, reintroduce the hardware one piece at a time to find which element broke the capture. Disconnect any app that is encoding video in the background before retesting.
-
Take the VPN and the far end of the Wi-Fi out of the equation
Disable any VPN client on the Mac, bring both devices onto the same network and the same band, and move the Mac within a normal distance of the access point. Sustained bitrate is what mirroring needs; a link that passes a handshake can still fail the stream.
-
Cold-boot the receiver, then reconnect
End the session on the Mac first, then pull the receiver's power for thirty seconds. This clears cached session state that can leave a receiver believing a stream is live. Reconnect only after the receiver has fully finished starting up.
-
Skip mirroring and cast the file itself
If the file plays perfectly on the Mac but the television shows black, the problem is the transport, not the video. Open the file in a player and use its own casting control, which sends one video rather than a captured desktop. This is the step that fixes the cases nothing else will.
If you reach step eight, notice what you have learned: the Mac decodes the file without complaint, the receiver is awake and reachable, and the only thing that failed was the mechanism used to move pixels. That is a strong signal. It means the file is fine and the display path is fine, and the answer is a different transport rather than another configuration change. The next section is about that transport.
Cast the File Instead of Mirroring the Mac
Mirroring exists to show a desktop. Using it to watch a film is a workaround that happens to be convenient, and it carries every weakness described above: a live encoder that can stall, a capture that protection can blank, a bitrate that scales with the whole screen rather than the video, and a resolution decided by your display settings instead of by the movie. Casting a file is the other arrangement. The player opens the video, decodes it, and sends that one stream to the receiver. There is no desktop to capture, so the encoder problems disappear; the player owns the pixel pipeline, so a window it is allowed to draw is a window it can send; and the bitrate follows the video rather than your wallpaper.
| Mirror the Mac's screen | Cast the file from a Mac player | |
|---|---|---|
| What travels | A continuous capture of the whole display | One video stream, at the file's own resolution |
| Who decodes | The Mac encodes, the receiver decodes everything you see | The Mac decodes; the receiver displays the result |
| Subtitles | Whatever the mirrored player draws, at whatever size fits the capture | Drawn by the player, with the font, size, and colour you chose |
| Resolution and refresh | Inherited from your display settings | Follows the video, not the desktop |
| Black screen risk | Encoder stalls, capture refusal, protection blanking | None of those three apply |
| Best for | Showing a slide deck, a browser, or an app to a room | Watching a video file on a television |
The practical version of this is what Total Video Player for Mac does. Open the file — MP4, MKV, MOV, AVI, M4V, MPEG, WMV, FLV, WebM, MTS, M2TS, or TS, with the audio inside it including MP3, AAC, AC3, FLAC, WAV, WMA, OGG, and M4A — and the app decodes it on the Mac, 4K UHD included, with H.264 and H.265 handled by the Apple Silicon media engine. Then send the picture to the screen over AirPlay, Chromecast, or DLNA. Because the television is no longer being asked to open the container, the format arguments that produce a black panel on a mirroring session never arise. If you want the whole picture of how the three transports differ, the casting guide compares them directly, and the AirPlay from Mac guide covers the receiver side in more depth.
What you keep is everything that makes a player worth having. Dual subtitle tracks for watching with a translation, subtitle styling so captions are readable from the sofa, playback speed up to 10x for lectures and interviews, A-B loop for a passage you want to hear again, playlists for a whole season, rotate and mirror for footage that arrived sideways, and a screenshot control for a frame you want to keep. Files can stay where they are too: SMB, NFS, SFTP, FTP, and WebDAV playback means the film never has to be copied off the NAS, and the built-in DLNA Media Server covers the case where the receiver would rather browse a folder than accept a cast. The positioning is the argument in one line — play locally, stream from your network, cast to the big screen. The Pro edition page sets out the two feature sets if you want the paid tier, and the product page has the full list.
One honest caveat, because it saves time: mirroring is still the right tool for the things it was built for. Showing a Keynote deck, walking someone through an app, demonstrating a website to a room — those need a desktop on the screen, and a player cannot help. The mistake is using a desktop transport for a file, then spending an hour repairing the desktop transport. Pick the tool by what you are showing: a file goes through a player, a desktop goes through mirroring.
Frequently Asked Questions About AirPlay on Mac
Why does AirPlay play audio but show a black screen on my Mac?
Because the receiver was opened as a sound output device rather than a display. macOS keeps those two lists separate, so selecting the television in the sound settings starts an audio-only session: the set wakes, plays sound, and never receives a picture. Open Control Center, check that Screen Mirroring shows no active display, switch the sound output back to the Mac's speakers, and then start the session from the Screen Mirroring menu instead.
Why is only part of the mirrored screen black on my Mac?
That is copy protection, not a fault. When a player is showing protected material, the system blanks that region rather than sending it to a receiver whose protected path cannot be verified. Your wallpaper, windows, and menu bar keep mirroring normally while the video area goes black, often with the player's own controls still drawn on top. Nothing in the settings will change it; the file itself carries the restriction.
Does a black screen mean my Wi-Fi is too slow?
Sometimes, but it is not the first suspect. A slow link usually shows as stutter, blocky frames, or audio that keeps playing while the picture freezes, because the session degrades rather than dying. A clean, stable black screen from the first second points at an encoder stall or a receiver that never decoded. The network is worth checking when the black screen is intermittent or when the Mac is at the edge of coverage.
Why does AirPlay show a black screen for one specific video file?
Because the receiver is refusing that stream, not failing at AirPlay. Mirroring a file means the Mac captures whatever it draws, so a single file that blacks out while others work is usually a protection flag on that file, or a receiver that will not accept its properties. Opening it in a Mac player and casting from inside the app bypasses the receiver's format negotiation entirely.
Can I fix an AirPlay black screen without restarting anything?
Often, yes. Ending the session from the Screen Mirroring menu, waiting a few seconds, and reconnecting from a different display mode clears an encoder that stalled on its first frame. If that does not work, switch the Mac's display to its default resolution and try again before resorting to a restart — that single change resolves more cases than rebooting either device.
Why does mirroring work on one TV and show black on another?
Because the two receivers implement the mirrored display path differently. Apple's hardware follows a documented path for a captured Mac display; third-party televisions build their own implementation and can fail quietly when the stream's resolution, frame rate, or colour properties are outside what they expect. If one receiver works and the other does not, the Mac is fine and the fix is a lower mirrored resolution or a different transport.
Does casting from a Mac player avoid the black screen?
It avoids the three causes that come from mirroring, because there is no desktop capture involved: no encoder to stall, no protected window to blank, and no display resolution inherited from your settings. Total Video Player for Mac decodes the file on the Mac and sends the finished picture over AirPlay, Chromecast, or DLNA, so the receiver only has to display what it is given.
Is a black screen a sign the Apple TV is faulty?
Rarely. A receiver that goes black mid-session is usually asleep, showing a screensaver, or has had its input switched by another device, and a cold boot with the Mac's session already closed clears most of those. Persistent black on every source, including the receiver's own menu, is a hardware question — but that is the receiver failing at everything, not failing at AirPlay.
Get the Picture Back on the Big Screen From Your Mac
The useful thing about an AirPlay black screen is that it is not vague. It is one of four specific failures, and each one announces itself if you know what to look for: audio with no picture means the wrong mode was opened; a black rectangle inside a working desktop means protection; a flash followed by black on every attempt means the encoder stalled; a session that stays connected with nothing at all means the receiver never decoded. Work the checks in order, and you will usually land on the answer within a couple of minutes rather than a couple of hours.
And when the answer turns out to be "this transport will not carry this file", stop repairing the transport. The Mac can already play the file — that is what it was doing before you tried to put it on the television. Let it finish the job: decode the video, draw the subtitles, and send the picture. That is not a workaround for AirPlay. It is the arrangement AirPlay was designed for, used the way it was meant to be used.
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.