How Long Should a Live Wallpaper Loop Be?
Choose a live wallpaper duration by destination. Ten seconds is the catalog cycle for designed 4K masters; iPhone Live Photos stay at one to two seconds.
For a desktop, Android, or Linux video wallpaper, start with about ten seconds of one complete motion cycle. That is long enough for a radar sweep, a tunnel pass, or a particle orbit to finish, and short enough that an H.264 playback copy stays small. Most wallpaper apps can then seek back to the first frame without a visible pause.
An iPhone Lock Screen is a different job. Apple Live Photos record about 1.5 seconds before and after the still. Converters commonly refuse or trim anything much longer than one or two seconds.
Loop length is not the same problem as a seamless join. The seamless-loop guide covers how to hide the restart. This page is only about how many seconds that cycle should contain before you export.
The destination sets the ceiling
A wallpaper player can only play what the operating system will accept. Desktop apps such as Lively or Wallpaper Engine will repeat a local MP4 for as long as the file lasts. Phones will not.
| Destination | Typical useful length | Hard or practical ceiling | What happens if you go longer |
|---|---|---|---|
| Windows, macOS, Linux desktop | 8–12 seconds | App and disk, not the OS | File size and loop-seek hitch grow; some players buffer more of the clip |
| Android Home or Lock Screen | 6–12 seconds | Device RAM and decoder | Stutter, heat, or the app downsamples the video |
| iPhone Lock Screen (Live Photo) | 1–2 seconds | Live Photo timing | Converter trims the clip or iOS reports motion as unsupported |
| OBS / HUD overlay | 8–12 seconds | Compositor and alpha decode | A long ProRes 4444 overlay saturates disk and GPU |
| Screen saver | 10–30 seconds | Idle player only | Longer is safer here because the clip is not under icons all day |
Apple documents Live Photos as 1.5 seconds of motion on each side of the key still (Take and edit Live Photos). On iOS 17 or later the Lock Screen can play that Live Photo when the phone wakes (Set a Live Photo as Lock Screen wallpaper). It does not play an arbitrary 4K MP4 behind the Home Screen. That is why the iPhone setup guide starts with a short conversion, not a ten-second desktop master.
Lively’s video notes say to keep loops under 30 seconds so RAM stays down and the replay does not stutter (Lively wallpaper types). Treat that as a player hint. Thirty seconds of 4K 60 fps is already a large decode job on a laptop.
How long should the loop be?
Ten seconds is the authored catalog cycle for designed 4K masters. iPhone Live Photos are a different job, not a shorter desktop file.
Designed catalog
The period already exists. Do not invent extra seconds to hide a join that was designed at 10.00s.
Win · Mac · Linux
The OS will play any local MP4. The limit is the player, disk, and the seek back to timestamp zero.
Android
Continuous Home Screen playback is allowed. Decoder and RAM are not. Keep the period, change the crop.
iPhone Live Photo
Live Photos record about 1.5s on each side of the still. iOS 17+ plays that on wake, not a desktop MP4.
Saver · OBS
Savers can run longer because they are not under icons all day. OBS overlays should stay on the authored period.
Ten seconds is a production cycle
Unique Live Wallpaper catalog pages list duration as 10.00 sec on current 3840×2160 masters. Tunnel, ring, and HUD titles in the same browse row are also 10.0s. The production master for Neon Particle Grid Tunnel is 3840×2160, 60.00 fps, Apple ProRes 4444, 2.00 GB for those ten seconds.
You do not have to open the MOV for that number to be useful. In this archive format a full-quality 4K 60 fps second costs about 200 MB. The H.264 MP4 you set as wallpaper is much smaller.
The ten-second figure exists because the motion is periodic. If a nested square tunnel, a radar sweep, or a particle orbit is built so every independent transform returns at 10.00 seconds, the first and last frames can match in position, velocity, and lighting. A one-minute file will not hide a join that was never designed.
PixeryHub’s beginner guide mentions “typically 3–15 seconds” as a type label and then moves on (What is a Live Wallpaper). Wave’s FAQ does not discuss duration at all (Wave FAQ). A 2017 Wallpaper Engine thread treated length as secondary to file size and guessed 30–60 seconds when the author could not loop particles (Steam discussion). Those pages skip the catalog rule that actually matters: pick the shortest cycle in which the motion already returns.
Match seconds to the kind of motion
Not every clip wants the same clock.
| Motion class | Why the clock matters | Working length | Risk if you shorten it | Risk if you lengthen it |
|---|---|---|---|---|
| HUD sweep, radar, targeting reticle | The graphic is a period. One full rotation or scan is the loop. | 8–12 seconds | The sweep looks rushed and the join is obvious | Extra seconds are empty holds or a second identical sweep |
| Geometric tunnel / wormhole | Perspective motion needs time to travel, then return to the same depth cue | 8–12 seconds | The tunnel pops at the restart | Decode cost rises; repetition still appears after a minute |
| Flag, silk, slow fluid | Viewers notice a short period as a pulse | 10–20 seconds | Fabric snaps back too soon | File size grows; a 60-second flag is rarely more convincing than a 15-second one |
| Nature / smoke / clouds | Organic motion has no exact period unless you blend | 12–20 seconds plus a crossfade | The blend window eats the whole clip | Players hitch at a long GOP seek |
| iPhone Lock Screen wake | iOS plays a Live Photo burst, not a desktop loop | 1–2 seconds | None. This is the platform. | Motion not supported |
| Screensaver or signage | The screen is idle. A longer unique stretch delays repetition. | 15–30 seconds | Fine if the motion is already cyclic | Use a playback MP4, not the 2 GB master |
A HUD that completes one orbit in ten seconds should stay at ten seconds. Padding it to forty seconds does not add information. It adds bitrate, disk, and a longer jump when the decoder seeks to timestamp zero.
If you are converting a live-action clip that was never designed to cycle, do not invent duration first. Find one useful phrase of motion, then decide whether an exact cut, an overlap blend, or a ping-pong edit can close it. That workflow lives in the make-from-video guide. Duration comes after you know whether a period exists.
What extra seconds actually cost
Assume a 3840×2160, 60 fps source. The catalog ProRes 4444 master at ten seconds is 2.00 GB. Scale that linearly and you get a planning table, not a promise that every encode will land on these bytes.
| Length | ProRes 4444 4K 60 master (from the 2.00 GB / 10 s catalog example) | Rough H.264 4K playback copy at ~20 Mbps | What you feel on the desktop |
|---|---|---|---|
| 2 seconds | ~400 MB | ~5 MB | Fine for a phone conversion. Too short for a tunnel or HUD sweep. |
| 10 seconds | 2.00 GB | ~25 MB | Default for a designed loop. Most apps reseek cleanly. |
| 30 seconds | ~6 GB | ~75 MB | Lively’s published upper hint. Laptop fans may rise if the player cannot pause. |
| 60 seconds | ~12 GB | ~150 MB | Rarely worth it for wallpaper. Better as a screen saver or a one-shot title. |
Twenty megabits per second is a planning bitrate for a clean 4K wallpaper MP4, not a measured export from every title. CRF 18–23 in HandBrake or FFmpeg, as Lively suggests, will move the MP4 column. It will not move the ProRes column much. Keep the 2 GB MOV as an edit master. Set wallpaper from a muted H.264 copy. The format guide covers that split.
What extra seconds actually cost
Scaled from a published catalog master: 10.00 sec, 3840×2160, Apple ProRes 4444, 2.00 GB. The H.264 column uses a 20 Mbps planning bitrate for a muted playback copy.
A 10-second file with a two-second keyframe interval has five clean landings. A 60-second file with the same interval has more data to scan if the player loops by seeking to timestamp zero. The hitch at the join is often that seek, not the animation.
10s · 2s keyframe interval · 5 I-frames
Length also changes how the player returns to frame one. Long-GOP H.264 stores a keyframe every n frames. A 10-second file with a two-second keyframe interval has five places the decoder can land cleanly. A 60-second file with the same interval has more data to scan if the player implements the loop as a seek rather than a gapless replay. Shorter files fail that test less often. If the timeline loops and the wallpaper app does not, re-encode a shorter H.264 file with a tighter keyframe interval before you redesign the motion.
Some desktop players keep a large decoded buffer. Thirty or sixty seconds of 4K 60 fps is a lot of frames to hold. Integrated laptop GPUs then share that heat with the CPU. That is a temperature problem, not the same question as gaming performance or battery drain. A ten-second loop that pauses in fullscreen still uses less standing decode work than a one-minute loop that never quite leaves memory.
A short loop can still look long
Viewers judge repetition, not runtime. A ten-second tunnel with several independent periods (grid, particles, center pulse) takes longer to read than a ten-second clip where every element shares one obvious beat. If the wallpaper feels too repetitive, add a second periodic system inside the same ten seconds. Do not buy another forty seconds of the same beat.
Designed animation and live-action edits part ways here. A Unique Live Wallpaper HUD or tunnel is built so transforms return. A phone clip of a street is not. Stretching that street clip to 45 seconds delays the jump cut. It does not create a cycle. If you cannot close the motion, use the file as a screen saver or a locked playlist, not as an all-day desktop.
How to choose in practice
- Write down the destination: desktop wallpaper, Android, iPhone Lock Screen, overlay, or screen saver.
- If the destination is iPhone, cut 1–2 seconds and convert to a Live Photo. Do not start from the ProRes master.
- If the destination is desktop or Android, open the clip and mark one complete period. For Unique Live Wallpaper titles that period is already 10.00 seconds.
- Export an H.264 MP4 at the native display resolution, constant frame rate, no audio.
- Repeat the export ten times in a normal player, then again in the wallpaper app after sleep and sign-in.
- If the app hitch is only at the join, shorten the file or tighten keyframes. If the whole clip stutters, drop to 30 fps or 1440p. If the motion itself snaps, the period is wrong; go back to the loop guide.
On a multi-monitor desk, keep one length across displays. Mixing a 10-second HUD with a 45-second landscape on the same machine gives you two seek behaviors and two thermal loads. The multi-monitor guide covers span versus per-screen layout. Duration should stay shared.
A transparent overlay for OBS should follow the desktop rule, not the iPhone rule. Ten seconds of ProRes 4444 at 4K 60 is the catalog master. Playback inside OBS is usually a smaller ProRes or a high-bitrate MOV with alpha, still around that same ten-second period. A minute-long alpha file is a compositor problem. See ProRes 4444 with alpha and OBS overlays.
What to do with a file that is already the wrong length
If you bought or downloaded a Unique Live Wallpaper original, do not stretch it. The cycle is authored at 10.00 seconds. Speed-ramping a 10-second orbit to 6 seconds changes velocity at the join. Time-stretching it to 20 seconds makes the HUD feel sluggish and can expose interpolation artifacts on thin lines.
If you have a 3-minute camera take, do not set the whole take as wallpaper. Extract one phrase. If no phrase closes, pick a 12–20 second window and use an overlap blend, then accept that it is a texture loop, not a mechanical cycle.
If an iPhone converter rejects the file, the length is probably the reason. Cut a 1–2 second portrait center from the H.264 copy. The desktop master can stay at ten seconds.