How to Edit an FDX File Without Final Draft (and Send It Back)

You can edit an FDX file without Final Draft by importing it into a screenwriting app that reads and writes the format, such as Zen Writer on iPhone, iPad, Mac or Android, editing it as a normal screenplay, and exporting FDX back so the producer gets their format returned. Viewing is easy anywhere; editing safely means never touching the XML by hand.

Updated 2026-09-22 · About 8 sections · 5 answered questions

Can you edit an FDX file without Final Draft?

Yes. An .fdx is plain XML, and Final Draft has no lock on it. Any app that understands the element types inside the file can open it, let you rewrite, and save a new FDX that Final Draft opens as if it had written the file itself. Zen Writer does this on iPhone, iPad, Mac and Android; several desktop apps do it too.

What you cannot do is treat the file as a text document and hope. The words live inside XML tags whose attributes carry all the formatting, and a text editor will happily let you break them. The rest of this page is about doing the job in a way that gives the producer back a file that works, which is a different problem from simply opening one. If you only need to read the script, how to open an FDX file covers the free routes, and what is an FDX file explains the XML you are about to avoid touching.

Viewing vs editing an FDX: why the difference matters

There are three levels of access to an FDX, and people get into trouble by using the wrong one.

Level	What you use	What you get	Risk
Viewing	Browser FDX viewer, PDF export	The script laid out correctly, read-only	None. You cannot change anything.
Editing the text	Notepad, TextEdit, any code editor	The raw XML, fully writable	High. One broken tag and the file will not open anywhere.
Editing the screenplay	An app that imports and exports FDX	A normal screenplay editor that writes valid FDX on export	Low. Element types travel with the text automatically.

Here is the same dialogue block at the second and third levels. In a text editor:

<Paragraph Type="Character">
  <Text>MARA</Text>
</Paragraph>
<Paragraph Type="Dialogue">
  <Text>Tell him the tide chart is wrong.</Text>
</Paragraph>

In a screenplay editor:

                    MARA
          Tell him the tide chart is wrong.

Change the sentence in the text editor and you are fine. Add a second speech, and you must type both <Paragraph> wrappers, get the case of Dialogue exactly right, and escape any ampersand as &. In the screenplay editor you press Enter and type. That is the whole argument.

Round-tripping: how the producer gets their FDX back

A round trip is import, edit, export. The FDX arrives, you work on it in your own software, and an FDX leaves. The producer opens it in Final Draft and sees a normal script with your changes. Done properly, they never need to know what you used.

Import the .fdx. The app parses the XML and turns each tagged paragraph into the matching screenplay element.
Edit as you would any script. Automatic formatting means element types are never something you touch by hand.
Export FDX. The app writes fresh XML with the correct Type on every paragraph, balanced tags and proper escaping.
Check the export by opening it in the browser viewer before you send it. Thirty seconds, and it catches a truncated file or a missing title page.

What makes this safe is that you never edit the markup, so the three things hand-editing breaks most often (element types, tag balance, character-name consistency) are handled by software. Zen Writer collects the character list automatically, so a renamed character is caught by search rather than discovered by the producer.

The round trip also protects the producer's workflow. If you send back a PDF or a Word file, someone has to rebuild the FDX from the PDF, and that conversion guesses at element types. Sending FDX means nothing has to be reconstructed.

What can break in an FDX round trip

The core of a screenplay survives any competent round trip: scene headings, action, character cues, parentheticals, dialogue and transitions. The Final Draft-specific extras are where apps differ, and you should know which ones matter to the person receiving the file.

Feature	Survives?	What to do
Scene heading, action, character, parenthetical, dialogue, transition	Yes, everywhere	Nothing.
Bold, italic, underline	Usually	Spot-check a styled line after export.
Title page	Usually	Check it is present and centred in the exported file.
Scene numbers	Often, but may be renumbered	If the script is locked and numbered, tell the coordinator you edited outside Final Draft.
Revision marks and coloured revision sets	Rarely	Do not round-trip a script in active production revisions. Send changes as notes or let the coordinator apply them.
Script notes	Rarely	Copy any notes you need out of the file before you import.
Dual dialogue	Depends on the app	Check every dual-dialogue passage after export; it may come back as two ordinary speeches.
Custom element settings and page layout	Reset to the app's defaults	Page count may shift by a page or two. Check it in the PDF, not the editor.

The practical rule: a spec script or a development draft round-trips cleanly. A shooting script in the middle of coloured revisions does not belong outside Final Draft, because the revision data is exactly what the production is tracking. Ask before you edit one.

Step by step: edit an FDX on iPhone or iPad

Save the .fdx to the Files app from Mail, Messages, AirDrop or a download.
Press and hold the file, tap Share, and choose Zen Writer. The script opens fully formatted.
Edit. Smart Enter moves from a character cue to dialogue and from dialogue back to action, so the formatting looks after itself. Use the scene navigator to jump between scenes and search to find every line that needs the same change.
Check script statistics for the effect on page count and estimated runtime before you send.
Export FDX, then share it straight back from the export sheet by Mail, Messages or AirDrop.

