Screenplay format

Screenplays follow a standard format — a specific layout of scene headings, action, character names, and dialogue. It's not arbitrary: format makes a script readable, professional, and timeable (~1 page ≈ 1 minute), and signals you know the craft. This lesson covers the core elements and how they go on the page, so your work looks right and reads cleanly. Good news: software does the layout — you just need to know the elements. Let's format like a pro. Let's learn the standard layout.

The core elements

STANDARD SCREENPLAY ELEMENTS (Courier 12pt, ~1 page = ~1 minute):

INT. COFFEE SHOP - DAY                        <- SCENE HEADING (slugline)

Maya sits alone by the window, a cold coffee     <- ACTION (present tense, visual,
in front of her. The door chimes. She looks up.     lean; describes what we see)

                    MAYA                        <- CHARACTER (name, centered, caps)
          (checking her watch)                  <- PARENTHETICAL (brief; how/what
     You're late.                                   they do while speaking)
                                                <- DIALOGUE (what they say)

               SAM
     Traffic. Sorry.

Sam drops into the seat across from her.         <- ACTION again

- SCENE HEADING / SLUGLINE: INT. (interior) or EXT. (exterior) + LOCATION + TIME
  (DAY/NIGHT). Starts every scene; tells us WHERE + WHEN.
- ACTION: present-tense description of what we see/hear.
- CHARACTER: the speaker's name (caps), centered, above their dialogue.
- DIALOGUE: what they say. PARENTHETICAL (wryly): brief acting/action note — use
  sparingly.
- TRANSITIONS (CUT TO:, etc.) — mostly unnecessary; the cut is implied.

A screenplay is built from a small set of standard elements, laid out a specific way (traditionally Courier 12pt, which is why a page ≈ a minute). The scene heading (slugline) starts every scene: INT. (interior) or EXT. (exterior), the location, and the time (DAY/NIGHT) — e.g. INT. COFFEE SHOP - DAY — telling us where and when. Action is present-tense description of what we see and hear, kept visual and lean. When someone speaks, their character name goes in caps, centered, above the dialogue (what they say); a brief parenthetical — (checking her watch) — can note how they say it or a small action, but is used sparingly. Transitions like CUT TO: are mostly unnecessary (the cut is implied by the next scene heading). That's essentially the whole vocabulary — headings, action, character, dialogue, the occasional parenthetical — arranged in a consistent layout so any reader can instantly parse who's speaking, where we are, and what's happening.

Formatting habits and tools

FORMATTING THAT READS WELL:

- USE SOFTWARE — it handles ALL the spacing/margins/indents automatically. You
  just pick the element type (heading/action/character/dialogue) + type. Free
  tools: Fade In (trial), Celtx, WriterDuet, StudioBinder, or Fountain (a plain-
  text format) + a converter. (Final Draft is the paid industry standard.)
- ONE SCENE = ONE SLUGLINE. New location or time (INT->EXT, DAY->NIGHT) = new scene
  heading.
- KEEP ACTION LEAN — short paragraphs (1-4 lines), lots of white space. Break big
  chunks up. CAPS a character's name on FIRST appearance in action; caps important
  SOUNDS/props sparingly for emphasis.
- DON'T over-direct — write the story, not the shots. Avoid camera directions
  (CLOSE ON, PAN) unless essential; let the director direct. Convey emphasis
  through the WRITING, not shot calls.
- PARENTHETICALS + TRANSITIONS: minimal. Trust the dialogue + the cut.
- TITLE PAGE: title, "written by", your contact. Number scenes only for a shooting
  script, not a spec.

THE PRINCIPLE: correct, clean format makes your script readable + professional +
timeable. Learn the elements; let software do the layout; keep it lean.

The reassuring part: software does the layout for you — you just choose the element type (heading, action, character, dialogue) and type, and it handles all the spacing, margins, and indents. Free tools include Celtx, WriterDuet, StudioBinder, and the Fountain plain-text format (with a converter); Final Draft is the paid industry standard. A few habits keep it clean: one scene = one slugline (a new location or time means a new heading); keep action lean (short 1–4 line paragraphs, lots of white space, CAPS a character's name on first appearance and important sounds/props sparingly for emphasis); and crucially, don't over-direct — write the story, not the shots, avoiding camera directions (CLOSE ON, PAN) unless essential, because that's the director's job (convey emphasis through the writing, not shot calls). Keep parentheticals and transitions minimal — trust the dialogue and the cut. And put a simple title page (title, "written by," your contact), numbering scenes only for a shooting script, not a spec. The principle: correct, clean format makes your script readable, professional, and timeable — so learn the elements, let software do the layout, and keep it lean.

The mistake beginners make

The first mistake is ignoring standard format — inventing a layout, so the script looks unprofessional and hard to read (and breaks the page-per-minute timing); use screenwriting software and the standard elements. The second mistake is over-directing with camera shots — filling the page with CLOSE ON, PAN, ZOOM, which isn't your job and clutters the read; write the story, let the director choose shots. The third mistake is dense action + overused parentheticals/transitions — thick description, a parenthetical on every line, CUT TO: everywhere; keep action lean and use parentheticals/transitions sparingly. And wrong scene headings — missing INT./EXT./time or not starting a new scene at a new location; slug every scene correctly. Use standard format via software, don't over-direct, keep action lean with minimal parentheticals, and slug scenes correctly.

Your turn

---

Your turn

1. Set up a tool: open a free screenwriting app (Celtx, WriterDuet, StudioBinder) or use the Fountain format, so the layout is handled and you just pick element types and type.
2. Format a scene: write one short scene with a correct scene heading (INT./EXT. + LOCATION - DAY/NIGHT), a few lines of lean present-tense action, and a short dialogue exchange with centered character names.
3. Slug it right: give a two-location moment two scene headings (e.g. INT. then EXT.), confirming each new location/time starts a new slugline.
4. Resist over-directing: write a dramatic beat WITHOUT any camera directions (no CLOSE ON/PAN), conveying the emphasis through the action writing and dialogue instead.
5. Trim the clutter: take a scene and cut unnecessary parentheticals and transitions (CUT TO:), trusting the dialogue and the implied cut — and break any dense action into short paragraphs.

Key points

• Standard screenplay elements (Courier 12pt, ~1 page = ~1 minute): SCENE HEADING/slugline (INT./EXT. + LOCATION + DAY/NIGHT — starts every scene), ACTION (present-tense, visual, lean description of what we see/hear), CHARACTER (name in caps, centered, above dialogue), DIALOGUE, and the occasional brief PARENTHETICAL.
• Software does the layout — pick the element type and type; free tools: Celtx, WriterDuet, StudioBinder, Fountain (plain-text) + converter (Final Draft is the paid standard). You just need to know the elements.
• Habits: one scene = one slugline (new location/time = new heading), keep action lean (short 1-4 line paragraphs + white space; CAPS a name on first appearance + key sounds sparingly), minimal parentheticals + transitions (trust the dialogue + the implied cut).
• DON'T over-direct: write the story, not the shots — avoid camera directions (CLOSE ON, PAN, ZOOM) unless essential; let the director direct, and convey emphasis through the writing. A simple title page (title / 'written by' / contact); number scenes only for a shooting script.
• The mistakes: ignoring standard format (unprofessional, unreadable, breaks timing), over-directing with camera shots (not your job, clutters), dense action + overused parentheticals/transitions, and wrong/missing scene headings.