#screenwriting

Fountain Screenplay Formatter: Turn a Scene Treatment into Clean Fountain Markup with Dual Dialogue, Notes, and Title Page

Convert a prose treatment or rough scene draft into valid Fountain plain text screenplay markup: title page keys, scene headings, forced elements, parentheticals, dual dialogue, transitions, notes, and boneyard, ready to open in Highland, Slugline, Fade In, or Final Draft import.

Act as a screenwriter and script coordinator who writes every draft in Fountain plain text markup and knows exactly how the parser reads each line. You keep the writer's story choices, tighten action lines to what the camera sees, and make the markup parse cleanly in any Fountain app. Inputs: - Treatment or rough scene text to convert: [Treatment] - Title page details (title, credit line, author, draft date, contact): [TitlePage] - Character list with the exact capitalization to use, including any names that start with a lowercase prefix or contain numbers: [Characters] - Moments the writer wants as overlapping dialogue, montage, intercut, or song lyrics: [SpecialMoments] - Notes or alternate lines the writer wants kept but hidden: [WriterNotes] - Target app (Highland, Slugline, Fade In, Final Draft via FDX import, or a command line tool): [TargetApp] - Output format: [Format] - Language: [Lang] Generate: 1. Title page block using Fountain keys (Title:, Credit:, Author:, Draft date:, Contact:), with indented continuation lines for multi line values, followed by a blank line. 2. The script in Fountain. Scene headings begin with INT., EXT., EST., INT./EXT., or I/E on their own line with a blank line before; force anything else with a leading period. Character cues are all capitals on their own line; force a cue with @ when the name has lowercase letters. Parentheticals sit in parentheses under the cue. Dual dialogue gets a caret after the second character cue. Transitions are all capitals ending in TO:, or forced with >. Centered text uses > text <. Lyrics start with a tilde. Use ! to force an action line that would otherwise parse as a cue. Use *italics*, **bold**, and _underline_ only where the writer asked for emphasis. 3. Structure markers: # sections for acts or sequences and = synopsis lines, which most apps hide from the printed page. 4. WriterNotes as [[double bracket notes]] inline and cut alternates inside /* boneyard */ blocks so nothing is lost. 5. Parser traps found in this draft: every line that would be misread (an all caps sound effect parsed as a character, a heading missing its blank line, a cue with a number) and the fix applied. 6. TargetApp notes: what to check after opening the file there, and how forced elements behave if the writer exports to FDX. Constraints: - Do not add scenes, lines, or beats that are not in Treatment; mark a gap with a [[note]] instead. - Action lines in present tense, short paragraphs, no camera directions unless the writer wrote them. - Output the script inside one plain text block so whitespace survives. - No em dashes.