Fountain Format vs .fdx Files: Screenplay Formats Explained

TL;DR. Fountain and .fdx solve the same problem — storing a screenplay in a file — from opposite philosophies. Fountain is an open, plain-text markup syntax: human-readable, editor-agnostic, version-control friendly, and free forever. .fdx is Final Draft's XML document format: richer, more structured, and the de facto delivery standard in Hollywood production pipelines. You don't have to pick a side. Write in the format your software prefers, archive in Fountain, and convert to .fdx at the moment a pipeline demands it.

If you have ever emailed a script and gotten back "can you send that as a Final Draft file?", or opened a .fountain attachment and seen what looked like plain notes instead of a screenplay, this guide is for you. We'll cover what each format actually is, how Fountain's syntax works (with real examples), why .fdx occupies the position it does in the industry, when to use which, how to convert between them, and which major screenwriting editors support what.

The Two Philosophies of Screenplay Files

Every screenplay file format has to answer one question: how do you mark that a line is a scene heading and not a character name?

There are two honest answers.

Answer one: infer it from the text itself. A line that starts with INT. or EXT. is obviously a scene heading. A line in ALL CAPS followed by an indented-looking line of speech is obviously a character cue and dialogue. This is Fountain's answer — encode screenplay structure in conventions writers already use, so the file stays ordinary readable text.

Answer two: label every element explicitly. Wrap each paragraph in a tag that says what it is — <Paragraph Type="Scene Heading"> — so no software ever has to guess. This is the .fdx answer, and XML is the natural container for it.

Both answers are correct. They just optimize for different things: Fountain for portability and longevity, .fdx for structural precision and pipeline interchange. Everything else in this article follows from that split.

What Is Fountain Format?

