A script runtime estimator turns a screenplay's page count into a working estimate of how many minutes the finished film or episode will run on screen. It builds on the oldest rule of thumb in screenwriting, that one properly formatted page equals about one minute, and then makes it smarter by letting you adjust for the kind of pages you have actually written. Type in a page count, note whether the script leans on dialogue or action, pick the format you are writing in, and the tool gives you a runtime in minutes and seconds. It is the fastest way to answer the question every writer eventually asks: how long is this thing going to be.
That question matters more than it first appears. A feature that reads long on the page can get passed over before anyone reaches the good scene on page 90. A television script has to land inside a slot. A short film festival caps its entries by minutes, not pages. Knowing your likely runtime early lets you shape the script to fit, and a script runtime estimator gives you that number in seconds instead of a full read aloud with a stopwatch.
What the script runtime estimator does
At its core, the tool multiplies your page count by an expected number of seconds per page, then converts the result into minutes. The default pace is the traditional one minute per page, but you are not locked to it. You can choose a balanced pace that reflects the real world average of about 55 seconds per page, a faster pace for dialogue heavy material, a slower pace for action heavy material, or a format preset for feature film, hour long drama, half hour comedy, or animation.
Because a single number can be misleading, the estimator is built to show you a range. A talky comedy and a wall to wall action piece with the same page count will play at different lengths, so seeing a low, middle, and high estimate is more honest than pretending there is one exact answer. You get a quick, realistic picture of where your runtime is likely to fall, which is all the rule was ever meant to provide.
Who this tool is for
Screenwriters are the obvious audience. From a first feature draft to a pilot polish, length is something you have to watch, and a script runtime estimator gives you a fast gut check between drafts. It is handy at the outline stage too, when you can estimate from a target page count before writing a word.
Filmmakers and producers use it to plan. A rough runtime feeds into everything from a festival submission to a pitch, and it helps flag a script that is running long before it becomes an expensive problem in the edit. First assistant directors and line producers glance at page counts all day, and turning those into minutes supports scheduling and budgeting conversations.
Students and script readers round out the group. Film students learn the page per minute rule early, and a tool that shows its strengths and limits teaches the concept better than a flat number. Contest readers and development staff, who assess many scripts, can sanity check a stated runtime against the page count in a moment.
The one page, one minute rule and where it comes from
The rule is beautifully simple: one page of a properly formatted screenplay runs about one minute on screen. It has been passed down for generations because standard screenplay format is remarkably consistent. When a script uses 12 point Courier or a close equivalent, roughly one inch margins, and the conventional indentation for scene headings, action, character names, and dialogue, each page holds a fairly predictable amount of story. That consistency is what lets a page stand in for a minute at all.
The reason the rule works is that Courier is a monospaced font, so every character takes the same width, and the fixed layout means a page cannot secretly cram in extra material. A minute of screen time and a page of that format happen to carry a similar load of dialogue and action, at least on average. Strip away the standard format and the whole thing collapses, which is why the first question behind any estimate is whether the script is formatted correctly.
Writers lean on the rule because it is a shared language. When someone says a script is 110 pages, everyone in the room hears "about an hour and 50 minutes" without doing any math. That shorthand is useful precisely because it is close enough, most of the time, to be worth trusting for a first pass.
What the data actually says
The rule is a starting point, and the honest version of the story is more interesting. One large analysis looked at roughly 2,520 scripts and compared each script's page count to the finished film's runtime. The average came out to about 55 seconds per page, not a full minute. Put another way, scripts carried around 9 percent more pages than the film had minutes, so films tended to run slightly shorter than the naive prediction.
The spread is the eye opener. Only about 18 percent of the scripts landed within five percent of a clean one to one match. The other four out of five differed by more than a handful of minutes in one direction or the other. So the rule is a good center of gravity, but any single script can sit well off it. That is not a flaw in your writing, it is the nature of turning pages into time.
Length itself bends the ratio. Shorter scripts in the 60 to 89 page range tended to produce films longer than their page count, while scripts in the 110 to 130 page range ran a bit shorter than predicted, and very long scripts past 150 pages ran much shorter than their pages implied. The takeaway for a script runtime estimator is clear: a fixed one minute per page will mislead at the extremes, so a good estimate accounts for the kind of script you have.
Why dialogue and action change the math
The single biggest reason two scripts of equal length run at different times is what fills the pages. Dialogue and action move at opposite speeds relative to the page.
Dialogue heavy pages run faster than a minute. Spoken lines fill a page quickly on the screen because people talk at a brisk clip, and a page packed with back and forth banter can play in 40 to 50 seconds. Comedies, which lean on rapid dialogue, tend to run a little short of their page count for exactly this reason. In the data, comedies averaged about 1.15 pages for every screen minute, meaning each page bought a bit less than a minute.
Action heavy pages run slower than a minute. A line of description can be short to read and long to watch. "They battle through the burning warehouse" is under a second on the page but might play for two full minutes on screen. Chases, fights, montages, and set pieces all stretch time this way. Musicals show the same effect from a different angle: a song might take a few lines of script and several minutes of screen, so musicals averaged about 0.9 pages per minute, running longer than their page count.
This is why a smart script runtime estimator asks about content. Setting a faster pace for a dialogue driven piece or a slower pace for an action spectacle gets you far closer than a one size fits all minute. Most scripts mix both, which is why the balanced 55 second pace is a sensible default for a typical feature.
How format changes the ratio: film, TV, and animation
Beyond content, the format you write in shifts the numbers, sometimes dramatically.
Feature films track the rule most closely. A typical screenplay runs about 90 to 120 pages and produces a film of roughly 90 to 120 minutes. Comedies often come in around 90 to 100 pages and dramas around 110 to 120. This is the arena the one minute per page rule was really built for, so a plain estimate works reasonably well here.
Television splits into cases. A network hour long drama script of about 44 to 45 pages lines up with roughly 44 minutes of actual content, since a broadcast hour leaves room for advertising. Premium and streaming hours run longer scripts, about 55 to 65 pages, because they use the full 60 minutes. Half hour comedy is where the rule breaks most. A single camera sitcom script of 30 to 35 pages often plays in about 22 minutes, and multi camera sitcoms, with their dialogue heavy, generously spaced format, run faster still. Comedy simply plays quicker than drama.
Animation is the biggest outlier. Animated comedy scripts run closer to two pages per minute, so a roughly 22 minute animated episode can fill 44 to 50 pages. Describing visual gags takes space on the page, but those gags play fast, and animated comedy paces quickly. If you write animation and apply a straight one minute per page, you will overestimate the runtime badly. The estimator's animation preset corrects for this by assuming more pages per minute.
How to use the ToolFiddle script runtime estimator
The tool is designed to give a useful answer in a few seconds. Here is the whole process.
- Enter your page count. Use the real page count from your screenplay software, since that already reflects standard formatting. A partial page counts as a partial page, so you can enter something like 97.5 if you want.
- Choose a pace or format. Pick the balanced average, a dialogue heavy or action heavy pace, or a preset for feature, hour long drama, half hour comedy, or animation. This is where the script runtime estimator earns its keep, because it fits the math to your material instead of forcing a single ratio.
- Read your runtime. The tool shows an estimated runtime in minutes and seconds, and it displays a range from a faster to a slower pace so you see the likely spread rather than one deceptively precise figure.
- Adjust and compare. Try a couple of paces to bracket your script, or change the page count to see how trimming ten pages would affect the length. This makes the estimator a quick planning companion during revisions, not just a one time calculation.
Nothing you type is sent anywhere. Your page count and settings live only in your browser while the page is open, which we say more about below.
Worked examples with page counts and minutes
Concrete numbers make the method click, so here are several worked through in full.
A 120 page feature. At the classic one minute per page, that predicts 120 minutes. At the measured average of 55 seconds per page, it is closer to 110 minutes. If it is a dialogue driven comedy at about 50 seconds per page, figure around 100 minutes. If it is an action spectacle at about 68 seconds per page, it could run near 136 minutes. So a realistic range for a 120 page script is roughly 100 to 135 minutes, centered near 110 to 120.
A 100 page script. The rule says 100 minutes. The 55 second average gives about 92 minutes. That gap of eight minutes is exactly the kind of difference the plain rule hides, and it can matter for a tight festival slot or a broadcast window.
A 5 page short film. One minute per page suggests 5 minutes. In practice a dialogue light, atmospheric short might run 6 or 7 minutes, while a fast, talky one could come in under 5. Short scripts swing widely in percentage terms because a single long take or silent beat is a big share of the total.
A 45 page network hour drama. The rule points to 45 minutes, and that matches the roughly 44 minutes of content in a broadcast hour once ads are removed. This is a case where the one to one estimate holds up nicely.
A 32 page single camera sitcom. The rule would say 32 minutes, but the episode likely plays in about 22. Comedy pacing and the half hour slot mean the page count overestimates here, which is why a comedy preset shifts the pace faster.
Real-world ways writers use a runtime estimate
A quick runtime number does more work than it seems, and seeing the uses shows why writers keep the tool close.
Hitting a target length is the main one. If you are aiming for a 100 minute feature or a 22 minute pilot, checking the estimate as you draft tells you if you are on track or drifting long. Catching a bloated act at page 70 is far cheaper than discovering it in an edit bay.
Submitting to festivals and contests often means declaring a runtime or fitting under a cap. A script runtime estimator gives you a defensible number to put on the form and a warning if your short is creeping over the limit.
Pitching and packaging benefit too. Producers and executives think in slots and budgets, both of which connect to runtime. Being able to say your script lands around 105 minutes, and to explain why the action sequences push it there, signals that you understand the craft. Pair the number with a sharp logline and the pitch practically writes itself.
Scheduling and budgeting on the production side lean on the page to minute relationship as well. Page counts drive shooting schedules, and translating them into screen minutes helps everyone picture the finished piece. Even a rough estimate keeps those early conversations grounded.
Tips and common mistakes to avoid
A few habits keep your estimates honest, and a few common errors trip writers up.
- Format the script properly first. The whole rule rests on standard screenplay format, 12 point Courier or its equivalent, standard margins, and standard indentation. If you wrote in a word processor with your own layout, the page count means little, and so does any estimate built on it.
- Match the pace to the content. Applying one minute per page to an action spectacle or an animated comedy will mislead you. Take a moment to size up the pages, mostly talk or mostly motion, and set the pace to suit. This is the difference between a lazy estimate and a useful one.
- Read a range, not a single number. Because only about one in five scripts hits the clean one to one mark, treat the estimate as a window. If the tool says 100 to 112 minutes, plan around that spread rather than fixating on a single figure.
- Do not forget the format you are in. A 45 page hour drama and a 45 page chunk of a feature imply different things, especially on broadcast TV where ad breaks shape the content time. Use the right preset for the medium.
- Remember the estimate is not the final cut. Editing, performance, pacing choices, and reshoots all move the real runtime. The number from a script runtime estimator is a planning figure for the page, not a promise about the finished film.
Formatting that keeps the estimate honest
Since standard format is the foundation of the whole method, it is worth a closer look at what that format actually is. A screenplay page in 12 point Courier holds a specific rhythm. Scene headings, or sluglines, sit at the left margin in capitals. Action description runs the full width in sentence case. Character names sit indented above their lines, and dialogue occupies a narrower center column. Parentheticals tuck in tighter still. Those fixed widths and indents are what make a page a reliable unit of time.
This is also why certain pages estimate poorly on their own. A page that is one long uninterrupted action paragraph reads fast but can play slow. A page of clipped, one word dialogue exchanges has lots of white space and can play faster than its length suggests. Montages, intercut scenes, and oners, those single unbroken shots, all bend the relationship. Over a whole script these tend to average out, which is why the rule works better across 100 pages than across any single one.
If you write in professional screenwriting software, the page count already reflects this format, so your estimate starts on solid ground. If you export to a different layout or paste into another program, the pagination can shift, and with it the runtime estimate. The safest input is the page count your screenwriting app reports, because that is the one the industry rule was calibrated against.
Your script details stay on your device
Everything you enter into the estimator stays with you. When you type a page count and choose a pace, that information is handled by code running inside your own browser and is never sent to a server. There is no upload at any point, nothing is stored, and nothing is logged on our end. An unreleased script is sensitive, and the details of yours are simply not something we can see.
This on device approach is deliberate. Plenty of free tools quietly send what you type to a remote server, sometimes bundled with tracking, just to run a small calculation. Ours does the math locally, so there is nothing to leak and nothing to collect. If you turned off your connection right after the page loaded, the script runtime estimator would keep working exactly the same, which is the clearest sign that your information has nowhere else to go.
Genuinely free, with no sign-up
This tool is free in the plain sense of the word. There is no account to create, no email to hand over, and no payment at any step. You will not hit a wall that asks you to register before it reveals your runtime, and there is no locked premium tier dangling the features that matter, because every feature is already here for everyone.
We point this out because gating simple tools has become common. Some sites collect an email or push a subscription in exchange for a number you could work out with a calculator. We think a runtime estimate should just be available. There are no daily limits either, so check one draft or run a hundred estimates across a rewrite, the tool behaves the same every time.
Instant results with nothing in the way
Because the calculation happens on your device, your runtime appears the instant you enter a page count. There is no spinner while a request travels to a server and back, no queue at busy times, and no drag from the heavy advertising scripts that bog down so many screenwriting sites. The page is deliberately light, so it loads fast even on a modest phone and a slow connection.
That speed is part of the point. You usually want this number in the middle of writing, when a quick answer keeps you in the flow and a slow, cluttered page would pull you out. The estimator gives you a runtime right away, then gets out of the way so you can get back to the script.
Works on every device, even offline
The estimator behaves the same on a phone at a coffee shop, a tablet on the couch, or a laptop at your desk. The layout adjusts to the screen so the input and the result stay large and readable. Once the page has loaded, the calculation no longer needs the internet, so a plane, a train tunnel, or a dead zone will not stop you from estimating a runtime. Nothing depends on a particular brand of browser, as long as it is a reasonably modern one, and there is nothing to install.
Related tools on ToolFiddle
A script is words on pages, and ToolFiddle has light, private tools for the rest of that work. To gauge a spoken word or narration script by length, the Word Counter counts words and characters, which pairs well with a speaking rate for voice over timing. When you rehearse a scene or a table read against your estimate, the Stopwatch times the real performance, and the Countdown Timer helps run a timed reading or a writing sprint. To reformat a title page or slug lines quickly, the Case Converter switches text between upper and lower case. Each keeps your work on your device, just like this tool.
A quick recap
A script runtime estimator converts a screenplay's page count into an estimated screen runtime, starting from the classic one page equals one minute rule and refining it for your material. The measured average across thousands of scripts is closer to 55 seconds per page, dialogue heavy pages run faster while action heavy pages run slower, and format changes everything: features track the rule well, network hour dramas of about 45 pages match their 44 minutes of content, half hour comedies play shorter than their pages, and animation runs closer to two pages per minute. Format your script in standard screenplay layout, match the pace to genre and content, and read the result as a range rather than a single number. The ToolFiddle estimator does the math instantly, keeps your script details private on your device, and stays free with no sign-up.