A MacBook with a black screen can be fully awake, fast asleep, or completely without power, and the screen alone will not tell you which. The keyboard backlight, the fan, and the sound of the startup chime each narrow the possibilities, and skipping that observation leads people to recovery steps for a machine that only needed its brightness turned up. This guide shows how to fix MacBook screen black by establishing what the machine is actually doing before choosing a remedy.
Black screens divide into two families. In one, the machine is running and only the display is dark, which points at brightness, an external display setting, or a display fault. In the other, the machine never started, which points at power or battery. Telling those families apart in the first minute changes everything that follows.
Why This Fault Appears
Before the steps, it helps to know that this fault rarely has a single cause, and the table below separates the likely causes by the sign you actually see, so you can start at the row that matches your situation rather than at the top of a generic list. Working out how to fix MacBook screen black starts with that match, because the right first step depends on the symptom in front of you.
| Likely cause | Sign you will see | First check |
|---|---|---|
| Brightness at minimum | Screen dark but machine running | Raise brightness and test |
| Stuck power state | No response to power button | Force a shutdown and restart |
| Display cable fault | Picture changes with lid angle | Test with an external display |
| Login or software freeze | Black after Apple logo | Boot into Safe Mode |
| External display conflict | Black only with a monitor attached | Disconnect the monitor |
| Hardware failure | Black after all software steps | Book a service check |
Note what changed before the fault began, what still works, and what you have already tried, because those three facts turn a frustrating afternoon into a short sequence of tests. A short note on those points, written before you start, also makes any later conversation with support far shorter, since you can describe what you have ruled out instead of repeating the symptom.
Before You Boot Into Safe Mode
Read the whole guide once before changing anything, because the order matters, and a step skipped early often returns as a larger problem later. Where a price or a feature is given, check it on the vendor page before you commit, since pricing and features change, and the right choice depends on your situation and your existing setup.
When you approach fix MacBook screen black, keep a simple log of each test and its result, even a few lines on paper. Change one thing, test, and note the result before moving on, because changing three things at once and seeing an improvement leaves you unsure which change helped, and the fault returns when the unhelpful changes are undone.
Back up anything important before the later steps, even if you do not expect to reach them. A backup made while the device still works is worth far more than a backup attempted after a destructive step, and it removes the fear that keeps people from taking a legitimate last resort step. Check that the backup completed, rather than assuming it did, since a backup that never finished offers no protection at all.

