Automate

How to Automate Screenshots on Mac

The steps you repeat after every capture are the ones worth removing. Save to the right folder, blur the customer's email, pull out the text, export a PDF — each is small, and each is a decision you make dozens of times a week.

An automation in Snip Studio has three parts: a trigger, some conditions, and an ordered list of actions. Nothing about it is programming — it reads as a sentence.

Build an automation

  1. Choose the trigger

    Two options. After every capture runs the rule whenever you capture anything. On demand runs it only when you ask, and can be given its own global hotkey — which effectively lets you define capture shortcuts of your own.

    Two triggers. On demand can carry its own hotkey.
  2. Narrow it with conditions

    Conditions decide whether the rule applies to a given capture. You can match on:

    • The source app — only captures taken from Safari, or from Xcode
    • The website, for browser captures
    • The capture type — area, window, display, scroll
    • The window or page title
    • The recognised text inside the capture
    • The display it came from
    • The width or height

    Operators are is, contains, greater than and is present, combined with AND and OR. So "from Safari, and the page title contains Invoice" is expressible directly.

  3. Add the actions, in order

    Actions run top to bottom, and the order is the part that matters most:

    Actions available in a Snip Studio automation
    ActionWhat it does
    Recognise textRuns OCR so later actions can use the text
    Copy image / copy textPuts one or the other on the clipboard
    RedactApplies redaction to everything detected
    Save to folderWrites a file where you choose
    Export PDFWrites a PDF instead
    Pin to screenFloats the capture on top of everything
    Run a ShortcutHands off to macOS Shortcuts
    Show a notificationTells you the rule fired
    Open in editorBrings it up for annotation
  4. Put the redaction first

    A redact action bakes into everything downstream. Placed before a save or a copy, it is not possible for the rule to write the unredacted version — the later actions only ever see the redacted image.

    This is the single most useful property of the whole system. A rule that redacts and then saves to a shared folder is safe by construction, not by your remembering.

    Redaction runs first, so nothing downstream can leak.
  5. Hand off to Shortcuts for anything else

    Snip Studio exposes App Intents, so it appears in the Shortcuts app — there is a capture-area intent and one that runs text recognition on whatever is on your clipboard. An automation can call a Shortcut as its last action, which is the escape hatch for anything the built-in actions do not cover.

    There is also a URL scheme and a command-line helper for driving captures from outside the app.

Automations are an ULTRA feature

Capturing and the searchable library are free. Automations, the editor, recording, scroll capture and the Safari extension are part of the paid ULTRA upgrades, bought in-app through Apple. Recurring automations specifically are gated behind ULTRA.

Four rules worth stealing

Bug reports that redact themselves. After every capture · source app is your issue tracker · redact detected items, recognise text, copy text. You paste a redacted image and a searchable text block, every time, without deciding to.

Documentation that files itself. After every capture · window title contains your project name · save to that project's folder, open in editor. The capture is where it belongs before you have finished annotating it.

A reference you can keep looking at. On demand with a hotkey · pin to screen. A specification or a design stays floating over your work while you build against it.

Everything from the browser as a PDF. After every capture · source app is Safari · export PDF, save to folder, show a notification. Good for archiving pages you need a record of.

Where automations beat doing it by hand

Not everywhere. A one-off capture is faster to handle manually than to write a rule for, and a rule you write for a single occasion is wasted effort.

The threshold is roughly: the same three actions, on the same kind of capture, more than a few times a week. Below that, do it by hand. Above it, the rule pays for itself in a day — and, more importantly, it stops being something you can forget to do.

That last part is why the redaction case is the strongest one. Remembering to blur a customer's email works until the day you are in a hurry.

Common problems

The automation did not fire

Check the conditions. AND requires every condition to match; a title condition is case-sensitive to what is actually in the title bar, which is often not what you expect. Loosen to contains and test again.

It fired on captures you did not want

Add a condition rather than removing the rule. Source app plus capture type narrows most rules down correctly.

The saved file is not redacted

The redact action is after the save. Actions run in order — move redaction above it.

Text-based conditions never match

They rely on recognised text, so put Recognise text before any condition or action that depends on it.

The Shortcut does not run

Open Snip Studio once after installing so its App Intents register, then check the Shortcut runs on its own before calling it from a rule.

You want the rule off for a while

Disable it rather than deleting it — the conditions are the part that took thought.

Frequently asked questions

How do you automate screenshots on a Mac?

In Snip Studio, build an automation: a trigger (after every capture, or on demand with a hotkey), conditions matching the app, title, text or dimensions, and an ordered list of actions such as redact, recognise text, save to a folder or export a PDF.

Can a screenshot be redacted automatically?

Yes. A redact action bakes into every action after it, so a rule that redacts and then saves cannot write the unredacted version.

Does it work with the Shortcuts app?

Yes. Snip Studio exposes App Intents — a capture-area intent and one that runs text recognition on the clipboard — and an automation can call a Shortcut as an action.

Can an automation have its own keyboard shortcut?

Yes. An on-demand automation can be given a global hotkey, which effectively lets you define your own capture shortcuts.

Are automations free?

No — automations are part of the paid ULTRA upgrades. Capturing and the searchable library are free.

Triggers, conditions, operators and actions are from Snip Studio's own documentation and App Store listing. Last checked 1 September 2026.