A "line" in a stage script is any string of characters terminated by a line break, so counting lines in a play means tallying every line of dialogue, stage direction, scene heading, and blank separator the file contains, then breaking the total down into meaningful categories such as non-blank and whitespace-only lines. The fastest way to get that breakdown for a complete script is a browser-based Line Counter that shows total, non-blank, blank, and longest-line counts side by side the moment you paste your text, with no upload step and no account to create.
Writers and producers ask this question for several practical reasons. A dramaturg may want to know whether a new draft is still within the running-time window the director set. A festival reader needs a quick estimate of how dense a one-act is before deciding whether to read it in full. A translator checking page rate wants to compare a translated version against the source line count. A student formatting a class assignment wants the dialogue-line count to put in a cover page. In every case, the same raw operation applies: paste the script, read the four counters, and decide what the numbers mean for the task at hand.
Why a Line Counter Beats Counting by Hand for Scripts
Stage scripts are unusually hard to count by eye. They mix dialogue, parentheticals, character cues on their own line, scene transitions, and dense blocks of stage directions, often separated by single blank lines that exist purely to make the page readable. A two-act play in standard format can easily contain several thousand lines once you include every blank line between scenes, and the difference between "total lines" and "non-blank lines" is meaningful because the blank-line padding is part of what makes the script readable on stage.
Manual counting is also prone to miscounts around soft line wraps. When a long stage direction is wrapped in your word processor to fit a printed page, the on-screen display shows two lines, but the underlying text file may still be a single line. The Line Counter reports the underlying line structure, which is the number that matches any command-line tool and the number you would quote in a production meeting. Working from the displayed wrap is the most common reason a hand count disagrees with a tool count.
What the Four Counters Actually Mean
Before you paste anything in, it helps to know what each counter represents so you can pick the right one for the question you are trying to answer.
| Counter | What it counts | Typical use for a play |
|---|---|---|
| Total lines | Every line break in the file, including blank lines | Page-rate quotes, file-size sanity checks |
| Non-blank lines | Lines containing at least one visible character | Dialogue plus stage-direction totals |
| Blank or whitespace-only lines | Lines made up entirely of spaces, tabs, or nothing | Verifying scene spacing or removing padding |
| Longest line | The single line with the most Unicode code points | Spotting unusually wrapped stage directions |
If a festival submission asks for "lines of text excluding blank lines," the non-blank figure is the one to submit. If a tool such as wc -l on a Linux machine gave you a number yesterday, that number corresponds to total lines on the Line Counter, because wc -l counts newline characters.
How to Count Lines in a Play
- Open the Line Counter in your browser. No file is uploaded and no account is needed.
- Copy the full script from your word processor or plain-text editor. Use "Copy" rather than "Copy with formatting" so hidden styling does not affect the count.
- Paste the text into the editor on the Line Counter page. The counters update as you paste, so no submit or upload button is required.
- Read the four results: total lines, non-blank lines, blank or whitespace-only lines, and the length of the longest line in code points.
- Compare the total with the newline rules listed on the page if the result looks off. Different line endings (LF, CRLF, or CR) and trailing newlines can change the total by one or two lines.
- Copy the number you need and paste it into your production note, submission form, or class cover page.
Counting Lines for Plays on Specific Platforms
If your script lives in a word processor rather than a plain-text file, the workflow changes slightly because rich formatting can hide the true line structure.
From Microsoft Word or Google Docs
Open your play in Word or Google Docs, press Ctrl+A to select everything, then copy with Ctrl+C. Paste directly into the Line Counter editor. The tool strips formatting during paste and counts only the underlying characters and line breaks. If your document uses soft line wraps to fit a printed page, those soft wraps disappear on paste and the count drops to the true logical lines, which is what you want for any script-length comparison.
From a Plain-Text File
Open the .txt or .md file in Notepad, TextEdit in plain-text mode, or VS Code, select all, and paste into the Line Counter. Plain-text files are the cleanest source because there is no formatting layer between you and the line breaks.
From a PDF
PDFs do not store real line breaks the way text files do, so a PDF page can report a different number than the script's logical lines. Open the PDF in a PDF reader, choose "Copy" or "Export text," and paste the result. If the export introduces extra hard breaks at the end of every printed line, the count will reflect those breaks rather than the script's logical lines, in which case a re-export with "preserve layout" turned off is usually closer to the truth.
Understanding Newline Rules and Unicode Behavior
The Line Counter follows standard Unicode rules for line breaks, which is why its result matches editors and command-line tools more often than a hand count does. The most common reason two tools disagree on a script's line count is the difference between LF (Unix), CRLF (Windows), and CR (classic Mac) line endings. A single script saved on Windows and then read on a Mac without conversion will sometimes show one extra blank line at the end of the file because both the carriage return and the line feed are interpreted as a single break plus a stray character.
Trailing newlines are another frequent source of mismatch. Most editors add a final newline at the end of a file by convention, which can change "total lines" by exactly one compared with a tool that strips the trailing break. The Line Counter states its rule for trailing whitespace on the page, so read that note when comparing numbers across tools.
Longest-line counts are reported in Unicode code points, which means every visible character, mark, and combining sequence counts once. For most English-language scripts this behaves like a character count, but for scripts with accented letters, emoji stage directions, or non-Latin character names, the code-point figure can differ from a simple byte length. If you need a character count alongside the line count, the Character Counter handles that side of the analysis.
Using the Counts in Real Play-Production Decisions
Once you have the four numbers, the question becomes what they mean for the work in front of you. A one-act play that lands between roughly 1,500 and 2,500 non-blank lines is usually a comfortable 45 to 60 minutes in performance, though exact running time depends on dialogue density and the number of stage-direction pauses the director calls. A full-length two-act script that runs more than 4,000 non-blank lines may need cuts before the next workshop.
The blank-line count is also useful for cleanup. A script with an unusually high proportion of blank lines (say, more than one blank line for every five non-blank lines) often signals double-spaced scene breaks that a director will want tightened for the rehearsal draft. If you need to act on that, the Whitespace Remover and the Remove Empty Lines tool let you collapse or strip those blank lines in a controlled way.
For festival submissions that ask for a precise line count in the cover page, the safest number to quote is total lines from a known plain-text source, taken with the same tool you used during drafting. Submitting the non-blank figure instead is reasonable if the festival defines "lines" as visible content; otherwise stick with total lines to match the most common command-line interpretation. Whichever number you choose, write the tool name and the date alongside it so a reviewer can reproduce the count.
Frequently Seen Questions About Counting Lines in a Play
Two practical questions come up often. The first is whether soft wraps count. They do not, because they are a display feature rather than a line break in the file. The second is whether a line with only a character cue such as "HAMLET." should be counted as a line. By the standard definition used here, yes, it counts as one non-blank line because it contains a visible character. If your festival defines a "line of dialogue" differently and excludes character cues, subtract the number of character-cue lines manually or filter them with the Remove Empty Lines approach followed by hand filtering.
For scripts you would rather not paste anywhere online, the entire operation runs locally in the browser, so the text never leaves your machine. That makes the Line Counter suitable for unpublished drafts, contest submissions under embargo, and licensed translations that you are not free to share.
If you want a deeper dive into related text operations, the guide on counting lines in a file in Linux without command-line hassle explains how the same idea works in a terminal environment, and the guide on counting lines in a file covers the differences you will see between LF, CRLF, and CR endings. For other playwright-side formatting tasks, the reverse text without breaking emoji guide is handy when a director asks for reversed character cues in a prompt-side script.
Related reading: How to Random List in Python Without Writing Code.