PageSourceSearch

https://shiftplus.app/assets/stage-manager-loses-window-layout-76ApPRdL.js

js shiftplus.app collected 2026-10-08 01:58:02 UTC 7,726 bytes, 110 lines download raw bytes

1const e=`---
2title: "Stage Manager Keeps Losing Your Window Arrangement? What Actually Works"
3excerpt: "You group windows into a set, come back later, and the group has changed. Windows moved, resized, or ended up in another pile. Here's what Stage Manager actually remembers, and when to stop fighting it."
4date: "2026-07-31"
5lastUpdated: "2026-07-31"
6readTime: "7 min read"
7category: "Guides"
8image: "/blog-posts/images/stage-manager-layout-cover-v2.png"
9seoTitle: "Stage Manager Not Saving Your Window Layout? Here's What Works"
10seoDescription: "Stage Manager keeps rearranging your window groups and forgetting sizes after a restart. Here's what it actually stores, why groups drift, and how to get a layout that stays put."
11keywords:
12  - stage manager not saving layout
13  - stage manager rearranges windows mac
14  - stage manager loses windows
15  - stage manager groups keep changing
16  - macos stage manager window layout
17  - stage manager vs spaces
18---
19
20You put a browser, a notes app and a spreadsheet on screen together. Later you click that thumbnail in the strip and get the browser and the spreadsheet. The notes window is now grouped with something else. Or all three come back and one is half the width it was.
21
22You didn't do anything wrong. Stage Manager doesn't have the feature you're assuming it has, and once you see why, most of the frustration makes sense.
23
24## Groups aren't things you own
25
26Stage Manager keeps a list of recent stages, meaning sets of windows that happened to be on screen together. That set is derived, not declared. Click an app in the Dock, drag a window in from the strip, open a new document, and macOS revises its idea of what belongs with what.
27
28Which means there's no "save this group" command, because groups aren't objects. There's no name, so nothing to refer to, search for, or bind a hotkey to. Ordinary use rewrites them: drag one window out and what comes back next time has a different shape. And the strip holds a limited, recency-ordered set, so older stages fall off the end.
29
30Compare that with Spaces, where a desktop is a real container you deliberately put windows into. Stage Manager is closer to a smart recent-items list than to a workspace system.
31
32![Stage Manager inferred groups compared with Spaces and named workspaces](/blog-posts/images/stage-manager-vs-spaces.png)
33
34## Build groups the way it expects
35
36You get noticeably more stable groups by adding windows the way Stage Manager wants rather than the way you'd fill a Space.
37
38Drag a window's thumbnail from the left strip onto the main area, or Shift-click it in the strip. To take one out, drag it back into the strip.
39
40What you want to avoid is clicking an app in the Dock to bring it in. That often replaces the current stage instead of joining it, and it's the single most common way people lose a group.
41
42## Turn off the settings that cause drift
43
44In **System Settings → Desktop & Dock → Stage Manager**, open the Customize control.
45
46**Show recent apps in Stage Manager** hides the strip until you move the pointer to the edge when it's off. Fewer accidental clicks reshuffling your groups, at the cost of some discoverability.
47
48**Show windows from an application** matters more. *All at Once* keeps every window of an app together on the stage, which is usually what you want for a browser or an editor. *One at a Time* is behind a lot of "half my windows disappeared."
49
50Then check **Click wallpaper to reveal desktop** and set it to *Only in Stage Manager* or *Never*. On the aggressive setting, one stray click on the wallpaper sweeps everything aside, and it reads exactly like your group vanished.
51
52## Why nothing survives a restart
53
54Window size and position are stored per window by each app, through macOS window restoration. That machinery is unreliable on its own, and we went through its failure modes in [why your Mac doesn't remember window positions](/blog/mac-doesnt-remember-window-positions/). Stage Manager sits on top of it and inherits every one of them.
55
56Display changes make it worse. Connect or disconnect a monitor and macOS re-places every window onto whatever screens remain. Groups get re-derived afterward, and what comes back is often not what you had.
57
58On top of that the stage list is recency-based. Right after a restart, with barely any recent activity to work from, there's very little for macOS to reconstruct groups out of.
59
60## My honest read
61
62Stage Manager solves visual clutter. It shows one working set and hides everything else, and it does that well. On a 13-inch MacBook with 
62no external display it's genuinely good.
63
64It does not solve context restoration. Nothing named to save, no way to summon a specific arrangement, no persistence guarantee across restarts or display changes. Those aren't features that might land in a future release. They follow directly from groups being inferred rather than declared.
65
66So "give me my invoicing setup back" isn't a setting you've missed. The concept isn't there.
67
68If you've been fighting it for weeks, the fix is usually to turn it off with Ctrl-Cmd-S and organize with Spaces instead. That's not giving up. It's picking the model that fits your setup. Running Stage Manager and Spaces together is where most of the pain comes from anyway, since they're two different ideas about the same screen and their interaction is inconsistent.
69
70If you want to keep it for focus, keep it. Just don't expect it to hold your layouts.
71
72## Named layouts, for when you do need them
73
74That's the part ShiftPlus handles. Arrange your windows once and capture it as a named workspace: which apps, which windows, what size, which display, which Space. Restoring rebuilds that arrangement on a hotkey.
75
76The difference from Stage Manager is that you declared the group instead of macOS guessing it. It has a name. It doesn't drift when you open something unrelated. It survives a restart, because it's stored as a definition rather than reconstructed from recent activity. And it can hold parts of a working context that have nothing to do with window management, like which browser profile belongs to this project, or which directory and environment the terminal should start in.
77
78You can keep using Stage Manager for focus while workspaces handle restoration. They're not after the same job.
79
80Needs macOS 14.6 or later, plus Accessibility permission to position windows.
81
82## Three models side by side
83
84| | Stage Manager | Spaces | Named workspaces |
85|---|---|---|---|
86| Groups are explicit | No, inferred | Yes | Yes |
87| Can be named | No | No, numbered | Yes |
88| Restore on demand | No | Switch to it | Hotkey |
89| Survives restart | Unreliable | Desktops persist, contents don't | Yes |
90| Survives display change | Poorly | Poorly | Rebuilt on restore |
91| Covers browser profile and terminal state | No | No | Yes |
92
93## FAQ
94
95**Can I save a Stage Manager group?**
96
97No. Groups have no identity, so there's nothing to save or name. That's a design property rather than a setting you've overlooked.
98
99**Why do my windows keep leaving the group?**
100
101Usually because they were brought in by clicking the app in the Dock, which tends to replace the stage rather than join it. Drag from the left strip instead. The other common cause is having windows from an application set to One at a Time.
102
103**Does Stage Manager work with multiple displays?**
104
105It does, and you can enable it per display, but this is where it's least predictable. Groups get re-derived when the display set changes, so regular docking and undocking scrambles them.
106
107**Does it replace Spaces?**
108
109No, they coexist, and each Space keeps its own Stage Manager state. In practice running both is more confusing than useful, and most people settle on one.
110`;export{e as default};

Line numbers count LF bytes from the start of the resource, as the search results do. Vendor segments are library code the classifier recognised; they are stored but not indexed. Bytes are shown as Latin1 characters, one per byte.