Script

Writing and managing the episode screenplay in Fountain format.

The Script page is where you write and manage the screenplay for an episode. Screenplays are written in Fountain format -- a plain-text markup language designed for screenwriting.

The three modes

The page is not tabbed: it shows one of three modes at a time, and the button at the top right switches between them.

View

The default. Displays the screenplay as formatted script pages. A resizable side panel lists the episode's Scenes -- each with its scene number as a button -- so you can jump to any scene in a long script. A scene number shown in red, or as a ?, means the heading has no stable #N# number yet.

Edit

A raw text editor for writing Fountain markup directly. Use Save to persist changes, Cancel to discard. Fountain Syntax Help opens the syntax reference, and while the script is still empty a Load Template button inserts a starter structure.

Saving is what updates everything downstream -- there is no separate parse or analyse button here. The AI pass over the finished draft is run from Review Screenplay on the Script AI Review page.

A script that is not in Fountain yet

If you wrote the script somewhere else -- in a word processor, or as plain prose -- paste it into the editor and ask the assistant to convert it. It rewrites the whole script in the form this app reads: scene headings with their #N# numbers, character cues, dialogue and parentheticals, and any paragraph that is none of those left where it is as an action line. It does not invent scenes, characters or dialogue your draft does not contain, and it does not quietly drop anything it cannot classify. Paste its answer back over the draft and Save -- that save is what creates the scenes and picks up the characters.

Change Source

Links the screenplay to an external source:

  • Google Doc -- paste a sharing URL; the platform fetches the latest version on refresh
  • Google Drive -- a file kept in Drive, such as a Final Draft .fdx export or a Fountain .fountain file; paste its Share link
  • Local file -- upload a file from your computer
  • In-app -- write it in the app itself

With a source linked, the button at the top right becomes Refresh, which pulls the latest version in; pulling a document in re-parses it exactly as saving does, and then also generates a shot list for each scene it found. Its dropdown carries Change source and Edit local copy. Unlinking removes the connection and returns to local editing.

A screenplay you write in the app has no external source to pull from, so it has no Refresh -- the button is Edit, with Change source on its dropdown, and Save is what updates everything downstream.

Assets are not created here

The panel beside the text lists the episode's scenes only. While you are drafting, a heading is often still a placeholder -- so a name in the script is not yet a name worth creating an asset from.

The check that every character and location the script names exists as an asset runs in Script Analysis, after the AI pass has had a chance to tell a new name from a spelling of an existing one. Every name the script uses is listed there, each with a dropdown showing the asset it is linked to; names with no asset come first, showing "Select location to link to" (or character). The dropdown offers Create the name as a new asset, every existing asset of that kind (so WEATHER SCREEN can mean your "Weather Desk"), Do not link to location (or character) for a name that is not an asset at all, and -- once you have linked a name -- Clear linkage, which goes back to matching it by name. Names are listed alphabetically under Locations and Characters. The links belong to this episode, so the same name can mean different assets in another episode. You can also create one from the scene that needs it -- see Scenes.

Cast and places before the first scene

A screenplay may open with a short list of its cast and its places, between the title page and the first scene heading. One paste of the script then sets them up, instead of describing each character and location separately afterwards.

Title: No News is Good News
Author: Alan Kent

# Cast

JULIE - evening news anchor in a navy suit; serious and composed, plays everything straight.
SALLY - weather presenter in a frilly pink maid dress; loopy, relentlessly cheerful.

# Places

NEWSROOM - evening TV studio: news desk on the left, weather wall on the right.

INT. NEWSROOM - ON AIR #1#
...
  • One entry per line: the name in capitals, a hyphen with a space each side, then the description (NAME: description works too, but only after a title page -- without one, Fountain reads a first line like that as the title page). Write a character's name exactly as its dialogue cue, and a place's name as it appears in the scene headings (NEWSROOM for INT. NEWSROOM - ON AIR).
  • # Cast (or # Characters) and # Places (or # Locations, # Sets) say which is which. Without them, an entry whose name is the place in one of your scene headings is a place, and any other entry is a character.
  • Lines that do not look like an entry -- a note to yourself, a sentence in ordinary case -- are left alone, and any other section (such as # Look) is ignored for now.
  • It is still a normal Fountain file. The # lines are outline sections, which Fountain apps do not print, and the entries read as action lines, so other screenwriting tools still open it.

The list is never a scene: it does not become scene 1, and it is not part of any scene's text.

Script Analysis uses it. Running the analysis first goes through the list:

  • A name with no character or location yet is created, with the entry as its description -- even a character who never speaks.
  • An existing one with no description gets the entry as its description.
  • An existing one whose description says something else is not changed. The entry is offered as a proposal on that character's or location's Properties page, to accept or reject -- what you wrote is never overwritten.

The analysis also reads the list, so its report includes what the list says about each one.

Scene parsing

Whatever changes the stored screenplay parses it: saving the editor, refreshing from a linked document, and importing a Final Draft file all do the same work. There is no separate button for it.

  • Each scene heading (e.g. INT. KITCHEN - DAY #1#) becomes a scene entry in the episode's scene list
  • The scene text (action lines and dialogue) is stored separately and used for AI generation
  • The Title: on the screenplay's title page becomes the episode's name -- unless you have renamed the episode yourself, in which case your name is kept
  • Dialogue is extracted onto each scene, so lines you can record appear without any AI step
  • A scene whose text did not change is left completely alone, including its shots
  • A scene the screenplay no longer mentions is shelved, not deleted -- it keeps its media and comes back if its scene number reappears

Scene numbers are scene identity. The #1# at the end of a heading is what ties a scene to everything already attached to it. Inserting a scene between 1 and 2 should number it 1b rather than renumbering the rest; renumbering makes the platform treat every scene after the change as a different scene.

Your text is always saved. A heading without a number simply does not become a scene. If a heading has no #N#, or two headings share one, the screenplay is stored exactly as you wrote it, but those headings are not imported: there is no number to file the scene under, and one cannot be invented without attaching the scene's work to an identity you did not choose. You are told which headings, and the scene panel shows them in red or as a ?.

While any heading is like that, the platform will not act on the screenplay. Script Analysis and generating shot lists across the episode both refuse, and say which headings to number, rather than working from an episode that is quietly missing a scene. Nothing you already have is taken away either: a scene whose number you deleted by accident is not set aside while the mistake stands. Number the headings, save again, and everything proceeds.

Shots come from the scene, not from here

Saving or importing a script never touches shots. Shots are planned one scene at a time, from the scene's own band on the shot list. Replanning a scene proposes changes to values you already filled in, for you to accept or reject, and offers a missing beat as a shot you can add -- it never removes anything and never adds a shot on its own. The one exception is Refresh on a linked document, which plans every scene it pulled in.

Generating a scene's shots also fills in the scene's location and cast. Each shot then inherits those, and only carries its own where it genuinely differs -- a close-up on one character in a two-hander, or a cutaway to another part of the set. Change the location on the scene and every shot that inherits it follows.

Script AI Review

The Script AI Review page runs an AI analysis of the full screenplay. You can change the review instructions from the page's overflow menu (Edit Review Instructions) and run the analysis at any time. Results stream in and are rendered as markdown. A timestamp shows when the last review was generated.