The short version: the laptop-plus-monitor setup is the most common configuration in professional Mac use and the one that breaks most often, because the hardware changes shape twice a day. The workable approach isn’t a perfect layout — it’s a layout cheap enough to rebuild in five keystrokes when the shape changes. Below: what belongs on the small screen, throwing windows across with Rectangle, the clamshell question, and the settings that fix windows landing on the wrong display.
Decide what the laptop screen is for
Most people never make this decision, which is why their laptop screen ends up as an overflow area holding whatever didn’t fit. That’s the worst use of it, because you get a screen full of things you’re not looking at and no idea what’s where.
Three coherent strategies, pick one:
The communication screen. Chat, email, calendar — everything that interrupts. The physical position of the laptop, lower and off-axis, means looking at it is a deliberate movement rather than a glance, which turns the interruption cost into something you can feel. This is the most popular arrangement and probably the right default.
The reference screen. Documentation, a spec, whatever you consult while working on the main display. Suits people whose work involves constant lookup, and turns the small screen into something you use rather than something you monitor.
The monitoring screen. Logs, dashboards, build output — things that must be visible but never focused. Fits developers and operations work particularly well, because the content is glanceable by design.
What matters isn’t which you choose, it’s choosing. A screen with a defined job stays organized; a screen without one accumulates.
Throwing windows across
The single most useful shortcut in this setup is next-display: move the focused window to the other screen without touching the mouse.
Dragging a window between displays is genuinely tedious — a long mouse journey, usually with a moment of the window catching on the boundary. The shortcut is instant, and it re-proportions the window to the new screen so a half-width window from the laptop arrives as a half-width window on the monitor rather than a stranded rectangle.
Two settings make this better.
There’s a subsequent-execution mode where pressing a position shortcut twice repeats the same action on the next display. So left-half, left-half gives you a left half on both screens — one key doing the work of two concepts.
And there’s a cursor-follow option. By default your pointer stays put when a window moves across, which means after throwing a window you have to travel to it. Turning on cursor movement for any shortcut, not just cross-display ones, keeps the pointer with the window:
defaults write com.knollsoft.Rectangle moveCursor -int 1
Restart the app afterward. On a wide desk this removes a small irritation you’d otherwise never think to fix.
When windows land on the wrong screen
The most common complaint in multi-display setups, and it usually has one of two causes.
Cursor versus window. Snapping acts on the display the focused window occupies — which isn’t necessarily where your cursor is. If you’ve clicked into an app on the monitor and left the pointer over the laptop screen, a shortcut goes where the window is, not where you’re pointing. There’s a setting governing which of the two decides, and picking the one that matches your habits resolves most of these reports.
Display ordering. Next-display needs an order, and the default is left-to-right, line-by-line. If your monitor sits above the laptop rather than beside it, that ordering may not match your mental model of “next.”
You can switch to strict x-coordinate ordering, regardless of vertical position:
defaults write com.knollsoft.Rectangle screensOrderedByX -int 1
This was the behavior before version 0.87, and for stacked or vertically offset arrangements it’s often the more intuitive of the two. Worth trying if Next Display keeps surprising you.
The clamshell question
Closing the lid and running on the external display alone is, from a window management perspective, the easiest configuration there is. One screen, one set of positions, no cross-display anything. If your monitor is large enough, it removes the entire class of problems this article is about.
The catch is that you’re paying for a laptop screen you’re not using, and losing whatever job you’d assigned it.
The real argument for clamshell is ergonomic rather than technical: a laptop screen at desk height puts your neck at a bad angle, and the second screen tempts you to use it despite the position. Closing the lid removes the temptation.
One thing to know if you use it intermittently: a window left on the built-in display when you close the lid moves to the external, and doesn’t return when you open it again. Same recovery as any disconnection, covered below.
The disconnection mess
Unplug the monitor and macOS moves the orphaned windows onto the laptop screen. What it doesn’t do is resize them, so you get several monitor-sized windows overlapping on a 14-inch display, most of them extending past its edges.
Reconnecting doesn’t undo it. Nothing re-fires to send windows back where they were.
People try to solve this by looking for a tool that saves and restores layouts. That exists in paid tools and it’s genuinely useful, but the free answer is more robust than it sounds: make your layout cheap to rebuild.
If your standard arrangement is five keystrokes, disconnection stops being an event. Cmd-Tab to each app, press its position shortcut, done in under ten seconds without thinking. Compare that to hunting for the title bar of a window whose title bar is off-screen.
Which is the general principle in this setup and worth stating plainly: chasing a layout that survives hardware changes is chasing something macOS won’t give you. Making rebuilds trivial is achievable today with the Rectangle app and four shortcuts.
One genuine emergency tool: if a window is so far off-screen you can’t grab it, focus its app and press any position shortcut. It’ll be pulled back onto a visible screen regardless of where it was.
Different resolutions, one layout
A concern that comes up and mostly shouldn’t: a 14-inch laptop and a 27-inch monitor have wildly different pixel counts, so does a layout make sense across both?
Yes, because snapping is fractional. A left half is half of whichever display holds the window. The same shortcut produces a sensible result on both screens without any per-display configuration.
Where it breaks down is the arrangement rather than the shortcuts. Thirds are excellent on a 27-inch monitor and unusable on a 14-inch laptop, where a third is about phone width. So the same key gives you a good result on one screen and a bad one on the other.
The practical answer is to use different position vocabularies per screen — halves and two-thirds on the laptop, thirds and quarters on the monitor — rather than expecting one set of habits to be optimal everywhere. It sounds like extra cognitive load and isn’t, because the screens look different enough that you never confuse them.
The whole setup, briefly
Assign the laptop screen a job. Learn next-display and two or three position shortcuts. Turn on cursor-follow. Check display ordering matches your physical arrangement. Accept that disconnection means rebuilding, and make rebuilding fast.
That’s about fifteen minutes of setup for the configuration most Mac professionals actually work in, and it’s the highest-value fifteen minutes a free Mac window manager can buy you. Everything past it is refinement.
Frequently asked questions
Where do windows go when I disconnect the monitor?
They move to the remaining screen at their old sizes, so you get oversized overlapping windows. Reconnecting doesn’t send them back. A layout you can rebuild in a few keystrokes is the practical answer.
Why does my window snap to the wrong display?
Snapping acts on the display holding the focused window, not necessarily where your cursor is. Check the setting that decides between the two, and verify your display ordering matches your physical arrangement.
Does this work in clamshell mode?
Yes, and it’s the most predictable configuration — one active display, so cross-display commands have nowhere to send anything and there’s nothing to get confused about.