How To Take Screen Shot On Mac

Tips
1

I just switched to a Mac and can’t figure out how to take screenshots the way I used to on Windows. I need to quickly capture my full screen and specific portions of the screen for work tutorials and bug reports, preferably using built-in macOS shortcuts. What are the easiest ways to do this, and how can I change where the screenshots are saved?

2

On macOS you have three main shortcut groups. They cover full screen, windows, and custom regions.

  1. Full screen
    Press: Shift + Command + 3
    This saves a PNG to your Desktop by default.
    Hold Control as well (Shift + Command + Control + 3) to copy to clipboard instead of a file. Then paste in Slack, email, etc.

  2. Selected area
    Press: Shift + Command + 4
    Your cursor turns into a crosshair. Click and drag to select the area.
    Release to save a PNG to Desktop.
    Again, add Control if you want it to go to the clipboard.
    Tips:
    • Press Space after Shift + Command + 4 to switch to “window capture” mode. Hover a window, then click.
    • While dragging, press Space to move the whole selection.
    • While dragging, hold Option to resize from the center.
    • While dragging, hold Shift to lock one dimension.

  3. Screenshot toolbar (most useful for tutorials)
    Press: Shift + Command + 5
    You get a small toolbar at the bottom. It lets you:
    • Capture entire screen
    • Capture selected window
    • Capture selected portion
    • Record screen as video (entire or selection)

Click “Options” in that toolbar. There you set:
• Save to: Desktop, Documents, Clipboard, Mail, Messages, Preview, or a custom folder
• Timer: None, 5 seconds, 10 seconds
• Show or hide mouse pointer in screenshots and recordings

For work tutorials, a common setup:
• Shift + Command + 5
• Mode: Record selected portion
• Options: Show mouse pointer ON, Microphone ON if you want voice
This creates a .mov file.

  1. Where screenshots go
    Default: Desktop with names like “Screenshot 2026-02-17 at 09.10.23.png”.
    You change the default folder through Shift + Command + 5 → Options → “Save to”.

  2. Edit quickly
    After you take a screenshot, a small thumbnail pops up at the bottom right. Click it to open Markup. You can:
    • Add boxes, arrows, text, highlights
    • Crop
    • Add signatures
    Then hit Done. It saves over the same file. For bug reports this is handy.

  3. Change defaults if shortcuts feel weird
    Go to:
    System Settings → Keyboard → Keyboard Shortcuts → Screenshots
    Here you rebind Shift + Command + 3 or 4 if they conflict with other tools.

  4. Extra tip for Windows migrants
    If you used Print Screen → Paint, the closest flow is:
    • Use Shift + Command + Control + 3 or 4
    • Then Command + V into whatever app you want.

If you used Snipping Tool, the closest is Shift + Command + 4 or Shift + Command + 5 with “Selected portion”.

That covers most normal workflows for tutorials and bug reports on a Mac.

3

If you want to go a bit beyond what @reveurdenuit covered and make this feel closer to your old Windows workflow, here are some extra tricks and alternatives that are actually useful for tutorials / bug reports:

  1. Use Preview like an old‑school “Paste into Paint”

    • Take a screenshot with the normal shortcuts they mentioned.
    • Or: hit Shift + Command + Control + 3 or 4 so it goes to the clipboard.
    • Then open Preview → File → New from Clipboard.
    • From there you can crop, annotate, export as JPG/PDF, etc.
      It’s surprisingly close to the “Print Screen → Paint” vibe, just with fewer ugly pixels.

  2. Built‑in annotation from Finder (faster than you’d think)

    • After the screenshot saves, find it in Finder.
    • Hit Space for Quick Look.
    • In the Quick Look window, click the little markup icon (pencil in a circle).
    • Draw arrows, blur sensitive stuff, add text, then Save.
      I actually prefer this to clicking the little thumbnail popup; that popup sometimes disappears too fast if you’re juggling windows.

  3. Change the file format (PNG is nice, but kinda bloated)
    If you’re sending lots of screenshots in tickets or emails, PNGs are huge. You can switch to JPG permanently with a terminal command:

    defaults write com.apple.screencapture type jpg
killall SystemUIServer

    You can also use pdf, png, tiff, gif. For bug reports, JPG is usually fine and smaller.

  4. Stop cluttering your Desktop with 200 screenshots
    I slightly disagree with sticking to the Desktop default like @reveurdenuit implies. That gets nasty fast.

    • Create a folder like ~/Screenshots or even per‑project folders.
    • Shift + Command + 5 → Options → Save to → Other Location… → pick that folder.
      Now you don’t end up with a museum of old bugs all over your Desktop.

  5. Use Safari’s “Capture Entire Page” for long web pages
    If your tutorials involve web apps:

    • In Safari, right‑click in the page → “Inspect Element” to open Web Inspector.
    • In the Web Inspector’s three‑dot menu, there is an option like “Capture Screenshot” or “Capture Full Size Screenshot” depending on macOS / Safari version.
      That grabs the entire page, including the stuff below the fold. Way better than stitching multiple screenshots.

  6. Blur / hide sensitive info quickly
    Apple’s markup tools are kind of clunky for real redaction. If you’re doing bug reports with usernames, keys, etc.:

    • Use the rectangular shape filled with solid color to cover text.
    • Or, for a quick hack, use the highlight tool multiple times until it is essentially opaque.
      Not perfect, but faster than firing up Photoshop every time.

  7. Global “snipping tool” alternative
    If you really miss the Windows “Snip & Sketch” feel, the closest built‑in flow is:

    • Shift + Command + 4 for area selection.
    • Hold Control so it goes to clipboard.
    • Paste directly into your ticketing system, chat, email, or Preview.
      Personally I find this faster than opening the Shift + Command + 5 toolbar every time.

  8. For tutorial videos, compress after recording
    Those .mov files from Shift + Command + 5 get big. If you’re sending them in bug reports:

    • Open in QuickTime.
    • File → Export As → 720p.
    • Or run through HandBrake / another encoder to shrink them.
      Saves your teammates from downloading a 500 MB clip of you clicking two buttons.

