Goethe Write
EN

Fountain vs FDX: which should you write your screenplay in?

Fountain vs FDX is rarely an either-or. Most screenplays end up in both at some point. The real question is which one you draft in, and how the script crosses from one to the other.

By Goethe Write Team · Published · 7 min read · Formats

Two formats, two jobs

If you want to know what the two formats are, our guide to screenplay file formats explains them in detail. Here is the short version. Fountain is a way of writing a screenplay in plain text: a few conventions tell a program which line is a scene heading, which is a character and which is dialogue. It was created by the screenwriter John August and the filmmaker Stu Maschwitz, and its rules are published at fountain.io. FDX is the file format of Final Draft: XML that stores every paragraph with its element type, plus the title page, the page layout, scene numbers, revisions and more.

So the formats are not rivals. Fountain is built for writing. FDX is built for carrying a script through a production. The decision this article helps with is a practical one: where does the draft live while you are writing it?

When drafting in Fountain makes sense

Fountain's strength is that it is just text. That has consequences that matter day to day.

Any editor, any device

A .fountain file opens in every text editor on every system. You can draft on a laptop, fix a line on a phone in a notes app and continue on another computer, without a particular program installed. If an app disappears, your script does not.

Version control that actually works

Because each line is a line of text, tools such as Git can show exactly what changed between two drafts: this speech was shortened, that scene heading was renamed. For writers who already use version control – or for teams that keep scripts alongside other text in a repository – this is the single biggest reason to draft in Fountain.

Writing without formatting

In Fountain you type INT. KITCHEN - NIGHT and the next line in capitals becomes a character. Many writers find that this keeps them in the words. There are no element menus, no margins to look at, only the text.

Long-term archiving

A plain text file is about as durable as a digital format gets. Many writers keep a Fountain copy of every finished draft next to the PDF, so the words can be opened decades from now.

When drafting in FDX makes sense

FDX carries more than words, and that is exactly what a production relies on.

The production speaks Final Draft

Many production offices, studios and co-writers work in Final Draft. When someone says "send me the script file", they usually mean an .fdx. If your draft is heading there anyway, writing in an app that reads and writes FDX saves a conversion step at the worst possible moment.

Pages that must not move

A screenplay page stands for roughly a minute of screen time, and once a script is in production, page and scene numbers become addresses: the schedule, the budget and the call sheets point to them. FDX stores the page layout and scene numbers, so the same file shows the same pages to everyone using the same program.

Revisions in colour

In production, changes come in rounds, each with its own page colour and a mark in the margin – blue pages, pink pages and so on. Fountain carries the words and their structure, but not revision colours. If you are rewriting a shooting script, you need a format that keeps them, and that is FDX.

Title page, notes and everything else

FDX also holds the title page, script notes and the SmartType lists of names and locations. A Fountain file can carry title page fields too, but much of what a production adds to a script has no place in plain text.

A decision table

Your situationDraft inHand over as
Writing alone, early drafts, any deviceFountainPDF to readers
You keep drafts in Git or another version control systemFountainFDX or PDF when asked
Co-writing with someone who uses Final DraftFDXFDX
The script is in pre-production or productionFDXFDX and PDF
Submitting to an agent, a contest or a festivalEitherPDF
Archiving a finished draftBothPDF and Fountain

The pattern is simple: the earlier and more personal the draft, the more Fountain fits; the closer the script gets to a production, the more FDX takes over. Readers – agents, contests, actors, financiers – almost always want a PDF, whatever you write in.

Working across both

Most writers do not stay in one format for the life of a script. A common path is Fountain for the first drafts, FDX once a producer or co-writer is involved, and PDF for everyone who only reads. The crossings are where things go wrong, so it pays to handle them deliberately.

Convert once, at a clear point

Converting back and forth after every session is how scripts lose small things: a forced scene heading, a centred line, a note. Pick a moment – the draft goes to a producer, a co-writer joins – and make that the point where the master copy changes format. After that, work in the new one.

Check three things after every round trip

When a script moves from one program or format to another, compare the page count, the scene numbers and the revision marks before and after. If any of them changed, the two sides disagree about the format, and it is better to know now than on the day of the table read.

Keep notes where they survive

Fountain notes in double brackets do not print, and not every program treats them the same way on import. Before an important conversion, look at the notes you care about and make sure they arrived.

Name the master copy

Whatever you choose, make it obvious which file is current. A file name with the draft and the date – Harbour_Draft3_2026-11-13.fdx – prevents the classic mistake of two people revising two different files.

Collaboration changes the answer

Writing alone, you can choose purely by taste. Writing with others, the format is part of the agreement. Two writers who both use Git may happily share a Fountain file. A writing team that works with a production office will usually settle on FDX, because that is where scene numbers and revision rounds live. If you are not sure, ask early what your collaborators and the production use, and draft in a tool that can hand them exactly that.

For the formatting conventions that both formats encode, see our guide to screenplay format; for the specific layout of television scripts, see how to format a TV pilot.

How Goethe Write helps

Goethe Write is built so that the Fountain vs FDX choice does not lock you in:

See screenwriting in Goethe Write and import and export. Goethe Write for the Mac is on the Mac App Store, at US$79.99 once with 14 days free; the companion app for iPhone and iPad, which also opens and saves FDX and Fountain, is free.