How to Automate Screenshots on Mac with Built-In Tools

macOS has three built-in ways to take screenshots on a schedule: the screencapture command, Automator, and the Shortcuts app. All three can capture, wait and repeat without extra software. This guide helps you pick one, prove it works with a three-frame test, and fix the problems that show up in longer runs.

Choose the built-in method that fits the job

Method	Good for	Weak spot
screencapture in Terminal	Fixed regions, exact file names, scripts you run often	Needs shell knowledge
Automator	A visual workflow saved as a double-click app	Native screenshot action can overwrite file names
Shortcuts	Menu bar and keyboard launchers, automations on recent macOS	Window and region capture need a script step

All three use the same capture engine and the same permission model. Pick the one you already know. If you know none of them, start with Terminal, because the test takes two lines.

Before you start: allow screen capture and test three frames

macOS requires screen recording permission for any app that captures other apps' windows. The app that runs the capture needs it: Terminal for a shell loop, Automator for a workflow (and the saved app separately), Shortcuts for a shortcut.

Open System Settings, then Privacy and Security, and turn on the app in the screen recording list. The label varies by macOS version. Quit and reopen the app after the change.

Test with three frames before any long run. Three frames show whether permission, file names and timing work, and the test takes about ten seconds. A run of 500 frames that saves only wallpaper wastes much more time.

Run a three-frame screencapture test in Terminal

mkdir -p ~/Captures/test
for i in 1 2 3; do
  screencapture -x -m ~/Captures/test/frame-$i.png
  sleep 3
done
open ~/Captures/test

Check three things in the folder: there are 3 files, each shows your open windows, and the names follow capture order. The -x flag silences the shutter sound and -m limits capture to the main display. The command line guide adds fixed regions, JPG output and longer runs.

Use Automator for a visual workflow

Create a new Workflow in Automator. Add Take Screenshot, then Pause set to 3 seconds, then Loop set to loop automatically and stop after 3 times. Run it and check the folder.

If only one file appears, the action wrote the same name on every pass. Replace Take Screenshot with Run Shell Script and use the screencapture line from the Terminal test with a numbered name. Save the finished workflow as an Application to run it with a double-click. The Automator walkthrough has the full shell action.

Use Shortcuts for launchers and triggers

Create a shortcut with Repeat set to 3. Inside the block, add Take Screenshot, Save File with the Repeat Index variable in the file name, and Wait set to 3 seconds. Run it and check the folder.

Shortcuts can then run from the menu bar, a keyboard shortcut, or shortcuts run in Terminal. On macOS Tahoe 26 and later, a personal automation can start it at a set time. The Shortcuts walkthrough covers triggers and script permissions.

Add page turns only after the capture works

Paging through slides or a document needs a key press between frames. Add it after the three-frame test passes, so a capture problem and a key problem never appear together.

All three methods send keys the same way, through System Events:

osascript -e 'tell application "System Events" to key code 124'

Key code 124 is Right Arrow. Order matters: capture, press the key, then wait long enough for the next page to render. Skip the key after the last frame so the document does not move past the final page. The app that sends the key needs Accessibility permission, and the target app must be in front.

Fix common screenshot automation problems

• Wallpaper only. The running app lacks screen recording permission. Allow it and reopen the app.
• One file instead of many. Each pass writes the same name. Add a counter to the file name.
• Black frames late in the run. The display slept. Run caffeinate -di in Terminal for the length of the run.
• Skipped pages. The key fired before the page rendered. Lengthen the wait after the key.
• Extra page at the end. The key fired after the last capture. Skip it on the final pass.
• Second display missing. Capture each display separately with -D 1 and -D 2.

When built-in tools stop being the simpler option

Built-in tools handle a fixed count at a fixed pace well. Each further need adds a script: capturing a single window by name, stopping at a clock time, pausing and resuming mid-run, or producing a searchable PDF or a video.

A dedicated app moves these into settings. In Temposhot's Auto Capture, you choose a source from Screens, Windows or Custom Area, then set the stop condition (Screenshots, Duration or End time), the interval in ms, seconds, minutes or hours, an optional Key press, and a Countdown. A floating toolbar pauses, resumes and finishes the run, and the results export as PNG, JPG, ZIP, searchable PDF or MP4. Presets such as Kindle (20 screenshots, 500 ms, Right Arrow, 3 s countdown) store a setup for reuse.

FAQ

Which built-in method is fastest to set up?

The Terminal loop. It needs one permission and five lines, and the same lines work later inside Automator or Shortcuts.

Do I need to keep the Mac awake?

Yes. A sleeping display produces black frames, and a locked screen interrupts capture. caffeinate -di keeps the display and system awake while a command runs.

Can built-in tools capture a single window?

screencapture -l captures a window by ID, but macOS has no built-in command that lists window IDs. A helper script or a dedicated app is needed.

What is screenshot automation, exactly?

It means a tool takes screenshots on a rule (an interval, a click, or a list of URLs) instead of a person pressing a shortcut each time. The screenshot automation glossary entry has a fuller definition.

Turn repeatable screenshots into finished work

When the built-in loop needs a window source, page turns, and PDF or MP4 export, see screenshot automation on Mac or follow the automated capture guide.