ETA Calculator from Processing Speed — Free
Runs 100% in your browser — your files never leave your device.
Batch jobs, downloads, migrations, and manual tasks all answer the same question: if this many items took this long, when will the full workload finish? Enter the total units, observed units, elapsed time, and start timestamp to get the projected duration and completion time.
How it works
- 1
Enter the total workload
Set the number of units the full job must process.
- 2
Enter observed throughput
Provide completed units and the time they took.
- 3
Read the ETA
See both total duration and the projected completion timestamp.
About this tool
How the estimate works
Enter how many units you processed and how long it took, plus the total to process — the tool computes your real pace and projects the completion time. The estimate is only as honest as the numbers: measure the elapsed time with the stopwatch and the projection is solid.
The batch-processing use case
Converting 500 files and 37 finished in 4 minutes, uploading a queue with a measured rate, transcribing a batch at a known speed — any total with a measured partial progress becomes a completion time. Plan breaks and deadlines around a number instead of a feeling.
Estimates assume constancy
The projection extends your measured pace linearly — it cannot see slowdowns, failures, or speedups ahead. Re-measure after progress milestones and the estimate sharpens; treat the first projection as a first draft.
Frequently asked questions
Why should I measure with the stopwatch first?
Guessed paces are systematically optimistic. Thirty seconds of measured input gives an ETA you can actually plan around — the stopwatch exists precisely for this.
Can I enter a pace I want and solve for something else?
The tool projects from measured facts. For planning backward — how fast must I go to finish by X — compute the required rate from the total and remaining time.
Why does my ETA keep changing?
The estimate follows your real pace, so re-measuring after progress updates it. Changing estimates mean the pace is not constant — re-measure at milestones.