Starting a thousand-video job is easy. Waiting for it with no idea what is happening is not. So the batch page on Scriptube now shows you the whole story live.
Here is what you will see and how to use it.
The progress bar, speed and time left
At the top of the batch page you get three things:
- A progress bar showing how much of the batch is done.
- Videos per minute, so you know the current pace.
- Time left, an estimate based on that pace.
The time-left figure is an estimate, not a promise. It will move as the pace changes, which is normal on large jobs. What matters is that you can plan: if you see a couple of hours left, go and do something else and check back.
The batch map
Under the progress bar is the batch map. It shows one coloured square per video. You can take in the state of a huge job at a glance:
- A screen full of completed squares means things are healthy.
- A cluster of a different colour tells you something specific happened to a group of videos, so you know where to look.
- Squares changing colour over time is the visual version of progress. Watching it fill is oddly satisfying.
For a 3,199-video channel, a list would be exhausting to scroll. A map you can read in two seconds is far better.
Status tabs: find exactly what you need
Below the map, the videos are grouped into tabs:
- Failed: videos that did not produce a transcript and may be worth retrying.
- Waiting: videos still to be processed, or waiting to resume.
- Completed: videos with a transcript, ready to read and export.
- Skipped: videos that were set aside and not processed.
Each tab lists 50 videos per page, so even a very large batch stays easy to browse.
Retry failed videos with one click
If the Failed tab has entries, you can retry them with a single click. No re-pasting links, no starting a new batch. We cover when retrying makes sense in retrying failed transcripts.
Some videos will not succeed on retry, because YouTube has no captions for them at all. That is common with long live streams and old clips. You are only charged for transcripts you actually get, so these cost you nothing. Our article why some videos have no transcript explains the reasons.
You do not have to stay on the page
Live progress is there for your peace of mind, not because the job needs supervision. Big jobs keep going on their own. If YouTube slows things down, waiting videos automatically resume, and nothing is charged until a transcript arrives. Close the tab, come back later, and the page shows where things stand. If you prefer to be notified, developers can use webhooks for completion; see webhooks vs polling.
What if credits run out?
You will see it on the same page. If credits run out mid-batch, everything already transcribed stays with you and the rest is cancelled and not charged. A batch never fails silently. Details are in you only pay for what you get.
A simple routine for big jobs
- Check the estimate and confirm the batch.
- Open the batch page and note the videos per minute and time left.
- Come back when it suits you and glance at the batch map.
- Open the Failed tab and retry anything worth another try.
- Move to your library to search, sort and export.
Why it matters
Trust in a tool comes from being able to see what it is doing. A black box that says "processing" for three hours does not build any. A progress bar, a pace, a time estimate and a map of every single video do. That is the standard we want for every batch, small or large.
See it in action: start a batch from your dashboard, or check plans and credits for bigger jobs.