Everything above works offline and without an account, so a rewrite on a train is not a problem. The free tier is one screenplay with watermarked exports, which is enough to test the round trip on a real draft; Pro removes the watermark and the one-script limit. Device-specific detail lives in opening an FDX on iPhone and opening an FDX on iPad. The Android flow through Google Files and Drive is the same three steps: opening an FDX on Android.

Step by step: edit an FDX on Mac

Right-click the .fdx in Finder, choose Open With, and pick Zen Writer for Mac. Or drag the file onto the app window.
Rewrite with a full keyboard. The character list, full-script search and the scene navigator are the tools for a structural pass.
Export FDX to a folder you control, and keep the original file beside it. Never overwrite the file the producer sent.
Open the export in the free FDX viewer to confirm it renders, then send it.

The Mac has one trap the other platforms do not: TextEdit. If you open a working FDX in TextEdit to look at it and save, TextEdit can rewrite the encoding declaration and Final Draft will refuse the file. Look in the viewer instead. The Mac guide lists the other Finder and Quick Look pitfalls.

Alternatives: Fountain, desktop apps and careful text editing

Three other ways to get the job done, each with a cost.

The Fountain detour. Convert the FDX to Fountain with the free FDX to Fountain converter, edit the plain text in any editor on any device, then convert Fountain back to FDX. Fountain marks elements with conventions rather than tags, so a scene heading is any line starting INT. or EXT., and a character cue is a line in caps above a speech. Revision marks and script notes are dropped; dual dialogue and scene numbers depend on the converter. Fine for a spec, wrong for a production draft.

Other desktop apps. Fade In, Highland, WriterDuet, Arc Studio, KIT Scenarist and Trelby all import FDX and most export it. Check how each handles dual dialogue and notes before you trust it with a whole script. The Final Draft alternatives roundup covers platforms and pricing models.

Careful text editing. If the change is one word, a text editor can work. Edit only what is inside <Text>, keep a copy of the original, save as UTF-8 with no byte-order mark, and never touch a Type attribute or a RevisionID. The moment the edit adds, moves or splits a paragraph, stop and use an app.

Mistakes that break the file or the relationship

Sending back a PDF. The producer asked for an FDX because their pipeline runs on it. A PDF costs them a conversion and a day.
Round-tripping a script in coloured revisions. Revision data is what the production tracks. Send notes instead, or ask.
Overwriting the original. Export to a new file. If anything went wrong, the original is your only fallback; there is no FDX repair tool.
Renaming a character in one place. Use search and change every cue. The character list shows you whether the old name is still in the script.
Trusting the editor's page count for a page-limited submission. Pagination is recomputed per app. Check it in the exported PDF.
Sending a watermarked export as a deliverable. Watermarks are fine for a look and wrong for a submission.

The reason FDX exists is to move a screenplay between tools without losing its structure. An app that imports and exports it does that by design. Everything else in the FDX guide follows from that.

Frequently asked questions

Can I edit an FDX file in Notepad or TextEdit?

Technically, because FDX is XML text. Changing words inside a Text element works if you are careful, but element types, paragraph tags and revision IDs are easy to break, and a file with one unbalanced tag will not open in any screenplay app. Use an app that imports and exports FDX instead.

Will a producer be able to tell I did not use Final Draft?

Not from a clean round trip. An exported FDX with correct element types opens in Final Draft like any other script. The tell-tales are lost dual dialogue, missing script notes or reset revision marks, so check those before sending if the original contained them.

What do I lose if I convert FDX to Fountain to edit it?

Revision marks and script notes are dropped, and dual dialogue, scene numbers and title-page alignment depend on how well the converter and your editor handle the equivalent Fountain syntax. Scene headings, action, dialogue, parentheticals and transitions come through reliably.

Can I edit a Final Draft file on my phone?

Yes. Zen Writer imports FDX on iPhone and Android, formats every element as you type, and exports FDX back out. Save the file to Files or Downloads, share it to the app, edit, and export. It works offline and needs no account.

What happens if I break an FDX file while editing?

It stops being valid XML, so Final Draft and every other app report an invalid document and refuse to open it. There is no repair tool and no partial import, which is why you should always keep the original file untouched and export edits to a new one.

Ready to turn this idea into a screenplay?

Zen Writer imports an FDX, lets you rewrite it as a properly formatted screenplay with Smart Enter and a scene navigator, and exports a valid FDX straight back.

Edit an FDX in Zen Writer

Free on iPhone, iPad, Mac and Android.

Continue reading

FDX & Final Draft Files

How to Edit an FDX File Without Final Draft (and Send It Back)

Can you edit an FDX file without Final Draft?

Viewing vs editing an FDX: why the difference matters

Round-tripping: how the producer gets their FDX back

What can break in an FDX round trip

Step by step: edit an FDX on iPhone or iPad

Step by step: edit an FDX on Mac

Alternatives: Fountain, desktop apps and careful text editing

Mistakes that break the file or the relationship

Frequently asked questions

Ready to turn this idea into a screenplay?

Continue reading

What Is an FDX File?

How to Open an FDX File Without Final Draft (Free, Any De…

FDX vs Fountain: Which Screenplay Format Should You Use?

How to Convert Fountain to FDX (Fountain to Final Draft)

FDX to Fountain Converter

Free FDX Viewer

More in fdx & final draft files