How to Convert PDF to FDX (Screenplay PDF to Final Draft)

Can you convert a PDF to FDX? Yes, if the PDF has text

A screenplay PDF exported from Final Draft, Fade In, WriterDuet or any other screenwriting app carries a text layer: every letter is stored as a character at a known position. That is enough to rebuild the script. A converter reads each line, measures where it starts, checks whether it is in capitals, and tags it as a scene heading, action, character cue, parenthetical, dialogue or transition. The result is a valid .fdx you can open and edit.

The conversion is a rebuild, not a restore. A PDF stores appearance and an FDX stores meaning, so nothing in the PDF says "this line is dialogue" — the converter infers it. On a standard-format PDF that inference is right almost every time. On a scanned PDF, a Word export in a proportional font, or a script laid out on odd margins, it degrades, and the rest of this article is about knowing which case you are in and fixing what breaks.

Two free routes, both covered step by step below: the browser-based PDF to FDX converter, which returns a file you can open in any app that reads Final Draft's FDX format, and importing the PDF directly into Zen Writer on your phone, tablet or Mac, which skips the download step entirely.

Text-based PDF vs scanned PDF: check this first

Two very different files share the .pdf extension, and only one of them converts.

• Text-based PDF. Made by exporting from software. The words are stored as text. You can select a line of dialogue, search for a character name, and copy a paragraph.
• Scanned or image PDF. Made by a scanner, a photocopier or a phone camera. Each page is a picture. There are no characters in the file, only pixels arranged to look like characters.

The ten-second test: open the PDF and try to select a line of dialogue. If the words highlight one by one, you have a text layer. If the whole page highlights as one rectangle, or nothing does, you have a scan. Searching for a character name is the same test: a scan returns nothing.

A scan needs OCR — optical character recognition — before any converter can touch it. Most PDF apps can run OCR and save a new PDF with a text layer under the image. Expect it to misread the characters Courier makes ambiguous: 1, l and I; 0 and O; rn read as m. It also reports line positions roughly, and screenplay conversion depends on exact positions, because the gap between action and dialogue is about an inch of indent. An OCR'd feature converts, but plan on a few dozen hand corrections rather than a handful.

How PDF to Final Draft conversion detects each element

Every screenplay element lives at a fixed horizontal position on a standard page, and that geometry is what a converter reads. Action starts at the 1.5" left margin, dialogue about 2.5" from the page edge, character cues around 3.7", parentheticals around 3.1", and transitions at the right margin. Add capitalisation and the blank lines between blocks, and a converter can classify almost every line:

So this passage on the PDF page:

INT. HARBOUR OFFICE - NIGHT

A single desk lamp. DEV counts cash into a tin, twice.

                    DEV
          (not looking up)
     You're late, and you're wet.

                                        CUT TO:

becomes six typed paragraphs in the FDX:

<Paragraph Type="Scene Heading"><Text>INT. HARBOUR OFFICE - NIGHT</Text></Paragraph>
<Paragraph Type="Action"><Text>A single desk lamp. DEV counts cash into a tin, twice.</Text></Paragraph>
<Paragraph Type="Character"><Text>DEV</Text></Paragraph>
<Paragraph Type="Parenthetical"><Text>(not looking up)</Text></Paragraph>
<Paragraph Type="Dialogue"><Text>You're late, and you're wet.</Text></Paragraph>
<Paragraph Type="Transition"><Text>CUT TO:</Text></Paragraph>

Notice what the converter has to guess. DEV in the action line is a character introduction, not a cue; position, not case, tells them apart. The rules hold as long as the columns hold, which is why a PDF on non-standard margins is the single biggest cause of a bad conversion.

Step by step: convert PDF to FDX with the free browser tool

1. Open the PDF to FDX converter. It runs in the browser on any device, with no login.
2. Drop the PDF in. The tool reads the text layer, measures each line against the standard margins and applies the rules above.
3. Read the preview. If it is page after page of action with no indented dialogue, the PDF is a scan or was not laid out in screenplay geometry, and the download will not help until that is fixed.
4. Download the .fdx. Save it under a new name — Title_from-PDF.fdx — so the original PDF stays your reference copy.
5. Open it and run the check pass described two sections down. Do this before you write a word of new draft, because a mis-tagged element that survives into the next draft costs more to find later.

