FDX and Fountain: screenplay file formats explained
A screenplay travels: from the writer to the producer, from the first draft to the production office. Three file formats carry most of that traffic. Here is what each one is for.
Final Draft (.fdx)
Final Draft saves screenplays as .fdx files. Inside, an FDX file is XML: plain text with tags, which other programs can read. Each paragraph carries its element type – scene heading, action, character, parenthetical, dialogue, transition, shot – together with the text and its formatting.
Besides the script itself, an FDX file holds much of what a production relies on:
- the title page;
- the page layout and the settings for each element;
- the SmartType lists – the character names, locations, times of day and transitions that the program suggests while you type;
- scene numbers and revisions, with their marks and page colours;
- script notes and other information from the writer.
Because so many productions work with Final Draft, .fdx is the format to send when someone says “send me the script file”. If you use another program, make sure it reads and writes FDX without losing what it doesn’t show.
Fountain (.fountain)
Fountain is a way of writing a screenplay in plain text. It was created by the screenwriter John August and the filmmaker Stu Maschwitz, and its rules are published openly at fountain.io. A few simple conventions tell the program which element a line is:
| You type | It becomes |
|---|---|
A line starting with INT. or EXT. | Scene heading |
| A line in capitals, followed by text on the next line | Character and dialogue |
| A line in parentheses under a character | Parenthetical |
A line in capitals ending in TO: | Transition |
| Any other paragraph | Action |
. at the start of a line | Forces a scene heading |
@ at the start of a line | Forces a character name |
> at the start of a line | Forces a transition |
[[ and ]] around text | A note that does not print |
Here is a short scene in Fountain:
EXT. HARBOUR - DAWN
Fog over the water. LENA (30s) walks the empty pier.
LENA
(to herself)
Forty-eight thousand. For fog.
CUT TO:
Fountain files open in any text editor, on any system, and they work well with version control such as Git. They carry the words and their structure, but not everything a production needs, such as revision colours.
A PDF shows the pages exactly as they are printed. Send a PDF when someone is going to read the script: agents, contests, actors, financiers. It cannot be edited, and every reader sees the same page breaks. Send FDX when someone is going to work on the script.
Which one to use
| Situation | Format |
|---|---|
| Submitting to an agent, a contest or a festival | |
| Handing the script to a production or a co-writer who uses Final Draft | FDX |
| Writing in a text editor, or keeping drafts in Git | Fountain |
| Keeping a copy that opens in decades | PDF and Fountain |
Moving between apps without losing anything
Whenever a script moves from one program to another, check three things after the first round trip: the page count, the scene numbers and the revision marks. If any of them changed, the two programs disagree about the format.
Goethe Write opens and saves both FDX and Fountain. Paragraphs you did not change are written back exactly as they came in, so a script can go from Final Draft to Goethe Write and back. Its pages break the way Final Draft 13 breaks them, so the page count stays the same. See import and export in Goethe Write.