How to Create a Timelapse of Your Screen on Mac (2026)

You want to show 8 hours of design work in 60 seconds. Screen recording gives you an 8GB file and hours of fast-forwarding. There's a better way.

TL;DR: Capture timed screenshots at intervals, then export as MP4. No massive files, no boring dead air, no accidental notification captures. Shotomatic does this natively; you can also DIY with screencapture + FFmpeg.

Why Timelapse Beats Screen Recording

Screen recording captures everything — every frame, every pause, every bathroom break. For a timelapse of your work, that's overkill.

File size. A 4-hour screen recording at 1080p runs 4-8GB. The same session as a timelapse with 5-second intervals? Under 100MB as an MP4. That's the difference between "I can't upload this" and "here's a Slack message."

No dead air. Screen recordings include every moment you stared at your screen thinking, scrolled Twitter, or waited for a build. Timelapses skip idle time by design — every frame shows actual work.

Easy editing. With a screen recording, cutting out a 30-minute lunch break means firing up a video editor. With screenshot-based timelapses, you just delete the frames you don't want before export. No video editing skills needed.

Privacy. Screen recordings capture everything — Slack messages, email notifications, password prompts, personal browsing. Timelapse screenshots at intervals are easier to review and scrub before sharing. You see every frame as a thumbnail and can remove anything sensitive in seconds.

3 Ways to Create Screen Timelapses on Mac

Method 1: Shotomatic (Recommended)

Shotomatic is a macOS app built for automated screenshot workflows. For timelapses, the process is straightforward: set an interval, capture, export MP4.

How it works:

1. Set your capture interval (e.g., every 5 seconds)
2. Choose window or screen capture
3. Hit Start — work normally while it captures
4. Review frames, delete any you don't want
5. Export → MP4

Pros:

• Native MP4 export — no external tools needed
• Frame review and deletion before export
• Window targeting (captures one app even if other windows overlap)
• Presets for common workflows
• Optional countdown timer before capture starts

Cons:

• Mac-only
• Paid app (free trial available)
• No audio capture (it's a timelapse, not a recording)

Best for: Anyone who wants a working timelapse in under 5 minutes without touching the terminal.

---

Method 2: macOS screencapture + FFmpeg

The free, manual approach. macOS has a built-in screencapture CLI command, and FFmpeg can stitch images into video.

The script:

#!/bin/bash
# Capture a screenshot every 5 seconds
mkdir -p ~/timelapse
i=0
while true; do
  screencapture -x ~/timelapse/frame_$(printf "%05d" $i).png
  i=$((i + 1))
  sleep 5
done

Stop the script with Ctrl+C, then stitch with FFmpeg:

ffmpeg -framerate 30 -i ~/timelapse/frame_%05d.png \
  -c:v libx264 -pix_fmt yuv420p timelapse.mp4

Pros:

• Completely free
• Full control over every parameter
• No third-party app needed

Cons:

• Requires terminal comfort
• No GUI for frame review — manual file deletion
• screencapture captures the full screen (no window targeting without extra scripting)
• No preview before export
• Two-step process (capture, then stitch)
• Easy to forget to stop the script

Best for: Developers comfortable with the terminal who want a free, no-install solution.

---

Method 3: OBS Studio

OBS Studio is a free, open-source screen recording tool. It doesn't create timelapses directly — you record at full speed and fast-forward in post.

How it works:

1. Set up a screen or window capture source in OBS
2. Record at full resolution
3. Import the recording into a video editor (iMovie, DaVinci Resolve, etc.)
4. Speed up the footage 10-60x

Pros:

• Free and open-source
• Can include audio if needed
• Powerful recording options (multiple sources, overlays)
• Cross-platform

Cons:

• Produces massive files (gigabytes per hour)
• Requires a separate video editor to create the timelapse effect
• Multi-step workflow: record → edit → export
• Overkill for simple workflow timelapses
• Higher CPU usage during capture

Best for: Users who already have an OBS + video editor workflow, or who need audio in the final output.

Comparison Table

Feature	Shotomatic	screencapture + FFmpeg	OBS Studio
Cost	Free trial / Paid	Free	Free
Setup time	1 minute	5-10 minutes	10-15 minutes
Terminal required	No	Yes	No
Native MP4 export	Yes	Via FFmpeg	Via video editor
Frame review	Yes (GUI)	Manual file deletion	Video editor scrubbing
Window targeting	Yes	Extra scripting	Yes
File size (4hr session)	~50-100MB	~50-100MB	4-8GB raw
Audio capture	No	No	Yes
Post-processing needed	No	FFmpeg command	Video editor

Step-by-Step: Create a Timelapse with Shotomatic

1. Set Your Capture Interval

Open Shotomatic and configure the interval. This controls how often a screenshot is taken.

Recommended intervals:

• Quick demo/tutorial: 1-3 seconds (smooth, detailed playback)
• Design or coding work: 5-10 seconds (good balance of detail and file size)
• All-day documentation: 30-60 seconds (compact, high-level overview)

For a first attempt, start with 5 seconds. You can always adjust after seeing the result.

2. Choose Your Capture Mode

Window capture focuses on a single application — your code editor, design tool, or browser. Even if other windows overlap or you switch apps briefly, only the target window is captured. This keeps the timelapse focused and clean.

Screen capture grabs your entire display. Good for showing multi-app workflows but captures everything visible, including notifications and the dock.

For most timelapses, window capture is the better choice. It produces a cleaner, more focused result.

3. Start the Capture Session

Click Start. Shotomatic begins capturing at your configured interval. An optional countdown gives you a few seconds to switch to your target app.

Now just work normally. Shotomatic runs in the background.

Tips during capture:

• Avoid dragging windows over your target app (if using window capture, this doesn't matter)
• Dismiss notifications that pop up — or better, enable Focus mode on macOS
• If you need to take a break, stop the capture and restart when you're back

4. Review and Remove Unwanted Frames

After stopping the capture, review your screenshots in Shotomatic's gallery. Each frame is a thumbnail you can quickly scan.

Delete frames showing:

• Password prompts or login screens
• Slack messages or email notifications
• Personal browsing
• Long idle periods (if you forgot to pause)

This step is one of the biggest advantages over screen recording — you see every frame individually and can clean up in seconds.

5. Export as MP4

Select Export → MP4. Shotomatic stitches your screenshots into a video.

The exported MP4 is ready to share — upload to Twitter/X, LinkedIn, Slack, or embed in a client presentation. No video editor needed.

Best Interval Settings by Use Case

Use Case	Interval	~Frames/Hour	Result
Quick demo / tutorial	1-3 seconds	1,200-3,600	Smooth, detailed playback
Design work (Figma, Sketch)	5-10 seconds	360-720	Captures meaningful changes
Coding session	5-10 seconds	360-720	Good detail without excess frames
All-day work documentation	30-60 seconds	60-120	Compact daily summary
Dashboard monitoring	60+ seconds	60 or less	Periodic snapshots

Rule of thumb: If changes happen fast (drawing, rapid coding), use shorter intervals. If changes are gradual (writing, reading docs), use longer intervals.

Use Cases

Progress updates for clients. Instead of describing what you did this week, send a 30-second timelapse. Clients see the work happen. It builds trust and looks impressive with minimal effort.

Social media content. Dev and design timelapses perform well on Twitter/X and LinkedIn. A 60-second timelapse of building a UI component or fixing a tricky bug is engaging content that showcases your skills.

Daily standup demos. Replace "I worked on the login page" with a 15-second timelapse showing exactly what changed. More informative, more engaging, takes less time to present than a verbal explanation.

Tutorial creation. Show the entire process of building something — a website, an illustration, a spreadsheet model — compressed into a digestible video. Pair with a voiceover recorded separately for a polished tutorial.

Portfolio showcases. Designers and developers can demonstrate their process, not just the final result. A timelapse of a logo design from blank canvas to final version tells a story that a static portfolio page can't.

FAQ

What's the difference between a screen timelapse and a screen recording?

A screen recording captures every frame continuously, producing large video files (often gigabytes per hour). A screen timelapse captures screenshots at intervals — every few seconds or minutes — and stitches them into a short video. The result is a compact file that skips idle moments and shows only meaningful progress.

How much disk space does a screen timelapse use compared to screen recording?

Dramatically less. A 4-hour screen recording at 1080p can easily reach 4-8GB. The same session as a timelapse with 5-second intervals produces roughly 2,880 screenshots, which export to an MP4 under 100MB. That's 40-80x smaller.

What capture interval should I use?

Depends on the activity. For coding or design work, 5-10 seconds captures enough detail. For all-day documentation, 30-60 seconds keeps file sizes small. For quick demos, 1-3 seconds provides smooth playback. See the interval table above.

Can I create a screen timelapse for free on Mac?

Yes. Use the macOS screencapture CLI with a shell script and FFmpeg to stitch frames into video. It's free but requires terminal comfort. Shotomatic offers a free trial with a simpler GUI workflow.

Does a screen timelapse capture audio?

No. Since timelapses are built from screenshots taken at intervals, there's no continuous audio stream. If you need audio, record a voiceover separately or use a screen recording tool like OBS and speed up the footage in a video editor.