How to fix MacBook screen black in the Right Order
Working through fix MacBook screen black in this order keeps the least disruptive tests first, so a simple settings fault is found before anyone considers a reinstall, a replacement, or a repair booking, and each step below ends with what a success looks like, so you know when to stop.
- **Listen for signs that the MacBook is running.** Press the power button or Touch ID once, then listen for fan sound, startup chime, or disk activity, and watch for keyboard backlight. A running machine with a black screen is a display fault, while a silent machine is a power fault, and the two need different steps. Note exactly what you hear and see before changing anything. If this step restores normal behaviour, stop here and note what worked, because continuing past a working fix only adds risk.
- **Raise brightness and check the lid.** Press the brightness up key several times, and slowly adjust the lid angle while watching the screen. A screen set to minimum brightness can look dead, and a display cable fault can appear and vanish with lid position. Test in a dim room if possible, since a faint picture is easier to see there. If this step restores normal behaviour, stop here and note what worked, because continuing past a working fix only adds risk.
- **Force a shutdown and restart.** Press and hold the power button for about ten seconds until the MacBook turns off, wait a few seconds, then press power again. A forced shutdown clears a frozen state that a normal restart cannot reach. Wait for the full startup sequence rather than pressing power repeatedly, since repeated presses can interrupt it. If this step restores normal behaviour, stop here and note what worked, because continuing past a working fix only adds risk.
- **Disconnect all external devices.** Unplug monitors, docks, hubs, drives, and adapters, leaving only the charger connected. An external display or dock can seize video output and leave the built in screen dark, even when the MacBook itself is healthy. Test the built in screen alone before reconnecting anything. If this step restores normal behaviour, stop here and note what worked, because continuing past a working fix only adds risk.
- **Test with an external display.** Connect an external monitor or TV with a known good cable and adapter, power both on, and watch for a picture. If the external display shows macOS, the MacBook is running and the built in display or its connection is the fault. If both screens stay dark, the fault sits deeper in software or hardware. If this step restores normal behaviour, stop here and note what worked, because continuing past a working fix only adds risk.
- **Charge for at least thirty minutes.** Connect the original or a known good charger and leave the MacBook charging undisturbed for thirty minutes. A deeply drained battery can leave the screen dark even while the charger is connected, and the charging indicator may take time to appear. After thirty minutes, try powering on once and note any change. At this stage of fix MacBook screen black, a success here is especially valuable, because it proves the fault sat in the middle of the sequence rather than at either end. If this step restores normal behaviour, stop here and note what worked, because continuing past a working fix only adds risk.
- **Boot into Safe Mode.** On Apple silicon, press and hold power until startup options appear, select the startup disk, then hold Shift and click Continue in Safe Mode. On Intel models, restart and hold Shift immediately. Safe Mode loads only essential software, so a screen that works there points at a login item or third party software fault. If this step restores normal behaviour, stop here and note what worked, because continuing past a working fix only adds risk.
- **Reset NVRAM on Intel models.** On Intel MacBooks only, shut down, then power on and immediately hold Option, Command, P, and R for about twenty seconds. NVRAM holds display and startup settings that can corrupt and leave the screen dark. Apple silicon MacBooks do not use this step, since their startup settings reset through a normal restart. If this step restores normal behaviour, stop here and note what worked, because continuing past a working fix only adds risk.
- **Try macOS Recovery.** On Apple silicon, press and hold power until startup options appear, then choose Options. On Intel models, restart and hold Command and R. From Recovery, try Disk Utility First Aid on the startup disk before considering a reinstall. Note any error reported, since it guides the next decision. If this step restores normal behaviour, stop here and note what worked, because continuing past a working fix only adds risk.
- **Test with a different user account if possible.** If the screen works in Safe Mode but fails at login, test with another user account or create one in Safe Mode if the system allows. A fault tied to one account points at login items or account settings, while a fault in every account points wider. This test prevents a full reinstall for an account level fault. If this step restores normal behaviour, stop here and note what worked, because continuing past a working fix only adds risk.
- **Reinstall macOS as a last resort.** Back up through Recovery or Target Disk Mode if possible, then reinstall macOS from Recovery, keeping your files where the installer allows. A reinstall that fixes the screen points at deep software corruption, while a screen that stays black after reinstall points at hardware. Do not skip the backup attempt, since later steps can erase data. If this step restores normal behaviour, stop here and note what worked, because continuing past a working fix only adds risk.
- **Stop and book service for hardware signs.** Stop when the screen stays black on both the built in and external displays after Safe Mode and Recovery, when the picture changes with lid angle, or when the fault began after a drop or spill. Further software steps cannot repair a display cable or logic board fault, and continued forcing risks further damage. If this step restores normal behaviour, stop here and note what worked, because continuing past a working fix only adds risk.

