Choose the change and duration before calculating intervals
A time-lapse compresses a long change into a short sequence. A city shot might follow lights appearing at dusk; a workshop or exhibition shot might reveal a process. Define the change and its editing purpose before committing to a position and recording period.
For a still-image sequence, the approximate frame count is output seconds multiplied by output frame rate. A hypothetical 10-second shot at 25 fps needs 250 images. At four seconds between exposure starts, the time between the first and last start is about 249×4 seconds, plus the final exposure and preparation margin. These numbers demonstrate the calculation, not a universal setting.
The interval controls how frequently movement is sampled; shutter time controls blur within each frame. Test both. Confirm whether the device measures intervals between starts or as a pause after an exposure, and leave room for exposure, writing and processing. Nikon's time-lapse guide distinguishes still sequences from in-camera time-lapse movies. Check which files your chosen mode preserves if individual-frame editing matters.
Plan position, movement and power for the entire period
Scout for more than the opening view. Anticipate signs, vehicle lights, reflections and obstructions after dark. Use a stable position where filming and continued access are permitted, keep routes clear and prepare suitable protection for changing conditions.
With a motion-control head or slider, rehearse the full path. Check framing at both ends and along the route, cable clearance, support and compatibility. A fixed position can communicate change effectively; camera movement should earn its place rather than compromise the sequence.
Check storage and power against the planned frame count and duration. Record a short test and review focus, exposure, white balance and file order. Use manual focus or a tested locking method to prevent unwanted refocusing. Keep white balance controlled so that automatic shifts do not create unintended colour jumps.
Plan exposure changes across the transition
Fixed exposure can provide continuity under steady light. A large transition into darkness may exceed what one setting can cover, so plan how exposure will change. Manual steps, supported smoothing features and dedicated controllers each require testing with the actual camera and workflow.
For a manual approach, first establish aperture and depth of field, then define usable shutter and ISO ranges. Watch essential highlights and shadows without chasing each passing headlight. Keep original images and EXIF data, and note significant adjustment points. Software can help connect exposure changes; it cannot reliably restore clipped details, missed focus or a displaced camera.
Preserve a meaningful difference between daylight and night. The aim is continuity, not identical brightness in every image. A bracketed HDR sequence also needs separate checks for moving-object ghosts and consistent merging. A day-to-night sequence is not automatically an HDR sequence.
Develop transitions, then review flicker and output
Back up the full sequence and inspect ordering, missing frames and interruptions. Compare representative daylight, transition and night images before deciding the intended colour and brightness progression.
The official LRTimelapse workflow includes keyframe edits, calculated transitions and visual deflicker. When using Lightroom Classic, follow the metadata exchange required by the installed versions and confirm that edits appear in the developed previews. A finished still is not proof that the entire sequence is ready.
Judge flicker in a relatively stable region, avoiding lights that are supposed to change rapidly. Play the sequence after correction, looking for removed natural variation, colour jumps or local brightness pumping. Export a representative section first, then complete the agreed frame rate, framing and resolution.
Retain source images, adjustment files, software versions and export settings. Hand over actual intervals, timing, exposure changes and exceptions so that revisions can start from known choices. Reviewed on 2 October 2026; calculations and working checks are editorial recommendations. Software controls depend on the installed version.