How to Send Async Progress Updates with Screenshot Timelapse on Mac

You finished a 4-hour design sprint. Your client wants to see progress. Your options: schedule a 30-minute call to screenshare and narrate, write a detailed text update that no one reads, or send a 45-second timelapse that shows the entire arc of your work.

The timelapse wins every time.

TL;DR: Capture screenshots at intervals while you work, export as MP4, drop in Slack or email. Recipients see hours of progress in under a minute. No meetings, no walls of text, no screen recordings to scrub through.

Why Async Progress Updates Matter

Remote work runs on async communication. But text updates — even good ones — have a ceiling. "Finished the hero section layout and iterated on the color palette" tells your client something happened. It does not show them what happened.

Screenshots help, but sending 15 screenshots in a Slack thread is noisy. The recipient has to click through each one, reconstruct the order, and guess the timeline.

A timelapse compresses all of that into a single, self-explanatory artifact. The recipient hits play, watches 30-60 seconds of accelerated progress, and understands exactly where things stand. No context-switching, no scheduling, no meeting fatigue.

Who benefits most

Freelancers and contractors. Clients want visibility without micromanagement. A weekly timelapse shows you're making progress and gives them a natural point to leave feedback — "love the direction at 0:22, but the sidebar at 0:35 feels cluttered."

Remote engineering teams. Async standups work better with visuals. Instead of "worked on the dashboard refactor," you drop a 40-second timelapse showing the before, the intermediate states, and the current result.

Founders updating investors or advisors. A 60-second product timelapse is more compelling than a paragraph of text. It shows momentum.

Design teams. Iteration is the work. A timelapse shows how a design evolved — the explorations, the pivots, the refinements — in a way that a final mockup cannot.

The Problem with Other Approaches

Screen recording

You could record your screen for 4 hours. But then what? The recipient is not watching a 4-hour video. You need to edit it, speed it up, trim the dead time, cut around sensitive notifications. That's a video editing project, not a progress update.

Even at 8x speed, a 4-hour recording is still 30 minutes. Nobody is watching that.

Screenshots in a thread

Twelve screenshots dumped in Slack. The recipient scrolls through, loses context between images, doesn't know how long each state lasted or what order the changes happened. It's better than nothing, but barely.

Written updates

"Refactored the component library, updated the color tokens, and started on the responsive layout." Accurate. Informative. Completely fails to convey the actual work. Text is great for decisions and blockers — it's weak for showing visual progress.

How to Create Async Progress Timelapses

Step 1: Choose your interval

The interval depends on how fast things change visually in your work.

A shorter interval gives smoother playback but more frames to review. A longer interval gives a more compressed summary but might miss intermediate states. For most async updates, 10 seconds is a good default.

Step 2: Target the right window

This matters more than people realize. If you capture your full screen, the timelapse includes every app switch, every notification, every time you checked Slack. The result is noisy and potentially exposes private information.

Window capture solves this. Select the specific app window — Figma, your browser, VS Code — and Shotomatic only captures that window. The timelapse stays focused on the work.

If you're working across multiple apps (designing in Figma, then implementing in VS Code), consider running two separate capture sessions and sharing them individually. A focused 30-second Figma timelapse plus a 20-second VS Code timelapse is clearer than a single chaotic video switching between apps.

Step 3: Work normally

Start the capture and forget about it. That's the whole point. You don't need to perform for the camera or narrate your decisions. Just work. The timelapse captures the natural rhythm of your process.

Some tips for cleaner captures:

• Close notification panels before starting. Even with window capture, system alerts can overlay your target app.
• Use fullscreen or maximized windows. Consistent framing makes the timelapse easier to follow.
• Don't worry about mistakes. If you delete a component and redo it, that's actually useful context — it shows the iteration process.

Step 4: Review before export

This step is critical. Before exporting, scrub through the captured frames and remove anything you don't want shared:

• Slack messages or email notifications that appeared over your work
• Password prompts or login screens
• Browser tabs showing personal content
• Any frame where you switched to a different app accidentally

This is one of the biggest advantages over screen recording. With a recording, you'd need a video editor to cut these moments. With screenshots, you just deselect the frames you don't want.

Step 5: Export and share

Export as MP4. The file is typically small — a 2-hour session at 10-second intervals produces a video under 20MB in most cases. That's well within Slack's file upload limit and light enough to attach to an email.

