How to Send Async Progress Updates with Screenshot Timelapse on Mac

A written status update says what changed. A 30-second timelapse shows how the work moved: the layout that was tried and dropped, the screen that took most of the afternoon, the state at the end of the day. Paired with three or four lines of text, it replaces many status calls for design and development work.

When a timelapse works for async updates

A timelapse adds value when the work is visual and changes on screen over time:

• Design. Layouts, illustrations, prototypes and slide decks.
• Front-end development. A page or component taking shape in the browser.
• Data and dashboards. A report filling in, or a long import or build progressing.
• Client work. Showing effort and direction between milestones without scheduling a call.

It works best for audiences who review in their own time zone. A short MP4 plays in most chat tools, email clients and project trackers without an account or a link to a shared workspace.

Create an async progress timelapse

The setup below captures one app window, so other windows and notifications stay out of the frames.

1. Pick the source

   Press Command+1 for Auto Capture, open the Windows tab in the source picker, and select the design tool or browser window.

2. Set the interval

   Set Interval to 10 seconds for a half-day session, or 5 seconds for one or two hours.

3. Set the stop condition

   Choose End time and enter the time your work block ends, such as 17:30. Duration and End time need Temposhot Pro. On the free version, use Screenshots with a count.

4. Start and work

   Select Start Capture. Use Pause capture on the floating toolbar during breaks or private tasks, and Resume capture when you return.

5. Review and export

   When the run ends, clear the checkbox on any frame that shows private information. Select MP4, choose 30 fps and Medium quality, and export.

A 4-hour block at a 10-second interval produces 1,440 frames, which plays for 48 seconds at 30 fps. At 60 fps the same frames play in 24 seconds.

Example async updates

Keep the text short and specific. The video shows the process, so the text covers decisions and questions.

Design update to a client

• Video: 45 seconds, Tuesday's session on the pricing page.
• Done: two layout directions, picked the comparison table version.
• Needs your input: the third plan name, by Thursday.
• Next: mobile layout and the FAQ block.

Development update to a team

• Video: 30 seconds, building the settings screen.
• Done: form layout, validation messages, dark mode.
• Blocked: the API error format for expired sessions.
• Next: keyboard navigation and tests.

Weekly progress to a manager

• Video: 40 seconds from Thursday's 2-hour session at a 6-second interval (1,200 frames).
• Done: onboarding flow screens 1 to 6.
• Risk: illustration work is a day behind.

Make the update easier to review

• Keep it under 60 seconds. Raise the export frame rate or shorten the run. Viewers rarely watch long progress clips to the end.
• Use one window. A window source keeps chat, mail and notifications out of every frame.
• Trim the start and end. Deselect setup and wrap-up frames before export.
• Add stills for decisions. Export the two or three frames that matter as PNG and attach them next to the video.
• Pick a size that plays everywhere. Medium quality usually keeps the file small enough for chat attachments. Check your tool's upload limit.
• Name the file by date and topic, such as 2026-07-27-pricing-page.mp4, so it is easy to find later.

For a short loop inside a message, choose GIF from Export settings… on the export bar. GIFs get large quickly, so keep them to a few hundred frames, or build one later with Images to GIF.

When not to use a timelapse

• The update is a decision, not progress. Write it down. A video adds nothing to "We chose option B".
• The work is not visual. Back-end changes, research and writing show little on screen.
• The viewer needs to follow exact steps. Use a step-by-step guide with one screenshot per click. See step-by-step guides vs screen recording.
• The screen shows confidential data that you cannot exclude by window or by deselecting frames.
• The audience wants a conversation. A short call can resolve open questions faster than a recorded update.

Frequently Asked Questions

How long should an async timelapse be?

Aim for 20 to 60 seconds. At 30 fps that is 600 to 1,800 frames, so pick an interval that fits your work block.

Can I send the video without uploading it to a cloud service?

Temposhot saves the MP4 on your Mac and has no upload feature. You attach it in your chat, email or tracker, so it goes wherever that tool stores files.

What if I forget to pause during a private task?

Clear the checkbox on those frames in the results pane before exporting. Only selected frames go into the MP4.

Can I make a timelapse from screenshots I took another way?

Yes. Images to Video turns a set of images into an MP4 in your browser.

Turn repeatable screenshots into finished work

Save your interval and stop condition as a preset with Save Current Setup, then pick the window again after applying it, since presets do not store the source. The capture presets guide shows how, and the timelapse walkthrough covers interval choices.