For plain text instead of Final Draft XML, the sister tool PDF to Fountain runs the same detection and writes a .fountain file.

Step by step: import the PDF straight into Zen Writer

If the reason you want the FDX is to keep writing, you can skip the intermediate file. Zen Writer imports text-based PDF screenplays directly, on iPhone, iPad, Mac and Android, and runs the same element detection on import.

1. Import it. Open the PDF in Zen Writer for iPhone (or the iPad, Mac or Android app) and choose it as a screenplay import. Nothing is uploaded; the conversion happens on the device.
2. Fix what the check pass finds. Tap into any line that came through as the wrong element and switch its type. The scene navigator gives you a quick count of headings to compare against the PDF.
3. Export FDX whenever you need to hand the script to someone in Final Draft. The same document also exports PDF, Fountain and plain text.

This is also the answer for anyone who wants to edit an FDX without owning Final Draft: import, edit, export, and the file that goes back out is the same format that came in.

What to check after converting PDF to FDX

Ten minutes on this list saves an afternoon later. Work through it on every conversion, in this order.

1. Sluglines. Count the scene headings in the PDF (search for INT. and EXT.) and in the new file. A missing heading has usually been tagged as action or fused onto the line above. A slugline without INT. or EXT. — LATER, BACK TO SCENE — will nearly always come through as action and needs retagging.
2. Character cues. Open the app's characters list, which is collected automatically from the cues. A cue that was tagged as action does not appear, and a cue with a typo — DEV and DEV (CONT'D) are fine, DEV. is not — appears as a second character.
3. Parentheticals. An action line that happens to begin with a parenthesis can be mis-tagged as a parenthetical, and a long parenthetical that wrapped in the PDF can come through as two elements. Search for ( and skim.
4. Page breaks and page-break markers. Page numbers are print artefacts and are dropped, which is correct. But (MORE) and (CONT'D) were generated by the old pagination and are now stray text. Remove every (MORE), and remove the (CONT'D) from any cue that only carried it because a page break split the speech. The CONT'D article covers which ones should stay.
5. Dual dialogue. Two speeches printed side by side arrive as two consecutive speeches. Nothing flags them; you have to know where they were.
6. Title page. It comes through as a few centred lines of text at best. Rebuild it in the app rather than trusting the conversion.
7. Page count. The new file repaginates to its own template, so the total should land within a page or two of the PDF. A 108-page PDF that becomes 90 pages has lost or merged something.

If the PDF was a shooting script, expect stray scene numbers in the margins to come through as text on the heading line. The spec vs shooting script article explains why those numbers exist; the free spec/shooting toggle strips them.

PDF to FDX failure modes and how to fix them

One last rule: a PDF sent to you for reading is not an invitation to rewrite it. Convert your own drafts, or drafts you have been asked to work on. The rest of the FDX guide covers the reverse trip — converting FDX back to PDF — and how to open the converted file on each device.

Frequently asked questions

Continue reading

More in fdx & final draft files

• What Is an FDX File? Final Draft's XML Format Explained
• How to Open an FDX File Without Final Draft (Free, Any Device)
• How to Edit an FDX File Without Final Draft (and Send It Back)
• How to Open an FDX File on iPhone (Files, Mail, AirDrop)
• How to Open an FDX File on iPad (and Rewrite in Split View)
• How to Open an FDX File on Mac (Without Final Draft)
• How to Open an FDX File on Android (Free FDX Viewer and Editor)
• How to Convert FDX to PDF (Final Draft Script to PDF)
• How to Convert FDX to Word (.docx) or Google Docs
• How to Convert Fountain to FDX (Fountain to Final Draft)
• What Is Fountain? The Plain-Text Screenplay Format Explained
• FDX vs Fountain: Which Screenplay Format Should You Use?
• Final Draft Alternatives: The Best Screenwriting Apps Compared
• Final Draft Alternatives for iPhone: The Best Screenwriting Apps
• Final Draft Alternatives for iPad: The Best Screenwriting Apps
• Final Draft Alternatives for Mac: The Best Screenwriting Software
• Best Screenwriting Apps for Android: The Honest Guide
• Free Screenwriting Software: The Best Free Apps, Honestly Compared