Is it safe to restart my Mac? When a restart helps, when it does not, and what you lose

Is it safe to restart a Mac?

Yes, completely. Restarting is the normal, designed way to reset a Mac. Choose Apple menu, Restart, and macOS asks every open app to save and quit, writes everything it needs to disk, and starts fresh. Nothing is deleted. Your files, settings, apps and login stay exactly as they were.

The question usually comes from one of two worries. The first is "will I lose something?", and the short answer is only unsaved work in apps that do not autosave (covered below). The second is "is it bad for the Mac?", and the answer is no: modern Macs are built to restart thousands of times. Leaving a Mac running for months is also fine. MacRumors forum regulars report uptimes of "well beyond 50 days, beyond 60 days" with no issues, and one with "well over a year". Neither habit harms the hardware.

A restart is different from a forced restart (holding the power button until the Mac goes dark). That one skips the clean shutdown and should be kept for a Mac that is frozen solid. Even then, APFS is designed to survive it, but you lose anything unsaved. Try force quitting the stuck app first.

When a restart actually fixes something

A restart clears every process and starts them again from a known state. That fixes a specific set of problems, and knowing the set saves you from restarting for things it will not touch.

• An app that has grown for days. Browsers, Slack, Mail and Electron apps can slowly use more memory the longer they run. Quitting and reopening the one app is usually enough, but after a week or two a restart resets everything at once.
• Stuttering animations, slow window dragging, a laggy cursor. That is WindowServer, the process that draws the screen, and it grows with every window opened and every display connected. You cannot quit it. Logging out resets it; a restart does too.
• Right after a macOS update. The update already restarts the Mac, but if apps behave strangely afterwards, one more restart lets everything load fresh.
• Wi-Fi, Bluetooth or audio acting up. Toggling the setting is the first try. A restart resets the daemons behind them when toggling does not.
• An external display or dock not recognized. Unplug, restart, plug back in.
• Memory pressure in the red for hours with nothing obvious open. Something leaked. A restart puts it back to green.

MacRumors users describe the same pattern when asked how often they reboot: "Only when needed, sometimes things start to seem sluggish or wifi randomly stops working so I reboot." That is the right instinct. Restart in response to a symptom, not on a calendar.

When a restart makes things worse

The one case where a restart is actively unhelpful is a Mac that is slow because it is working. For a day or two after a macOS update, and after adding thousands of photos or files, Spotlight (mds_stores), Photos (photoanalysisd) and iCloud (bird) run flat out rebuilding their databases. The Mac feels slow and the fan may be on. A restart interrupts that work. It picks up where it left off, but you lose the minutes it takes to shut down and start, and if you restart several times a day you can stretch a two-day settle into a week.

How to tell: open Activity Monitor, CPU tab, sort by % CPU. If the top entries are mds_stores, mdworker, photoanalysisd, mediaanalysisd or bird, the Mac is indexing. Plug it in and leave it alone. The full picture is on the slow after update page.

Two other cases where a restart is not the fix: a Mac that is slow because the disk is nearly full (a restart changes nothing; free space does), and a single misbehaving app (quit that app; restarting everything is overkill). The general checklist is on why is my Mac so slow.

Restart, log out, quit the app, or wait?

Should you restart right now? A quick check

Answer a few questions about what the Mac is doing and this tells you whether a restart, a log out, quitting one app, or simply waiting is the right move.

If the result is "wait", give it until tomorrow morning plugged in. If it is "quit the app", do that first; most restarts people perform would have been fixed by quitting one thing.

What a restart clears, and what it does not

Cleared: all running processes and the memory they held, including leaks; WindowServer's accumulated state; temporary files in the per-boot temp folders; the kernel's caches; stuck network and Bluetooth connections; any app that was wedged.

Not cleared: your files; your settings; login items and background items, which all start again; app caches on disk (those persist, which is good, since rebuilding them is what makes a Mac slow); the Spotlight index (it resumes); browser tabs, if you have the browser set to restore them; the cause of a problem, if the cause is an app or a setting. Whatever was wrong because of a login item will be wrong again two minutes after the restart.

That last point is why a restart that "fixes it for a day" is a clue, not a solution. Something that starts at login is doing it. The Energy and CPU tabs in Activity Monitor an hour after a restart will show what. If you want that watched for you, Safe to Quit tracks each process over hours and flags the ones that grow back after every restart.

What you lose when you restart

Less than people fear, but not nothing.

• Unsaved work in apps that do not autosave. Apple's own apps (Pages, Numbers, TextEdit, Preview) autosave and come back exactly as they were. Microsoft Office autosaves to OneDrive if you have it on. Many other apps will prompt you to save when the restart asks them to quit, and the restart waits. Terminal sessions, running scripts and anything in a virtual machine are gone.
• The clipboard. Whatever you last copied is lost.
• Downloads and uploads in progress. Browsers usually resume downloads; uploads to web forms usually do not.
• Window positions, if you turn off reopening. The restart dialog has a checkbox, Reopen windows when logging back in. Leave it on and your apps and windows return. Turn it off for a truly clean start when you suspect one of those windows is the problem.

Save first with ⌘S in anything you care about, then Apple menu, Restart. Total time on a modern Mac is under a minute plus whatever your login items take.

How to restart safely, in order

1. Check it is not indexing

   Activity Monitor, CPU tab. If mds_stores, photoanalysisd or bird are at the top, plug in and wait instead.

2. Try the lighter fix first

   Quit the one app that is slow (⌘Q). If the screen itself is laggy, log out and back in, which resets WindowServer without a full restart.

3. Save your work

   ⌘S in every app with unsaved changes. Copy anything important out of the clipboard.

4. Apple menu, Restart

   Leave Reopen windows checked unless you want a clean start. Let apps that ask to save do so.

5. Wait for it to settle

   Give login items a minute or two. Then check Activity Monitor again. If the same process is back at the top, that process is the problem, not the uptime.