How to screenshot a menu that closes when you try
You open a dropdown, reach for the screenshot shortcut, and the dropdown closes. Or you capture successfully and the tooltip you wanted has vanished from the image.
This is one of the most common small frustrations in taking screenshots, and there are three dependable ways around it.
Method one: a timed capture
Both operating systems can delay a capture by a few seconds, which is enough time to open the menu and get your hands off the keyboard.
macOS. Press Cmd Shift 5 to open the capture toolbar. Under Options,
choose a five- or ten-second timer. Start the capture, open your menu, and wait.
Windows. The Snipping Tool offers a delay in its own window — open the app
directly rather than using Win Shift S, set the delay, then trigger it.
Timed capture is the most reliable method because it removes all interaction during the capture itself. It's also the slowest, which matters if you need twenty of these.
Method two: capture the whole screen and crop
Full-screen shortcuts are usually less disruptive than region-selection ones, because region selection requires you to click and drag — and the click is what dismisses the menu.
On macOS, Cmd Ctrl Shift 3 copies the entire screen to the clipboard
with no interaction beyond the key press. On Windows, Win PrtScn writes a
full-screen file.
Capture everything, then crop afterwards. This is often faster than a timer, and it works with most menus that only close on click rather than on focus loss.
Method three: freeze it in the browser
For web content specifically, developer tools can hold an element in a particular state indefinitely.
In Chrome or Firefox, open DevTools, select the element in the Elements panel,
right-click it, and look for Force state — you can pin :hover, :focus,
or :active. The tooltip or hover menu then stays visible while you do anything
else, including a leisurely region capture.
For dropdowns that appear and disappear based on JavaScript rather than CSS
state, the alternative is to set a breakpoint or use debugger in the console
while the menu is open. Execution pauses, the DOM freezes, and the menu stays
put.
There's also a blunter trick: in the console, run something like
setTimeout(() => { debugger; }, 5000), then open your menu. Five seconds later
the page freezes exactly as it is.
Which one to reach for
- Native application menus — use the timer. Nothing else reliably works, because system menus capture input globally.
- Web dropdowns and tooltips — force the CSS state. It's the fastest once you know where the option lives, and it keeps the menu open indefinitely.
- Anything you need twenty of — full screen, then crop in a batch.
The one that catches people out
Some menus close not on click but on focus loss — the moment the window stops being frontmost. A screenshot utility that presents its own overlay can take focus and dismiss the menu before capturing.
If a timer isn't working, this is usually why. The full-screen shortcut is the workaround, since it doesn't put anything on screen before capturing.