What a page-based estimate can answer
A screenplay runtime calculator answers a planning question: given the pages you already have, what duration should you allow before rehearsals or editing give you something better? It cannot watch the imagined film. It cannot know how long an actor waits before answering, how quickly a character crosses a room, or whether the director intends a long uninterrupted take. Those decisions become measurements only when somebody performs or stages them. Start with a clear assumption, keep the calculation visible, and replace assumptions when real timings arrive.
The familiar starting point is one minute per properly formatted screenplay page. Final Draft describes that relationship as a rough timing rule, with important exceptions for action. The page count works as a useful shorthand because conventional screenplay layout constrains how much material normally fits on a sheet. It stops being comparable when the font, margins, line spacing, or document type changes. Ninety pages of a novel and ninety pages of a screenplay are different inputs. This tool expects the second kind.
Use the calculator to compare a draft against a target, explain the effect of additional credits, or estimate how much revision may be necessary. Keep the exported result with the draft version it describes. If you change the script, repeat the calculation. A precise-looking number without a matching document is harder to trust than an explicitly rough estimate tied to a named revision. The practical value is the decision the arithmetic supports: rehearse, trim, expand, or change the intended length.
The arithmetic, including the pages that do not play
The calculation begins by subtracting non-story sheets from total document pages. A title page normally belongs in that exclusion. A contact sheet, contents page, or other front matter may belong there too. Count the actual pages in the document rather than relying on the highest printed page number, because screenplay exports sometimes leave the title sheet unnumbered. The total and the exclusion must describe the same file. This calculator requires whole page counts and at least one remaining story page.
Story minutes equal remaining story pages multiplied by your chosen minutes-per-page rate. Separate opening credits and separate closing credits are then added. For an illustrative document containing 101 sheets, one title sheet, a rate of one minute per page, no separate opening sequence, and four minutes of end credits, the result is 100 story minutes plus four credit minutes: 104 minutes altogether. The calculator shows each term so another person can check whether you counted the credits twice.
The target works backward. Subtract separate credits from the target duration, divide by minutes per story page, and round down to a whole-page budget. That rounding is deliberate. If the available time permits 86.7 pages at the selected pace, a budget of 87 whole pages would already exceed it. The output identifies how many current story pages sit above that budget. It does not prescribe which pages to remove, and it does not claim every removed page saves exactly the same screen time.
| Input or result | Meaning | A common mistake |
|---|---|---|
| Total document pages | Every sheet in the current formatted export | Entering the final printed page number instead |
| Non-story pages | Sheets whose text does not become story duration | Subtracting a page that actually contains action |
| Minutes per story page | Your explicit pacing assumption | Treating a default as measured performance |
| Separate credits | Screen time outside action already counted | Adding credits that run over an existing scene |
| Story-page budget | Whole pages supported by the remaining target time | Reading the budget as a rewrite instruction |
Calibrate pace with a timed sample
One minute per page is a starting convention, not a rule that your actors must obey. A better estimate can come from a representative sample. Choose several pages that resemble the rest of the script, perform them at the intended pace, and divide elapsed minutes by the number of pages tested. If ten pages take eleven minutes, enter 1.1 minutes per page. A read-through of ten pages in eight minutes suggests 0.8 for that sample. Neither figure automatically describes every scene.
Use several kinds of material when the screenplay changes rhythm. A quiet confrontation, a chase, and an opening montage may produce very different timings. If you combine samples into one rate, divide their total elapsed minutes by their combined page count. Do not simply average the rates when the samples have unequal lengths. In an illustrative rehearsal, a two-page scene lasting four minutes and an eight-page scene lasting eight minutes produce twelve minutes across ten pages, or 1.2 minutes per page overall.
Record what you timed. Reading action descriptions aloud is not the same as performing the action they describe. A sentence about a long search may be spoken in three seconds yet require a much longer screen sequence. Conversely, a dense action paragraph may describe events that happen almost simultaneously. For a dialogue-heavy scene, the dialogue runtime calculator provides a complementary estimate based on spoken words and pauses. Compare the methods, then investigate disagreements instead of choosing whichever number suits the desired target.
A feature-length planning example
The following feature example is hypothetical, created to demonstrate the calculation rather than to describe a measured production. Suppose an export contains 111 document pages, with one title page. At one minute per story page, the script contributes 110 minutes. Allow three minutes of closing credits and no additional opening sequence. The resulting planning duration is 113 minutes. If the intended slot is 105 minutes, the available story allowance is 102 minutes after subtracting those credits.
At the same rate, 102 minutes supports 102 whole story pages. The current draft contains 110, leaving eight pages above the target. That result gives the writer a starting scale for revision. It does not mean deleting the last eight pages, compressing the font, or removing the scenes with the least dialogue. A useful revision pass identifies scenes that repeat information, entrances that begin too early, and endings that continue after the dramatic turn has already occurred. Preserve the cause-and-effect chain that makes the story understandable.
Now test a faster pace of 0.9 minutes per page, while keeping the same pages and credits. The story estimate becomes 99 minutes, and the total becomes 102. The screenplay fits the 105-minute target under that assumption. This is why the pace must come from an intended performance or a representative rehearsal. Changing an input to make the result fit is different from learning that the existing material actually plays more quickly. Keep both scenarios until a timed sample gives you evidence for one.
Working with a short-film limit
For a short, title cards and credits can consume a substantial fraction of the available time. An illustrative ten-minute project might contain eight story pages and one title page in its document. If the pages play at 1.1 minutes each, the story takes 8.8 minutes. One minute of separate closing credits brings the total to 9.8 minutes. The whole-page budget is eight because nine available story minutes divided by 1.1 gives approximately 8.18. Eight fits; nine does not.
A six-page story at the same pace would take 6.6 minutes, or 7.6 including that credit allowance. The unused time is not an instruction to add a speech. A short can end before a maximum. Decide whether the current length serves the story, the screening requirements, and the audience. Some submission rules distinguish total runtime from other measurements, so check the actual rules of the destination you intend to use. The calculator has no live connection to festival or platform requirements.
The short film length checker serves a different stage: comparing a duration with a chosen limit. Use that after you know or estimate the total length. This calculator starts earlier, with pages and a pace. Once an edited export exists, its measured duration is the stronger input for delivery planning. Do not keep substituting a page-based guess for a video file that already tells you precisely how long the finished piece runs.
Treat credits as a scheduling choice
Only add credit time that occurs outside the scripted duration. If an opening scene lasts two minutes and the credits appear over that scene, those two minutes are already part of the story estimate. Adding them again would inflate the total. If a separate title sequence appears before the story begins, enter its independent duration. The same principle applies to end credits that begin over the final scene and continue after it: count only the portion that extends beyond the time already budgeted.
A written title sheet is not an on-screen title card. Subtracting the document’s title page removes a sheet from the page model; it does not add or remove a second of actual film. If an on-screen title occupies separate time, account for that in the opening allowance or in the screenplay itself. Choose one method and record it. The calculator cannot inspect your layout or decide which headings describe actual footage, so clear bookkeeping remains part of using it well.
If credits alone fill or exceed the target, the output explicitly warns that revising the story cannot solve the stated timing plan. For instance, two opening minutes and three closing minutes already exceed a four-minute target before any action plays. Change the target or the credit plan before cutting scenes. The page budget becomes zero in this situation. That is an arithmetic boundary, not a suggestion to produce a film with no story. It identifies conflicting inputs that need a human decision.
Compare sensitivity without inventing confidence
The results include three scenarios: your selected pace, a page duration twenty percent shorter, and one twenty percent longer. These are deliberate arithmetic comparisons. They are not statistical confidence intervals, predicted probabilities, or results derived from a database of finished films. The choice of twenty percent simply makes the effect of pace visible. Separate credit allowances remain fixed in every row, because changing the speed of story performance does not automatically shorten a credit sequence.
For an illustrative ninety-page story at one minute per page with three closing minutes, the central result is 93 minutes. The faster scenario uses 0.8 minutes per page, giving 72 story minutes and 75 total. The slower scenario uses 1.2, giving 108 story minutes and 111 total. The spread is intentionally obvious. It helps a team recognize that an unverified rate can dominate the decision. It does not promise the finished film will fall somewhere between those outer results.
A measured sample can still be unrepresentative. Timing only a rapid argument and applying that pace to a contemplative film will underestimate other scenes. Timing only the longest monologue may do the opposite. Rehearse material from different parts of the script and note any sequences that need separate treatment. If the project requires a more detailed model, work scene by scene outside this calculator and sum the measured or staged durations. The whole-script model remains useful as a quick independent cross-check.
Formatting changes can distort the input
Page count depends on layout. Smaller type, narrower margins, and tighter line spacing can reduce the number of sheets without removing any dramatic material. That changes the calculator’s input while leaving the intended performance largely unchanged. It is therefore a poor way to solve a runtime problem. Export from the screenplay editor using the intended format, keep those settings stable between revisions, and evaluate story changes separately from cosmetic pagination changes. Consistent inputs make the resulting comparisons more meaningful.
The screenplay format checker can help inspect the structure of pasted script text, but it is not a substitute for viewing the final formatted file. The page-based runtime tool does not parse PDFs, identify margins, or validate font size. It accepts the page totals you supply. If a collaborator provides an export made with different settings, establish a common format before comparing its count with an earlier draft. Otherwise the apparent improvement may come entirely from document layout.
Fractional occupancy is another source of uncertainty. A final sheet with only a few lines still counts as a whole document page here. The inputs deliberately use whole pages so the page budget stays easy to understand. For a very short script, that rounding can matter proportionally more than it would for a feature. Refine the minutes-per-page rate using a timed sample or use the dialogue timer for a closer look at a specific exchange. Do not interpret the displayed decimals as proof that the source estimate has matching precision.
Action, silence and simultaneous events
A screenplay can describe a long interval in a short sentence. A character waiting at a station, a ship crossing an ocean, or a search continuing through the night might occupy little paper. The screen duration depends on how the sequence is staged and edited. Conversely, a densely described visual event can occur in seconds. The one-page convention works best as an aggregate planning shortcut, and unusual sequences should be reviewed individually before a team commits to a tightly constrained delivery duration.
Silence is also material. A pause may carry a reaction, reveal a changed relationship, or make the next line believable. Cutting every pause to fit a mathematical target can damage the scene the screenplay is trying to create. If rehearsal consistently takes longer than the page model, examine whether those pauses are deliberate and necessary. Then revise the estimate or the scene. A timing discrepancy is information about the intended film, not automatically an error by the actor, writer, or calculator.
Simultaneous action requires the opposite caution. Two characters can cross a room while a third speaks; the film does not necessarily need the sum of all three actions considered separately. A read-through that narrates each description one after another may overstate that interval. When precision matters, stage the sequence or create an animatic with the intended overlap. This calculator cannot model blocking, parallel dialogue, overlapping transitions, or editorial rhythm. It supplies a transparent page-based starting estimate against which those better measurements can be compared.
Use the result to guide a revision meeting
Bring three items to the conversation: the exact script revision, the timing assumptions, and the target the team is trying to meet. The downloadable result preserves the numerical inputs in the formula note, along with the calculated page budget and scenarios. It does not contain the screenplay itself. Add a draft name and date in your own project notes so a later reader can connect the estimate to the right document. That small habit prevents teams from comparing unrelated versions as if they were equivalent.
If the estimate runs long, identify the source of the overrun before rewriting. A longer credit allowance, a more deliberate performance, and extra scenes require different decisions. Separate fixed time from story time, then compare the same pace across drafts. A change from 100 to 95 story pages at an unchanged rate represents a different kind of revision from changing the assumed pace from 1.0 to 0.95. Both can reduce the displayed result, but only one necessarily reflects fewer pages of dramatic material.
If the estimate fits, retain a verification step. A passing result means the entered model fits the entered target. It is not a production guarantee. Read the script aloud, time important action sequences, and eventually compare the assembled edit with the original estimate. Record the difference to improve the next project’s assumptions. BookWriter’s free filmmaking course walks through the progression from a small story to a script, a shot plan, and a short film you can actually review.
Choose the right tool for the material you have
Use the book-to-film runtime estimator when the source is a prose manuscript and you are considering adaptation scope. A novel’s word count does not directly become screenplay pages without creative decisions. The adaptation may combine characters, omit subplots, move an internal thought into visible action, or expand a brief passage into a full scene. This screenplay calculator begins after those choices have produced a formatted script. It deliberately does not provide a second prose-to-film conversion disguised under a different title.
Use the dialogue runtime calculator when the material is a particular exchange of spoken words. Its speaking-rate and pause controls address a narrower question than whole-script pagination. Use the storyboard shot list generator when you need to plan coverage. A screenplay page is not a shot count, and a scene may require multiple camera views even when it occupies little paper. Keeping these tasks separate gives each calculation an input that actually matches the question it answers.
For a complete project, screenplay and film plans connect the writing stage with character and shot planning. Read the product page to see what the currently available plan includes and what you make yourself. A free calculator does not produce a complete adaptation or finished video. Its role is to make one planning decision clearer before you invest effort in the larger project. You can copy or download the result without creating an account, then continue with whichever workflow fits your film.
Input checks and practical boundaries
The form accepts up to 5,000 total document pages, excludes fewer non-story pages than the total, and allows a pace from 0.1 to 10 minutes per story page. Those broad bounds prevent invalid arithmetic without pretending that every allowed combination is typical filmmaking practice. Separate opening and closing allowances each run from zero to 120 minutes. Targets run from one to 1,000 minutes. An out-of-range value needs correction; it is not quietly replaced with a convenient default.
A blank numeric field is also invalid. It should not silently become zero, especially for a pace or target that controls the rest of the calculation. If you clear a field, enter a valid replacement and calculate again. Editing an input removes the previous interactive output so you are not left looking at a result derived from earlier numbers. The server-rendered examples below the tool remain illustrative demonstrations with their own stated inputs; they do not change to match your form.
The calculation itself runs in your browser. Tool-use events can record the tool name and completed interaction, but the runtime event does not include your entered numbers or script content. Copy creates plain text, and download saves a text file through your browser. Neither action creates a saved BookWriter project. Keep any result you want before closing the tab. If the tool’s code fails to load, the retry control attempts to load it again while preserving the values already entered in the form.
Sources and a repeatable verification routine
The timing convention is grounded in Final Draft’s explanation of the one-page timing rule. Its screenplay formatting guide explains the layout context behind screenplay pages. These sources support the convention and formatting distinction; the adjustable pace, credit allowance, whole-page budget and sensitivity rows are this calculator’s explicit planning model. None of those controls should be mistaken for measurements supplied by the source documents.
To check a result independently, write the six inputs on paper, subtract non-story pages, multiply by the selected rate, and add separate credits. For the budget, remove those same credits from the target, divide by the rate, and round down. Compare the steps with the formula note and metrics. If the values disagree, first check whether credits overlap action or whether the total includes unnumbered sheets. Those bookkeeping mistakes can change an apparently straightforward result without anything being wrong with multiplication or division.
Finally, compare the planning estimate with a representative performance, then with the assembled film when it exists. The strongest use of a calculator is a repeatable process that becomes better informed over time. Keep assumptions visible, label invented examples as examples, and allow measured evidence to replace the initial convention. That produces a runtime estimate the writer and production team can discuss clearly, revise consistently, and use for the next concrete decision.