A timelapse without a timer has no scale — 40 seconds could be an hour or a week. How to add one at capture time instead of fighting it in an editor.
A timelapse on its own has no sense of scale. You're watching 40 seconds of a design coming together and there's nothing telling you whether that was one hour or three days. The compression is the whole point of the format, and it's also the information the format destroys.
A timer fixes that. It's a small addition that changes how the video reads, and it's the single thing I'd add first to any process video.
Pick the kind of timer
Three that make sense, and they say different things:
Elapsed time. Counts up from zero — 00:00:00 to 03:47:12. The default choice. It accumulates, so it reads as effort, and by the end the number is the proof.
Clock time. Shows the actual time of day as it was. Better for anything where the time of day is part of the story — a full working day, an all-nighter, a sunrise. "07:14" hitting "19:02" tells a story that "11:48:00" doesn't.
Countdown. Counts down to zero from a target. Good for a session with a fixed deadline — a pomodoro, an exam, a hackathon submission — and bad for open-ended work, because a countdown makes the end feel like a limit rather than an achievement.
For most process content — coding, design, art, study — elapsed time is the right answer.
Do it at capture, not in the edit
This is the part worth getting right, because doing it afterwards is genuinely painful.
To add a timer in post you need to know the mapping between video time and real time, then animate a text layer at that rate across the whole clip. In Premiere or After Effects that means an expression; in Resolve, a Fusion node; in CapCut, doing it by hand with keyframes. And you have to redo it if you retrim the clip, because the mapping shifts.
At capture time it's a setting. The recorder already knows the real elapsed time of every frame, because it stamped them. It burns the right number into each one as it goes, and no arithmetic exists for you to get wrong.
Tau does this through its timer overlays — pick the type, the position and the styling, and it's composited into the export automatically.
Add a timer without touching an editor
Elapsed time, clock, or countdown — styled how you want and burned into the export as you record.
Where to put it
Position matters more than it sounds:
Bottom right is the default for a reason. Eyes land there last, so it doesn't compete with the work.
Top left if the bottom right of your screen has something important in it — a terminal, a properties panel, a taskbar.
Centred and large is a style choice rather than an information one. It works for short social clips where the duration is the hook, and it's distracting anywhere else.
Avoid the bottom third entirely if this is going to TikTok, Reels or Shorts, because platform UI sits there. There's more on those safe zones in how to make a vertical timelapse.
Styling it so it doesn't look stuck on
A few things that separate a timer that looks designed from one that looks like a default:
Use a monospace font. In a proportional font the digits are different widths, so the timer visibly jitters as the numbers change. Monospace holds still. This is the single biggest one.
Drop the opacity. Somewhere around 70–85% lets the timer sit in the image rather than on top of it.
Size it relative to the frame, not absolutely. Something readable on a 1440p monitor is illegible after a platform re-encode and a phone screen. When in doubt, larger.
Pick a colour with contrast against what's behind it. White over a dark IDE is fine. White over a design tool with a light canvas disappears. If the background varies across the session, a subtle shadow or a low-opacity plate behind the text solves it.
If you have to do it in post
Sometimes the recording already exists. The least painful route:
- Work out the mapping — real duration ÷ video duration is your multiplier. A 3 hour session as a 60 second video is 180x.
- In Premiere or After Effects, add a text layer with a time expression scaled by that multiplier.
- In Resolve, the Fusion Time Code node with a modified rate.
- In CapCut and other simple editors there's no expression system, so it's manual keyframes — realistically only viable if you accept a timer that updates every few seconds rather than continuously.
It's doable. It's just an hour of work to reproduce something that was a checkbox before you hit record, and it breaks the moment you re-trim.
Why bother at all
The honest reason is that it's the difference between "here's a video of some work" and "here's what three hours looks like." The second one is the interesting claim, and without a timer you're asking the viewer to take it on trust.
It also makes the video useful to you. Going back through old sessions and seeing where the hours actually went is more informative than any time tracker, because you can see the work alongside the number.