Free screenplay converter
Fountain to FDX Converter
Plain text to a Final Draft file, free
Convert a Fountain screenplay into a Final Draft .fdx file that opens in Final Draft, Fade In, WriterDuet, Celtx, Arc Studio and ScreenWeaver. Every element is typed, emphasis and scene numbers are kept, dual dialogue is paired, and the title page is built. Free, in your browser, no upload.
- Private: your script never leaves this browser tab.
- Free, no signup, no watermark.
- Industry layout kept: scene headings, cues, dialogue, (MORE) and (CONT'D).
Private by design: the conversion runs in this tab and nothing is uploaded.
How it works
The converter parses the full Fountain syntax (title page, natural and forced elements, dual dialogue, emphasis, sections, synopses, notes, page breaks) and writes each element as a typed Final Draft paragraph with its style runs. Scene numbers go into the Number attribute, dual dialogue into a DualDialogue block, sections and synopses into Final Draft's outline elements, page breaks into StartsNewPage. The document carries the standard element settings, so Final Draft opens it with the usual margins.
Every screenplay format, both ways
Any format in the left column converts to PDF, Final Draft, Fountain, Word or plain text. Apps without a writable format here all open FDX or Fountain.
| Format | Reads | Writes |
|---|---|---|
| Final Draft (.fdx) | ||
| Fountain (.fountain) | ||
| Word (.docx) | ||
| Fade In (.fadein) | Use FDX, which it opens | |
| Highland (.highland) | Use Fountain, which it opens | |
| Celtx (.celtx) | Use FDX, which it opens | |
| WriterDuet (.wdz, .json) | Use FDX, which it opens | |
| Trelby (.trelby) | Use FDX, which it opens | |
| Text (.txt) |
From Fountain to Final Draft for production
Writing in Fountain is fast, but production runs on Final Draft. Agents, producers, script coordinators and breakdown tools ask for an .fdx. Converting Fountain to FDX hands them a file where every scene heading, cue and line of dialogue is already typed, so revisions, scene numbering and reports work from day one.
The quality of the conversion shows in the details: a cue with an extension like (V.O.) stays one element, forced scene headings keep their type, a speech marked with ^ becomes real dual dialogue, and bold or underlined words stay styled. That is what this converter checks, element by element.
Prefer to review it first? The preview shows the script paginated exactly as the PDF would print, and the same page also writes PDF and Word.
Who uses it
- Highland, Beat and text editor writers: deliver the .fdx a producer or agency asks for.
- Writers joining a writers' room: bring drafts into the room's Final Draft workflow.
- Production: import a Fountain script into scheduling and breakdown software that reads FDX.
Stop fixing margins.Formatting is built in.
ScreenWeaver handles industry-standard formatting and exports to PDF and Final Draft (.fdx). Free, with unlimited pages.
- $0, does not expire
- PDF and Final Draft export
- Mac, Windows, Linux, iPad
Fountain to FDX Converter: the complete guide
It parses the full Fountain syntax and writes each element as a typed Final Draft paragraph with style runs, scene numbers in the Number attribute, dual dialogue blocks, outline elements, page breaks and Final Draft's standard element settings.
For this workflow, the central problem is clear: production runs on Final Draft files, and a Fountain script imported carelessly loses cues, dual dialogue or emphasis. Left unresolved, this creates downstream friction and slower decisions. The practical target is a Final Draft file with every element typed, styling, scene numbers and dual dialogue kept, and a proper title page.
Limitation to keep in mind: Fountain notes have no visible equivalent in the FDX and are left out; lyrics become italic action because Final Draft's default template has no lyrics element.
Advanced workflow: Writers keep the Fountain file as the master in Git and generate the FDX on delivery, so the production copy always matches a tagged draft.
Step-by-Step Workflow
- Paste the Fountain or drop the file.
- Check the title page and the scene and character counts.
- Choose the scene number option.
- Download the .fdx and open it in Final Draft.
Use Cases By Profile
- Writer: deliver the .fdx a producer or agency asks for.
- Writers' room member: bring a draft into the room's Final Draft workflow.
- Production: import a Fountain script into software that reads FDX.
Common Mistakes To Avoid
- Importing Fountain into an app that ignores forced elements and dual dialogue.
- Sending an FDX without a title page.
- Leaving scene numbers off a shooting script.
Professional Best Practices
- Number scenes only when production asks for it.
- Use the element view to confirm cues and headings before delivery.
- Keep the Fountain source: convert again after every rewrite.
Treat this tool output as a decision support layer, not a replacement for authorship. Great scripts are remembered for specific choices, emotional precision, and clarity of dramatic movement. Tools help by removing noise so your energy can go where it matters: character, conflict, escalation, and payoff. If you review outcomes after each pass and keep an explicit log of accepted changes, your workflow becomes faster and more predictable from draft to draft. That consistency is exactly what professional collaborators value: fewer surprises, clearer rationale, and a script that evolves with intent.
Extended FAQ
Will Final Draft open the file?
Yes. The FDX carries Final Draft's standard element settings and typed paragraphs.
Is dual dialogue kept?
Yes. A speech marked with ^ becomes a DualDialogue block in the FDX.
Are bold and italic kept?
Yes. Fountain's **bold**, *italic* and _underline_ become styled text in Final Draft.
Which other apps open the FDX?
Fade In, WriterDuet, Celtx, Arc Studio, Highland and ScreenWeaver.
Is my script uploaded?
No. It is converted inside your browser tab.