Fast user switching on a Mac: two workdays on one machine

Two jobs, two sets of accounts, one Mac. Fast user switching is the built in answer, and it is a good one for the case it was designed for: handing the machine to a different person without either of them closing anything. Whether it is the right answer for one person running two work identities is a separate question, and the honest answer depends on how much memory the machine has and how often the switch happens.

What follows is what the feature does at the system level, where the switch to turn it on moved to in the current macOS, what stays running and what does not, and the point at which a second account stops being the cheaper option.

What it does under the surface

The name suggests a faster version of logging out and back in. It is not that at all. Apple's description is that when a Mac has multiple users, an administrator can turn on fast user switching, which allows quick switching between accounts when more than one user is logged in at the same time. The important phrase is at the same time.

Both sessions stay alive. Nothing is closed, nothing is saved, and no login items run again on the way back. A Mac with two users switched in this way is running three login sessions at once: one for the system itself, plus one for each user.

What changes for the session in the background is its access to hardware rather than its right to run:

[Its processes] can't receive local keyboard/mouse/trackpad input, and don't output to the display or audio; as far as those processes are concerned, it's as if the display has gone to sleep. Source: eclecticlight.co

That single sentence explains most of the surprises. A download continues. A long build continues. A backup continues. A video call does not, because it has no camera, no microphone and no speaker while it sits in the background. A screen recording captures nothing useful. Anything driven by a timer keeps firing, which is why notifications from the other account can still arrive as badge counts waiting when the switch back happens.

Turning it on, and why the old instructions no longer match

Most guides on this topic point at a pane that has been renamed. In the current Mac User Guide, for macOS 27 Golden Gate, the control lives under System Settings, then Menu Bar in the sidebar, which may need scrolling to reach. Older advice sends people to Control Center, and older advice still to Users & Groups, and neither path matches the current pane.

From the Menu Bar pane there are two routes. Either select Fast User Switching and choose an option from the pop up menu on the right, or click Add Controls, click Fast User Switching on the right, and choose Add to Menu Bar. Then click Done. The same Add Controls flow offers Add to Control Center instead, for anyone who would rather not spend menu bar width on it.

Once it is showing, switching takes a click on the fast user switching menu in the upper right corner, then a user name or icon, then a password and Return. Depending on the Menu Bar settings, the menu shows either a user icon or the name of the current user.

On Macs with Touch ID there is a shortcut worth setting up, because it removes the password typing that makes frequent switching tedious. When two or more users are already logged in, a Mac or Magic Keyboard with Touch ID and no Touch Bar switches on a single press of Touch ID until it clicks. On a Mac with a Touch Bar, rest a finger on Touch ID until the Touch Bar shows the prompt naming the account to switch to, then press until it clicks.

One setting to leave alone while doing this: automatic login. Apple's guidance is explicit that automatic login should not be set up for an administrator, because anyone could restart the Mac and gain administrator access. Automatic login is disabled outright when FileVault is on.

What it costs

Running two sessions at once costs what running two sessions at once should cost. The resources used by processes across all open login sessions are significantly greater than with a single user logged in, and memory is the constraint that bites first.

The arithmetic is unforgiving on a machine with 8GB. A browser in each session, a chat client in each session and a mail client in each session is six sets of the same processes, none of which can be closed by the session that is not in front. macOS will compress and swap rather than fail, so the symptom is not an error message. It is the machine getting slower in a way that has no obvious cause, because the cause is sitting in a session nobody is looking at.

There is a second cost that is easy to miss. Apple's own advice on troubleshooting relies on logging out, and fast user switching does not log anything out. A session left switched in the background for a week has a week of accumulated state, and none of the ordinary remedies apply to it because it is never the front session when anyone thinks to try them.

Three things to settle before the second account exists

Creating the account is a minute's work. The decisions around it are what determine whether the arrangement holds up, and all three are easier to make before the account exists than after.

The account type. Apple offers administrator, standard and sharing only. An administrator can add and manage other users, install apps and change settings, and the guidance is not to share administrator names and passwords. For a second identity belonging to the same person, standard is usually right, because it still allows installing apps and changing that account's own settings while keeping the ability to alter the machine in one place.

