剧本时长计算器
免费剧本计时器 · 从字数到银幕时间 · 从剧本长度到时长
「一页等于一分钟」这条规则人人都知道，但编剧常常需要一个更精细的估算，把对白密度或动作戏的分量算进去。把这个页面当成免费的剧本计时器：它把你的字数或页数换算成银幕上的分与秒。
粘贴一段剧本，或者填入字数或页数。工具会估算出分钟和秒数的银幕时间。用节奏滑块（慢节奏正剧还是快节奏动作）把估算调得更准。
全部在你的浏览器里运行，没有任何数据被发送到服务器。算法基于字数（每分钟银幕时间约 130 到 150 词）。
慢节奏正剧：每分钟银幕上的词更少。快节奏动作：每分钟的词更多。
这个节奏按每分钟 140 词计算。
工作原理
银幕时间由字数估算得出。行业参考值大约是每分钟 130 到 150 词：对白重或节奏慢的素材偏向每分钟 130 词，动作重或对白干脆的偏向 150 词。滑块让你在两者之间选一个节奏。标准格式下一页剧本通常有 200 到 250 词，所以「一页等于一分钟」正好落在这个区间的中段。
怎么把剧本长度换算成银幕时间
大多数写作者都听过「一页等于一分钟」，然后才发现并非每一页都一样。三页留白很多的对白戏，和三页塞满描写与特技的动作段落，放出来完全不是一回事。一个从剧本长度到时长的计算器，会比单纯数页数给出更接近实际的估算。
估算银幕时间最简单的办法是看字数。一部拍出来的典型长片，大约以每分钟 130 到 150 词的速度推进，其中既有台词也有描写。对白重的正剧或沉静的作者电影接近每分钟 130 词；干脆利落、动作偏重的惊悚片可能靠近 150 词，尤其是当视觉叙事取代了长篇台词的时候。
如果你只知道页数，也能近似推算。很多标准格式的剧本每页在 200 到 250 词之间。一部 105 页的剧本，按每页约 225 词算，大约是 23600 词。按每分钟 140 词计算，接近 168 分钟。上下拖动节奏滑块，就能模拟一部更慢、更靠对白的电影，或者一部更快、剪辑更密的电影。
什么时候用得上时长计算器
- 规划电影节时长和排片档期 短片和电影节报名常有严格的时长限制。你不必只靠页数猜，把剧本粘进来就能看出自己更接近 8 分钟还是 14 分钟，再据此删减。
- 把结构（幕与节拍）对到分钟上 知道自己的中点、进入第三幕或关键反转大概落在第几分钟，能帮你把剧本节奏和常见结构做对比。从字数估出时长之后，你就能把节拍映射到大致的时间点上。
- 向制片和剧组说清预期 制片、执行制片和副导演做预算和排期时需要一个总时长的概念。从字数到银幕时间的估算，是一个快速判断稿子还是那部紧凑的 95 分钟电影、还是正在滑向更贵的 130 分钟的方法。
Script Time Calculator: the complete guide
It converts script words into an estimated runtime window, so you can validate pacing assumptions before table reads or expensive pre-production steps.
For this workflow, the central problem is clear: runtime estimates are often guessed from page count without accounting for dialogue density, pacing, or scene construction. Left unresolved, this creates downstream friction and slower decisions. The practical target is a more realistic runtime range that helps with rewrite decisions, pitch expectations, and production planning.
Limitation to keep in mind: It cannot predict performance timing, edit rhythm, or directorial style exactly, so it should be treated as a calibrated estimate, not a final runtime guarantee.
Advanced workflow: Advanced teams run this per act and per sequence, then compare runtime drift across versions to detect where rewrites are silently inflating duration.
Step-by-Step Workflow
- Paste either a full draft or a representative excerpt, then verify the word count baseline before making structural decisions.
- Set the pace according to your genre and scene style, then compare runtime between conservative and aggressive assumptions.
- Map estimated minutes to your major turns (catalyst, midpoint, all-is-lost) and check if your dramatic rhythm matches intent.
- Re-run after every major rewrite pass and track deltas in a changelog so runtime drift is visible, not accidental.
Use Cases By Profile
- Writer: verify whether second-act expansion is improving story or only adding runtime weight.
- Script editor: benchmark scene compression opportunities without guessing from page count alone.
- Producer: align early runtime expectations with budget and scheduling conversations.
Common Mistakes To Avoid
- Using one static pace value for every genre and every sequence.
- Treating the estimate as final truth instead of a planning signal.
- Ignoring how dialogue-heavy scenes and visual sequences affect real screen time.
Professional Best Practices
- Model best-case, expected, and worst-case runtime scenarios before handing pages to collaborators.
- Use act-level estimates, not only full-draft estimates, when diagnosing pacing.
- Pair runtime checks with beat placement to avoid late structural surprises.
Treat this tool output as a decision support layer, not a replacement for authorship. Great scripts are remembered for specific choices, emotional precision, and clarity of dramatic movement. Tools help by removing noise so your energy can go where it matters: character, conflict, escalation, and payoff. If you review outcomes after each pass and keep an explicit log of accepted changes, your workflow becomes faster and more predictable from draft to draft. That consistency is exactly what professional collaborators value: fewer surprises, clearer rationale, and a script that evolves with intent.
Extended FAQ
How accurate is runtime estimation from words?
It is directionally strong for rewrite and planning decisions, especially when you calibrate pace by genre. Treat it as a decision range, then validate with table reads or rough cuts.
Should I estimate runtime from full draft or sample scenes?
Use full draft for global planning and sample scenes for diagnosing specific pacing problems. Both views are useful and complementary.
Can this help avoid bloated second acts?
Yes. Track estimated minutes by act and compare against intended rhythm. If Act Two inflates repeatedly, trim before line-level polish.
Does page count still matter if I use words?
Yes. Page count is still a shared production language. Word-based estimation adds finer granularity when density varies.
When should producers request runtime checks?
At outline lock, first full draft, and after major structural revisions. Early checks prevent late expensive adjustments.
What is the best workflow with beat tools?
Estimate runtime first, then verify beat timing. Duration and structure should reinforce each other, not conflict.
关于剧本长度、页数、字数和银幕时间的常见问题
不是。「一页等于一分钟」是对标准格式、Courier 12 磅、动作与对白平衡的剧本而言的实用经验法则。实际上，一段无声的追逐或蒙太奇可能比一页密集的独白快得多。字数加上节奏，是更诚实的指标。
拿你的总页数，按每页大约 200 到 250 词估算，然后相乘。再除以一个现实的每分钟词数：慢节奏、对白重的作品用 130，非常干脆、偏视觉叙事的用 150。这个计算器让你粘贴文本或输入字数，再在慢节奏正剧和快节奏动作之间拖动滑块，看时长怎么变。
没有唯一正确的数值，但大多数长片在对白和描写平均之后，落在每分钟 130 到 150 词之间。低于 120 会显得很慢很稀薄，高于 160 通常在纸面和银幕上都显得赶。长镜头、潜台词浓的对白和视觉叙事，都会影响真实的节奏。
不能。剧本时长计算器是用来快速估算和在稿与稿之间做对比的。真正知道故事有多长的唯一办法，是围读、能看的动态分镜或剪辑。这个工具帮你尽早发现极端的时长问题，好在开拍前改稿。
能。无论你写的是 90 到 120 页的长片、10 页的短片还是 30 页的试播集，逻辑都一样。把最终会进剪辑的页面粘进来，在滑块上选一个现实的节奏，从字数到银幕时间的估算就会给你一个合理的成片时长区间。
想要的不止是一个计算器？
ScreenWeaver 是一个增强型的编剧工作环境，让结构、节拍和页面始终同步。用这个免费计算器给你的稿子做个体检，然后走进一个为节奏、改稿和面向制作的剧本而设计的工作空间。
了解 ScreenWeaver