Small Details That Decide the Result
A black MacBook screen asks one question before any other, which is whether the machine is running at all. Owners often answer that question by staring at the screen, yet the screen is the very part that cannot be trusted in this fault. Fan sound, keyboard backlight, and an external display answer the question far more reliably, and the whole repair branches on that answer. This distinction shapes how you should approach fix MacBook screen black.
Apple silicon and Intel MacBooks differ in their reset steps, and using the wrong sequence wastes time and creates confusion. NVRAM reset applies to Intel models, while Apple silicon models handle startup settings through a normal restart and through Recovery. Check which chip your MacBook uses in About This Mac, or from the model information, before attempting a reset step.
Login faults deserve attention because a black screen after the Apple logo often sits at login rather than at the display. A corrupt login item, a third party menu app, or a failing account setting can leave the screen dark while the system itself runs. Safe Mode and a second account test separate login faults from display faults without any reinstall.
The checks that matter most, in brief, are the first five steps of the sequence, and they deserve a second pass if the fault survives them.
- Listen for signs that the MacBook is running
- Raise brightness and check the lid
- Force a shutdown and restart
- Disconnect all external devices
- Test with an external display
Apple publishes MacBook display and startup guidance through its official support pages, and the startup sequences in this guide follow those pages. See Apple Support for the current steps for your MacBook model.
Testing one change at a time is the habit that separates a quick repair from a long afternoon of guessing. Change a single setting, run the same test you ran at the start, and write down the result before you touch anything else. When a later step appears to work, that note tells you whether the improvement came from the latest change or from an earlier one that only needed time to take effect. Support teams ask for the same log, so the habit pays twice.
A short note made before you start will save time later, especially if the fault returns or if someone else has to finish the job. Record what changed just before the fault appeared, which tests you have already run, and what each test showed. A fault that began after an update, a new accessory, or a move points in a different direction from a fault that appeared out of nowhere, and that single detail often narrows the search more than any single setting.
Do not judge a fix by the first few seconds after you apply it. Some settings need a restart, some connections need a fresh pairing attempt, and some apps need a full close before a change takes effect. Run the same real world test you used at the start, such as opening the feature, making a test call, or playing a short clip, and give the result a full minute before you declare the step a failure and move on.
If the same fault has appeared before, look for the pattern rather than treating each occurrence as new. A fault that returns after every update, every long trip, or every period of heavy use usually has a trigger that the ordered steps can expose. Fixing the trigger, such as a worn cable, a full storage, or an app that hogs resources, prevents the next occurrence far better than repeating the same quick fix.
Keep the accessories you use for testing in a known good state. A spare cable, a charged spare remote battery, or a second pair of earbuds turns a vague suspicion into a clear answer in under a minute. When the fault follows the accessory to another device, the accessory is the problem. When the fault stays with the original device, the device or its settings deserve the attention.
Before any step that erases data or resets settings, confirm where your important content lives. Photos, messages, and documents that sync to a cloud account usually return after a reinstall, while local downloads and unsaved work may not. A quick backup takes a few minutes and turns a last resort step from a risk into a routine procedure.
When a fault may end in a warranty claim, preserve evidence as you go rather than reconstructing it later. Keep dated notes, keep the original accessory that failed, and avoid opening a sealed device, since an opened device can complicate a claim even when the fault is genuine. A repair centre that receives a clear timeline and untouched hardware can usually decide faster than one that receives only a description.
After any system or app update, retest the feature that previously failed, even if the update notes do not mention it. Updates change drivers, permissions, and background behaviour in ways that release notes rarely capture fully, and a fault that an update quietly fixed can return with the next update just as quietly. A two minute retest after each update turns that uncertainty into a known result.
A second device is the cheapest diagnostic tool you can own for this kind of fault, because it answers the device versus environment question in a single test. Borrow a second phone, headset, remote, or monitor for ten minutes, and run the same test on both. When the fault follows the accessory, replace the accessory. When it stays with the original device, focus the repair there and stop buying accessories.

What Not to Do First
The following errors do not cause the original fault, but they regularly turn a short repair into a long one, and they are worth naming before you start.
- Reinstalling macOS before testing an external display, which erases software for a display cable fault.
- Using Intel reset steps on an Apple silicon MacBook, which cannot work and wastes the troubleshooting window.
- Pressing power repeatedly during startup, which interrupts the sequence and hides the real state.
- Reconnecting every dock and monitor before testing the built in screen alone, which reintroduces the conflict.
- Ignoring a screen that changes with lid angle, which is a strong hardware clue that software cannot fix.
Avoiding those errors keeps fix MacBook screen black short and calm, because every wasted reset or repeated test adds frustration without adding evidence, and a calm repair is a faster repair.

Knowing When to Hand It Over
Book an Apple service check when the screen stays black on both displays after Safe Mode and Recovery, when the picture depends on lid angle, or when the fault began after a drop, spill, or impact. Take notes on fan sound, keyboard backlight, and external display results, since those observations let a technician skip the early diagnosis. Stop if the battery looks swollen or the machine smells of burning.
Take your notes with you when you seek help, including which tests passed and which failed, and the exact conditions where the fault appears. Support moves faster with ruled out causes than with a repeated symptom description, and a clear log often leads to a faster repair or a correct replacement part on the first visit.

Stopping the Next Occurrence
Keep macOS updated, avoid forcing the lid past its natural range, and test the built in screen alone after any dock or monitor change. Review login items after installing menu bar apps, and keep a current backup so a Recovery step never threatens your files. A short check of brightness, lid behaviour, and external display output after each major update catches screen faults early.
A ten minute monthly check of updates, storage, cables, and permissions catches most problems while they are still small, and it builds a baseline so a future change stands out immediately. Prevention is not extra work on top of the repair, it is the same discipline applied before the fault appears, and it pays for itself the first time it saves a repeat repair.