Where to share:

• Slack/Discord: Drag the MP4 into the channel. It plays inline — no one needs to download anything.
• Email: Attach the file. MP4 files play inline in Slack, Discord, and Teams. Most email clients show video as an attachment rather than playing inline — consider uploading to a shared drive and linking instead.
• Notion/Confluence: Upload as an embedded video in your project page.
• Loom/Google Drive: Upload and share a link if the file is too large for direct sharing.
• GitHub PR: Attach to the PR description. Reviewers see the visual evolution alongside the code diff.

Real-World Workflows

Freelance web design

The scenario: You're redesigning a client's landing page. They want weekly updates.

The workflow:

1. Start a Shotomatic capture targeting your Figma window, 8-second interval
2. Design for 3 hours
3. Stop capture, review frames, remove any that show other client work or personal tabs
4. Export MP4
5. Drop in the client's Slack channel with a one-line summary: "Hero section and pricing table iterations — 3-hour session compressed"

The result: The client sees the evolution from wireframe to polished design. They can pause at any point and say "I liked it better at this stage." That's faster and more precise feedback than "I liked the earlier version better."

Remote engineering standup

The scenario: Your team does async standups. Everyone posts what they worked on yesterday.

The workflow:

1. At the start of your work session, start a capture targeting VS Code or your browser (for frontend work), 15-second interval
2. Code for the day
3. Export a 30-second timelapse
4. Post in the standup channel: "Dashboard refactor — component extraction and responsive grid" plus the timelapse

The result: Teammates can see the scope of the change at a glance. The engineering manager gets visual context without scheduling a review call.

Client project milestone

The scenario: You're a contractor building a mobile app. The client wants a milestone review every two weeks.

The workflow:

1. Throughout the sprint, capture key work sessions (2-3 per week)
2. At milestone time, share the most representative timelapse alongside your written update
3. The timelapse shows the process; the written update covers decisions, blockers, and next steps

The result: The client feels involved in the process without needing to attend daily standups. They can see you're not just billing hours — real work is happening.

Tips for Better Async Timelapses

Add context with the share message

A timelapse without context is just a fast video. Always include a one-line summary when sharing:

• "Login flow redesign — 4 iterations over 2 hours"
• "Performance dashboard — data viz exploration, landed on the bar chart approach"
• "Bug fix for #423 — traced the issue from the API response to the rendering layer"

Keep it short

A 30-60 second timelapse is ideal. Beyond 90 seconds, attention drops. If your session was very long, consider exporting only the most important segment rather than the entire session.

Be consistent

If you send a timelapse every Friday, your team or client starts expecting it. It becomes a rhythm — a low-effort way to maintain visibility and trust. Consistency matters more than polish.

Use GIF for micro-updates

For very short updates — a quick 5-second animation showing a UI interaction you built — GIF works well. It loops automatically in Slack and doesn't require the recipient to hit play. But for anything longer than about 10 seconds of playback, MP4 is better because GIF file sizes balloon quickly.

When Not to Use Timelapses

Timelapses are not a replacement for every communication method.

• Decisions that need discussion — Write a document or schedule a call. Timelapses show progress, not reasoning.
• Bug reports — A specific screenshot or short screen recording showing the bug is more useful than a timelapse of the debugging session.
• Architecture discussions — Text and diagrams are better for abstract concepts.
• Urgent blockers — Message the person directly. Don't make them watch a video to discover you're stuck.

Timelapses are best for one thing: showing visual progress over time. Use them for that, and use other tools for everything else.

Comparison: Timelapse vs Other Async Update Formats

The timelapse sits in a sweet spot: low effort on both sides, and it shows both the output and the process.

Getting Started

The setup takes about two minutes:

1. Open Shotomatic
2. Set your interval (start with 10 seconds)
3. Select your work window
4. Hit Start
5. Work for however long
6. Stop, review, export MP4
7. Share

That's it. No editing software, no narration, no post-production. The timelapse is ready to share the moment you export.

Try it for your next work session. Capture a 2-hour block, export the timelapse, and share it with your team or client. Most people who try it once make it part of their regular workflow.

Shotomatic has a free trial with limited captures, and paid plans for unlimited use. Everything runs locally on your Mac.

Download Shotomatic