Formatting is infrastructure, not the writing
A screenplay page has a strict visual grammar. Scene headings, action, character cues, dialogue, parentheticals, and transitions occupy different positions because readers and production departments need to scan them quickly. The writer should understand that grammar, but the software should carry the repetitive layout work.
Laper's editor does this by storing screenplay content as typed nodes. A character cue is not merely a centered line of text. It has a character node type. A scene heading is not a paragraph somebody made bold; it is a scene-heading node that can also provide structure to the rest of the project.
This distinction is the foundation of automatic screenplay formatting. The editor can apply the correct layout while preserving the semantic identity of every block.
What stays automatic
The formatting layer covers the recurring mechanics writers should not have to rebuild on every page:
- screenplay element layout for scene headings, action, character cues, dialogue, parentheticals, and transitions;
- keyboard movement and next-element behavior appropriate to a screenplay editor;
- pagination based on the structured document rather than arbitrary browser paragraphs;
- Hollywood and Asian presentation modes supported by the editor views;
- stable node identity so comments, AI tools, scene derivation, and collaboration can refer to the same block;
- structured output for PDF and Final Draft XML export services.
The editor deliberately does not treat formatting as permission to rewrite. Automatic indentation is tool work. Dialogue, action, rhythm, and dramatic choice remain writer work.
For a complete explanation of the industry rules themselves, read our screenplay format guide. This page explains how the product represents those rules.
Why typed elements matter beyond appearance
Plain text can look like a screenplay and still be structurally empty. If every line is just a string, the application must guess where scenes begin, which names are character cues, and which locations recur. Guessing becomes brittle as the draft changes.
Typed screenplay nodes make downstream behavior deterministic:
| Screenplay element | Product behavior it enables |
|---|---|
| Scene heading | Scene creation, scene order, location extraction, scene navigation, storyboard scope |
| Character cue | Character entity derivation and dialogue statistics |
| Dialogue and action | Correct page layout, targeted AI reads, line-level navigation, revision operations |
| Parenthetical and transition | Stable screenplay semantics during editing and export |
This is why the script structure view can remain connected to the page. It is also why the AI workspace can request a real scene or node instead of asking a language model to infer document structure from a pasted blob.
How AI interacts with the formatted draft
Laper's AI tools read compact representations of actual screenplay nodes. When an edit is approved, the browser applies screenplay operations through the editor. The change then follows the same Plate-to-Loro path used by human editing.
That path prevents a common AI-writing failure: the model returns a plausible-looking scene that loses element types when pasted back. In Laper, an AI operation can specify an action block, dialogue block, character cue, or other supported node deliberately. The editor remains the authoritative document.
There is an important boundary. The AI does not continuously “clean up” every line in the background. Unrequested rewrites would be destructive and would blur authorship. Formatting is automatic; text changes are explicit.
Pagination, import, and export are part of the document lifecycle
Screenplays leave the editor. They are read as PDFs, exchanged with Final Draft workflows, and sometimes imported from an existing draft. Laper includes dedicated PDF and FDX services rather than treating export as a browser print afterthought.
Structured export cannot guarantee that every third-party application's private behavior is identical, but it preserves far more intent than copying generated prose. The same typed nodes used for editing become the source for output.
If file formats are the immediate question, see Fountain versus FDX. If you are evaluating the whole workspace, continue to AI screenwriting software built around the script or open the screenplay editor overview.
The practical result
The best formatting feature is the one a writer stops noticing. Laper makes the screenplay page predictable so attention can stay on action, character, and causality. The format remains visible to the system—where it can power scenes, characters, AI tools, collaboration, and export—but quiet for the person writing.