Product — Script Editor

Your screenplay is the prompt.

Upload a Final Draft, PDF, or Fountain file. Induce reads every slug line, action cue, and line of dialogue — and converts your entire script into a shot-ready breakdown without a single text prompt written by you.

See the breakdown
FDX · PDF · Fountain · Plain text · No prompt engineering
/ SCRIPT → SHOT
EDITOR / 01·BREAKDOWN
— How it works

Induce reads your screenplay the way a line producer does. Every slug line becomes a scene. Every action cue becomes a shot. Every character auto-casts into a persistent continuity graph — before a single frame is generated.

Most AI video tools ask you to describe each clip in a text box. That workflow fails the moment your project has more than one scene — because nothing connects shot to shot. Induce treats the screenplay as the source of truth.

0Prompts you write manually
4Supported ingestion formats
L/LEvery line → its own shot
<10sFull-script breakdown time
— Supported formats

Upload the file you're already writing.

Every major screenwriting format supported. No conversion, no reformatting — drop in the file your final draft is saved as.

.fdx
Final Draft
Full document structure — slug lines, dual dialogue, scene annotations, production notes
Supported
.pdf
PDF Screenplay
Standard screenplay formatting detected — slug lines, action, character, dialogue parsed automatically
Supported
.fountain
Fountain Plain Text
Full Fountain spec — scene headings, action, character, dialogue, dual dialogue, lyrics, transitions
Supported
Paste
Plain Text / Draft
Paste any properly formatted screenplay text — Induce auto-detects the structure
Supported
— What gets read

Every element of your script. Nothing compressed.

Induce doesn't flatten your screenplay into a summary. It reads the document structurally — the same way production software does.

Scene Header
Slug Line
INT. POLICE PRECINCT — NIGHT
→ Scene node: interior, precinct, night
Shot Source
Action Paragraph
Marcus crosses the room, knocks twice.
→ Shot: medium, movement, tension beat
Character Line
Dialogue Exchange
MARCUS: "You weren't supposed to be here."
→ Shot: close-up, performance, Marcus cast
Performance Note
Parenthetical
(barely holding it together)
→ Emotion flag applied to shot parameters
Layout
Dual Dialogue
Side-by-side character columns
→ Two-shot or intercut sequence generated
Production Note
Scene Annotation
PRACTICAL FIRE · NIGHT EXT ONLY
→ Environment flag passed to generation model
— Key insight

Character names in action lines and dialogue are automatically cross-referenced. The first time Marcus appears on page 3, Induce seeds a character node that every subsequent scene — through page 94 — reads from.

— The breakdown architecture

Script → Scenes → Shots → Cut.

Four layers of structure — each one feeding the next.

01

Script ingestion — structure detected in seconds

Induce reads the raw file, identifies format, and applies the appropriate parser. Slug lines become scene anchors. Characters are extracted into a provisional cast list.

Ingestion
02

Scene breakdown — every beat, its own container

Each scene gets its own node: location, interior/exterior, time-of-day, characters present, emotional register, and dominant action.

Scene Map
03

Shot breakdown — line by line, nothing skipped

Within each scene, Induce converts action paragraphs and dialogue exchanges into individual shots with provisional camera, lens, and blocking parameters.

Shot List
04

Generation — models routed per shot, cut assembled

Each shot enters the generation queue, routed to the optimal model for its content type. You watch a first cut, not a folder.

Assembly
— Script-first vs. prompt-first

The difference a screenplay makes.

Every prompt-first tool puts the burden of story structure on you.

Prompt-first tools (Runway, Kling, Veo direct)

One clip. One prompt. No memory.

Write a prompt. Get a clip. Write the next prompt — describing the same character, the same location, the same tone — all over again. Nothing carries forward.

Script-first (Induce)

One upload. Every shot. Full continuity.

Upload your screenplay once. Induce reads the whole story — casts the characters, maps the locations — and generates every shot from the same source of truth.

— Frequently asked

Script editor questions answered.

— Next in the pipeline

Breakdown is the start. Continuity is what holds it together.

Once Induce has your shot list, the Continuity Engine locks every character, wardrobe detail, location, and mood across the whole cut — so your protagonist looks the same in scene 40 as they did in scene 1.

— Upload your script

Stop prompting.
Start writing.

Upload a screenplay. Induce does the rest — breakdown, continuity, direction, and a first cut that's ready to refine.

Back to overview
Free beta · No credit card · Commercial rights included