Post actualizado el día octubre 28, 2026 by DeiviSanzPlay
I’ve been capturing screens on Macs since the era of Command-Shift-3 producing a lonely PNG on the desktop with no preview, no editing, and no idea where it went. What changed everything wasn’t a third-party utility — it was the moment macOS turned its built-in screenshot tool into a small app of its own. Command-Shift-5 opens a floating toolbar that most people never touch, and that toolbar covers the vast majority of real-world capture needs once you understand its quirks.
This piece is built around actual situations: the bug report that needs an annotated crop, the client handoff that needs a clean window shot, the tutorial that needs a timed menu capture, the family member who needs a screenshot texted without touching Photos. No app store links, no subscriptions, no installers.
The floating toolbar is the whole game
Press Command-Shift-5 and a small panel appears near the bottom of the screen with five icons: capture entire screen, capture selected window, capture selected portion, record entire screen, record selected portion. To its right sit two menus: Options and Capture (or Record). That’s it — that’s the native screenshot app, and it hides in plain sight.
The Options menu is where the practical value lives, and it’s the menu almost nobody opens. Inside you’ll find:
- Save to — Desktop, Documents, Clipboard, Mail, Messages, Preview, or a custom folder. Choosing Clipboard is the single biggest time-saver for anyone who pastes screenshots into Slack, Jira, or an email body.
- Timer — Off, 5 seconds, 10 seconds.
- Show Floating Thumbnail — the little preview that appears in the corner after each capture. Turn it off if it distracts you; turn it on if you annotate immediately.
- Remember Last Selection — keeps the same capture rectangle between sessions.
- Show Mouse Pointer — off by default, and essential for tutorials.
One behavior worth knowing: the toolbar remembers your choices per session, but Save to resets to Desktop after a restart in some macOS versions. I’ve watched colleagues lose a morning of screenshots into the Desktop because they assumed Clipboard would persist. Check the menu the first time you capture each day if it matters.
Real scenario: the annotated bug report
You’re reporting a layout bug to a developer. Raw pixels are useless; the developer needs to know which element is broken.
- Command-Shift-5, set Save to → Preview (or just leave it on Desktop).
- Capture the portion, then click the floating thumbnail before it fades.
- In the markup view that opens, use the arrow, rectangle, and text tools to circle the broken element and label it.
- Hit the share icon and send it straight to Mail or Messages, or save and attach.
The thumbnail markup editor is genuinely capable for this task — arrows, boxes, circles, freehand, text, signature, rotation, crop, and a magnifier. It is not a design tool. It doesn’t do layers, alignment guides, or precise pixel placement, and the text tool has no font choice. If you need a polished annotated diagram for documentation, you’ll outgrow it within a week. For a quick «this button is misaligned» report, it’s faster than anything you’d install.
Window captures: the shadow problem and the fix
Command-Shift-4 then Spacebar turns the cursor into a camera and captures a single window with a soft drop shadow and a transparent background. This is the cleanest way to grab an app window for a slide deck or a support ticket.
The common complaint is the shadow. There’s a native trick: hold Option while clicking the window, and the shadow disappears, giving you a tight crop of just the window content. Most people never learn this because it isn’t documented anywhere in the UI. Try it on a Finder window and compare — the difference matters when you’re pasting into a document with a colored background.
What this method does not handle well: floating palettes, tooltips, or any element that disappears when the window loses focus. Capturing an open dropdown menu with a window capture is essentially impossible because the menu vanishes the instant you press Spacebar. For those, use the timed full-screen or portion capture instead.
Capturing menus, tooltips, and transient states
This is where the native tools show their limits, and where honest advice matters. There is no native way to freeze a screen state the way some third-party tools can. Your options:
- Timer capture — set 5 or 10 seconds, open the menu, wait for the countdown. Works with menus that stay open while you move the pointer to them, which many don’t.
- Full screen capture then crop — capture the whole screen while the menu is open, then crop in Preview. Reliable but slow.
- Keyboard-triggered portion capture — press Command-Shift-4, then press Spacebar while a menu is open; the menu often stays visible long enough to click it. This is inconsistent across apps.
I’ve wasted more time than I’d like trying to capture a context menu with the timer, only to have it close on the fourth attempt. If your work regularly involves documenting menu states — technical writing, QA, training material — the built-in tools will frustrate you, and that’s a legitimate reason to look elsewhere. For occasional needs, the timer gets the job done.
Screen recording without installing anything
Command-Shift-5 also records. Choose Record Entire Screen or Record Selected Portion, click Record, and the menu bar shows a stop button. The Options menu adds a microphone selector, so you can narrate. The resulting file lands wherever Save to points, typically as a .mov.
Practical notes from repeated use:
- There’s no pause button — only stop. Plan your takes accordingly.
- System audio capture requires macOS 13 or later and is enabled in the microphone dropdown as an option in recent versions; older systems won’t offer it.
- Recordings of protected content (DRM video in some apps, certain streaming services) come out black. That’s a system-level restriction, not a bug.
- File sizes grow fast. A ten-minute 4K recording can run into hundreds of megabytes.
For a quick «here’s how to reproduce the issue» clip, this is entirely sufficient and requires zero setup. For anything involving editing, multiple tracks, or trimming, you’ll move the file into QuickTime Player, which is also built in and handles basic trim and export.
The clipboard route most people miss
Setting Save to → Clipboard means every capture goes straight into memory. Press Command-V in your chat app and it appears. No file cleanup, no Desktop clutter, no dragging.
The catch: you only get one. Capture again and the previous screenshot is gone from the clipboard. If you’re collecting several screenshots to paste into one document, this workflow breaks — you’d need to paste each one immediately or switch back to file saving.
A hybrid I use: keep Save to on a dedicated Screenshots folder, then drag the floating thumbnail directly into an email or chat window. The thumbnail acts as a temporary file handle, and the file itself stays on disk if you need it later.
Where the screenshots actually go (and how to change it)
By default, Command-Shift-3 and Command-Shift-4 save to the Desktop with names like Screen Shot 2026-02-14 at 10.32.11.png (the naming format varies by macOS version). Command-Shift-5 respects its own Save to setting.
You can redirect the default location natively without any app, using Terminal:
defaults write com.apple.screencapture location ~/Pictures/Screenshots killall SystemUIServerThat’s a documented system preference, not a hack, though it’s an unofficial one — Apple doesn’t surface it in System Settings. It survives restarts. To revert, run the same command pointing back at ~/Desktop.
Also worth knowing: you can change the default format from PNG to JPG or PDF with defaults write com.apple.screencapture type jpg. PDF is handy for archiving; JPG saves space. The downside of JPG is visible artifacts on text-heavy screenshots, so I’d keep PNG for anything with small type.
Permission prompts and the Screen Recording privacy wall
Since macOS Catalina, capturing the screen — including with the built-in tools in some contexts — can trigger a Screen Recording permission request under System Settings → Privacy & Security. The built-in screenshot shortcuts generally work without this, but screen recording via Command-Shift-5 may require it depending on the macOS version and whether you’re capturing certain windows.
This trips people up constantly. A user reports «the screenshot tool is broken» and it turns out a permission was denied months ago after an OS update reset it. If captures come out blank or black, check that privacy panel before assuming hardware failure.
What the native tools genuinely can’t do
Being straight about limitations is more useful than pretending built-in is always enough:
- Scrolling capture — capturing a full webpage or long document beyond the visible screen isn’t possible natively. You’ll stitch manually in Preview or reach for a dedicated tool.
- OCR text extraction — Live Text works on images in Preview and Photos, but the screenshot flow doesn’t hand you extracted text directly; you capture, open, then select the text.
- Scheduled or automated capture — no native scheduling. Shortcuts app can trigger screenshots, which is the closest native-adjacent option, but it’s scripting, not a built-in feature.
- Pixel-precise measurement — the capture region shows dimensions while dragging, but there’s no ruler overlay or coordinate readout after the fact.
- Cloud sync and sharing links — you save a file; hosting and link generation are separate.
If your job is producing documentation at volume, these gaps add up, and a paid tool may genuinely pay for itself. For everyone else — support replies, bug reports, teaching a relative, grabbing a receipt — the native path is faster because it’s already there.
Keyboard shortcuts worth memorizing
Beyond the famous trio, a few combinations change the outcome meaningfully:
- Command-Shift-3 — full screen to file.
- Command-Shift-4 — portion to file.
- Command-Shift-4, then Space — window capture with shadow.
- Command-Shift-4, then Space, hold Option — window capture without shadow.
- Command-Shift-5 — the toolbar with all options.
- Command-Control-Shift-3 / 4 — same as above but straight to clipboard.
- Command-Shift-6 — captures the Touch Bar on Macs that have one (a genuine curiosity now that the Touch Bar is discontinued).
- Escape — cancels any capture in progress.
The Control modifier is the one people forget. Adding it to any of the base shortcuts routes the capture to the clipboard instead of a file, which is exactly the behavior you want when pasting into a form.
A worked example: capturing a receipt for expenses
Your finance team wants a screenshot of an online receipt, but the page is long and the relevant totals sit below the fold.
- Command-Shift-5, Capture Selected Portion, drag over the visible receipt area.
- Because the totals are cut off, scroll down and repeat for the second half.
- Open both in Preview, select all in the second, copy, and paste into the first to combine vertically.
- Export as a single PDF from Preview and attach to the expense form.
This is the honest native workflow for long pages: two captures and a manual stitch. It takes about ninety seconds and produces a clean result. Third-party scrolling capture would do it in one click, but if you file expenses once a month, the manual route is fine and doesn’t require installing anything on a work machine — which, in many corporate environments, is the deciding factor anyway.
Preview as the post-processing layer
Most people forget that Preview — preinstalled, no download — is a competent screenshot editor. Open a capture and you get markup tools, crop, rotate, resize, color adjustment, and export to a dozen formats. You can also capture directly into Preview via File → Take Screenshot, choosing From Entire Screen, From Window, or From Selection, with an optional 10-second timer.
That menu is arguably the most overlooked native capture path on the Mac. It’s slower than the keyboard shortcut but drops the image straight into an editable window with no floating thumbnail to chase. For anyone who always edits before sending, it removes a step.
What Preview won’t do: batch-process a folder of screenshots, add arrows with consistent styling across images, or handle very large captures without some lag. It’s a viewer with editing bolted on, not a production tool.
Deciding whether native is enough for you
A simple test: count how many screenshots you took last week and what you did with them. If the answer is «a handful, pasted into chat or saved for reference,» the built-in tools cover you completely, and installing anything is wasted disk space and another permission to manage.
If the answer involves long pages, annotations at scale, consistent branding, cloud links, or video walkthroughs with editing, the native path will feel like using a butter knife as a screwdriver — it works, awkwardly, until it doesn’t. Recognizing that boundary early saves frustration. The tools are good at what they do; they simply weren’t designed for production documentation.
One last practical tip that took me an embarrassingly long time to internalize: after any macOS major update, test your screenshot shortcut once. Updates have a habit of resetting permissions, changing default save locations, or re-enabling the floating thumbnail. Thirty seconds of verification beats discovering mid-presentation that your captures have been landing in a folder you forgot existed.
Perfiles verificables: Sitio web
Publicado el 28 de October de 2026. Última revisión: 28 de October de 2026.
