A practical guide to FrameDraft
Best Tools for Importing Word and Fountain Scripts Into a Comic Workflow
Compare Word and Fountain import in Scrivener, Story Architect and FrameDraft, plus Superscript’s text workflow and checks for comic pages and panels.
Scrivener and current FrameDraft releases document imports of both Word and Fountain scripts. Story Architect also documents DOCX import and Fountain support for comics, with options varying by document type. Superscript is worth considering for a comic-specific text workflow, but its reviewed documentation does not establish a native Word or Fountain importer. Choose according to your starting file and the cleanup required—not the assumption that importing a screenplay automatically creates comic pages and panels.
This guide is published by FrameDraft’s developer. It compares official documentation checked on November 4, 2026, not hands-on migration tests or a universal ranking. Check the installed version and test a copy of your script before committing.
Which tools can move a Word or Fountain script into a comic workflow?
| Tool | Word route | Fountain route | What needs checking? |
|---|---|---|---|
Scrivener | DOC and DOCX are listed as supported imports. | Native .fountain import is listed. | Importing text is separate from assigning comic-script elements and page structure. |
| Story Architect | DOCX import is documented for scripts and text documents. | Comic Fountain import is explicitly documented. | Supported formats vary by document type; confirm the destination editor. |
| FrameDraft | DOCX import is listed in the current release notes. | .fountain import is also listed. | Review detected pages and panels. Free access is limited; check feature access in-app. |
| Superscript | Plan for copying text and adapting it; native DOCX import was not verified. | Adapt text to Superscript syntax; native Fountain import was not verified. | Its documented comic syntax differs from standard Fountain. |
Story Architect’s 0.7.7 release notes document DOCX text importing. Its current repository overview cautions that import/export availability varies by document type and direction. FrameDraft’s current import behavior is described in its App Store version history; its free allowance is one comic with up to three pages.
Why is importing different from converting a script into comic pages?
Fountain’s syntax describes screenplay elements such as scene headings, action, characters and dialogue. A scene heading is not automatically a comic-page heading, and an action paragraph is not necessarily one panel.
A screenplay may contain several moments that need separate images. Conversely, a Word document’s printed page breaks may reflect font size rather than intentional comic-page turns. Decide where each comic page and panel begins, then check that the destination recognizes those decisions.
Fountain can be adapted for comics: writer Antony Johnston provides a comic-script template and example. That does not guarantee identical interpretation in every app. Keep the original file and compare the imported result.
When does Scrivener make sense for an existing Word draft?
Scrivener is a practical candidate when you want to organize a long draft alongside research. Its import guide lists Word and Fountain, while its template guide confirms a Comic Script template.
For DOCX, the developer documents File → Import → Files. Its Word workflow guide also describes Import and Split, using document headings or a chosen separator to create separate Binder documents. Consistent headings can therefore help organize an existing draft.
The limitation: splitting a document is not the same as recognizing dialogue, captions or panel descriptions. Review those elements in the comic template. Import and Split is not available on Scrivener for iOS, so do not assume the desktop migration workflow is identical on iPad.
What does Story Architect offer for Fountain comic scripts?
Story Architect’s import instructions list DOCX and Fountain. Its 0.7.3 release notes explicitly introduced Fountain import/export for comics and described transferring text between its script editors by copying and pasting.
That makes it a candidate when you need both an imported source and a comic editor within one project. However, the older release’s comic-import restrictions should not be treated as the full current format list: later release notes added DOCX importing for text documents.
Confirm which document type the installed importer creates. If Word arrives as a text document rather than a structured comic, allow time to move and classify the text in the comic editor. File acceptance alone is not proof of correct page-and-panel conversion.
Can Superscript import Word or Fountain without adaptation?
The Superscript homepage advertises export to Word, PDF, Markdown, rich text and plain text. Export support is not evidence of import support; a native DOCX or Fountain importer was not verified in the official pages reviewed for this guide.
Its documentation explains a distinct comic syntax: PAGE 1 and Panel 1 headings, character headings ending in a colon, and dialogue indented with two spaces or a tab. Standard Fountain instead recognizes uppercase character cues with dialogue immediately below them.
If you choose Superscript, test copying a short passage and adapting those elements first. This is a manual text-conversion route, not a promised one-click import. Its comic numbering and spoken-word counts may be useful once the script follows its syntax.
Where does FrameDraft fit, and what is its limitation?
FrameDraft’s App Store release notes list .docx, .fountain, .txt and .frd imports. Version 2.4.9 describes reading classic comic scripts and plain text, with a preview that lets you fix or remove pages and panels before importing.
It is therefore one option for moving existing writing into a comic-focused editor. The practical limitation is that detected structure still needs your review; the release notes do not promise preservation of every Word layout, annotation or imported element. Its free allowance is one comic with up to three pages, not unrestricted full access. Check the in-app import and subscription requirements before migrating a long script.
For the destination structure, see our FrameDraft comic-script walkthrough. It explains the writing workflow, not an import-fidelity guarantee.
What should you check before importing the whole script?
- Work from a copy. Preserve the original Word or Fountain file and a readable reference export.
- Use a representative excerpt. Include page and panel headings, dialogue, a caption, SFX and any notes or images you rely on.
- Inspect element recognition. Check whether captions became dialogue, descriptions became character cues, or several panels merged.
- Compare content, not just appearance. Look for missing lines, changed emphasis, misplaced notes and unintended page breaks.
- Test the outgoing document. Save, reopen and export a sample in the format your artist or editor needs.
Pick the tool that passes this test with tolerable cleanup. A supported extension is the beginning of a migration, not its quality check.
Frequently asked questions
Does renaming a Word file to .fountain convert it?
No. Fountain uses plain-text screenplay syntax; DOCX is a different document format. Export or copy the text, then adapt its structure rather than merely changing the filename.
Will Fountain preserve Word images and tracked changes?
Do not expect it to. Fountain is a plain-text syntax, not a container for the complete Word document. Keep the Word original and verify separately how your chosen app handles annotations and reference material.
Which route should I try first?
For a Word-heavy draft, test Scrivener’s documented import and organization tools. For a Fountain comic, check Story Architect’s comic importer. Current FrameDraft releases document both formats with a preview. Consider Superscript when you are comfortable adapting text to its comic syntax. To explore FrameDraft’s destination workflow, visit the app overview.
