Window layout for two monitors on Mac: what goes where, and why

Search for dual-monitor advice and you get desk photography: monitor arms, viewing angles, which cable carries power. All useful once. None of it answers the question you actually have at 9am on a Tuesday — what should be on each screen? A good window layout for two monitors on a Mac is not an arrangement you build once and admire. It is a small set of rules you can re-apply in about four seconds, every time something knocks the windows out of place.

Here are the rules that hold up.

Start with one decision: which screen is for making things

Every layout that works follows the same split. One display holds the thing you are producing — the document, the code, the design, the spreadsheet. The other holds everything you are consulting while you produce it: reference material, chat, the logs, the call.

Call them the making screen and the watching screen. Once you've named them, most of the small decisions answer themselves. New browser window full of documentation? Watching screen. Slack? Watching screen, always, no exceptions — the moment chat lands on the making screen you have started reading instead of writing.

The making screen should be the one directly in front of you, and it should be your primary display, so new windows and dialogs open where you are already looking. Set that in System Settings → Displays → Arrange: drag the white menu bar onto the display you want as primary, and fix the physical arrangement while you're there — the multi-monitor setup guide covers that side.

Window layout for two monitors on Mac: three that actually work

Almost every real setup is a variation on one of these three.

Layout	Making screen	Watching screen	Best for
Make / Reference	Editor or document, roughly two-thirds width; scratch window in the remaining third	Browser with docs, plus a terminal or notes	Writing, coding, research
Make / Comms	The one app the job is done in, near full width	Slack, Mail and Calendar stacked as thirds	Meeting-heavy and support roles
Wide / Tall	Code or design at two-thirds, preview at one-third	A vertical display: logs on top, docs below	Developers, anyone reading long output

The pattern underneath all three: the making screen holds one or two windows, the watching screen holds three or four. Resist the urge to tile the making screen into quarters. Splitting the screen you are concentrating on is how you end up with four things you are half-doing.

How many columns each display deserves

This is where generic advice falls apart, because the right grid is a function of physical width, not preference.

13–14" laptop screen: two columns. Halves only. A third of a 14-inch display is roughly 60 characters of text — narrow enough that you'll widen it again within a minute.
24–27" at 16:9: three columns. The two-thirds / one-third split is the workhorse of this size, and thirds are where tiling starts paying for itself.
32" or a 4K panel running a scaled resolution: three or four columns, and a second row is finally worth having.
Ultrawide: its own problem, covered in tiling windows on an ultrawide.
A display in portrait: think rows, not columns — two or three horizontal bands, because you rotated it for height.

The consequence is the important bit: two displays of different sizes want different grids. A tool that gives you one fixed set of regions for every screen you own will be wrong on at least one of them.

Why macOS makes this harder than it should

Built-in tiling has improved, and for a single screen it is fine. Across two, three gaps show up quickly:

The regions are fixed. fn-control-arrows give you halves, quarters and corners. No thirds, no two-thirds — the exact splits a 27-inch display is asking for.
There is no keyboard way to move a window to the other display. Apple never shipped one. Every workaround is covered in how to move a window to another monitor.
Spaces and displays interact oddly. Whether the two screens scroll independently is one checkbox with real consequences — see Displays have separate Spaces.

And then there is undocking. Unplug the second display and macOS piles everything onto the laptop screen; plug it back in and the layout does not come back. That is why your windows resize when you connect a monitor, and it is the reason the goal below is rebuilding fast, not saving perfectly.

Build it in seconds instead of saving it

Layouts that restore themselves sound better than they are. They break when an app isn't running, when a window has a different title, when the displays come back in a different order. The habit that survives is being able to put four windows where they belong faster than you can think about it.

That's the job Let's Tile does. Press ⌘-↵ and a grid drops over the window you're already using; steer with the arrow keys, press ↵, and the window snaps into that region. There is nothing to memorise, because the layouts are on screen. The free tier is a 3 × 2 grid — halves, thirds, two-thirds, quarters, full screen — which covers every layout in the table above on a single display.

The two-monitor parts are Pro ($9.99, paid once, no account, up to 20 devices per key): ⌥+arrows reshapes the grid mid-place, so the wide display gets four columns and the laptop gets two; each display remembers its own preferred grid; and ⌘-⇧+arrows sends the grid to the other display so you drop the window straight into the right cell over there, in one motion.

Being fair about the alternatives: Rectangle is free and open source, and its directional "move to next display" shortcuts are a perfectly good answer if fixed halves and thirds suit your screens. Moom can save a named layout and reapply it, which is the closest thing to genuine restore-on-dock — worth it if your setup really is the same every day. Let's Tile is the newer tool of the three, and its argument is the visible grid: one shortcut, every layout, nothing to remember per display.

The other half of two monitors: reaching the window

A layout only helps if you can get to what's in it. Cmd-Tab switches apps, not windows, so it lands you on whichever window of Chrome was last used — often the one on the other screen, and now you're hunting with the mouse.

Let's Switch fixes the same gap from the other side: hold ⌥-⇥ and you get a live preview of every open window across both displays, most recent first, and release to land on the exact one. ⌥-` cycles just the current app's windows. Both are free. Pro adds an ⌥-Space search palette when you have too many windows to flip through. If the frustration is more about focus than layout, switching focus between monitors goes deeper.

Frequently asked questions

Which monitor should be my primary display on a Mac? The one directly in front of you, and the one you produce work on. New windows and dialogs follow the menu bar, so putting it on a side display means constantly dragging things back.

Should my MacBook screen be one of the two displays? If the external is larger, use the laptop as the watching screen — chat, calendar, a terminal — and keep the making work on the big panel. Two columns is its limit; don't try to run thirds on it.

Can I save a window layout on macOS? Not natively. Third-party tools can save and reapply named layouts with mixed reliability; saving window layouts on Mac covers what actually works.

Is a vertical second monitor worth it? For anyone reading long output — logs, PRs, long documents — yes. Treat it as rows rather than columns, and expect to give it its own grid rather than reusing the horizontal one.