AI time-lapse video prompts: make the change visible
Describe what the shot starts with, how it visibly changes, and where that change ends. Keep the framing simple enough to follow the process. An AI time-lapse prompt requests the appearance of compressed time; it does not record real elapsed time or set an actual capture interval. Choose the delivered clip length through the service's supported controls, separately from the story you want to depict.
1. Story time, clip length and playback speed are separate
A flower can appear to open in a short generated clip even though the depicted process suggests a longer period. That is a creative temporal effect. It is different from recording a real flower at intervals and assembling those captured images into a time-lapse.
Google's video prompt guide treats time-lapse as a pacing choice and distinguishes it from gradual evolution within a shot. Runway's prompt ideas guide also includes a flower time-lapse among its nature examples. These are useful creative directions, rather than proof that every model can reproduce an exact schedule or a particular biological process.
On a small screen, scroll the table sideways.
| Decision | What you choose | What to check |
|---|---|---|
| Time represented | A bud opening or clouds crossing the sky | Does the visible progression communicate that process? |
| Delivered duration | A short clip length supported by the selected workflow | Do the actual settings and exported file match your plan? |
| Playback adjustment | Whether to retime accepted footage in an editor | Does the changed speed remain usable and readable? |
Writing “one frame every minute” does not make a generative service capture those minutes. Likewise, export frame rate does not establish how much real time a generated scene represents. If a precise interval or a real process record is essential, use a capture workflow and source material that can establish it.
2. Give the process an opening, progression and ending
“Make a beautiful time-lapse” leaves the transformation unspecified. Name one change that should be visible in the same scene. Start with a limited progression before requesting a complete season, a growing garden and a moving camera together.
Subject and visible opening state: One process to depict in compressed time: Intermediate change a viewer should be able to follow: Intended ending state: Camera position and stable scene landmarks: Lighting: steady or deliberately changing: Reference file, actual model/mode and duration setting: Output ID, observed progression and acceptance decision:
For our original planning scene, use a single pale-yellow flower bud on a short stem in a dark blue pot on a white shelf. The intended change is a partial opening, with the petal tips separating enough to reveal the interior. The pot, shelf and stem give you landmarks for checking stability while the flower changes. The aim is a readable illustration, not a botanical measurement.
A closed bud fading into a different open flower may give you two attractive endpoint images without the continuous opening you wanted. Write the intermediate change you intend to see, then inspect whether it actually appears. An ending image alone does not establish the process between the frames.
3. Adapt these original time-lapse prompts
These are unrendered draft examples, with no benchmark or success-rate claim. Use the selected model's documented inputs and duration options for a small initial trial.
Text-to-video: a partial flower opening
Locked close view of one pale-yellow flower bud on a short stem in a dark blue pot, centered on a white shelf. In a compressed-time progression, the closed bud gradually opens partway: the petal tips separate and the interior becomes visible. The same flower remains attached to the stem throughout the change. The pot, shelf and camera stay steady in soft, even light. The shot finishes with the partially open flower clearly visible.
The limited ending gives the trial one question: can you follow the bud opening while the rest of this scene stays recognizable? A prompt can express that goal but cannot guarantee petal structure, identity or biologically accurate development.
Image-to-video: animate the supported change
The visible bud opens partway in a continuous compressed-time progression. Its petal tips separate to reveal the interior while it remains attached to the stem. The pot, shelf, lighting and camera stay steady. The ending holds the partially open flower in view.
Use this with a reference that already shows the intended bud and composition. Attach the actual file through the supported image input. If your source already shows a fully open flower, this prompt asks for a conflicting opening state; prepare a different reference or choose a change that fits the image.
Alternative scene: clouds over a fixed rooftop
Fixed wide view of a gray tiled rooftop with one orange chimney beneath an open sky. Clouds pass briskly across the sky in a time-lapse progression, with broad patches of light and shade moving over the roof. The roof tiles and chimney retain their positions and shapes. The camera holds the same view throughout the clip.
Here the changing light is intentional. A rule that demands identical brightness in every frame would conflict with this brief. Decide which changes belong to the process and which are unwanted flicker. The lighting guide helps make that distinction explicit before a trial.
4. Inspect the progression through the whole take
- Read the process at normal speed. Does the intended change register within the delivered duration?
- Inspect intermediate states. Pause or scrub to look for replacement, a dissolve, a sudden jump or an unrequested reversal.
- Follow stable landmarks. Check whether the pot or roof warps along with the intended subject change.
- Compare light to the plan. Separate deliberate cloud-shadow movement from unrelated brightness pulses.
- Check the ending. Make sure the intended final state is visible long enough for its use in the edit.
Save a concrete observation such as “the bud is replaced halfway through while the pot shifts” or “the cloud motion reads, but the chimney bends.” Keep the reference, exact prompt, settings and output ID with that note. Frame inspection reveals visible issues, not the model's internal cause or a measured physical timeline.
5. Simplify the change before adding more instructions
If the result jumps straight to the ending, try a smaller amount of change. If the setting transforms too, reduce competing scene changes and simplify the framing. If the opening does not fit the reference, fix that mismatch first. Keep the other inputs recorded when comparing attempts, while allowing for generation varying between runs.
Retiming can change how quickly existing footage plays; it cannot supply an opening process that the source never showed. Review the pacing and retiming guide for that separate decision. If you need several distinct stages, plan them with the storyboard template and accept that a sequence of shots serves a different edit from one continuous time-lapse. Set an attempt limit before generating.
Shotmelo currently helps organize manual image and motion briefs, preview a local reference, and save or export text drafts. It does not generate time-lapse footage, capture images at intervals, analyze growth or retime video. Use the planning fields here to prepare a brief, then create and inspect the actual clip in your chosen service.
Published November 5, 2026. Official guidance checked on that date. Scene, prompts and review criteria are original planning examples; no paid rendering tests or guaranteed temporal result.