Check Final Draft screenplays from an .fdx upload
Screenplay-native Story Bible tracking for Final Draft
Start freeHow it works
Upload your Final Draft screenplay
Export to .fdx or .fountain and upload it directly. Watching the file with the Companion is not open yet.
PlotLens parses the uploaded screenplay's structure
Scene headings, character cues, dialogue, and action lines are understood as structured screenplay elements.
Review continuity findings by scene
Findings are organized by scene and character, matching the way you think about your screenplay.
It reads your screenplay like a script supervisor
PlotLens understands scene headings, character cues, dialogue attribution, and action lines. Not generic document parsing — screenplay-native validation.
How setup will work once Final Draft opens
Choose your .fdx screenplay in the Companion
Sign in, choose the .fdx file, and review the structure preview. Adding an .fdx file is refused until Final Draft watching opens.
Choose the book it goes into
Pick an existing book or start a new one. The Companion opens your .fdx read-only and never writes to it.
Check the saved file and review findings by scene
An .fdx file starts on Manual only: setup runs one first check, then you click Check saved file again to check the whole saved file. Findings are grouped by scene.
Limitations
Final Draft watching is not open yet, and nothing on this page should be read as saying otherwise. The Companion ships Final Draft support, but the rollout unlocks Scrivener first, so adding an .fdx file to the Companion is still blocked server-side. The steps above describe the setup once that stage opens — not a workflow available today.
What works right now is the direct path: export your screenplay to .fdx or .fountain and upload it to PlotLens. Screenplay format is parsed natively, so scene headings, character cues, and action versus dialogue are all distinguished rather than flattened into prose, and the Story Bible you get is the same Story Bible the Companion would build.
Everything downstream of getting the text into PlotLens is unaffected by the wait. Extraction returns characters, locations, events, items, organizations and concepts with the source passage when it matches your text word for word; auto-derived facts arrive pending with the snippet they came from, so you accept or reject each one; batch validation sweeps whole documents and returns findings with a severity, a conflict type, a suggested fix and, when it matches your text word for word, a quote from your manuscript. Spot Check will take a pasted excerpt of up to roughly two thousand words with no project documents required, free on every tier and outside the monthly quota — which makes it the cheapest way to check one revised passage while an integration is still closed.
Two Companion limits will still apply when Final Draft watching does open. The Companion never writes to a source file — no in-place comments, no applied fixes, no annotation of your .fdx — and Final Draft navigation is file-level rather than scene-level: there is no scene deep link, so opening a finding hands the .fdx to your operating system and you select the scene yourself. There is also no project-wide report in the Companion; a full pass means exporting and uploading to the web app.
Final Draft is the industry standard for screenwriting. Upload a .fdx or .fountain export, and when you run a check PlotLens reads the screenplay the way a script supervisor would — tracking characters across scenes, catching continuity breaks in dialogue, and flagging timeline contradictions before they reach production.
Watching a Final Draft file with the PlotLens Companion is not open yet: the Companion opens Scrivener first. Until then, export and upload each draft directly.
Ready to add PlotLens to Final Draft?
Start free — no credit card required.