Skip to main content
Inkwell uses Fountain, a plain-text screenplay format that converts your typing into industry-standard screenplay layout. This guide covers all Fountain elements and how Inkwell interprets them.

​
What is Fountain?

Fountain is a markup language for screenwriting. Instead of clicking buttons to format elements, you write naturally and Fountain converts your text into proper screenplay format. Benefits:
  • Write without interrupting your flow
  • Plain text is future-proof and version-control friendly
  • Works across any device or text editor
  • Industry-standard output (identical to Final Draft)
Inkwell auto-formats as you type. You rarely need to think about Fountain syntax—just write naturally.

​
Scene headings

Scene headings (also called slug lines) establish location and time of day.

​
Auto-detection

Inkwell recognizes scene headings automatically when a line starts with:
  • INT. (interior)
  • EXT. (exterior)
  • INT./EXT. (combined)
  • I/E (shorthand)
Example: 
INT. COFFEE SHOP - DAY

EXT. CITY STREET - NIGHT

INT./EXT. CAR - CONTINUOUS
Result: Scene headings appear in BOLD ALL CAPS with proper spacing above and below.

​
Force a scene heading

If Inkwell doesn’t auto-detect your scene heading, force it by starting the line with a period (.): 
.FLASHBACK - 1985
This is useful for non-standard headings like flashbacks, montages, or dream sequences.
Scene headings always appear in ALL CAPS. Type them in any case—Inkwell converts them automatically.

​
Action lines

Action lines (also called description) describe what we see on screen. They’re the default element—any regular paragraph becomes action. Example: 
Alice enters the coffee shop, scanning the crowded room. She spots Bob at a corner table.

Bob doesn't look up from his phone.
Result: Action uses standard sentence case and is left-aligned.

​
Best practices

  • Keep it visual: Describe what the camera sees, not what characters think
  • Short paragraphs: Break long action into 2-3 line chunks for readability
  • Present tense: “Alice walks” not “Alice walked”
  • Active voice: “Bob throws the ball” not “The ball is thrown by Bob”

​
Character names

Character names introduce dialogue. Type them in ALL CAPS on their own line. Example: 
ALICE
I wasn't sure you'd come.

BOB
I almost didn't.
Result: Character names are centered and appear in ALL CAPS.

​
Character extensions

Add extensions in parentheses after the character name: 
ALICE (V.O.)
I should have seen it coming.

