Why Chrome Windows Disappear When You Go Fullscreen on macOS
You have a Chrome window with documentation open. You click into your editor, which is fullscreen. Chrome is gone. Not behind the editor — gone, with no way to click back to it without a Mission Control swipe or a Space switch.
This confuses people more than almost anything else in macOS window management, partly because the advice you'll find for it doesn't work.
The window isn't hidden. You left it behind.
When a macOS app enters fullscreen, it doesn't simply resize to fill the screen. macOS creates a new Space, a separate virtual desktop, and moves that one app into it.
Your Chrome window is still sitting on the desktop Space you started from, exactly where you put it, still open. You didn't lose it or send it behind anything. You navigated to a different desktop, and it isn't on this one.
That's why the obvious fixes fail. There's nothing to bring forward. Ordering windows isn't the problem. You're in the wrong room.
Why "Assign to All Desktops" doesn't fix it
The advice you'll find most often is: right-click the app's icon in the Dock, Options, Assign To, All Desktops.
That setting is real and it does something useful — the app's windows will now follow you between desktop Spaces. If you keep three desktops and switch between them with a four-finger swipe, this stops you losing Chrome on desktop one.
It doesn't help with fullscreen. A fullscreen app's Space isn't an ordinary desktop, and windows assigned to "all desktops" don't appear over it. People try this, see it work when they swipe between desktops, assume it's working generally, and then get confused all over again the first time they go fullscreen.
Why Picture in Picture does work
A video in Picture in Picture stays visible above fullscreen apps. So does the volume overlay,
and so do notification banners. These aren't special-cased by name — they're ordinary windows
whose owners set a specific flag saying "this window may appear over a fullscreen app". In
AppKit terms that's a window collection behaviour, and the relevant part is
fullScreenAuxiliary.
Ordinary Chrome windows don't set it, and there's no user-facing setting to turn it on, because it's a decision the app makes about each window when it creates it. That's the whole story: not a permission you're missing, not a preference buried somewhere. The window was built without the flag.
So any real fix does one of three things: put the other window in the same Space, stop using a separate Space in the first place, or use an app whose window sets that flag.
The free fix most people don't know
Stop using fullscreen. Fill the screen instead.
macOS has more than one "make this window big" behaviour, and only one of them creates a new Space:
- Click the green button → fullscreen. New Space. Everything above is in play.
- Fill → the window covers the desktop, menu bar and Dock stay put, and it remains an
ordinary window on your current desktop. On macOS Sequoia and later:
fn+Control+F, or the Window menu → Move & Resize → Fill, or hover the green button and pick Fill from the panel. - Zoom (Option-click the green button) → the window grows to fit its content, which is not always the whole screen. Safari tends to stop at a comfortable reading width, Finder sizes to its columns. Still stays on your desktop, so it solves the same problem; it just may not look as big as you expected. This one has been in macOS for many years, so it's what you have on macOS 14.
All three leave the window large but still on your desktop Space, so every other window behaves normally around it. Your Chrome window is right there. Command-Tab works the way you expect. Nothing disappears.
For a large number of people who thought they had a fullscreen problem, this is the entire fix, and it costs nothing. The trade-off is that you keep the menu bar and Dock, which some people prefer anyway and others specifically went fullscreen to be rid of.
If you actually need fullscreen
Some workflows genuinely want the real thing: menu bar gone, distractions gone. In that case:
Split View puts a second app into the same fullscreen Space, tiled beside the first. Built in, free, and it solves the visibility problem completely. The cost is that it's a commitment: two apps, fixed, until you dismantle it. It fits a settled hour of work better than an occasional glance.
A second display sidesteps the whole thing. A fullscreen app takes one display; the other display carries on as a normal desktop with your Chrome window on it.
A floating browser is a small always-on-top window that loads web pages and whose window does set the flag, so it appears over fullscreen apps. Helium and Float are the usual names. Good when it's one page you need.
A summonable web workspace is the same idea with more than one page: a panel holding several tabs that appears over your fullscreen app on a keyboard shortcut and disappears again. Overlay is in this category. It only handles web pages — if the thing you need visible is a native app window, none of this last group helps, and Split View or a second display is where you should be looking.
Summary
| What you want | Do this |
|---|---|
| Keep other windows reachable, don't truly need fullscreen | Fill the screen instead (fn+Control+F), or Zoom with Option-click |
| Truly need fullscreen, one other app, settled session | Split View |
| Truly need fullscreen, have a second display | Put the browser there |
| Truly need fullscreen, one web page, on demand | A floating browser |
| Truly need fullscreen, several web pages, all day | A web workspace with a global shortcut |
| A video | Picture in Picture — it already works |
Next time a window vanishes on you, remember that nothing is broken and nothing is hidden. macOS put your app in its own room and left the other window in the previous one. Every fix above is a different answer to which room each thing should be in.