Try this flow for work:

  • Use Shift + Command + Control + 4 for quick “snips” you paste straight into Jira / Slack.
  • Use Shift + Command + 5 only when you’re doing longer tutorial captures or need timed screenshots.
  • Point screenshots to a dedicated folder so your Desktop doesn’t look like a crime scene of failed UI experiments.

Once you’ve done this a few times, it’s honestly quicker than Windows’ tools, even if it feels alien for a couple days.

4

You already got a solid workflow from @reveurdenuit and the follow‑up, so here are extra angles that feel more “Windowsy” without repeating their steps.

1. Treat Shift + Cmd + 6 as your “PrintScreen” for laptops with Touch Bar
If you’re on a MacBook with a Touch Bar, Shift + Command + 6 snaps just the Touch Bar. Niche, but great for documenting UI in dev tools or creative apps that stick actions up there. On Windows you never had that strip to worry about.

2. Remap shortcuts so your muscle memory survives
This is where I slightly disagree with sticking to the stock key combos; if you came from Windows, your fingers will hate Shift + Cmd + 4.

  • Install Karabiner‑Elements or BetterTouchTool.
  • Map something like Fn + PrintScreen (or any spare key combo) to “run shortcut: Shift + Cmd + 4” or “Shift + Cmd + 3”.
  • Result: feel closer to PrtSc and Win + Shift + S from Windows.

Pros:

  • Much smoother migration, less “wait, what was that shortcut again”.
  • You can even map middle mouse button or trackpad gestures to screenshots.

Cons:

  • Extra app, extra config.
  • Might be overkill if you only take screenshots once in a while.

3. Use Automator / Shortcuts for one‑click “capture & auto‑annotate” flows
If you do repetitive tutorial screenshots, you can build a custom workflow:

Example idea:

  1. Use Automator or Shortcuts to create a “Service” that:
    • Runs /usr/sbin/screencapture -i (interactive selection).
    • Opens the result in Preview or your favorite editor.
  2. Bind that Service to a shortcut in System Settings → Keyboard → Keyboard Shortcuts.

Now your flow is basically: shortcut → draw rectangle → instantly in editor, similar to Windows Snipping Tool popping open.

4. Skip Desktop clutter with a smart folder approach
The other answer suggested redirecting everything to a folder like ~/Screenshots. Good. I’d take it further:

  • Keep the default save location in one central folder.
  • Create Smart Folders in Finder filtered by date, filename, or tags like “tutorial”, “bug”, “docs”.
  • When you annotate, tag the file accordingly instead of moving it.

This avoids the “which Jira ticket did this belong to” mess later. You get organization without manually sorting.

5. Use third‑party tools when built‑ins hit their ceiling
Apple’s tools are usable, but for heavy tutorial / bug work they get clunky. Compared to what @reveurdenuit described, I’d strongly consider a dedicated app if you live in screenshots all day.

Typical pros of dedicated screenshot apps:

  • Instant annotation UI, not an extra markup mode.
  • Numbered callouts, blur, arrows that snap nicely.
  • Auto upload and copy link for bug trackers.

Typical cons:

  • Extra cost or subscription.
  • Slight learning curve and more background processes.

Evaluate whether the built‑in stack plus little tricks like Automator, Quick Look markup, and custom shortcuts get you close enough before you jump.

6. Keyboard technique for precision captures
For detailed UI bug reports:

  • Start region capture with Shift + Cmd + 4.
  • Press Space to switch to window capture mode.
  • Then Option while clicking to remove the drop shadow from the window shot.

That no‑shadow version looks cleaner in docs and plays nicer when pasted onto backgrounds, which is handy for polished tutorials.

7. Text‑only capture instead of images (for dev‑heavy work)
If your bug reports are often about console output or logs, screenshots are actually the worst option. Instead:

  • Select text directly, then Cmd + Shift + 4 is not what you want.
  • Use Cmd + Shift + 4 only when layout or visual context matters.
  • Otherwise, copy text into fenced code blocks in your tracker or docs so it is searchable and diffable.

Sounds obvious, but a lot of people carry the “PrintScreen everything” habit from Windows where markup was the only easy tool.

If you plug these into the stuff already covered by @reveurdenuit and the extended tricks post, you end up with a workflow that is faster than Windows for both quick snips and polished tutorial screenshots, without your Desktop looking like a failed QA graveyard.