BOB (O.S.)
Alice! Wait!
Common extensions:
  • (V.O.): Voice-over (character’s internal thoughts or narration)
  • (O.S.): Off-screen (character is present but not visible)
  • (CONT'D): Continued (character keeps speaking after an action line)
  • (PRE-LAP): Dialogue begins before the scene starts
  • (FILTERED): Voice over phone, radio, etc.

​
Character auto-complete

Once you’ve used a character name, Inkwell remembers it. Start typing the first few letters and press Tab to auto-complete. Example: Type AL + Tab → ALICE

​
Dialogue

Dialogue is what characters say. Type it directly below a character name. Example: 
ALICE
We need to talk about what happened.

BOB
There's nothing to talk about.
Result: Dialogue is indented and appears below the character name.

​
Multi-line dialogue

Keep typing—Inkwell handles line breaks automatically: 
ALICE
I know you think I betrayed you, but that's not what happened. I was trying to protect you. You have to believe me.
Press Enter twice to end the dialogue and return to action.

​
Parentheticals

Parentheticals (also called wrylies) are brief actor directions inserted in dialogue. Wrap them in parentheses on their own line. Example: 
ALICE
(nervous)
I wasn't sure you'd come.

BOB
(not looking up)
I almost didn't.
Result: Parentheticals appear indented between character name and dialogue.

​
When to use parentheticals

  • Actor direction: (angry), (whispers), (sarcastic)
  • Brief action: (stands), (checks watch)
  • Tone: (defensive), (joking)
Use sparingly. Over-directing actors with parentheticals is considered poor form. Only include them when the delivery isn’t obvious from context.

​
Dual dialogue

Dual dialogue shows two characters speaking simultaneously, with their dialogue appearing side-by-side on the page. This is used for overlapping speech or interruptions.

​
How to create dual dialogue

Add a caret (^) after the second character’s name: Example: 
ALICE
I didn't do it!

BOB ^
Yes, you did!
Result: The dialogue blocks appear side-by-side:
  • Alice’s dialogue on the left
  • Bob’s dialogue on the right
  • Both at the same vertical position

​
The trailing caret syntax

The ^ must be:
  • After the character name (with a space): BOB ^
  • Not before: ^ BOB won’t work
  • On the second speaker: The first character is normal, the second gets the ^
Step-by-step:
  1. Write the first character’s dialogue normally
  2. Add a blank line
  3. Type the second character’s name + space + ^
  4. Write the second character’s dialogue

​
Multiple lines of dual dialogue

Each character can have multiple lines, including parentheticals: 
ALICE
I'm telling you—

BOB ^
(interrupting)
No, you're not listening!
Both blocks will align side-by-side with their parentheticals intact.

​
When to use dual dialogue

Good uses:
  • Overlapping arguments: Two characters talking over each other
  • Phone conversations: Both sides of a call shown simultaneously
  • Interruptions: One character cutting off another
  • Comedic timing: Simultaneous reactions or realizations
  • Chaotic scenes: Multiple people speaking at once
Avoid for:
  • Alternating dialogue: If they’re taking turns, use normal dialogue
  • Long speeches: Dual dialogue is hard to read if either block is more than 2-3 lines
  • Clarity: If it confuses the reader, break it into sequential dialogue

​
Dual dialogue examples

Argument (overlapping): 
ALICE
You never listen to me!

BOB ^
That's not true!
Phone call (both sides): 
ALICE
(on phone)
Where are you?

BOB ^
(on phone)
Stuck in traffic!
Simultaneous realization: 
ALICE
Wait... you're the—

BOB ^
You're the one who—
Dual dialogue is rare in professional screenplays. Use it sparingly for maximum impact. If you find yourself using it frequently, consider whether sequential dialogue would be clearer.
Dual dialogue can be confusing to read. Make sure both blocks are short (2-3 lines max) and the overlap serves the story. When in doubt, use regular back-and-forth dialogue.

​
Transitions

Transitions indicate how one scene moves to the next. Type them in ALL CAPS, right-aligned. Example: 
CUT TO:

FADE OUT.

DISSOLVE TO:
Auto-detection: Inkwell recognizes common transitions like CUT TO:, FADE IN:, FADE OUT., and DISSOLVE TO:.

​
Force a transition

If your transition isn’t auto-detected, force it with a greater-than symbol (>): 
> TIME CUT:
Modern screenplays use transitions sparingly. Only include them when the cut method is crucial to the story.

​
Centered text

Center any text by wrapping it with > and <: Example: 
> THE END <

> TEN YEARS LATER <
Result: Text appears centered on the page. Use cases:
  • Chapter titles or act markers
  • “THE END” cards
  • Montage or dream sequence headers

​
Sections and synopses

​
Sections

Sections organize your script into acts, sequences, or chapters. Start a line with one or more # symbols: Example: 
# ACT ONE

## Opening Sequence

### Scene Group A
Result: Sections appear in the Navigation panel as a hierarchical outline. They don’t appear in the final PDF export. Usage:
  • # = Top-level (Acts)
  • ## = Second-level (Sequences)
  • ### = Third-level (Scene groups)

​
Synopses

Synopses are brief scene summaries. Start a line with =: Example: 
= Alice confronts Bob about the missing money

INT. COFFEE SHOP - DAY
Result: Synopses appear in the Navigation panel next to scenes but don’t print in the PDF.
Use synopses as mini beat sheets. They help you track story structure without cluttering your script.

​
Inline notes

Notes are personal reminders or production notes. Wrap them in double brackets: Example: 
[[ TODO: Research 1980s coffee shop decor ]]

[[ Note: Bob's motivation unclear here—revisit in rewrite ]]
Result: Notes appear in the Navigation panel and can be hidden in exports. They’re visible in the editor but don’t print by default. Use cases:
  • Script notes during development
  • Production notes for crew
  • Revision reminders
  • Research to-dos

​
Rich text styling

Inkwell supports bold, italic, and underline for emphasis.

​
Bold

Wrap text in double asterisks or use Cmd/Ctrl+B: Example: 
**BANG!** The door slams shut.

She sees the **MYSTERIOUS FIGURE** in the doorway.
When to use:
  • Sound effects (**BANG**, **CRASH**)
  • First character introductions
  • Emphasizing important objects

​
Italic

Wrap text in single asterisks or use Cmd/Ctrl+I: Example: 
She *remembers* the conversation clearly now.

*Flashback music intensifies.*
When to use:
  • Emphasis in dialogue (use sparingly)
  • Foreign words or titles
  • Internal thoughts (though V.O. is preferred)

​
Underline

Wrap text in underscores or use Cmd/Ctrl+U: Example: 
The sign reads _EMPLOYEES ONLY_.
When to use:
  • Very rare in modern screenplays
  • Sometimes used for signs or text on screen
Use formatting sparingly. Over-styled scripts look amateurish. Let your words carry the emphasis.

​
Scene numbers

Scene numbers are used in production for tracking shots and scheduling.

​
Auto-number scenes

Go to Screenplay → Number Scenes to automatically number all scene headings. Example before: 
INT. COFFEE SHOP - DAY
Example after: 
1   INT. COFFEE SHOP - DAY   1

​
Manual scene numbers

Add custom scene numbers by wrapping them in #: Example: 
#42# INT. COFFEE SHOP - DAY

​
Clear scene numbers

Remove all scene numbers with Screenplay → Clear Scene Numbers.
Scene numbers are added during production. Don’t include them in spec scripts or early drafts.

​
Title pages

Title pages are stored separately in Script Info (Project Panel → Script Info tab). Inkwell auto-generates a properly formatted title page when you export to PDF. Required fields:
  • Title: Your screenplay name
  • Written by: Your name
  • Contact: Email or representation
Learn more about Script Info →

​
Page breaks

Inkwell automatically handles page breaks following industry standards:
  • 1 page ≈ 1 minute of screen time
  • Dialogue never splits across pages (actor-friendly formatting)
  • MORE/CONT’D markers appear when dialogue continues across pages
You don’t need to manually insert page breaks—Inkwell handles this in the PDF export.

​
Common formatting questions

Not really! Inkwell auto-detects most elements. Just write naturally and the editor formats it correctly. The forcing characters (. for scenes, > for transitions, etc.) are for edge cases.
Inkwell only supports Fountain syntax. Manual formatting (like tabs or multiple spaces) won’t work. Trust the auto-formatting—it follows industry standards.
Use forcing characters to override auto-detection. For example, if action is mistaken for a character name, you can’t force it, but you can rephrase. Most issues resolve by following Fountain conventions.
Yes! Export your script as Fountain (.fountain) from the File menu. This shows the plain-text markup behind the formatted view.
Inkwell supports all standard Fountain elements. Experimental or non-standard extensions may not work. Stick to the elements in this guide for best results.

​
Practice exercise

Write a short scene (5-10 lines) that includes:
  1. A scene heading
  2. Action description
  3. Two characters
  4. One parenthetical
  5. One bold sound effect
Example: 
INT. LIBRARY - NIGHT

Sarah tiptoes through the dark stacks. **CREAK.** She freezes.

SARAH
(whispers)
Who's there?

VOICE (O.S.)
You shouldn't have come here.
Preview your scene with Cmd/Ctrl+P to see the formatted PDF output.
You now understand all core Fountain elements! Keep writing and refer back as needed.

​
Next steps

Navigation & productivity

Speed up your writing with shortcuts and navigation tools

Revisions

Track changes with revision marks and colors

Project Panel

Organize sections, characters, and script metadata

Export your script

Save as PDF, Fountain, or Final Draft format