Fountain is a plain-text markup syntax for screenplays, released in 2012 by screenwriter John August (Big Fish, Charlie's Angels) and filmmaker Stu Maschwitz, who merged their two earlier projects (Scrippets/Screenplay Markdown) into a single open specification. The design goal, stated on the official spec, is that a Fountain file should be readable as a screenplay even by someone who has never heard of Fountain.

A .fountain file is nothing but UTF-8 text. That single fact carries most of the format's benefits:

• Any editor opens it. Notepad, VS Code, iA Writer, your phone's notes app.
• It survives software death. A binary format from 2005 may be unreadable today; a text file from 1985 still opens.
• It diffs. Git, or any version-control system, shows you exactly which lines changed between drafts — something binary and XML formats do poorly.
• It's free and open. No license, no vendor, no lock-in. The spec is public at fountain.io.

Fountain Syntax by Example

Here is a complete, valid Fountain scene. Paste this into any Fountain-aware application and it renders as a correctly formatted screenplay page:

INT. COFFEE SHOP - DAY

MAYA, 30s, wired on her third espresso, stares at a
laptop screen full of red revision marks.

The door chimes. DANIEL enters, shaking rain off
his jacket.

DANIEL
Tell me you fixed the second act.

MAYA
(not looking up)
I fixed the second act.

DANIEL
Now tell me without lying.

She closes the laptop. Beat.

MAYA
The second act fixed me.

CUT TO:

Notice there is no markup visible at all — that's the point. The structure comes from conventions:

• INT. COFFEE SHOP - DAY begins with INT., so it's a scene heading.
• DANIEL is an uppercase line followed immediately by text, so it's a character cue, and what follows is dialogue.
• (not looking up) sits inside a dialogue block wrapped in parentheses, so it's a parenthetical.
• CUT TO: is uppercase and ends with TO:, so it's a transition.
• Everything else is action.

Forcing Elements

When the automatic rules guess wrong, Fountain provides one-character overrides:

.MONTAGE - MAYA'S REWRITE WEEK

!BANG! The printer jams again.

@McCONAUGHEY
(mixed-case character name, forced with @)
Alright, alright, alright.

> FADE TO BLACK.

• A leading . forces a scene heading (useful for headings that don't start with INT/EXT, like MONTAGE).
• A leading ! forces action (useful when an action line is all-caps and would otherwise read as a character cue).
• A leading @ forces a character name that contains lowercase letters.
• A leading > forces a transition (or centers text if it also ends with <).

Notes, Boneyard, and Title Pages

Fountain also handles the writing-process layer — the stuff that must never print:

Title: THE REWRITE
Credit: Written by
Author: Maya Chen
Draft date: 7/5/2026

[[This note appears in the editor but never in output.]]

/*
Everything in the boneyard is omitted entirely —
dead scenes you can't bring yourself to delete.
*/

Notes in [[double brackets]] and boneyard text in /* comment blocks */ are preserved in the file but excluded from formatted output. The title page is a block of Key: Value lines at the top of the document.

Fountain Syntax Quick Reference

That table is essentially the whole language. A working screenwriter can learn Fountain in fifteen minutes, because ninety percent of it is how screenwriters already type.

What Is a .fdx File?

A .fdx file is the native document format of Final Draft, the screenwriting application that has dominated professional film and television for over three decades. The extension stands for Final Draft XML: introduced with Final Draft 8 in 2009, it replaced the old binary .fdr format with a structured, text-inspectable XML document.

Where Fountain infers structure, .fdx declares it. Here is roughly what the coffee-shop scene looks like inside a .fdx file:

<FinalDraft DocumentType="Script" Template="No" Version="5">
  <Content>
    <Paragraph Type="Scene Heading">
      <Text>INT. COFFEE SHOP - DAY</Text>
    </Paragraph>
    <Paragraph Type="Action">
      <Text>The door chimes. DANIEL enters, shaking rain off his jacket.</Text>
    </Paragraph>
    <Paragraph Type="Character">
      <Text>DANIEL</Text>
    </Paragraph>
    <Paragraph Type="Dialogue">
      <Text>Tell me you fixed the second act.</Text>
    </Paragraph>
  </Content>
</FinalDraft>

Every paragraph carries an explicit Type. Beyond the visible script content, a real .fdx also stores things Fountain deliberately leaves out of scope:

• Revision tracking — colored revision pages (blue, pink, yellow...) and per-line revision marks, which production drafts depend on.
• Page-layout settings — margins, element indents, fonts, header/footer content, locked page numbers.
• Scene metadata — scene numbers, omitted-scene records, ScriptNotes.
• Title page as a structured object rather than a text block.

Why .fdx Is the Industry Standard

The honest, unromantic reason: Final Draft got there first and production infrastructure grew around it. Scheduling software, budgeting software, breakdown tools, coverage systems, and studio archival pipelines all accept .fdx as canonical input. Agencies expect it. Union and studio delivery requirements frequently name it. When a script moves from writer to line producer to first AD, .fdx is the container it usually travels in — a point covered in depth in our Final Draft vs Laper head-to-head comparison.

This is a network effect, not a technical verdict. XML with explicit types is a perfectly good design, but .fdx's position comes from three decades of adoption, not from being unbeatable engineering. That distinction matters when you decide what to write in, because it means the constraint is about delivery, not drafting.

There is one more practical property worth naming: .fdx is a vendor-defined format. Final Draft, Inc. controls it. Other applications read and write it through reverse-engineered compatibility, which is very good in 2026 but not guaranteed by any open specification. Fountain is the opposite — an open spec nobody owns. That asymmetry is exactly why the archival advice later in this article says what it says.

Fountain vs .fdx: The Practical Differences

Read that table with one caveat: it compares file formats, not writing experiences. Almost nobody hand-types raw Fountain in Notepad all day or hand-edits XML; you write in an editor that gives you live formatting either way. The format question is really about what happens to your script between and after editors — sharing, converting, archiving, delivering.

When to Use Fountain

Use Fountain when portability outranks production machinery.

• Drafting anywhere. A .fountain file follows you from a desktop editor to a phone text editor to a plain terminal without ever losing content. No app, no problem.
• Version control. If you keep drafts in git — increasingly common for writer-programmers and writing teams with technical habits — Fountain is the only screenplay format that produces meaningful diffs. You can see, line by line, what changed between draft 4 and draft 5.
• Long-term archives. Twenty years from now, the safest bet for a readable script file is plain text. Export your finished drafts to Fountain and every future version of every future tool will open them.
• Interchange between mismatched editors. When writer A's app and writer B's app don't share a native format, Fountain is the lingua franca both almost certainly read.
• Automation and tooling. Because it's plain text, Fountain is trivially scriptable — generating sides, extracting character line counts, feeding analysis pipelines — with nothing more exotic than a text parser.

Fountain's honest limitations: no revision stars, no colored pages, no locked page numbers. The moment a project enters physical production and the AD department starts issuing colored revision pages, Fountain stops being sufficient as the working format.

When to Use .fdx

Use .fdx when the pipeline demands it.

• Contractual delivery. If a studio, network, or agency contract specifies file delivery, it will almost certainly name Final Draft format. Deliver .fdx. This is not a fight worth having.
• Active production. Locked pages, revision colors, scene omissions, and production-draft conventions live natively in .fdx and in the software built around it.
• Handing off to departments. Scheduling and breakdown tools ingest .fdx cleanly. Sending a Fountain file to a line producer in 2026 mostly means they'll convert it to .fdx themselves and mutter about it.
• Collaborating with Final Draft users. If your co-writer lives in Final Draft, round-tripping through their native format loses the least.

The corollary: if none of those describe your current phase — you're drafting, rewriting, getting notes — the .fdx requirement is not yet real, and you can write in whatever environment makes you fastest, converting later. For a full treatment of margins, element indents, and everything else that makes a screenplay page look right regardless of file format, see our screenplay format guide.

Converting Between Fountain and .fdx

The good news: for standard screenplay content — scene headings, action, dialogue, parentheticals, transitions — conversion in both directions is fast, free, and effectively lossless. The formats describe the same underlying structure; only the encoding differs.

Fountain → .fdx

1. Highland (Mac). John August's own editor is Fountain-native: open the .fountain file, then export to Final Draft. This is the lowest-friction path and the one we recommend to Laper users who need a .fdx deliverable today.
2. afterwriting (free, open source). A web app and command-line tool that converts Fountain to FDX and PDF. The CLI version makes it scriptable — useful if you batch-convert or automate deliveries.
3. screenplain (free, open source). A Python-based converter that reads Fountain and writes FDX or HTML. Solid choice for anyone comfortable with a terminal.
4. Any editor that reads Fountain and writes .fdx — WriterDuet and Fade In both do — works as an interactive converter: import, inspect, export.

.fdx → Fountain

Highland, Fade In, and WriterDuet all import .fdx and export Fountain or plain text. Final Draft itself can also open Fountain files, so the round trip is well-trodden in both directions.

What to Check After Any Conversion

Conversion is lossless for the core elements, but three areas deserve a thirty-second review:

• Dual dialogue — expressed differently in each format; verify side-by-side blocks survived.
• Notes and boneyard — Fountain notes may become ScriptNotes, be preserved as text, or be dropped, depending on the tool.
• Revision metadata — Fountain has no concept of revision colors, so converting a production .fdx to Fountain strips revision marks by definition. Keep the .fdx as the production record.

Editor Support Matrix: Who Reads and Writes What

Here is where the major screenwriting editors stand on the two formats in 2026. "Native" means the format is the application's primary document type.

Two practical readings of this table:

If your world is Fountain-first — you draft in plain text, keep scripts in git, or move between many tools — Highland is the purest environment, and WriterDuet and Fade In are the most flexible bridges.

If your world ends in .fdx — studio delivery, production drafts — Final Draft is the destination format's home, and every other tool on this list can get your script there, natively or through the Fountain conversion path described above.

Where Laper Fits

Laper treats the screenplay itself — not the file — as the source of truth. You write in a real-time collaborative editor where scene headings automatically derive your scene list, character cues derive your character roster, and locations derive from headings; the AI reads the full script as context. On the format side, honestly stated: Laper exports PDF (industry-standard pagination) and Fountain today; direct .fdx import is on the roadmap. Bringing in a Final Draft script currently means pasting the text (the editor auto-detects scene headings, characters, and locations — expect a few minutes of cleanup on a feature), and producing a .fdx deliverable means exporting Fountain and converting with Highland or an open-source tool. The Junior tier is free with no credit card, and paid plans are listed on the pricing page — so testing whether the Fountain-based workflow covers your delivery needs costs nothing.

The Workflow That Uses Both

After all the comparison, here is the format strategy we'd actually recommend to a working screenwriter in 2026:

1. Draft in the editor that makes you fastest. The file format of your drafting phase is an implementation detail; your words per productive hour are not.
2. Archive every finished draft as Fountain. Plain text is the only format guaranteed to outlive every application on the support matrix above. One export per milestone draft, kept alongside the PDF.
3. Deliver PDF for reading. Contests, managers, first reads — nearly all of them want a locked, paginated PDF, not an editable file.
4. Produce .fdx when — and only when — a pipeline names it. Contract delivery, production handoff, a Final Draft-native collaborator. At that moment, export or convert. Until that moment, it's a requirement you don't have yet.

Fountain and .fdx are not rivals so much as two ends of a script's life: Fountain is how a screenplay stays yours — readable, portable, permanent — and .fdx is how it enters the industrial machine that turns it into a schedule, a budget, and eventually a call sheet. Learn the fifteen minutes of Fountain syntax, know your conversion path, and the format question stops being a source of anxiety and becomes what it should have been all along: a checkbox at export time.