Skip to content
Free · private browser tool

Free Final Draft FDX inspector

Open an FDX file privately in your browser to inventory revision sets, locked pages, scene numbers, and portability risks before you import or convert.

Private by design

Inspect a Final Draft file in your browser

Open a local .fdx before you import or convert. Parsing stays on this device—no upload, no account, no screenplay text in analytics.

Current source

No file selected yet

  • Draft identity & health

    Confirm the file is readable Final Draft XML and see version, title page, and parse warnings.

  • Portability report

    Classify locked pages, revision sets, omitted scenes, and custom styles by import consequence.

  • Consistency queue

    Surface character and location spelling variants without silently merging them.

Local .fdx file

Your screenplay stays in this tab. Refreshing the page clears it.

No inspection yet

Load the production-shaped sample or choose a local .fdx (up to 12 MB) to see readability, production features, and portability findings.

Useful output, not a score

What this tool gives you

Draft identity and health

See whether the screenplay text is readable, which FDX version and title-page fields are present, and whether the file looks malformed or merely uncommon.

Portability report

Classify locked pages, revision sets, omitted scenes, custom styles, and pagination-sensitive settings by what is likely to change during import.

Redacted diagnostic export

Download a local Markdown summary with structure and findings — never full dialogue — for support or collaborator handoff.

How to use it

  1. 1

    Choose a local .fdx file

    Open a Final Draft export on your machine, or load the built-in production-shaped sample. The file never leaves your browser.

  2. 2

    Review the four answers

    Check text readability, production features, likely import changes, and the next review step before converting or sharing.

  3. 3

    Export a redacted diagnostic

    Download the structure-and-findings summary, then continue into Plot or keep the original FDX as the production archive.

Questions writers ask

Is my FDX file uploaded or stored?

No. Parsing, inventory, and the diagnostic download all run locally in your browser. Inkwell does not receive the screenplay, file name, title, or author fields.

How is this different from the FDX import guide?

Migration guides explain common expectations before you move. The inspector answers what is unusual about this particular draft — revision sets, locked pages, custom styles, omitted scenes, and likely import loss.

Can I open an FDX without Final Draft?

Yes for inspection. The tool reads Final Draft XML in the browser and shows a writer-oriented structural map. It is not a full production editor and does not preserve locked-page workflow by itself.

What does the redacted diagnostic include?

Counts, portability findings, scene headings, revision-set names, and consistency variants. It intentionally omits dialogue and action body text so you can share a support-ready summary without sending the screenplay.

Does a warning mean the file is corrupt?

Not necessarily. The inspector distinguishes unsupported-but-valid features, uncommon constructs, and internally inconsistent references. Read the classification and next action on each finding.

Want to continue in Plot? Your screenplay stays in this browser tool and is not transferred automatically; paste or import it after you sign in.