If someone asks for an FDX file, they are usually asking for an editable screenplay, not just something they can read. That distinction matters. A PDF is fine for sharing. An FDX is what people want when the script needs to move into a professional workflow.

What is an FDX file?

FDX is Final Draft’s XML-based file format. It stores the text of the screenplay along with the structural information that tells Final Draft what each line is: scene heading, action, character name, dialogue, parenthetical, transition, and so on.

That structure is what makes the file useful. Without it, the script may look right in one app but fall apart when it opens somewhere else.

Why FDX matters

FDX is common because it solves practical problems:

• Collaboration: Writing teams and production offices often work in Final Draft.
• Editing: The script stays editable instead of being locked like a PDF.
• Revisions: Notes, revisions, and production workflows are built around the native format.
• Compatibility: Sending the format people expect removes one more barrier.

Where exports go wrong

A weak export usually fails in one of three ways:

• Dialogue and action are mapped to the wrong element types
• Metadata or structural information gets dropped
• Special characters or formatting survive badly in the new file

That is why screenplay export is not just a file conversion problem. It is a structure problem.

Exporting from Plotten

Plotten can export a screenplay to FDX using the structure already in your project:

1. Write in a screenplay project so the document is tagged correctly from the start.
2. Review the script and fix any places where an element was identified incorrectly.
3. Export to FDX from the share or export options.
4. Open the file in Final Draft, or send it to the person who requested it, and spot-check a few pages if you can.

Because the screenplay elements are structured as you write, the export is based on more than visual formatting alone.

Tips for a clean export

• Use the screenplay template from the beginning. Converting a loosely formatted document later creates more cleanup.
• Keep scene headings consistent. Clear INT. / EXT. headings make downstream handling more reliable.
• Use styling sparingly. Basic emphasis can transfer, but unusual formatting is always more fragile.
• Test before sending. If you have access to Final Draft, open the file and skim several scenes.

Beyond FDX

FDX is useful when someone needs to edit, mark up, or continue working on the script. PDF is still the better choice when you only want the script read as-is.

The real goal is simple: write in the environment you prefer, then hand off the script in the format the next person needs.

Plotten is available on the App Store if you want to export to FDX from the same screenplay project.