Measured speed
How long Stitchfilm takes, measured on a real laptop.
Scanning runs at about 2.7 seconds of work for every second of footage. These are our own measurements from November 2026, with the method and the gaps stated.
What we measured
Measured on one Windows 11 laptop, 16 GB RAM, CPU only, November 2026
| Task | Input | Time |
|---|---|---|
| Scan footage | 145 seconds of phone footage | 6 min 43 s |
| Scan, face and body detection off | The same 145 seconds | 6 min 17 s |
| Export with music | A 133-second cut | 3 min 30 s |
What that means for a real event
Dividing 6 min 43 s (403 seconds) by 145 seconds gives about 2.7. Applied to longer footage, it gives these estimates for scanning. They are arithmetic, not separate measurements, and they assume the speed stays the same for longer and bigger files, which we have not checked.
| Footage | Estimated scan time |
|---|---|
| 5 minutes | About 13 to 14 minutes |
| 30 minutes | About 1 hour 20 minutes |
| 1 hour | About 2 hours 40 minutes |
| 2 hours | About 5 hours 20 minutes |
| 4 hours | About 10 hours 40 minutes |
Scanning runs while you do something else, so for long events, start it when you finish for the day.
How we measured
Real phone footage, scanned and exported inside the app on a 16 GB Windows 11 laptop with no graphics card used. The same machine did the scan and the export. Times will differ on other computers.
What is not measured yet
- An 8 GB machine.
- A very long single project.
- 4K or other large camera files, and clips much longer than a few minutes.
- HDR footage and unusual camera formats.
- Any faster scanning mode. It is on the roadmap, and we will update this page when it changes.
Last updated 20 November 2026. Questions or your own timings: support@stitchfilm.com.
Or write to support@stitchfilm.com