How to Edit an FDX File Without Final Draft

You can edit an FDX file without Final Draft, but not by treating it as a text file. The words live inside XML elements whose type attributes carry the formatting, so hand-editing risks a file that no app will open. The reliable routes are the free browser tools for viewing and converting, and an app that imports FDX, lets you edit it as a script, and exports FDX back.

Updated 2026-09-18 · About 6 sections · 5 answered questions

What you can and cannot change by hand in an FDX file

An FDX file is text, so a text editor opens it and lets you type. Which parts are safe depends entirely on whether you are touching content or structure. Here is a dialogue block from a real FDX file:

<Paragraph Type="Character">
    <Text>MARA</Text>
</Paragraph>
<Paragraph Type="Parenthetical">
    <Text>(into the radio)</Text>
</Paragraph>
<Paragraph Type="Dialogue">
    <Text>You can see the whole coast from up here.</Text>
</Paragraph>

The three Type attributes are the only thing telling an app that this is a character cue, a parenthetical and a speech. Strip them and the block becomes three untyped paragraphs with no indentation. Change Dialogue to Action and the speech is formatted as description.

Edit	Result
The words inside `<Text>`	Safe. Rewording a line, fixing a typo or shortening a sentence all work.
Text on the title page	Safe. The title page lives in its own self-contained block, separate from the script body.
A `Type` attribute	Risky. It is the only structural information in the file, and everything else is derived from it.
Renaming a character cue	Modifies one cue only. The character list and any other cues for that character stay as they were, so the script becomes inconsistent.
Deleting a paragraph	Fine if you remove the opening and closing tags as a balanced pair. A missing close tag stops the file parsing at all.
Scene numbers	Editable, but pages renumber themselves from the layout anyway, so hand-numbering is rarely worth it.
Revision IDs	Leave them alone. They point back at the file's revision set, and orphaned ones break revision colours.

Why hand-editing goes wrong, and why there is no repair tool

XML is unforgiving in five specific ways, and an FDX file hits all five.

Case matters. Type="dialogue" is not Type="Dialogue". An unrecognised value can be silently treated as general text, which is worse than an error because you only notice it on the page.
Ampersands and angle brackets must be escaped. A character called MARA & JON has to be written MARA & JON in the file; a bare & makes the document invalid.
Tags must balance. One missing closing tag and the whole file stops parsing. Apps will tell you it is not a valid Final Draft document, and there is no repair tool — no partial recovery, no import-what-you-can. Your only fallback is the copy you kept.
The encoding declaration has to stay true. The header declares UTF-8. Save the file as something else, or add a byte-order mark, and accented names and dashes turn into mojibake or trip the parser.
Some structures nest. Dual dialogue wraps two dialogue blocks, and inline styling wraps runs of text. Delete one tag from a nested block and you orphan its contents.

There is also a subtler problem. <Text> holds a run of characters, not a line: a single paragraph can contain several runs, one per style change, and pressing Return in a screenplay app creates a whole new <Paragraph>. So inserting a newline character inside <Text> does not reliably produce a line break on the page. Hand-wrapped dialogue tends to do nothing, or to shift spacing in ways you did not intend.

Put plainly: hand-editing can get the words right while leaving the structure exactly as accurate as it was before — and the moment the job involves moving, splitting or retyping anything, you are fighting the format instead of using it.

The free browser tools that do the work instead

Four browser tools cover most of what people actually want from an FDX file, with nothing to install and no account:

Script Viewer — open the FDX and read it laid out as a screenplay, with a page count and scene list. This is where to start: always read the file before deciding how to change it.
FDX to Fountain — convert to Fountain, a plain-text screenplay format you can edit in any text editor. Fountain marks elements with simple conventions, so a scene heading is a line starting with INT. or EXT. and a character cue is a line in caps above a speech.
FDX to PDF — produce a fixed, sendable document when the reader does not need to edit anything.
PDF to FDX — for when the only copy you have is a PDF. This direction is heuristic: the converter infers element types from layout, so expect to check the result rather than trust it.

The Fountain detour is the honest answer for a writer who wants to make small text edits in a plain editor. Understand the trade first: scene headings, action, character, parenthetical, dialogue and transitions survive the round trip, but revision marks and script notes do not, and dual dialogue, scene numbers and title-page alignment depend on how well your converter and editor handle the equivalent Fountain syntax. Convert one scene, check it, then convert the script.

The round trip that avoids the XML entirely

The clean way to edit an FDX without Final Draft is to let an app own the format while you own the words. Zen Writer imports FDX, edits it as a normal screenplay, and exports FDX again:

