How long does video restoration take? The factors that move it
Roughly: processing time ≈ total pixels × per-frame model cost ÷ machine throughput, plus encoding. To estimate a job, look at the frame count and the preset first.
Six factors
| Factor | Why it matters |
|---|---|
| Resolution | Pixel count grows with area — 1080p to 4K is roughly 4× |
| Duration and frame rate | Together they set the frame count, which scales time linearly |
| Model and preset | Accurate presets are slower but catch more and reconstruct better |
| Machine | The same clip can differ substantially between chips |
| Stacked jobs | Running restoration plus enhancement in one pass adds up |
| Encoding settings | Output codec and bitrate also consume time |
Estimating a job
- Run a 10–30 second sample at the same settings and note the time.
- Scale by duration to project the full clip.
- If you changed preset or stacked features, apply a multiplier — accurate presets are noticeably slower.
Speed versus quality
- Our default is quality first; we do not trade picture for speed by default.
- In a hurry? Run the fast preset across the whole clip, then re-run only the key shots at high quality.
- Avoid repeated passes: every reconstruction plus re-encode adds loss. Go from the original source once.
Frequently asked questions
Why does the same clip take very different times?
Mostly pixel count (resolution × frames), the model and preset you chose, your machine, and whether you stacked several jobs into one run.
How can I estimate a long job quickly?
Process a 10–30 second sample at the final settings, then scale the time by duration.
What if I need it fast but still want quality?
Scan the whole clip with the fast preset, then re-run the important shots at high quality instead of settling for one low setting everywhere.
More topics on the guides hub, or see what Lumasce does.