Shorts Script Timer (Free): will your script fit?

The number you find out too late

Almost everyone films the whole short before checking the one number that decides whether it works: how long the script actually takes to say out loud.

You find out at the edit, when the voice track runs forty-one seconds against a thirty-second plan. Every option at that point is bad — speed the voice up until it sounds synthetic, cut a line the rest of the script depends on, or let it run long. None of that is an editing problem. It was a scripting problem, and it was measurable before the camera came out.

This measures it in about five seconds.

Open it and use it

Download the package and open shorts-script-timer.html in any browser. That is the whole setup.

• No installation. It is one HTML file.
• No signup, no account, no API key.
• No coding tool of any kind. You do not need Claude Code, a terminal, Node, or Python. It is a web page that happens to live on your disk.
• Works offline. Turn off your network and it behaves identically.

Paste your narration into the box, one spoken line per row, and set your target length.

What it tells you

• Estimated spoken length, as a likely range rather than one number, because reading speed varies. Plan against the range.
• A verdict against your target — fits, borderline, or over, and how many seconds to cut.
• A line-by-line table with seconds per line and the slowest lines marked. Those are your first cuts: trimming the two slowest lines beats shaving a word off every line.
• A hook check. If the first line alone eats more than about two and a half seconds, you are spending the whole decision window on setup. Generic openers get flagged too.
• A caption-length warning for any line too long to read comfortably on screen.
• An ending check, because a long final line is a common quiet killer.
• A stopwatch that calibrates to you. Read the script aloud once and the estimate recalibrates to your measured pace. A generic words-per-minute figure is a starting point; your own pace is the real number.

Your script stays on your machine

The page makes no network requests. No analytics, no tracking, no telemetry, no server. What you paste is processed in the page and never leaves it — which is why it still works offline. Open your browser's network tab and watch nothing happen.

Honest limits

It is an estimate until you use the stopwatch, which measures one real read. It counts spoken length only — silent B-roll, a held beat before a reveal, or an outro card all add time it cannot see. The suggested platform windows are guidance, not hard limits, and platform limits change; check the platform's own current documentation. It does not write or rewrite your script — it tells you what runs long and which lines to look at first. It makes no claim about views, reach, followers, or revenue.

If you want the whole plan, not just the timing

Timing one script is the easy part. Producing one every day is the hard part.

Shorts Autopilot, from the same publisher, turns a topic into a complete faceless-short production package in a single reply — hook options with their visuals, a second-by-second shot list already timed to your target, TTS-ready narration, stock-footage search terms per shot, captions and tags for TikTok, Reels and YouTube Shorts, a cover-frame spec, retention weak points flagged before you build, and a series note. Thirty plans a month: one a day.

→ Shorts Autopilot: daily faceless video plans

This timer stays free either way. It is not a trial — nothing expires and nothing is withheld.

More from the same publisher

• Shorts Script Recut - your script runs long: cut it to length line by line, in one HTML file. → https://capafy.ai/agent/7636716964
• Shorts Factory Pro - turn a CSV of topics into finished vertical videos with voice and captions, on your own computer. → https://capafy.ai/agent/2178828395