Import the .fdx into Zen Writer on iPhone, iPad, Mac or Android.
Edit the script. Formatting stays automatic while you type, so element types are never something you touch.
Use the scene navigator to move between scenes, search to find every instance of a character or a phrase, the character list to keep cues consistent, and script statistics to see what a cut actually did to your page count.
Export FDX when the draft is done. The file you hand back is a valid FDX in the same format you received.

None of this requires a network connection, and no account is needed. The free tier covers one screenplay and exports carry a watermark; Pro adds unlimited screenplays, watermark-free PDF, FDX and Fountain exports, the dark theme, typewriter mode and full edit history.

The structural argument is the whole point. Because you never touch the markup, the file that leaves your device has correct element types, balanced tags and a consistent character list — the three things hand-editing is most likely to break.

Choosing a route: a rewrite pass or a trim

Different edits justify different tools. A trim is mostly deletion and page maths; a rewrite moves scenes and changes element types.

The job	Route	Why
Fix typos and reword a few lines	Zen Writer, or a text editor if you are careful	In a text editor, change only what is inside `<Text>` and keep a backup.
Change the title page	A text editor is genuinely fine	The title page block is self-contained and has nothing to do with the script body.
Cut pages to hit a target length	An app with a scene navigator and script statistics	Page count is recomputed from the layout, so you see the real effect of every cut as you make it.
Move scenes, merge scenes, retype a passage	Zen Writer FDX round trip, or Final Draft	Element types have to travel with the text. Hand-editing a restructure is where files get broken.
Pull one character's lines for a read-through	Zen Writer's character list and search	Faster and safer than stripping XML by hand.
Read a script someone sent you	Free browser viewer	No install, no account, nothing to break.
Hand back a deliverable to a Final Draft user	Export FDX from Zen Writer	It is the format they asked for, and it stays editable on their side.

The rule of thumb: if the edit is a word, any tool will do; if the edit changes structure, use something that understands structure.

Before you send the file back

Three things save a wasted round trip.

Match the format to the reader. An FDX if they work in Final Draft, a PDF if they only read, Fountain only if you know they use it. Sending a plain-text screenplay to someone who asked for an FDX costs a day.

If you did hand-edit the XML, say so and send the original file alongside the edited one. A file that will not open is expensive to diagnose at the other end, and a fallback copy turns a crisis into a five-minute fix.

Check the export settings. Watermarked exports are fine for a look and wrong for a submission; keep that in mind before you email a draft to a producer or a competition.

The reason FDX exists is to move a screenplay between tools without losing its structure. An app that imports and exports FDX does that job by design. A text editor does it only by luck.

Frequently asked questions

Can I edit an FDX file in Notepad or TextEdit?

Technically yes, because FDX is XML text. Changing the words inside a Text element works, and so does editing the title page. But anything structural — element types, paragraph tags, revision marks, scene numbers — is easy to break, and a file with one unbalanced tag will not open in any screenplay app.

What happens if I break an FDX file while editing it?

It stops being valid XML, so apps report that it is not a valid Final Draft document and refuse to open it. There is no repair tool and no partial import: keep a copy of the original before you edit anything by hand.

Will Word or Google Docs let me edit an FDX file?

No. Neither has a Final Draft importer, and Word's XML support is for a different vocabulary entirely. Convert the file to Fountain if you want to work on the text in a general-purpose editor, or open it in an app that reads FDX.

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 survive only as far as your converter and editor handle the equivalent Fountain syntax. Scene headings, action, dialogue, parentheticals and transitions come through reliably, so check one converted scene before you commit the whole script.

Do I need Final Draft to rewrite an FDX screenplay?

No. Zen Writer imports FDX on iPhone, iPad, Mac and Android, gives you automatic element formatting, a scene navigator, search, the character list and script statistics, and exports FDX back out when you are done.

Ready to turn this idea into a screenplay?

Zen Writer imports an FDX file, lets you edit it as a properly formatted screenplay, and exports a valid FDX straight back — no XML editing involved.

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

What you can and cannot change by hand in an FDX file

Why hand-editing goes wrong, and why there is no repair tool

The free browser tools that do the work instead

The round trip that avoids the XML entirely

Choosing a route: a rewrite pass or a trim

Before you send the file back

Frequently asked questions

Ready to turn this idea into a screenplay?

Continue reading

What Is an FDX File?

How to Open an FDX File (With or Without Final Draft)

How to Convert FDX to PDF

How to Convert a PDF to FDX

FDX vs Fountain: Which Screenplay Format Should You Use?

FDX to Fountain Converter

PDF to FDX Converter

More in fdx & final draft files