Import your script
Open Fountain, Final Draft FDX, TXT, DOCX or text-based PDF. Scene headings establish the first pass.
Turn a screenplay into a structured production breakdown. Detect scene headings and speaking characters, review potential props, costumes, vehicles, extras and effects, and deliver a clean handoff to your crew.
YOUR PRODUCTION WORKSPACE
A practical breakdown assistant, not a substitute for production review.
Drop a screenplay here, or choose a file from your device.
TXT · Fountain · Final Draft FDX · DOCX · text-based PDF (up to 16 MB)
All screenplay analysis happens on your device. PDF import loads a free PDF.js parser from a third-party CDN only when needed; the PDF itself is processed locally. Image-only scanned PDFs need OCR first.
CURRENT SCREENPLAY
CONFIRMED FOR THIS SCENE
CHECK BEFORE ADDING
Keyword matches are suggestions—not verified objects or required production expenses.
CROSS-SCENE REFERENCE
One row per unique element, with scenes and planned quantities.
| Element | Category | Scenes | Count | Qty. total | Manage |
|---|
READY FOR YOUR TEAM
Export editable reports and preserve your reviewed production decisions.
PRODUCTION REVIEW
Advisory checks based on your edits. Review these before distributing production reports.
BREAKDOWN SNAPSHOT
| # | Scene heading | Confirmed | To review | Status |
|---|
Locations and dialogue cues are extracted by text rules. Other candidates are inferred from keywords and require human review. If an item is absent, add it manually. Estimated pages are approximate. Cast scene grids are not day-out-of-days scheduling reports, and the planning CSV is not an optimized shooting schedule or budget.
FROM SCRIPT TO SHOOT
Designed for indie filmmakers, assistant directors, line producers, production managers, film students and commercial crews.
Open Fountain, Final Draft FDX, TXT, DOCX or text-based PDF. Scene headings establish the first pass.
Verify likely scene needs, add missing items and edit quantities, notes and review status.
Download scene sheets and inventory CSVs or save the editable project to return to later.
It is a deterministic, rule-based screenplay parser. It does not use a paid AI service, large language model or generative AI. Ambiguous item mentions remain suggestions for a human to verify.
No. Text extraction and breakdown happen in your browser. PDF imports fetch PDF.js code from a third-party CDN on demand, but your document is parsed locally. Export files are saved to your device.
TXT and Fountain work natively. FDX and DOCX use browser XML/ZIP handling. Text-based PDFs require an internet connection for the free PDF.js parser; scanned or image-only PDFs require OCR before import.
Yes. Approve or dismiss candidates, add and edit scene elements, enter notes, and save a JSON project. CSV exports are useful for spreadsheets and production reports. The tool does not automatically save your screenplay to a server.
Processing screenplay…
Turn a screenplay into an editable scene breakdown with suggested cast and production elements. Review every suggestion against the source text, add shoot-day metadata and export production handoffs.
Example: Import a short Fountain script, check a suggested prop against the original scene excerpt, add a missing location manually, then export the scene and element CSV reports.
Limits and privacy: Parsing uses screenplay-format heuristics and does not create a complete or certified breakdown. Shoot-day summaries do not optimize availability, travel or rest. PDF.js assets are fetched from external hosts for text-PDF import and may disclose the visitor IP; scanned pages need separate OCR. There is no autosave, and saved projects contain screenplay text. Work is processed in the browser. PDF.js, DOCX/FDX import, print and the complete report set remain unverified.