Keep the screenplay as the writing source and make a visual interpretation beside it. Storyboard Creator’s inspected importer accepts its own board JSON. It does not establish native Fountain, Final Draft FDX or Word parsing, nor a screenplay round-trip. You can still board a scene by reading it in its original application and copying the minimum reference notes manually.
Separate scene facts from camera choices
Fountain’s official syntax distinguishes scene headings, action, characters and dialogue. A scene heading identifies place and time; it is not a camera instruction. Open an FDX file in a compatible screenplay application rather than treating its raw XML as a shot list. Preserve the script filename, revision and scene reference in a separate mapping note. Use only material you are authorized to handle.
A complete six-beat mapping
For this original fictional exercise, scene 12 says: a woman notices a red apple, lifts it and places it in a blue bowl. It does not specify shot sizes. The six choices below are an interpretation, not six new screenplay lines.
| Code | Script fact | Proposed visual decision |
|---|---|---|
| 12-A | Kitchen location | Wide view establishes counter |
| 12-B | Apple beside bowl | Close view shows relationship |
| 12-C | Woman notices apple | Medium view makes intention legible |
| 12-D | She lifts apple | Close view shows start of action |
| 12-E | She places it in bowl | Medium view preserves direction |
| 12-F | Apple rests in bowl | Close view confirms result |
Build the cells without duplicating the script
Create six cells and enter 12-A–12-F as headings. In captions, write the visible action and a short script reference such as scene 12, revision r01. Keep dialogue intact in the screenplay; add only the cue needed to understand a panel. Avoid splitting every spoken line into a new shot. A reaction or a held frame may cover several lines, while one action may need several visual beats.
Record an explicit change request
Suppose r02 changes the apple to a pear. Mark B, C, D, E and F for review: the object appears or motivates action in all five. Update captions and artwork, then inspect A for a visible prop too. Keep stable shot codes unless the agreed numbering convention requires a change. Do not assume the software detected the script revision or updated another document automatically.
Verify the mapping against the source
Read the script and board side by side. For each cell ask which source fact it preserves, which camera decision you added, and whether the next cell continues the action. Check scene 12 still exists after renumbering. Save r02 JSON and a visual reference with matching revision names; keep a small change log so an old PDF cannot silently become the current board.
Limits and recovery
Six cells fit the free exercise; visual exports include a watermark. JSON is the editable Creator backup, not an FDX export. If a scene cannot fit six cells, choose a smaller unit for the exercise or review the current plan limits. A manual mapping does not verify dialogue timing, legal rights, screenplay formatting or import compatibility in another application. The four-panel illustration is deliberately condensed and is not evidence of a parser.
Sources and verification
Fountain’s official syntax is the primary reference for screenplay elements. Product verification record identifies the actual JSON importer and board fields inspected on 30 October 2026. The proposed apple scene and revision procedure are original editorial exercises, with no claimed writer experience or independent expert approval.

