Scene Extractor
Mini location list generator
Production assistants and screenwriters waste hours listing every location in a film. Paste your full script below. The tool detects each line starting with INT., EXT., I/E., or INT/EXT. (scene headings) and outputs a clean, alphabetically sorted list of all locations,ready to copy into Excel or a breakdown sheet.
This free scene heading extractor is designed for people in pre‑production who need a fast, reliable way to list every location in a script. Instead of scrolling through a PDF and manually copying sluglines by hand, you paste the screenplay here and get a ready‑to‑use list of locations in seconds.
The Scene Extractor scans your screenplay line by line, looks for standard scene headings (INT., EXT., I/E., INT/EXT.), and pulls them into a single, deduplicated list. It’s a lightweight script breakdown helper for location lists, shooting schedules, and call sheet prep.
Everything runs in your browser. No script pages are uploaded or stored anywhere. A small JavaScript loop searches for exact prefixes (INT., EXT., I/E., INT/EXT.) at the start of each line, normalizes spacing, removes duplicates, and sorts the result A–Z.
How this free scene heading extractor works
- Paste your full screenplay (or a specific act/episode) into the text area above. PDF exports converted to text and Fountain files both work as long as scene headings start with INT., EXT., I/E., or INT/EXT.
- The tool loops over every line and checks whether it begins with one of these prefixes. Matching lines are treated as scene headings, normalized (extra spaces removed), and stored in a set so duplicates are removed.
- The final list is sorted alphabetically and displayed in a second text area, one scene heading per line, ready to copy into Excel, Google Sheets, or any script breakdown software.
Who this script breakdown helper is for
- Assistant directors and production assistants building location lists and early shooting schedules.
- Screenwriters doing a quick pass on their own script to see how many locations they have and how often they repeat.
- Indie filmmakers who don’t yet have a full breakdown suite but still need a clean, exportable list of every scene heading.
Best practices for getting clean location lists
- Use standard slugline format: INT., EXT., I/E., or INT/EXT., followed by the location and time of day (e.g. “INT. APARTMENT: NIGHT”).
- Keep the location name consistent across the script (e.g. always “APARTMENT” instead of sometimes “JULIE’S APARTMENT”). This makes grouping scenes by location much easier later.
- If a scene can be played in multiple spaces, consider whether it should be written as separate scene headings for production clarity.
- After exporting the list into Excel, add columns for set type (INT/EXT), day/night, location category, and whether the location is practical or built.
From script to shots,in one place.
熙熙 turns your screenplay into an automatic shot breakdown, then a storyboard. Characters, locations and references carry from shot to shot.
- 免费, does not expire
- PDF and Final Draft export
- Mac, Windows, Linux, iPad
Scene Extractor: the complete guide
It extracts and deduplicates sluglines so location planning starts from a clean data base instead of manual copy/paste—eliminating the risk of duplicate entries or overlooked location variations across revisions.
For this workflow, the central problem is clear: manual location extraction from scripts is slow, error-prone, and difficult to maintain through revisions, especially when scene headings are reformatted or new INT./EXT. variations are introduced mid-draft. Left unresolved, this creates downstream friction in department handoffs and slower location-scouting decisions. The practical target is a clean, version-controlled location list that accelerates pre-production planning, streamlines spreadsheet-based breakdown workflows, and ensures production designers and location managers are working from the same canonical set of scene headings.
Limitation to keep in mind: It depends on consistent heading conventions—proper INT./EXT. prefixes, standard time-of-day markers like DAY or NIGHT—and will not infer malformed or non-standard sluglines reliably, such as abbreviated shorthand or prose-style action lines mistaken for scene headings.
Advanced workflow: Pair extracted location lists with scene counts and day/night tags to generate early schedule clusters before locking shooting order, allowing you to group practical locations by availability windows, daylight requirements, and cast schedules in preliminary stripboards.
Step-by-Step Workflow
- Paste the latest draft and confirm standard slugline prefixes are used consistently across scenes.
- Generate the list, then normalize naming variants to avoid duplicate location buckets.
- Tag each location with production metadata such as set type, day/night load, and logistics complexity.
- Re-run after structural changes so planning data stays synchronized with the latest draft.
Use Cases By Profile
- Writer: quantify location sprawl before rewrite lock.
- AD team: seed location breakdown spreadsheets in minutes.
- Producer: evaluate location complexity risk early.
Common Mistakes To Avoid
- Inconsistent slugline naming that multiplies duplicate entries.
- Treating extracted data as final without normalization.
- Skipping re-extraction after major rewrite passes.
Professional Best Practices
- Standardize naming conventions before sharing with production.
- Use location clusters to identify scheduling efficiencies early.
- Maintain a master breakdown sheet linked to draft versions.
Treat this tool output as a decision support layer, not a replacement for authorship or the creative judgment that defines your voice. Great scripts are remembered for specific choices, emotional precision, and clarity of dramatic movement—the accumulation of intentional beats that build character arc and escalate conflict. Tools help by removing noise so your energy can go where it matters: character behavior under pressure, conflict geometry, escalation tempo, and payoff that lands with thematic weight. If you review outcomes after each pass and keep an explicit log of accepted changes with brief rationale notes, your workflow becomes faster and more predictable from draft to draft, and you preserve an audit trail that clarifies which structural shifts were deliberate versus automated. That consistency is exactly what professional collaborators value: fewer surprises, clearer rationale for revision choices, and a script that evolves with intent rather than drift.
Extended FAQ
Can this replace a full location breakdown?
No. It accelerates the extraction workflow, but humans still need to normalize naming conventions and manually add production categories afterward.
What causes duplicate locations most often?
Inconsistent slugline naming across multiple drafts, such as alternate labels or different phrasings for the same location.
Should I extract before or after rewriting?
Both approaches serve distinct purposes. Early extraction reveals the overall scope and resource requirements; post-rewrite extraction ensures planning data stays current with script changes.
How do I prep results for scheduling?
Add columns for interior/exterior designation, day/night timing, practical location versus set build, and logistical complexity rating.
Can this work for episodic scripts?
Yes. The same heading logic and slugline parsing rules apply equally to pilots and episodic scripts when sluglines are standardized.
What is the best QA step after extraction?
Before finalizing your location distribution list, manually review the most frequently appearing locations in your extraction results and consolidate any naming variants—such as merging "COFFEE SHOP" and "COFFEE SHOP - DAY" into a single canonical entry—to ensure accuracy and consistency across your breakdown.
FAQ: scene heading extractor & script breakdown
A scene heading extractor is a specialized utility designed to parse through your screenplay and automatically identify scene headings—commonly referred to as sluglines—such as "INT. HOUSE - DAY" or "EXT. STREET - NIGHT". Once the scan is complete, it generates a compiled list of all those headings, allowing you to review every location mentioned in the script at a glance, without the need to manually read through the entire document line by line.
The accuracy of the extraction hinges on how consistently your screenplay adheres to industry-standard formatting conventions. When every scene heading starts with INT., EXT., I/E., or INT/EXT., the tool will reliably detect and list them. However, if your script contains headings written in non-standard formats or with inconsistent capitalization and punctuation, some locations may be overlooked entirely, or the same location may appear multiple times under slightly different names in the output.
Yes, with one caveat. The Scene Extractor gives you a fast, alphabetized list of all scene headings found in your script. It is ideal as a starting point for a location breakdown, but you will still need to clean labels manually, merge any duplicate entries, and assign production categories (set, practical location, VFX‑heavy) in your spreadsheet or production software.
Absolutely. The extractor doesn't care about total page count or act structure. You can paste a feature screenplay, a pilot, an anthology episode, or a short film script. As long as scene headings use standard prefixes (INT., EXT., I/E.), the tool will generate a location list for any format.
No. The Scene Extractor runs entirely in your browser. The JavaScript that finds sluglines and builds the location list executes locally on your device, and no script pages are sent to a server or stored anywhere.