More Reading on Stratilyze
More Reading on Stratilyze. If this guide helped, the related guides on this site cover the neighbouring faults that often appear alongside this one, including Fix Macbook Wont Turn On, Fix Macbook Battery Not Charging and Fix Macbook Fan Loud Noise. Reading the closest match first usually saves a second round of troubleshooting, because a fault in one feature often shares a cause with a fault in another. Keep this guide open while you check the related one, and compare the symptom tables before changing any setting, since the right fix depends on matching your exact symptom rather than the closest headline.
The Deeper Checks for a Fault That Persists
A second pass is not a repeat of the first pass, it is a different kind of test. The first pass rules out the common causes in order, while the second pass looks for a cause that was masked during the first, such as a second device interfering, a setting that reverted after a restart, or a fault that only appears under load. Work the second pass slowly, and change only one variable at a time, since a second pass done hastily produces the same confusion as the first pass done at random.
During the second pass, test under the exact conditions where the fault originally appeared, with the same app, the same accessory, and the same network or location. A fault that cannot be reproduced under test conditions has not necessarily been fixed, it may simply be waiting for its trigger. If the second pass still fails, the notes from both passes together give support a far stronger starting point than either pass alone, and they often reveal a pattern that a single pass hides.
A Last Look Before You Pack Up
Return to the first step and confirm it properly before moving on, because a step that was rushed the first time often looks like a failure when it was really an incomplete test. Give it the full time it needs, watch for the result described in the main sequence, and only then move to the next step. This habit of retesting the early steps, rather than jumping to the later and more disruptive ones, saves most of the time that troubleshooting usually wastes.
The diagnosis table at the start deserves a second look once the main steps are done, because a cause that seemed unlikely at the start can become the leading explanation once the obvious ones are ruled out. Compare what you observed with the sign described for each row, and if your observation matches a row you dismissed earlier, work that row again with fresh attention. Diagnosis improves when the table is treated as a checklist to revisit, not as an introduction to skip.
Test again the next day under normal use, not just in the moment after the fix. Some faults return when the device warms up, when a background app updates, or when the original trigger recurs, and a next day test catches those returns while the repair is still fresh in your mind. If the fault returns, note exactly what changed since the fix, since that change is the most likely trigger.
Frequently Asked Questions
Why did this problem start suddenly?
The commonest trigger is a change just before the fault, such as an update, a new accessory, a move, or a period without use. Tracing that change usually points at the cause faster than testing parts at random. Note the last change first, then work through the ordered steps, because a fault with a clear trigger often has a short fix and a fault without one needs the full sequence. Retest the exact action that failed before, not an easier one.
How long should each fix take before I move on?
Give each simple step a proper test rather than a glance, because a restart, a cable swap, or a permission change needs a minute or two to show its result, while a reinstall or a restore needs longer. If a step shows no change after a fair test, move on and note the result, because the log of failed steps is what narrows the remaining causes for the steps that follow. Retest the exact action that failed before, not an easier one.
Will clearing data or resetting settings delete my content?
Clearing a cache removes temporary files only, while clearing data or storage signs you out and removes local settings, so check where your content lives before the stronger step. Content that syncs to a cloud account usually returns after a reinstall, while local downloads and unsaved work need a backup first. Never take a destructive step on a device that holds the only copy of something important. Retest the exact action that failed before, not an easier one.
What if the fault affects only one app, one device, or one connection?
That pattern is useful evidence, because a fault tied to one app points at that app and its permissions, while a fault that follows the device points at the device itself. The ordered guide for fix MacBook screen black helps separate those two cases before you change settings everywhere, and testing with a second app, a second device, or a second connection is the fastest way to draw that line. Retest the exact action that failed before, not an easier one.
When should I contact support instead of trying more fixes?
Contact support after the ordered steps fail, or immediately if you see danger signs such as heat, swelling, liquid damage, or a burning smell, and take your notes on what you tried. Support moves faster when you can list the causes you have ruled out, and continuing to guess after that point risks making a repairable fault worse or turning a warranty claim into a dispute. Retest the exact action that failed before, not an easier one.
How do I stop this happening again?
Keep updates current, keep comfortable free storage, check cables and permissions monthly, and note any change before a fault appears, because most repeats come from the same neglected basics. A ten minute monthly check is cheaper than another afternoon of troubleshooting, and it builds a baseline that makes future changes obvious before they become faults. Retest the exact action that failed before, not an easier one.
Wrapping Up Without the Guesswork
Work through fix MacBook screen black in order, stop at the step that works, and keep the notes on what you tried, because that discipline turns a frustrating fault into a short sequence of tests, and it also means the next fault starts from a known baseline instead of from scratch.
Start with the first step today, test one change at a time, and let the result of each test decide the next move, because a calm ordered approach beats a fast random one, and the time saved by not repeating failed steps is time you get back for the work itself.
