How to Take Repeated Screenshots with Automator on Mac

Automator ships with macOS and can take a series of screenshots without extra software. A workflow of two or three actions captures the screen, waits, and repeats. This post builds that workflow two ways, saves it as an app, and lists the points where a dedicated capture tool takes less effort.

Check Automator's screen capture access

macOS treats screen capture as a protected permission. The first time a workflow captures the screen, macOS asks whether Automator may record the screen. If you decline, or the prompt never appears, the saved files show only the wallpaper and menu bar.

Open System Settings, then Privacy and Security, and find the screen recording list. The exact label differs between macOS versions. Turn on Automator there, quit Automator, and open it again.

A workflow saved as an app is a separate entry in that list. The app needs its own permission the first time it runs, even when Automator already has access.

Choose native actions or a shell action

Automator offers two routes to the same result:

• Native actions. The "Take Screenshot" action plus the "Loop" action. No code, but limited control over file names and the capture area.
• A shell action. The "Run Shell Script" action calls the screencapture command. It needs a few lines of shell, but you control file names, format and region exactly.

Start with native actions for a quick test. Switch to the shell action when files overwrite each other or when you need a fixed region.

Option 1: use Take Screenshot and Loop

1. Create a workflow

   Open Automator from Applications and create a new Workflow document.

2. Add Take Screenshot

   Search the library for "screenshot" and drag Take Screenshot into the workflow. Choose full screen capture and a destination in a folder used only for this job. The available options vary by macOS version.

3. Add a pause

   Add the Pause action and set the wait, for example 3 seconds.

4. Add the loop

   Add Loop at the end. Choose to loop automatically and stop after a count, such as 10 times, or after a number of minutes.

5. Run a short test

   Set the count to 3, select Run, and open the folder.

Check the file names after the test. If the action writes the same name on every pass, each capture replaces the previous one and you end up with a single file. Adding a Finder rename action that appends the date and time helps, but a sequence number is easier to sort. Option 2 solves this directly.

Option 2: combine Run Shell Script with Automator's Loop

Replace Take Screenshot with Run Shell Script and keep the Pause and Loop actions. Paste this into the action, with the shell set to zsh:

dir=~/Captures/automator
mkdir -p "$dir"
n=$(ls "$dir" | wc -l | tr -d ' ')
screencapture -x -t png "$dir/frame-$(printf %04d $((n + 1))).png"

Each pass counts the files already in the folder and writes the next number, so frames sort in capture order: frame-0001.png, frame-0002.png and so on. The -x flag turns off the shutter sound. Add -R 0,0,1440,900 before the file name to capture a fixed region instead of the whole screen.

Empty the folder, or change dir, before each new job. Otherwise numbering continues from the last run.

Save a reusable Automator app

Choose File then Save, and pick Application as the file format. Store the app somewhere stable, such as your Applications folder. Double-clicking it runs the workflow without opening Automator.

The first run of the saved app triggers its own screen recording prompt. If the workflow sends keys through AppleScript, the app also needs Accessibility permission.

Troubleshoot the workflow

Symptom	Likely cause	Fix
Images show only the wallpaper	Missing screen recording permission	Allow Automator or the saved app, then reopen it
Only one file after many loops	Fixed file name overwritten each pass	Use Option 2 or add a rename step
Loop runs once	Loop set to ask each time	Switch it to loop automatically
Second display missing	Full screen capture on one display only	Capture each display with -D 1 and -D 2
Frames are black	Display slept during the run	Keep the Mac awake for the length of the run

When Automator isn't enough

Automator covers a fixed count at a fixed pace. Several common needs take extra work:

• Keypress between frames. Turning a page needs an AppleScript step that sends a key through System Events, plus Accessibility permission.
• Stopping at a clock time. The Loop action counts passes or minutes. Stopping at 18:30 needs date logic in a script.
• Pause and resume. Stopping early ends the whole workflow.
• Searchable output. Automator can combine images into a PDF, but without OCR the PDF has no text layer.

Temposhot's Auto Capture handles these as settings. Each cycle saves a screenshot, sends the optional Key press, and waits for the interval. Stop conditions are Screenshots, Duration or End time, and the floating toolbar pauses, resumes or finishes the run. Exports include a searchable PDF and MP4. Keypress automation, Duration, End time and unlimited screenshots per session need Temposhot Pro.

FAQ

Does Automator still ship with macOS?

Yes. Automator is in the Applications folder on current macOS versions, alongside the Shortcuts app.

Can Automator capture a single window?

The Take Screenshot action does not target a window by name. The screencapture -l flag takes a window ID, but macOS has no built-in command that prints window IDs.

Why do my Automator screenshots overwrite each other?

The native action can write the same file name on every pass. Use the shell action in Option 2, which numbers each frame.

Can Automator make a PDF from the screenshots?

Automator includes an action that combines images into a PDF. The result has no text layer, so it is not a searchable PDF.

Turn repeatable screenshots into finished work

For timed runs with keypresses, stop conditions and PDF or MP4 export, read the automated capture guide or see screenshot automation on Mac. For the same loop without Automator, read automating screenshots from the command line.