Also known as Final Draft · .fdx
Final Draft’s native XML format — still the file many coordinators, studios, and production tools expect. Inkwell imports and exports FDX so a Plot draft can enter and leave a Final Draft workflow without rewriting by hand.
FDX is a handoff format, not a reason to stay locked inside one app forever. Many coordinators, studios, and production tools still expect Final Draft's XML on delivery day. Inkwell imports and exports FDX so a Plot draft can enter and leave that workflow without rewriting the script by hand.
On import, standard scene headings, cues, dialogue, and common elements map into Plot's structured types. Edge cases should surface as warnings rather than silent drops -- review them before you keep drafting so you are not surprised later when a dual-dialogue block or title page field needs a quick fix.
Export back when the next person still lives in Final Draft. FDX export is available on Writer and above. Edit where your history and review passes live; treat FDX as the exchange format that keeps production conversations unblocked when someone else needs that familiar file type.
Standard scene headings, cues, dialogue, and common elements map into Plot's structured types. Edge cases surface as import warnings rather than silent drops -- review them before you keep writing.
Yes. FDX export is available on Writer and above so you can return a structured draft to a Final Draft-centric pipeline when production asks for it.
Edit where your history and collaboration live. If you want named save points and reviewable skill passes, keep the canonical draft in Plot and treat FDX as an exchange format.
No. PDF is for reading and printing a page image. FDX is Final Draft's structured XML, which production tools can open and edit as a screenplay file.