Which files each account can see. Fast user switching requires a separate home folder for each user, and that separation is the feature being bought. What tends to catch people is the shared material: a project folder that both identities need, or a set of reference documents. The choices are the Shared folder inside Users, an external volume, or a synced folder, and picking one deliberately is better than discovering later that the only copy of something lives inside a home folder the other account cannot open.

What runs on login. Each account has its own login items, and each will start its own copy of whatever is listed there. Two sessions each opening a browser, a chat client and a mail client on login is how the memory cost arrives without anyone choosing it. Trimming login items in the second account is the single most effective way to keep the arrangement affordable on a machine with 8GB or 16GB.

What separates cleanly, and what does not

A second user account is the strongest separation macOS offers short of a second machine, and that is genuinely useful. Each account gets its own home folder, its own keychain, its own browser profiles and their cookies, its own Dock and Spaces layout, its own notification settings, and its own set of running apps.

The things that do not separate are all singular pieces of hardware or state.

Only one session at a time has the display, the keyboard, the pointer, the camera, the microphone and the audio output. The two user login sessions also cannot communicate or interact with each other directly, which is the security property being bought and, occasionally, the reason something expected to be reachable from both sessions is not.

Shutdown is the other shared thing worth knowing about. When the front session asks the Mac to shut down or restart, unsaved changes in the other session cannot be presented for saving, so the person at the front gets warned that the other login sessions will lose unsaved work before the shutdown proceeds. That warning is the only notice anyone gets, and it arrives at the moment it is least likely to be read carefully.

And most importantly, the switch is a switch. Two accounts means two workdays that are never on screen together. Anything that requires looking at both at once is outside what this feature can do, no matter how fast the switching is.

Need	Second user account	One account, one window per service
Two accounts on the same service signed in	Yes	Yes
Both visible on screen at once	No	Yes
Separate home folder and keychain	Yes	No
Separate file permissions	Yes	No
Memory cost	Two full sessions	One session
Time to move between them	A switch and a password	A click or a keystroke
Right for a different person	Yes	No

When a second account is the right tool

Three cases justify the cost without argument.

The first is a genuinely different person. A partner, a family member or a colleague sharing a machine should have an account, and the separation of home folders and keychains is the entire point. Apple's account types matter here: a standard user can install apps and change their own settings but cannot add other users or change another user's settings, which is usually the correct level for a shared machine.

The second is a hard requirement for data separation. Contract work that must not touch personal files, a client environment with its own compliance rules, or anything where an auditor would ask which user account the files live under. Profile separation inside a browser does not satisfy that; a user account does.

The third is a clean environment for testing or troubleshooting, with one caveat. A fresh account is an excellent way to tell an app problem from a configuration problem. For troubleshooting proper, though, logging out is the better move, precisely because fast user switching never logs anything out and therefore never clears the state being investigated.

When it is the wrong tool

The common case that does not fit is one person with two work identities who needs both available through the day.

Two email accounts, two chat workspaces, two project tools, one human. A second user account handles the sign in problem and creates a worse one, because the answer to is there a message waiting now requires a session switch and a password. Over a day of small checks, that cost dominates. The memory bill is paid on top of it.

The cheaper arrangement keeps one session and separates the services instead of the user. On macOS that means giving each service its own window with its own signed in session, so both identities are present at once and reachable from the app switcher. The Workspaces page describes how services are grouped that way, the Supported apps page lists which services can be kept signed in side by side, and the FAQ covers how the sessions are kept apart.

The test is simple. If the second identity belongs to a different person, use a second account. If it belongs to the same person at a different job, separating the services is the lighter answer.

What to change first

If fast user switching is already in use for a second person, add the menu bar control from System Settings, then Menu Bar, and set up Touch ID switching, which removes the password step that makes the feature tiresome.

If the second account exists because one person needs two sets of sign ins, the account is doing work that windows can do more cheaply, and giving each service its own window is what SpaceDeck is built for on macOS.