# Laper AI Screenwriting Software · Complete Reference > Laper is script-first AI screenwriting software. It combines automatic screenplay formatting, explicit AI reading and editing tools, Loro CRDT project synchronization, story planning views, and optional visual development while the screenwriter keeps creative authority. This is the comprehensive LLM-readable reference. For the short index, see [llms.txt](https://laper.ai/llms.txt). --- ## Product Overview - **Name**: Laper - **Category**: AI Screenwriting Software / AI Script Writer / Screenplay Editor - **Website**: https://laper.ai/ - **Founded**: 2024 - **Platforms**: Web, macOS desktop, Windows desktop - **UI locales**: 16 - **Pricing currency**: USD The screenplay editor is the source of truth. Scene headings determine scene order and feed location entities; character cues feed character entities. Beats, props, character relationships, scouting information, generation tasks, assets, and storyboard shots live beside the same document instead of becoming a second screenplay database. ## Verified Product Systems ### Typed screenplay editor - Plate-based screenplay nodes preserve element identity for scene headings, action, character cues, dialogue, parentheticals, transitions, pagination, and export. - PDF and Final Draft XML export services use the structured document. ### Structured AI context - Browser-side tools read explicit cursor, outline, scene, range, node, or full scopes. - Full mode is bounded to 800 screenplay nodes and reports truncation; longer drafts use outline plus targeted scene reads. - Approved AI edits execute through the active Plate editor and follow the normal Loro document path. - Laper does not claim that every request always contains a 200K-token or unbounded full screenplay. ### Loro collaboration - Project CRDT state synchronizes through a worker and dedicated lorosync WebSocket service. - Screenplay conflict granularity is node-level: different blocks synchronize independently; the same paragraph resolves at the node value boundary. - Existing projects require a server-first online initial sync before the editor becomes writable. An already-open project can retain pending local updates during a transient disconnect and synchronize after reconnect. - Supabase Realtime does not synchronize screenplay or CRDT data. ### Story and production views - Scenes and locations derive from scene headings; characters derive from character cues. - Character board, relationship graph, and casting table project shared character data. - Beats, props, locations, scenes, and storyboard shots are first-class project entities with specialized views. - AI media generation uses durable task and asset records. The API backend owns authorization, credits, status, retries, refunds, and persistence; the generation worker performs model calls and uploads. ### Open screenplay community - Only intentionally published public projects enter community discovery. - Public reading and comment listing are available through public services; authenticated members can comment, like, unlike, and copy when permissions allow. - Copying creates a separate project and does not edit the author's original. ## Current Pricing | Plan | Monthly | Annual | |---|---:|---:| | Junior | $0 | $0 | | Senior | $20 | $192 | | Elite | $60 | $576 | | Master | $100 | $960 | | Legend | $400 | $3,840 | Annual prices equal 80 percent of twelve monthly payments. Credit and project allowances are server-driven; use [Pricing](https://laper.ai/pricing/) for current plan details. ## Product Boundaries - AI is optional assistance, not an autonomous replacement for the screenwriter. - The official Script Doctor mode diagnoses before prescribing and is instructed to protect writer intent. - A full AI script read has a real 800-node boundary; it is not an unbounded context guarantee. - Project opening is server-first and needs connectivity; Laper does not advertise unrestricted offline opening. - Community visibility is explicit; private and invite-only projects are not public library content. - Competitor comparisons should acknowledge that Final Draft, WriterDuet, and Celtx each center different established workflows. ## Contact - Website: https://laper.ai/ - Email: support@laper.ai - Twitter / X: https://x.com/liangshizhi - Discord: https://discord.gg/UgUNCawXkW --- ## Product Tutorials (34) Source-backed guides for Script and Cinema projects, AI collaboration, production, permissions, and account workflows. ### What Laper is **URL**: https://laper.ai/docs/getting-started/introduction/ **Category**: Getting started Understand the two project types, the source-of-truth model, and where each kind of work belongs. ## The product in one minute Laper is a collaborative workspace for screenwriting and film pre-production. It has two project types: - A **Script project** is for screenplay text, outline, beats, derived scenes, characters, locations, props, shots, reference material, and collaboration. - A **Cinema project** is for turning short dramatic units into visual production pipelines: scene design, performance, shot design, storyboard images, and finished clips. Both project types use the same project list, episode navigation, collaboration layer, and offline-capable document foundation. Their creative data models remain separate, so a Cinema reel is not secretly a screenplay scene and a screenplay scene is not a video task. ## The screenplay is the source of truth In a Script project, structured data follows the screenplay. A scene heading creates or updates a scene and its location. Character cues create or connect character records. This matters because you should fix a wrong scene at its source: edit the scene heading in the script instead of trying to create a disconnected scene card elsewhere. Outline and beats help plan the story, but they do not replace the screenplay. They can change before the script, and the AI assistant may maintain them while working, yet the text remains the authoritative record of what is actually written. ## Project data and episode data Screenplay text, outline, beats, scenes, and shots belong to an episode. Characters, locations, props, worldview, knowledge files, and hired advisors are shared by the whole project. Moving between episodes changes your own view only; it does not force collaborators to follow you. ## AI is a collaborator, not a second document system Laper's AI reads the relevant project context and proposes or performs actions through the same browser workspace you use. Script edits ultimately enter the same collaborative document as keyboard edits. In read-only access, write actions are unavailable. Worldview changes require an explicit request in your latest message. Use the mental model throughout these tutorials: **write facts at their source, use derived views to inspect them, and use AI with a clear target and scope.** --- ### Quick start: idea to first scene **URL**: https://laper.ai/docs/getting-started/quick-start/ **Category**: Getting started Create a Script project from a premise, review the AI plan, and reach a clean first scene without losing control. ## Start with a useful brief Open **New project** and describe the story you want to make. A productive brief gives the assistant four things: 1. The protagonist and what they want. 2. The force opposing them. 3. The intended format or scale, such as a short film or episodic series. 4. A tonal or thematic constraint you care about. You may attach DOCX, PDF, TXT, or Markdown reference files. Attachments are context for the opening conversation; they are not automatically copied verbatim into the screenplay. ## Let the project open before judging the result Laper creates the project, opens its collaborative document, then starts the initial AI turn after the document and local cache are ready. The assistant may establish a title, outline, beats, core characters, locations, and opening scenes in stages. The exact order can vary as the writing agent evolves, so evaluate the resulting story structure rather than expecting a rigid wizard. ## Review in the right places - Read **Outline** for the overall dramatic promise and sequence. - Read **Beats** for turning points and units of change. - Return to **Script** to judge what is actually on the page. - Open **Characters** and **Locations** to check the entities derived or created for the project. If the direction is wrong, correct it early: “Keep the isolated lighthouse, but make the protagonist the missing keeper's daughter. Revise the outline only; do not write new scenes yet.” A bounded correction is safer than asking the AI to redo everything. ## Write the first scene deliberately Ask for a specific scene goal, conflict, and exit condition. For example: “Write the opening scene in the current episode. Establish the storm through filmable action, let Mara hide why she came, and end when the radio says her own name.” After the scene appears, inspect the scene heading, action, character cues, and dialogue. Fix structural mistakes at the text source. Use version history before a large experiment, and keep requests small enough that you can compare intention with result. --- ### Create a project or import Final Draft **URL**: https://laper.ai/docs/getting-started/create-and-import/ **Category**: Getting started Choose the correct project type, start from an idea, or import a supported FDX screenplay safely. ## Choose the project type first Create a **Script project** when the screenplay and its derived production information are your foundation. Create a **Cinema project** when you want to build visual reels and generated clips through a production pipeline. They are peer document types; one is not a view inside the other. The idea-first Script flow does not offer Blank, Three-Act, or Character-First templates. It accepts a written brief and optional reference files, then opens a normal editable project. You remain free to change the structure at any point. ## Import a Final Draft screenplay Use the import entry when you already have an `.fdx` file. Laper accepts Final Draft documents whose document type is **Script**. It reads screenplay paragraphs, converts supported paragraph types into Laper editor nodes, and derives project entities from the result. During import: - Scene headings are parsed into interior/exterior, location, and time-of-day data when possible. - Character cues are normalized so recurring names connect to the same character. - Locations and scenes are created from screenplay structure, not from a separate spreadsheet. - A progress overlay stays visible while the new project, entities, and script are written. Very large imports are limited by the temporary browser handoff used while opening the new project. If an import is rejected, simplify embedded metadata in Final Draft or split the document before retrying. ## What is not supported Cinema projects do not import FDX. Non-script Final Draft document types are rejected. Import is not a round-trip merge into an existing project; it creates a project and writes the imported screenplay into that new document. After import, check several scene headings, recurring character names, and unusual paragraph styles before continuing. The safest workflow is to correct conversion edge cases immediately, then name a version in history as your clean imported baseline. --- ### Navigate the workspace and episodes **URL**: https://laper.ai/docs/getting-started/workspace-and-episodes/ **Category**: Getting started Learn the three-column project shell, dimension navigation, episode scope, and local viewing behavior. ## Read the workspace from left to right A project uses a consistent editor shell: - The narrow navigation rail switches dimensions such as Script, Outline, Characters, Storyboard, or Assets. - The project panel contains the project title, episode list, project actions, and dimension-specific controls. - The central area displays the current editor, board, table, or canvas. - The AI panel floats above the workspace and can be moved or resized without becoming part of the document. Some dimensions offer more than one view. Characters can use a board, network, or casting table; scenes can use a canvas or table; assets can use a generation canvas or task list. Changing a view changes presentation, not the underlying entity. ## Know what changes with an episode In Script projects, screenplay text, outline, beats, scenes, and shots are episode-specific. Characters, locations, props, worldview, knowledge files, and advisors stay shared across the project. In Cinema, reels are episode-specific while characters, props, production settings, and tasks are project-level. When you switch episodes, only your own local route and document binding change. A collaborator can stay in episode 1 while you work in episode 4. This prevents routine navigation from dragging the whole room around. ## Create, rename, and remove episodes carefully Use the episode controls in the project panel. A newly created episode becomes your active episode and opens at a predictable primary dimension. Renaming changes the shared episode label. Removing an episode affects its episode-level screenplay or reels, so confirm the target and preserve a history version before destructive restructuring. ## Understand connection indicators Presence and connection indicators distinguish synchronized collaboration from local editing. Temporary disconnection does not create a second project; edits can remain in the local document layer and synchronize when the connection recovers. Avoid opening duplicate tabs to “force” a save. Let the connection state settle, and use history or export for explicit checkpoints. --- ### Script editor overview **URL**: https://laper.ai/docs/script-editor/overview/ **Category**: Script editor Understand cover and screenplay views, screenplay node types, derived entities, and safe editing habits. ## Cover and screenplay are two views The Script dimension contains the title-page cover and the screenplay editor. Cover fields describe the document; screenplay nodes describe the film. Keep marketing notes and planning prose out of the screenplay when they cannot be represented on screen. ## Screenplay structure is semantic Laper does not treat a script as a plain rich-text document. Paragraphs have screenplay roles such as scene heading, action, character, dialogue, parenthetical, transition, and related production forms. Their roles drive formatting, navigation, entity derivation, and export. A scene heading is especially important. Editing it can update the scene's location and time context. A character cue can connect dialogue to a project character. If you paste text as undifferentiated action paragraphs, those relationships cannot be inferred reliably. ## Use the cursor as context The current selection and cursor give both the interface and AI a precise working range. Select the lines you want revised when the request concerns exact wording. Leave a collapsed cursor inside a scene when the request concerns that scene. Name a different episode or scene explicitly when the target is not visible. ## Keep changes reviewable Prefer one dramatic purpose per edit. Ask the AI to preserve named lines, characters, or beats when they must survive. After a large insertion, verify: - the new scene is in the intended episode and order; - headings contain the correct location and time; - character cues use existing identities where appropriate; - action remains filmable rather than explaining private thoughts; - the outline still matches the actual sequence. Collaborative edits enter the same document whether made by keyboard or AI. Version history is the right checkpoint before a wide rewrite; a second copy of the browser tab is not. --- ### Format screenplay text **URL**: https://laper.ai/docs/script-editor/formatting/ **Category**: Script editor Apply semantic screenplay paragraph types and write action, dialogue, and transitions that export cleanly. ## Format by meaning, not appearance Choose a paragraph type because of what the line does in the screenplay. Do not imitate screenplay layout with spaces, manual centering, or repeated blank lines. Semantic formatting survives editing, collaboration, and export. - **Scene heading** establishes interior/exterior, place, and time. - **Action** describes visible or audible events in present tense. - **Character** identifies the speaker. - **Dialogue** contains the spoken line. - **Parenthetical** gives a brief playable qualification, not an essay. - **Transition** describes a deliberate editorial transition when it is truly needed. ## Write headings consistently Use a stable location name when returning to the same place. Small spelling differences can produce confusing location records. If a location is intentionally distinct, make that distinction clear in the heading, such as `WAREHOUSE - LOADING BAY` versus `WAREHOUSE - OFFICE`. ## Keep action filmable Replace internal explanation with observable behavior. “Jon is ashamed of lying” cannot be photographed; “Jon folds the unopened letter into a square and hides it under his tongue” can. Short action blocks help readers see rhythm and help the AI reason about scene beats. ## Use dialogue structure correctly Enter a character cue before dialogue so Laper can associate the speech with the character. Use parentheticals sparingly and keep performance choices playable. If a speaker name includes a delivery modifier in an imported script, review the normalized character identity so the modifier does not become a duplicate person. ## Choose the project format separately Project format settings control Hollywood or Asian screenplay presentation. They are not a substitute for semantic paragraph types. Change format when the production convention changes, then review page breaks and export rather than manually reformatting every paragraph. --- ### Use the timeline and project settings **URL**: https://laper.ai/docs/script-editor/timeline-and-settings/ **Category**: Script editor Track approximate runtime, move through the script, and configure project, format, and AI settings. ## The timeline is a reading aid The script timeline follows your cursor and estimates position using the common rule of roughly one screenplay page per minute. It is a read-only navigation and coverage aid, not a video-editing timeline. Zoom changes how much of the script you can inspect; it does not change screenplay length or clip duration. Use it to notice density, long uninterrupted scenes, and where the current cursor sits in the episode. Confirm actual production runtime through rehearsal and edit decisions rather than treating the estimate as a guarantee. ## Project settings have three scopes Open project settings from the project actions menu: - **Project** contains the shared project identity and relevant metadata. - **Format** controls screenplay presentation conventions, including Hollywood or Asian output behavior. - **AI** shows project-level AI-related settings and usage information exposed by the current product. These are project settings, not account preferences. Your account language and theme live in global Settings and do not rewrite the shared project. ## Use settings before a delivery pass Before exporting, confirm the title and format, then scan representative scene headings, dialogue blocks, and page breaks. A format switch can change pagination, which also changes the timeline's approximate runtime. Name a history version before a major format or structural pass so you can compare rather than guess. ## Avoid stale assumptions Older projects may contain fields that are no longer shown in the current settings UI. Follow the visible Project, Format, and AI tabs instead of tutorials that mention removed project-type or target-duration controls. The screenplay and its current format remain the authoritative delivery inputs. --- ### Export scripts and outlines **URL**: https://laper.ai/docs/script-editor/export/ **Category**: Script editor Select episodes, choose a screenplay convention, and export only the formats Laper currently supports. ## Choose what to export Open Export from the project actions. Choose **Script** or **Outline**, then select one or more episodes. When several episodes are selected, Laper merges them in the order shown in the export selection. Review that order before generating the file. ## Supported formats Script export supports two presentation conventions: | Content | Convention | File formats | | --- | --- | --- | | Script | Hollywood | PDF, DOCX, TXT, FDX | | Script | Asian | PDF, DOCX, TXT | | Outline | Not screenplay-formatted | PDF, DOCX, TXT | Fountain export is not currently available. FDX export is available for Hollywood script output, not for outlines or Asian output. ## Prepare a clean delivery 1. Confirm episode names and selected order. 2. Check the project title and screenplay format. 3. Inspect scene headings and character cues; exports can only preserve structure that exists in the editor. 4. Generate the file and open it in the target application. 5. Keep a PDF as a stable visual reference when exchanging an editable DOCX or FDX. Export availability can depend on membership and project permissions. A Viewer can export only when the project owner allows Viewer export in the sharing configuration. If the control is unavailable, verify both your role and the project's access setting. ## Export is a snapshot, not synchronization Editing an exported file does not update the Laper project. Importing FDX creates a new project rather than merging changes back into an existing document. Use collaboration for live work, version history for checkpoints, and exports for delivery or external review. --- ### Build and maintain the outline **URL**: https://laper.ai/docs/story-structure/outline/ **Category**: Story structure Use the Markdown outline as a structural contract, edit it incrementally, and keep it aligned with the screenplay. ## What the outline is for The Outline is a persistent Markdown story plan for the current episode. It is the right place for acts, sequences, turning points, scene intentions, and causal progression. It is not the screenplay and does not automatically become formatted scenes. A useful outline tells you what changes, why the next unit follows, and what pressure increases. Avoid a list of unrelated events. Use headings to make the hierarchy readable and concise bullets or paragraphs to express dramatic movement. ## Edit incrementally When a direction changes, update the affected section rather than replacing the whole outline. Whole-document replacement is appropriate only for an empty outline or a clearly confirmed reset. Incremental edits preserve accepted structure and make collaboration easier to review. Good requests name both scope and invariants: > Revise the second sequence only. Keep the ferry accident and the final reveal. Make each beat a consequence of Mara hiding the radio message. ## Align structure with pages Before writing several new scenes, confirm the relevant outline segment. After screenplay edits, return to the outline and update any promise that is no longer true. The AI assistant is designed to read structure before broad writing, but you should still verify that the final outline reflects the actual episode. ## Separate shared facts from episode structure Character identity, locations, props, worldview, and knowledge files are project-level. The outline may refer to them, but it does not own them. Put durable rules such as “time runs backward inside the archive” in Worldview, source research in Knowledge, and the episode-specific consequences in the Outline. --- ### Plan with beats **URL**: https://laper.ai/docs/story-structure/beats/ **Category**: Story structure Use episode-level beats to express dramatic change without confusing them with scenes or screenplay paragraphs. ## Beats are units of change A beat records a meaningful shift: a decision, reversal, discovery, escalation, or new obstacle. Beats belong to the current episode and can be arranged or reviewed as a list. They help test progression before the screenplay is fully written. Do not use beats as duplicate scene records. One scene may contain several beats, and one planned beat may later require more than one scene. Scenes are derived from screenplay headings; beats are planning entities. ## Write actionable beats A strong beat identifies cause and result. “Mara investigates” is vague. “Mara plays the damaged tape to prove the voice is fake; the tape answers with a secret only her father knew” contains an action, intent, and reversal. Arrange beats so pressure accumulates. If two beats can swap places without changing the story, the causal chain may be weak. Use the outline for higher-level structure and beats for the sequence of dramatic changes inside that structure. ## Work with the AI assistant Ask the assistant to read the current outline and beats before proposing changes. Specify whether it may edit beats or should only advise. For example: > Read episode 2's outline and beats. Identify the three beats with no causal link. Suggest replacements, but do not edit yet. After approval, request a bounded update. Broad structural rewrites should keep the outline and beats consistent before expanding into screenplay pages. ## Check the result against the script Beats are plans, not proof. Once scenes are written, verify that each promised change is visible in action or dialogue. Delete obsolete beats or revise them rather than leaving a second, contradictory version of the episode. --- ### Work with derived scenes **URL**: https://laper.ai/docs/story-structure/scenes/ **Category**: Story structure Inspect scene cards and tables, fix scene metadata at the screenplay source, and avoid disconnected scene records. ## Scenes come from scene headings Laper derives the Scenes dimension from `scene_heading` nodes in the screenplay. This is why there is no normal “create scene” button in the scene database: creating a detached record would let the project disagree with its own script. To create a scene, insert a properly formatted scene heading in the screenplay. To rename a location, change the heading. To remove a scene, remove or convert the corresponding scene-heading structure after checking its contents. ## Use canvas and table views The scene canvas is useful for spatial review and visual grouping. The table is useful for scanning structured attributes and comparing many scenes. Both are projections of the same episode data; moving between them does not duplicate anything. ## Keep headings stable Consistent headings help Laper associate repeat locations. Review imported headings that contain unusual dashes, prefixes, or combined location names. If two headings refer to the same set, normalize them in the script. If they represent distinct production spaces, name the distinction intentionally. ## Ask AI to work at the source A request such as “add a scene card” is underspecified. Say where the scene belongs, what it must accomplish, and ask the assistant to insert screenplay nodes in the target episode. It should read the surrounding scene order and use real project identities instead of guessing. When reordering, treat the screenplay order as authoritative. Verify transitions, setup/payoff, and outline alignment after the move. The scene view should then update from the document rather than requiring a second manual edit. --- ### Separate knowledge, worldview, and story structure **URL**: https://laper.ai/docs/story-structure/knowledge-and-worldview/ **Category**: Story structure Store research and durable story rules in the right project-level systems without bloating the outline. ## Three different jobs - **Outline** describes episode-specific dramatic progression. - **Knowledge** stores source material and reference documents the assistant can inspect. - **Worldview** stores concise project-level key/value rules such as technology limits, political systems, or a central premise. Keeping these roles separate reduces contradictions. A research PDF should not be pasted into the outline; a one-sentence world rule should not require reopening a forty-page file every time. ## Build a useful knowledge library Give files clear names and keep each source focused. The assistant first sees a knowledge index and can then list, search, inspect metadata, or read relevant bodies. It does not need every file injected into every turn. In a request, name the source or fact you expect it to consult. ## Use worldview as durable constraints Worldview is a flat set of fields. Official templates add only missing fields and never overwrite existing values. You can edit values in the interface; changes save after a short quiet period. The AI treats worldview as read-only unless your **latest message explicitly asks it to write specific values**. “Keep this in mind” is not permission to change the project. A safe request is: “Set `communication_delay` to `Messages take nine years between colonies` in Worldview.” The assistant may set values, but it cannot delete keys or silently fill the template. ## Promote facts deliberately Research becomes a project rule only after you decide it should. A project rule becomes plot only when an episode outline or scene applies it. This flow keeps evidence, design decisions, and dramatic execution traceable. --- ### Create and maintain characters **URL**: https://laper.ai/docs/cast-crew/characters/ **Category**: Cast & production entities Use character records as project-wide identities across screenplay cues, boards, relationships, and casting. ## Characters are shared identities A character belongs to the project, not a single episode. The same identity can appear in screenplay cues, relationship views, casting tables, storyboards, and AI context across the series. Character records may be derived when properly formatted character cues appear in the screenplay, and they can be enriched in the Characters dimension. Keep the canonical name stable. Dialogue modifiers such as voice-over or continued speech describe delivery; they should not become separate people. ## Choose the right view - The **canvas** is useful for visual organization and character cards. - The **network** emphasizes relationships between characters. - The **casting table** is useful for structured casting and production review. These views share one underlying identity. Editing a name affects references across episodes, so confirm broad renames with collaborators and review screenplay cues afterward. ## Give the AI enough identity For a new character, describe dramatic function, concrete behavior, pressure, and relationships—not only adjectives. Ask the assistant to read existing characters before creating one so it does not duplicate a nickname or alternate spelling. For a rewrite, name the real project character and the target episode or scene. A useful request is: “In the selected scene, sharpen Nia's evasiveness without changing Sol's lines or creating a new character.” ## Keep biography subordinate to drama Character detail is valuable when it changes choices, speech, costume, blocking, or conflict. Avoid accumulating biography that never affects the film. Use Knowledge for long research, Worldview for setting rules, and the character record for information needed to write and produce this person consistently. --- ### Use the casting table **URL**: https://laper.ai/docs/cast-crew/cast-list/ **Category**: Cast & production entities Review project-wide characters as production records and keep casting information connected to story identities. ## One list for the whole project The casting view presents the same project-level characters used by the screenplay and character boards. It is not a separate contact database. This prevents a performed role from drifting away from the identity used in scenes and dialogue. Use the table to scan structured character information, compare roles, and prepare casting discussions. Use the character canvas when images and spatial grouping matter, and the relationship network when dramatic connections matter. ## Prepare before casting review 1. Normalize recurring character names in the screenplay. 2. Merge or correct accidental duplicates before attaching production decisions. 3. Add only details that help casting, wardrobe, performance, or scheduling. 4. Verify which episodes and scenes actually use the character. Because characters are shared across episodes, a rename or deletion has project-wide consequences. Confirm destructive changes and use version history before a major cleanup. ## Work with images responsibly Character image generation and look development can attach visual assets to the character. Treat generated images as references, not proof that casting or rights are cleared. Keep the chosen image aligned with the written character and the project's visual direction. ## Keep permissions in mind Editors and above can update shared production data. Viewers can inspect but not rewrite character records. A creative craft label shown beside a collaborator is informational and does not grant casting or editing authority. --- ### Map character relationships **URL**: https://laper.ai/docs/cast-crew/relationships/ **Category**: Cast & production entities Model dramatic relationships without replacing the scenes that demonstrate them. ## Relationships describe project-wide connections The relationship network links existing character identities and helps you inspect alliances, conflicts, obligations, and changes across the project. It is a planning and review surface; the screenplay must still dramatize the relationship through action and dialogue. Create relationships between canonical characters rather than duplicating a person to represent a new phase. Name the connection in a way that explains pressure, not just category. “Sisters” is factual; “younger sister protecting the secret that could exile Mara” is dramatically useful. ## Use the network to find weak structure Look for central characters with no active pressure, relationships that never reach a scene, and several characters serving the same function. Compare the network with the outline and episode beats. A visually dense network is not automatically a rich story. ## Ask AI to analyze before editing The assistant can read characters and relationships. Ask it to identify contradictions or missing dramatic exchanges before requesting changes. For example: > Read the current character network and episode 1 outline. Which relationship is asserted in data but never tested on screen? Suggest one scene adjustment; do not add a character. Renaming or deleting a shared character can affect relationships and references across episodes. Make those changes deliberately, preferably after naming a history version. --- ### Manage locations and scouting **URL**: https://laper.ai/docs/cast-crew/locations/ **Category**: Cast & production entities Keep screenplay-derived locations consistent, organize them visually, and enrich them for production. ## Locations start in the screenplay Location identities are derived from scene headings. Consistent headings help recurring places resolve to the same project entity. Correct spelling and naming at the screenplay source before adding extensive scouting or visual data. ## Use the available views The location canvas supports visual organization. Network and grouping views help understand related spaces. The scouting table supports structured production review. All views describe the same project-level locations shared by every episode. ## Separate story place from production place A story location may later map to a real shooting location, set, or virtual environment. Keep the dramatic identity stable while enriching it with scouting details. If one dramatic location requires several production spaces, name and group them clearly instead of overloading one ambiguous record. ## Give AI filmable constraints When asking for a location or scene, specify observable constraints: scale, access, time, weather, light, sound, geography, and what the characters can or cannot do there. Ask the assistant to read existing locations first so a new scene does not introduce an accidental duplicate. ## Review after imports and renames FDX import parses common interior/exterior prefixes, dashes, and time labels, but screenplay conventions vary. Review unusual headings after import. A location rename can affect many episodes, so use version history and coordinate the change with collaborators. --- ### Track props and costume-relevant objects **URL**: https://laper.ai/docs/cast-crew/props-costumes/ **Category**: Cast & production entities Maintain project-wide props, connect them to story use, and generate visual references without duplicating facts. ## Props are project-level entities Props are shared across episodes and appear in a canvas and list. Use one canonical record for a recurring object, then describe variations or states clearly. Avoid creating a new prop each time the same object changes hands. Laper's current module is a prop system rather than a complete wardrobe department. Costume-relevant objects and visual notes can be tracked where useful, but do not assume a hidden costume breakdown workflow beyond the visible fields and project views. ## Make props dramatic and producible Record why the object matters, who controls it, visible states, continuity requirements, and any production constraint. “Old key” is weak; “brass archive key, tooth three filed flat, carried by Mara until scene 18” is actionable. ## Use AI and generated images deliberately The assistant can read and edit prop entities when you have write access. Ask it to reuse existing props and name the episode or scene where the change belongs. AI prop images are reference assets; verify scale, material, continuity, and rights before production. ## Audit continuity Compare props with screenplay scenes and beats. Check entrances, transfers, damage, and payoffs. Because props are shared across the project, a deletion or rename can affect later episodes. Preserve a history checkpoint before broad cleanup and fix story usage in the screenplay rather than relying on the prop card alone. --- ### How the AI assistant works **URL**: https://laper.ai/docs/ai-assistant/overview/ **Category**: AI assistant Use project-aware AI without treating chat as a separate copy of your screenplay. ## One assistant, two project contexts Script and Cinema projects use different writing agents because their creative units are different. The Script assistant works with screenplay nodes, outline, episodes, entities, worldview, knowledge, and shots. The Cinema assistant works with reels, performances, shots, characters, and visual production steps. In both cases, the assistant does not maintain a hidden second screenplay. It requests browser-side actions, and accepted writes enter the same project systems used by the interface. This is why your role, current episode, selection, and project state matter. ## Give every request a landing point The assistant first has to determine where your request belongs. Make that decision easy by naming one of these: - the selected text or current scene; - the outline or a particular beat; - an episode and scene range; - a character, location, prop, relationship, or shot; - a knowledge file or worldview key; - a reel and production stage in Cinema. A strong instruction combines **target, intention, constraints, and authority**: “In episode 3, revise the selected exchange so Nia wins the argument without revealing the key. Keep Sol's final line. Edit the script only.” ## Read before broad changes The assistant can inspect current focus, project entities, episode lists, script ranges, knowledge files, and worldview. Ask for analysis before a risky rewrite. When operating across episodes, it should use actual episode identities and switch context rather than guessing. ## Permissions remain real Viewers receive a read-only tool set. Switching episodes remains possible because it changes only their personal view. Worldview writes need an explicit request in the latest message. Advisors contribute read-only methods; they cannot hire themselves or acquire project permissions. The assistant's exact internal workflow can change through prompt experiments. Judge it by visible project changes and use bounded requests, selection, history, and review to stay in control. --- ### Develop an idea with AI **URL**: https://laper.ai/docs/ai-assistant/start-from-an-idea/ **Category**: AI assistant Turn a premise into a coherent outline, beats, entities, and opening pages through staged decisions. ## Begin with dramatic pressure A useful premise includes a person, an urgent desire, opposition, consequence, and a world constraint. Tone and references help, but they cannot replace conflict. If you have research or an existing treatment, attach it or add it to Knowledge and tell the assistant what role it should play. ## Work in stages The Script assistant may establish title, outline, beats, characters, locations, and opening scenes during a cold start. Its exact sequence is not a fixed product contract, so use these review gates: 1. **Premise gate:** confirm protagonist, goal, opposition, stakes, and format. 2. **Structure gate:** review the outline's causal progression and ending promise. 3. **Beat gate:** verify reversals and escalation in the current episode. 4. **Entity gate:** remove duplicate names and clarify relationships or locations. 5. **Page gate:** write a small group of scenes, then review before continuing. ## Ask for filmable writing Tell the assistant what should be visible or audible, what each character is trying to do, and where the scene must turn. Avoid requests for pages of internal explanation. A good opening request might be: > Write the first two scenes only. Establish the flooded archive through action, let Mara conceal that she recognizes the signal, and end the second scene when her brother hears it too. Use existing characters and locations. ## Correct without resetting everything If one part fails, name that part and preserve accepted work. “Keep the premise and final reveal; revise only sequence two so the investigation causes the arrest.” Incremental changes reduce collateral damage and keep collaborators able to understand what changed. Name a version before an experimental branch. After each writing pass, compare screenplay, outline, and beats instead of assuming the assistant updated every representation automatically. --- ### Revise screenplay pages with AI **URL**: https://laper.ai/docs/ai-assistant/revise-script/ **Category**: AI assistant Target selections, scenes, and cross-episode ranges while preserving accepted structure and voice. ## Select the smallest honest scope Use a text selection for wording, rhythm, or a precise exchange. Place the cursor inside a scene for scene-level work. Name an episode and scene when the target is elsewhere. Broad instructions such as “make it better” force the assistant to invent both diagnosis and scope. ## State what must survive Include invariants in the request: - lines or reveals to keep; - characters that may not be added or removed; - the required scene outcome; - tone, rating, length, or production limits; - whether outline, beats, entities, or script may be edited. For example: “Tighten the selected dialogue by about one third. Keep the phrase ‘nine years late,’ preserve Nia's lie, and do not alter the scene heading or following action.” ## Revise structure before prose when needed If the problem is causal or architectural, update the affected outline section and beats before generating many replacement pages. Daily line edits should remain local. Whole-outline replacement is appropriate only for an empty document or an explicitly confirmed reset. ## Review semantic structure After an AI edit, check paragraph roles, scene order, character identities, and derived locations. A beautiful block of prose is still wrong if it was inserted as action instead of dialogue or created a duplicate character. ## Cross-episode work needs explicit navigation The assistant should list real episodes and switch to the target before writing. It cannot safely edit another episode by guessing its identifier. Separate large multi-episode rewrites into reviewable passes and name a history version first. AI writing should remain filmable: observable action, playable dialogue, and dramatic change. Ask it to diagnose or propose before editing when you are uncertain which layer is broken. --- ### Use files and project knowledge with AI **URL**: https://laper.ai/docs/ai-assistant/files-and-knowledge/ **Category**: AI assistant Attach turn-specific sources, build a durable knowledge library, and tell the assistant what evidence to use. ## Attachments and Knowledge serve different time scales Files attached during project creation or chat provide context for that workflow. Project Knowledge is a durable library shared by the project. Use attachments for a current task and Knowledge for sources the team or assistant must revisit later. Supported idea-start attachments include DOCX, PDF, TXT, and Markdown. A file is evidence, not an instruction to copy every sentence. Tell the assistant whether it should summarize, extract constraints, match a voice, or compare facts. ## Make sources findable Use descriptive filenames and separate unrelated subjects. The assistant receives a knowledge index and can list, search, inspect, and read relevant files on demand. This selective reading avoids injecting an entire library into every conversation. A precise request names both source and use: > Read `Harbor_Tide_Research.pdf` and the current episode outline. List any scene whose tide timing is impossible. Do not edit yet. ## Distinguish evidence from story rules Knowledge stores source material. Worldview stores concise rules you have chosen for the fictional project. The assistant can read both, but it may write Worldview only when the latest message explicitly requests specific values. It cannot silently promote research into canon. ## Verify high-impact claims AI can misunderstand scans, tables, ambiguous terminology, or conflicting sources. Ask it to identify the file and relevant passage in its reasoning, then verify legal, medical, historical, financial, or safety-critical facts independently before production. Keep the screenplay readable: reference source facts through visible action and dialogue rather than pasting research prose onto the page. --- ### Use advisors and AI permissions **URL**: https://laper.ai/docs/ai-assistant/advisors-and-permissions/ **Category**: AI assistant Hire project advisors, activate their method in a conversation, and understand what they can never do. ## Advisors are methods, not collaborators with accounts The Advisors dimension presents official series and film advisors. Hiring an advisor attaches a read-only methodology to the project. A conversation can activate the relevant advisor so the AI reasons with that lens. An advisor does not become a project member, does not receive CRDT write access, and cannot act independently. The AI cannot hire, dismiss, or select an advisor for you. Those choices stay in the user interface. ## Hire deliberately Review the advisor's purpose, then hire it for the current project. The current product enforces a single-advisor workflow; dismiss the existing advisor before hiring another. Membership requirements, if any, are enforced by the visible product guard and backend rather than by the advisor itself. ## Activate the lens in conversation Use an advisor when you want a particular diagnostic method, not as a decorative title. Ask the AI to apply the method to a bounded artifact: an outline sequence, a character arc, a scene, or a Cinema reel. You can still instruct it to analyze only and wait before editing. ## Project permissions win OWNER, ADMIN, and EDITOR can write project data; VIEWER is read-only. The AI tool set follows that boundary. A collaborator's craft identity—director, writer, producer, and other roles—is presentation metadata and does not grant editing rights. Worldview has an additional content-specific gate: even an editor's AI cannot modify it without an explicit write request in the latest message. This protects durable project rules from conversational inference. --- ### Design storyboards from real scenes **URL**: https://laper.ai/docs/production/storyboard/ **Category**: Pre-production & Cinema Create episode-level shots tied to derived scenes and keep shot design separate from media generation. ## Start from the screenplay scene Storyboard shots belong to scenes, and scenes come from screenplay headings. Confirm the scene's action, characters, location, and dramatic turn before designing coverage. A shot list cannot repair a scene whose purpose is still unclear. The Storyboard dimension offers panel, table, and canvas views. They present the same episode-level shots in different forms: visual sequence, structured comparison, or spatial organization. ## Design decisive shots first Begin with the few shots that define the scene's dramatic logic. The AI assistant is guided to default to roughly three decisive shots and to reconsider plans that exceed six. This is a creative discipline, not a hard UI maximum: establish geography, pressure, and the turn before adding coverage. Each shot should express subject, framing, camera position or movement, action, and dramatic purpose. Use actual character names and scene facts so generated references and production discussion remain connected to the project. ## Chat writes design; generation is a separate action The Script assistant can read scenes and create or edit shot records. It should not promise that a chat message has generated finished media. Image, video, and audio outputs run through explicit generation tasks with visible cost, status, retry, and asset results. ## Review continuity Check screen direction, eyelines, entrances, prop states, and the relationship between adjacent shots. If the screenplay changes, revisit shots in that episode. Project-level character and location references help consistency, but the shot sequence remains tied to the episode's current scene. --- ### Review and refine the shot list **URL**: https://laper.ai/docs/production/shot-list/ **Category**: Pre-production & Cinema Use structured shot data for coverage review, continuity, and downstream visual generation. ## Use the table for comparison The shot list exposes episode shots in a structured view. It is useful for checking lens or framing choices, camera logic, repeated coverage, and whether each shot belongs to the correct scene. The panel is better for sequential reading; the canvas is better for spatial arrangement. ## Give every shot a job A shot should change what the audience knows, feels, or anticipates. Record concrete visual information rather than vague mood alone. Keep dialogue and action aligned with the screenplay, and use canonical character identities. Review a scene in layers: 1. Geography: can the audience understand the space? 2. Dramatic ownership: whose objective shapes each moment? 3. Reveal: what information is withheld or exposed by framing? 4. Continuity: do screen direction, props, light, and performance states connect? 5. Economy: can two redundant shots become one stronger shot? ## Work with AI without overcoverage Ask the assistant to read the scene and existing shots before adding more. State the production constraint and desired visual grammar. If you only need analysis, say “do not edit.” For a rewrite, specify which shots may change and which must remain. ## Keep downstream assets traceable Generated storyboard or scene images should originate from the real shot and entity data where the workflow supports it. Review generation results as references, then return to the shot record for the production decision. Deleting an asset does not automatically rewrite the shot plan. --- ### Understand AI tasks and assets **URL**: https://laper.ai/docs/production/ai-assets/ **Category**: Pre-production & Cinema Generate media through visible tasks, track status and cost, and distinguish task records from reusable outputs. ## Every generation is a task plus assets Laper separates the execution record from its outputs. A generation task owns status, credit charge, estimated progress, retry behavior, and failure handling. One task can produce one or more assets. This model is shared by Script and Cinema workflows. In a Script project, Laper Space aggregates project generation in a canvas and task list. Current production workflows include poster and casting images, trailer or scene dramatization video, and audio experiences such as director roundtables and script table reads. Available entries can evolve; use the visible task menu as the current truth. ## Dispatch deliberately Before generating, check the selected episode or entity, reference images, prompt, aspect ratio, and the credit cost shown on the action. Once dispatched, the task moves through queued, generating, completed, or failed presentation states while the backend maintains more detailed execution states. Do not start duplicate tasks because an estimate changes or the page is refreshed. Task and asset lists reconcile from the project and can include collaborators' work. ## Handle results and failures Open the task card to inspect outputs. Assets are reusable project results; they are not automatically screenplay edits. Entity-bound workflows can route a result back to a character, prop, shot, or reel field, while project-level free creation stays in the asset library. If a task fails, read the visible error and retry only after correcting the cause. Credits, refunds, congestion behavior, and estimated time are controlled by the current service configuration, so tutorials do not hard-code those numbers. --- ### Create and navigate a Cinema project **URL**: https://laper.ai/docs/production/cinema-projects/ **Category**: Pre-production & Cinema Set the film's visual parameters, understand reels and shared entities, and choose the right Cinema view. ## Create the production foundation A new Cinema project asks for a name, then production setup: landscape or portrait orientation, production type, camera style, and art style. These choices seed the project's shared film context. They can guide generation, but they do not replace the content of each reel. Cinema does not import FDX. If your source is a screenplay, keep it in a Script project and use Cinema as a separate visual-production document rather than expecting an automatic round-trip conversion. ## Understand scope Each episode owns its reels. Characters, props, production settings, and the task library are shared by the project. A new episode begins with a default reel so the workspace is not empty. Switching episodes changes your view without moving collaborators. ## Use the four dimensions - **Reels** provide board, timeline, and list views for production units. - **Characters** reuse project character capabilities and add Cinema-specific look development. - **Props** provide shared visual object references. - **Tasks** collect project-level free image, poster, and video creation plus generated results. ## A reel is not a screenplay scene A reel is a compact visual-production unit that passes through scene design, performance, shot design, storyboard image, and final clip. Its ordering belongs to the current episode. Use several reels to build a longer sequence and make continuity choices between them. The Cinema AI assistant reads and edits Cinema entities, not Script project pages. Give it the target reel and stage, and ask it to inspect existing characters, props, and neighboring reels before making a wide change. --- ### Run the five-stage Cinema pipeline **URL**: https://laper.ai/docs/production/cinema-pipeline/ **Category**: Pre-production & Cinema Move a reel from scene concept to a fixed 15-second clip while preserving characters, shots, and continuity. ## The five stages Each reel follows one production chain: 1. **Scene:** write the environment and add reference images; generate a scene image when ready. 2. **Performance:** write the playable dramatic action using `@character`, `#prop`, and quoted dialogue. 3. **Text storyboard:** create and refine real shot records, either with the Cinema assistant or by hand. 4. **Storyboard image:** generate a visual anchor from the shot sequence, scene, and references. 5. **Final clip:** start production and select among generated video versions. Scene and Performance can be developed in parallel. Text storyboard and later stages require their prerequisites so downstream media does not invent missing structure. ## Write a strong performance Describe what happens during the reel, not a production essay. Mention project characters with `@`, props with `#`, and put spoken lines in quotes. The shot plan should translate this performance into timed, visually distinct moments. ## Know the duration and film settings A final Cinema clip is fixed at **15 seconds**. Resolution and production level are film-level settings rather than per-reel duration controls. Design the performance and shot rhythm to fit that limit instead of asking one reel to contain an entire sequence. ## Maintain continuity across reels In last-frame continuity mode, the selected previous reel can provide its final frame as the next reel's opening anchor. Natural transition mode generates independently. Review costume, props, light, eyeline, and movement yourself; a reference anchor helps but does not guarantee continuity. New generations create versions. Select the preferred version deliberately and remove obsolete versions only after review. Project-level free-creation tasks stay in the task library, while reel-bound scene, storyboard, and final outputs route back to the reel. --- ### Collaborate with real-time sync **URL**: https://laper.ai/docs/collaboration/real-time-sync/ **Category**: Collaboration Understand shared CRDT editing, local episode focus, presence, offline behavior, and reconciliation. ## One shared document, independent views Script and Cinema creative documents synchronize through a conflict-tolerant collaborative document. Keyboard edits and accepted AI edits enter the same shared state. Collaborators can work in different dimensions or episodes without forcing navigation on one another. Presence shows who is connected and can distinguish synchronized online work from local editing. Presence is awareness, not a lock. Two editors can still change related content, so coordinate broad structural operations. ## Temporary disconnection The workspace has a local persistence layer. A network interruption can leave you editing locally until synchronization returns. Watch the connection indicator and avoid duplicating the project in several tabs as a recovery strategy. When the connection returns, let reconciliation complete before making a second copy of the same change. ## Data that is not in the collaborative document Comments, knowledge files, worldview, advisor relationships, generation tasks, and assets use project APIs and database-backed stores rather than screenplay CRDT nodes. They still respect project membership, but their update and reconciliation behavior differs from text editing. ## Safer team habits - Name a version before a large rewrite or episode deletion. - Tell collaborators which episode and layer you are changing. - Normalize shared character and location names before attaching production data. - Use comments for review rather than encoding discussion in screenplay action. - Export stable delivery copies when a milestone leaves the workspace. Synchronization prevents ordinary edit loss; it does not replace editorial communication or intentional checkpoints. --- ### Share projects and assign roles **URL**: https://laper.ai/docs/collaboration/sharing-and-roles/ **Category**: Collaboration Configure link access, member roles, Viewer export, and creative identities without confusing them. ## The share link always exists Every project has a stable share link. There is no separate “enable link” switch. The owner controls what that link allows through one of three access modes: - **Anyone Can View** - **Anyone Can Edit** - **Invited Only** Anyone Can Edit and Invited Only can require an eligible membership. The interface and backend enforce the current plan rule. ## Member roles control authority - **OWNER:** full project and access control. - **ADMIN:** can manage ordinary members, but cannot change the owner, peer admins, or access mode. - **EDITOR:** can edit project content. - **VIEWER:** can read and participate where view-only collaboration is supported, but cannot write the creative document. Only the owner can change access mode and decide whether Viewers may export. Permission checks fail closed: an unknown or unresolved role is treated as read-only. ## Creative identity is separate Members may choose a visible craft identity such as director, writer, or producer. This describes how they participate; it does not grant permissions. A Viewer labeled “Director” remains read-only, and an Editor labeled “Guest” remains an editor. ## Add and manage members Owners and admins can search for users and add them, normally as Editors, then change ordinary members between Editor and Viewer or remove them. Members can update their own creative identity. Presence indicators show activity but do not change role. Review access mode, member list, and Viewer export before sharing a project outside the core team. Do not rely on the craft label or copied URL alone to infer authority. --- ### Review work with comments **URL**: https://laper.ai/docs/collaboration/comments/ **Category**: Collaboration Anchor discussion to supported dimensions while keeping review data separate from the creative document. ## Comments are a review layer Comments are stored separately from the screenplay CRDT. They use a project dimension and anchor to point at script text, outline content, or supported canvas entities. This keeps discussion from becoming screenplay text and lets the team resolve review without rewriting the artifact. Current comment support covers the script, outline, and relevant canvas-style dimensions. Beats do not currently expose the same comment anchoring, so place beat-level discussion on the outline or in the related script context instead of expecting a hidden beat comment thread. ## Viewers can participate in review Viewer access is read-only for creative data but can still support comments. This distinction is useful for producers, clients, or reviewers who should discuss work without changing it. Project access and membership still determine whether the person can open the project. ## Write actionable comments Anchor the smallest useful target and state the decision needed. “This is confusing” is weak. “At this line, do we want Mara to recognize the signal, or should the reveal remain in scene 12?” gives location, problem, and choice. Use replies to keep one decision together. Resolve or close threads when the underlying change is accepted, rejected, or superseded. If the anchored content is moved or deleted, confirm that the comment still points to meaningful context. Comments are not version history. Preserve a version before large changes and use comments to explain decisions around that checkpoint. --- ### Use version history and restore safely **URL**: https://laper.ai/docs/collaboration/version-history/ **Category**: Collaboration Name milestones, inspect automatic entries, and understand that restore replaces the current document state. ## What history contains Version history lists automatic and named project snapshots. A version can have a name, description, author, and timestamp. Naming important milestones makes the list useful: “Imported FDX cleanup,” “Producer notes pass,” or “Episode 4 locked outline” is clearer than relying on dates alone. ## Restore is a document-level operation Restoring does not cherry-pick one paragraph. It brings the project's collaborative document back to the selected snapshot and asks for confirmation. In Script projects, the restore path checks episode compatibility and restores both screenplay and project entities. Cinema uses its own full-document reconciliation so entities added after the snapshot do not incorrectly survive. ## A safe restore workflow 1. Stop broad team edits and tell collaborators what you are doing. 2. Export or name a version of the current state if it might be needed. 3. Select the intended snapshot and read its name, author, and date. 4. Confirm the restore and wait for the project to reconcile. 5. Inspect representative episodes, entities, and views before continuing. A historical entry can be renamed or deleted if you have authority. Deleting history metadata should be treated as irreversible from the interface. ## History is not external backup Keep delivery exports for legal, archival, or external workflow needs. Version history is optimized for project recovery and creative comparison inside Laper; it does not synchronize edits made in an exported DOCX or FDX back into the project. --- ### Configure profile, language, theme, and account **URL**: https://laper.ai/docs/account/settings/ **Category**: Account & billing Know which preferences are personal, which are shared project settings, and where account actions live. ## Global Settings has five visible tabs - **Profile:** avatar, nickname, email display, and biography. - **General:** interface language and system, light, or dark theme. - **Billing:** subscription status, renewal, invoices, and plan actions. - **Usage:** current AI conversation allowance and period usage. - **Account:** join information, sign out, and account deletion. An older Invite implementation exists in the codebase but is not part of the current visible Settings navigation. Use the current five tabs rather than following stale screenshots. ## Personal settings do not rewrite the project Changing language or theme affects your interface. It does not translate screenplay content, rename shared entities, or change collaborators' displays. Docs use the same selected interface language when a tutorial translation exists. Project title, screenplay format, and project AI settings live in the project's own Settings modal. Those values are shared and should be changed with the team in mind. ## Account actions Signing out ends your session but does not delete projects. Account deletion is destructive and may affect owned project access; read the confirmation carefully and transfer or export important work first. Profile changes and account operations require a working authenticated session. If a save fails, verify connectivity and session status before repeating the action. --- ### Understand plans, AI usage, and credits **URL**: https://laper.ai/docs/account/plans-and-credits/ **Category**: Account & billing Separate chat allowances from media-generation credits and use live UI values instead of stale quota tables. ## Two kinds of consumption AI conversation usage and media-generation credits are related to your membership but are not the same meter. The Usage tab shows conversation allowance, period, and use. Generation actions show their current credit cost near the action and create a task when dispatched. Do not rely on quota numbers copied from old prompts, screenshots, or tutorials. Plans, promotional grants, and generation costs can change. The Billing, Usage, upgrade, and generation interfaces display the values that apply to your account now. ## Billing controls Billing can show the current plan, billing interval, renewal or access-end date, scheduled plan changes, invoice history, and available cancel or reactivate actions. Manual grants may have different cancellation behavior from a paid subscription. Plan changes can be immediate or scheduled depending on the action. Read the effective date before confirming, and cancel a pending change from Billing when that control is offered. ## Generation task accounting A task displays cost before dispatch. The backend owns charging, execution, failure, and refund behavior. Avoid repeated clicks while a task is queued or running. If congestion or a provider limit causes a terminal failure, use the visible status and account balance before deciding to retry. ## Collaboration does not pool identity Project membership determines access to shared work, but task streams and balances remain associated with users under the service rules. The project task and asset views can reconcile collaborators' visible outputs without turning all accounts into one billing identity. --- ### Troubleshoot common workflow problems **URL**: https://laper.ai/docs/account/troubleshooting/ **Category**: Account & billing Diagnose sync, missing entities, AI targeting, generation, import, export, and permission issues from the correct layer. ## A scene or location is missing Return to the screenplay and inspect the scene heading. Scenes and locations are derived from semantic heading nodes. Reformat pasted plain text as a scene heading and normalize the location name. Do not try to create a disconnected scene database row. ## AI edited the wrong place Stop and use history if the change is broad. Then select the exact text or place the cursor in the target scene, name the episode, list what must stay unchanged, and request a bounded correction. Cross-episode work must switch to a real episode rather than infer one. ## AI cannot write Check your project role. Viewer and unresolved roles are read-only. A creative craft identity does not grant write access. Worldview also requires an explicit write request in the latest message even when you can edit the project. ## Changes appear local or collaborators are absent Read the connection and presence indicators. Allow the local document to reconnect instead of opening duplicate tabs. Remember that collaborators can be online in different episodes and dimensions without sharing your current view. ## FDX import fails Confirm the file is an FDX Script document, not another Final Draft document type. Review file size and unusual embedded content. Cinema projects do not support FDX. Import creates a new project rather than merging into an existing one. ## Export format is unavailable Hollywood script supports PDF, DOCX, TXT, and FDX. Asian script supports PDF, DOCX, and TXT. Outline supports PDF, DOCX, and TXT. There is no Fountain export. Also check membership and whether the owner allows Viewer export. ## A generation seems stuck Check the task card rather than dispatching duplicates. Queued and running tasks keep their own status and estimate; refresh or navigation should reconcile them. For failure, read the terminal message, confirm credits and references, then retry only after correcting the cause. ## When to contact support Preserve the project URL, task or version timestamp, browser and app version, visible error, and the smallest reproducible steps. Do not send passwords, private API credentials, or unrelated source files. --- ## Core Advantages (11) Code-backed explanations of Laper as AI screenwriting software, including product behavior, architecture boundaries, and honest limitations. ### AI Screenwriting Software Built Around the Script **URL**: https://laper.ai/features/ai-screenwriting-software/ **Date**: 2026-07-15 **Author**: shizhi **Category**: Core Advantage **Keywords**: AI screenwriting software, AI script writer, screenplay software, AI screenplay writer, screenplay editor, human-led AI screenwriting **TL;DR**: Laper treats the screenplay as the source of truth. Formatting, structured AI tools, CRDT sync, planning views, and visual assets all work around that same draft. See how Laper combines screenplay formatting, structured AI tools, collaboration, planning views, and production assets without replacing the writer. {/* [INPUT]: 依赖 Laper-app 的 Plate/Loro/AI tool/任务资产/priceConfig 代码事实与竞品官方功能页 [OUTPUT]: AI screenwriting software 核心支柱文章，定义产品边界并串联所有 feature 子页 [POS]: content/features 的主题中心，首页与 Features 列表的首要内链目标 [PROTOCOL]: 变更时更新此头部，然后检查 CLAUDE.md */} --- ### Automatic Screenplay Formatting Without Format Chores **URL**: https://laper.ai/features/screenplay-formatting/ **Date**: 2026-07-14 (updated 2026-07-15) **Author**: chunxiang **Category**: Core Advantage **Keywords**: screenplay formatting, screenplay format software, movie script format, automatic script formatting, screenplay editor, Final Draft export **TL;DR**: Laper stores screenplay elements as typed nodes, applies layout while you write, and preserves structure for pagination, export, AI tools, and derived project views. Laper keeps scene headings, action, character cues, dialogue, parentheticals, transitions, pagination, and export inside a typed screenplay editor. {/* [INPUT]: 依赖 Script/editor 节点 schema、格式配置、分页与 export 服务的代码事实 [OUTPUT]: 自动剧本格式功能文章，解释 typed nodes 与 AI 写作的职责边界 [POS]: content/features 的格式化详情页，被 Hero 与 Just Works format 卡片引用 [PROTOCOL]: 变更时更新此头部，然后检查 CLAUDE.md */} --- ### Script Structure Visualization From the Draft **URL**: https://laper.ai/features/script-structure-visualization/ **Date**: 2026-07-13 (updated 2026-07-15) **Author**: shizhi **Category**: Core Advantage **Keywords**: script structure visualization, screenplay outline software, scene breakdown, story structure software, screenplay scene list, screenplay planning **TL;DR**: The screenplay stays authoritative: scene headings determine scene order and locations, character cues feed character entities, and planning views remain attached to that source. Laper derives scene order, scene entities, characters, and locations from screenplay nodes, then connects them to outlines, beats, boards, and production views. {/* [INPUT]: 依赖 scene_heading/character 派生、scriptMetrics 场次顺序、Scenes/Characters/Locations/Beats L2 事实 [OUTPUT]: 剧本结构可视化功能文章，说明 source-of-truth 与投影视图边界 [POS]: content/features 的结构详情页，被 Hero 与 Just Works structure 卡片引用 [PROTOCOL]: 变更时更新此头部，然后检查 CLAUDE.md */} --- ### Real-Time Screenplay Collaboration With Loro CRDT **URL**: https://laper.ai/features/real-time-screenplay-collaboration/ **Date**: 2026-07-12 (updated 2026-07-15) **Author**: shizhi **Category**: Core Advantage **Keywords**: real-time screenplay collaboration, collaborative screenwriting software, Loro CRDT, writers room software, screenplay version control, online screenplay editor **TL;DR**: Laper keeps one Loro document per project, syncs bytes through a worker and dedicated service, and requires a server-first initial sync before the editor becomes writable. Learn how Laper synchronizes screenplay and project state with Loro, what happens during disconnects, and where same-paragraph conflict boundaries remain. {/* [INPUT]: 依赖 shared/services/crdt、Plate op-bridge 与 lorosync 的现行协议和边界 [OUTPUT]: 实时剧本协作功能文章，公开说明 server-first、节点级冲突与断线恢复语义 [POS]: content/features 的协作详情页，被 Hero 与 Just Works collaboration 卡片引用 [PROTOCOL]: 变更时更新此头部，然后检查 CLAUDE.md */} --- ### How Laper Gives AI Structured Screenplay Context **URL**: https://laper.ai/features/ai-screenwriting-workspace/ **Date**: 2026-07-11 (updated 2026-07-15) **Author**: shizhi **Category**: Core Advantage **Keywords**: AI screenwriting workspace, AI screenplay context, AI script editor, AI script writer, screenplay analysis AI, AI screenplay assistant **TL;DR**: AI reads the smallest useful screenplay scope—cursor, outline, scene, range, node, or bounded full draft—then edits stable nodes through the active browser editor. Laper's browser-side AI tools read explicit screenplay scopes, locate stable nodes, and apply approved edits through the live editor instead of a detached chat document. {/* [INPUT]: 依赖 AgentChat read_script/read_current_script_focus/find_node/edit_script 工具代码与 Plate 写路径 [OUTPUT]: AI 上下文工作区文章，取代不可证的 200K always-on 宣称 [POS]: content/features 的 AI 工作区详情页，被 Just Works ai-context 卡片引用 [PROTOCOL]: 变更时更新此头部，然后检查 CLAUDE.md */} --- ### AI Production Assets Grounded in Project Entities **URL**: https://laper.ai/features/ai-production-assets/ **Date**: 2026-07-10 (updated 2026-07-15) **Author**: chunxiang **Category**: Core Advantage **Keywords**: AI production assets, AI storyboard generator, character portrait generator, AI scene stills, film pre-production AI, screenplay visualization **TL;DR**: Every generation is a durable task; every successful output is an asset. The backend owns status and credits, while project views supply scene, character, prop, or location context. Laper routes visual generation through durable tasks and assets, associates results with project entities, and keeps credits, retries, completion, and refunds server-owned. {/* [INPUT]: 依赖 ai_gen_tasks/assets 双表、gentask 后端、Gen Work 被调服务与 Assets 模块代码事实 [OUTPUT]: AI 制作资产功能文章，解释任务、产物、积分与 CRDT 的职责分离 [POS]: content/features 的生成资产详情页，被 Just Works assets 卡片引用 [PROTOCOL]: 变更时更新此头部，然后检查 CLAUDE.md */} --- ### Characters, Casting, and Relationship Mapping **URL**: https://laper.ai/features/characters-casting-relationships/ **Date**: 2026-07-09 (updated 2026-07-15) **Author**: chunxiang **Category**: Core Advantage **Keywords**: character relationship map, screenplay character breakdown, casting board software, character development software, screenplay characters, AI character portrait **TL;DR**: Laper derives characters from screenplay cues, stores profiles and relationships in shared project state, and presents the same entities as boards, graphs, and casting views. Character cues feed shared character entities that can be enriched in boards, relationship graphs, casting views, profiles, and AI-assisted visual development. {/* [INPUT]: 依赖 Characters 模块、character cue 派生、关系数据、CastingDirectorView 与资产生成路径 [OUTPUT]: 人物/选角/关系图功能文章，说明同一实体的多视图投影 [POS]: content/features 的人物详情页，被 Just Works characters 文本卡引用 [PROTOCOL]: 变更时更新此头部，然后检查 CLAUDE.md */} --- ### AI Storyboarding From Scene Context **URL**: https://laper.ai/features/ai-storyboarding/ **Date**: 2026-07-08 (updated 2026-07-15) **Author**: shizhi **Category**: Core Advantage **Keywords**: AI storyboarding, AI storyboard generator, screenplay to storyboard, shot list software, scene storyboard, film pre-production AI **TL;DR**: Storyboards live inside a scene scope. Shots keep stable order and explicit camera settings; AI can assist with breakdown and images without becoming the screenplay source. Laper breaks a real screenplay scene into ordered shots, preserves explicit camera choices, and routes storyboard frames through durable generation tasks and assets. {/* [INPUT]: 依赖 Storyboard 模块的 scene scope、shot order、参考图 slot 与显式镜头参数规则 [OUTPUT]: AI 分镜功能文章，说明场次上下文、连续性门禁与任务资产路径 [POS]: content/features 的分镜详情页，被 Just Works storyboard 文本卡引用 [PROTOCOL]: 变更时更新此头部，然后检查 CLAUDE.md */} --- ### Scenes, Beats, Props, and Locations in One Project **URL**: https://laper.ai/features/scenes-beats-props-locations/ **Date**: 2026-07-07 (updated 2026-07-15) **Author**: chunxiang **Category**: Core Advantage **Keywords**: script breakdown software, screenplay scene list, beat board software, film prop breakdown, location scouting software, screenplay planning **TL;DR**: Scene headings determine scene order and location structure; beats, props, stills, scouting data, and shots remain first-class project entities attached to the same draft. Laper keeps screenplay-derived scenes and locations beside beats, props, scene stills, scouting views, and shot planning without creating a second script. {/* [INPUT]: 依赖 Scenes/Beats/Props/Locations 模块、sceneMetrics 顺序与 loro-mirror 投影事实 [OUTPUT]: 场次/节拍/道具/地点功能文章，说明派生数据与第一类规划实体边界 [POS]: content/features 的项目实体详情页，被 Just Works entities 文本卡引用 [PROTOCOL]: 变更时更新此头部，然后检查 CLAUDE.md */} --- ### AI Script Doctor: Diagnosis Before Rewriting **URL**: https://laper.ai/features/ai-script-doctor/ **Date**: 2026-07-06 (updated 2026-07-15) **Author**: shizhi **Category**: Core Advantage **Keywords**: AI script doctor, screenplay analysis AI, script coverage AI, screenplay feedback, screenplay structure analysis, AI screenplay editor **TL;DR**: Script Doctor is an optional advisor mode: it names the root problem, locates it in the draft, gives an executable prescription, and protects the writer's intent. Laper's official Script Doctor mode diagnoses structure, character, scene function, theme, pacing, and dialogue before prescribing a prioritized revision. {/* [INPUT]: 依赖 Laper-chat official script-doctor skill 与 AgentChat 结构化读写工具事实 [OUTPUT]: AI Script Doctor 功能文章，解释诊断协议、理论刀具与上下文边界 [POS]: content/features 的剧本医生详情页，被 Landing AI Script Doctor 全模块引用 [PROTOCOL]: 变更时更新此头部，然后检查 CLAUDE.md */} --- ### Open Screenplay Community: Read, Discuss, and Remix **URL**: https://laper.ai/features/open-screenplay-community/ **Date**: 2026-07-05 (updated 2026-07-15) **Author**: chunxiang **Category**: Core Advantage **Keywords**: open screenplay community, read screenplays online, screenwriting community, public screenplay library, screenplay feedback, screenplay examples **TL;DR**: The community exposes only published public projects. Readers can inspect real scripts; authenticated members can discuss, like, and copy allowed projects into private workspaces. Published Laper projects can be browsed and read publicly, while signed-in members can like, comment, and copy an allowed work into a private project. {/* [INPUT]: 依赖 CommunityPublicWorksPanel、public script API、community_service 的 published gate 与 comment/like/copy 路由 [OUTPUT]: 开放剧本社区功能文章，取代 Landing 中虚构作品与阅读量暗示 [POS]: content/features 的社区详情页，被 Landing OpenScriptCommunity 全模块引用 [PROTOCOL]: 变更时更新此头部，然后检查 CLAUDE.md */} --- ## Comparison Pages (Laper vs Competitors) (6) Detailed comparisons between Laper and major competitors. These pages cover feature parity, pricing, and honest pros/cons for each product. ### Laper vs Fade In: Collaboration and AI vs the Best One-Time Buy (2026) **URL**: https://laper.ai/alternatives/fade-in/ **Date**: 2026-07-05 **Author**: shizhi **Category**: Alternatives **Keywords**: Fade In alternative, Laper vs Fade In, Fade In Pro comparison, screenwriting software comparison, one-time purchase screenwriting software, AI screenwriting software **TL;DR**: Choose Laper over Fade In for real-time multi-user collaboration, AI grounded in the full script, and auto-derived production views; choose Fade In if you want a professional, cross-platform editor for a single approximately-$80 one-time purchase with no AI and no subscription. Laper vs Fade In for screenwriters. Real-time collaboration, full-script AI, and visual production views vs Kent Tessman's respected cross-platform one-time-purchase editor. {/* [INPUT]: 依赖 Laper 当前功能/价格事实与 Fade In 公开产品资料 [OUTPUT]: Fade In alternative 比较文章 [POS]: content/alternatives 的 BOFU 页面，保留传统编辑器优势并陈述 Laper 边界 [PROTOCOL]: 变更时更新此头部，然后检查 CLAUDE.md */} **Start free.** Junior is free, no credit card required. Export a `.fdx` from Fade In, import it, write one real scene, and decide from the work, not from the comparison table. [Start free on Laper](/login/?utm_source=alternatives&utm_medium=comparison&utm_campaign=fade_in_alternative) · [View pricing](/pricing/?utm_source=alternatives&utm_medium=comparison&utm_campaign=fade_in_alternative) --- ### Laper vs Highland 2: Beyond Minimalist Mac Screenwriting (2026) **URL**: https://laper.ai/alternatives/highland/ **Date**: 2026-07-05 **Author**: shizhi **Category**: Alternatives **Keywords**: Highland 2 alternative, Laper vs Highland, Fountain screenwriting software, Mac screenwriting software alternative, real-time collaboration screenplay, AI screenwriting software **TL;DR**: Choose Laper over Highland 2 for real-time collaboration, AI-assisted writing, visual production views, and Windows or browser access; choose Highland 2 if you are a solo Mac writer who loves Fountain and distraction-free minimalism. Laper vs Highland 2 for screenwriters. Real-time collaboration, AI assistance, and cross-platform access vs John August's minimalist Mac-only Fountain editor. {/* [INPUT]: 依赖 Laper 当前功能/价格事实与 Highland 公开产品资料 [OUTPUT]: Highland alternative 比较文章 [POS]: content/alternatives 的 BOFU 页面，区分 Fountain 极简写作与结构化协作工作流 [PROTOCOL]: 变更时更新此头部，然后检查 CLAUDE.md */} **Start free.** Junior is free, no credit card required. Export a `.fdx` from Highland 2, import it, write one real scene, and decide from the work, not from the comparison table. [Start free on Laper](/login/?utm_source=alternatives&utm_medium=comparison&utm_campaign=highland_alternative) · [View pricing](/pricing/?utm_source=alternatives&utm_medium=comparison&utm_campaign=highland_alternative) --- ### Laper vs Sudowrite: AI for Screenplays, Not Just Prose (2026) **URL**: https://laper.ai/alternatives/sudowrite/ **Date**: 2026-05-19 **Author**: shizhi **Category**: Alternatives **Keywords**: Sudowrite alternative, Laper vs Sudowrite, AI screenwriting assistant, AI screenplay writer, AI script generator, screenplay AI assistant **TL;DR**: Choose Laper if you write screenplays — industry-standard format, scene-aware AI, real-time collaboration. Choose Sudowrite if you write novels or prose — it does not output screenplay format. Laper vs Sudowrite for screenwriters. Laper is AI-native screenwriting software with industry format; Sudowrite is AI prose for novelists, not screenplays. {/* [INPUT]: 依赖 Laper 当前结构化剧本能力与 Sudowrite 公开 prose 产品定位 [OUTPUT]: Sudowrite alternative 比较文章 [POS]: content/alternatives 的 BOFU 页面，明确 screenplay 与 prose AI 的工作流边界 [PROTOCOL]: 变更时更新此头部，然后检查 CLAUDE.md */} --- ### Laper vs Celtx: Screenwriting Without the Bloat (2026) **URL**: https://laper.ai/alternatives/celtx/ **Date**: 2026-05-19 **Author**: shizhi **Category**: Alternatives **Keywords**: Celtx alternative, Laper vs Celtx, screenwriting software comparison, AI screenwriting assistant, real-time collaborative screenwriting, modern screenwriting software **TL;DR**: Choose Laper for a smooth AI-powered writing experience and real-time co-writing; choose Celtx if your priority is bundled pre-production planning (scheduling, budgets, shot lists). Laper vs Celtx for screenwriters. Laper wins on writing experience, AI, and real-time collaboration; Celtx wins on integrated pre-production planning. {/* [INPUT]: 依赖 Laper 当前功能/价格事实与 Celtx 公开产品资料 [OUTPUT]: Celtx alternative 比较文章 [POS]: content/alternatives 的 BOFU 页面，区分 script-first 工作区与广域前期制作套件 [PROTOCOL]: 变更时更新此头部，然后检查 CLAUDE.md */} **Start free.** Junior is free, no credit card required. Import a `.fdx`, test one writing session, and only upgrade if Laper's editor, AI, and collaboration actually fit your workflow. [Start free on Laper](/login/?utm_source=alternatives&utm_medium=comparison&utm_campaign=celtx_alternative) · [View pricing](/pricing/?utm_source=alternatives&utm_medium=comparison&utm_campaign=celtx_alternative) --- ### Laper vs Final Draft: The Honest Alternative for Writers (2026) **URL**: https://laper.ai/alternatives/final-draft/ **Date**: 2026-05-10 **Author**: shizhi **Category**: Alternatives **Keywords**: Final Draft alternative, Laper vs Final Draft, screenwriting software comparison, real-time collaboration screenplay, character relationship map, modern screenwriting software **TL;DR**: Choose Laper over Final Draft for AI-assisted writing, real-time collaboration, FDX import/export, and a free tier; choose Final Draft when the room or studio explicitly standardizes on the Final Draft app. Laper vs Final Draft for screenwriters. Real-time collaboration, character maps, and a smoother writing experience vs the industry-standard app. {/* [INPUT]: 依赖 Laper 当前功能/价格事实与 Final Draft 公开产品资料 [OUTPUT]: Final Draft alternative 比较文章 [POS]: content/alternatives 的 BOFU 页面，协作口径使用 Loro node-level 边界 [PROTOCOL]: 变更时更新此头部，然后检查 CLAUDE.md */} **Start free.** Junior is free, no credit card required. Import a `.fdx`, write one real scene, and decide from the work, not from the comparison table. [Start free on Laper](/login/?utm_source=alternatives&utm_medium=comparison&utm_campaign=final_draft_alternative) · [View pricing](/pricing/?utm_source=alternatives&utm_medium=comparison&utm_campaign=final_draft_alternative) --- ### Laper vs WriterDuet: Beyond Real-Time Collaboration (2026) **URL**: https://laper.ai/alternatives/writerduet/ **Date**: 2026-05-10 **Author**: shizhi **Category**: Alternatives **Keywords**: WriterDuet alternative, Laper vs WriterDuet, real-time collaborative screenwriting, screenplay collaboration software, character relationship map, AI screenwriting assistant **TL;DR**: Laper matches WriterDuet on real-time collaboration and adds character relationship maps, AI visual generation, FDX import/export, and multilingual workflows — WriterDuet still wins on price and platform maturity. Laper vs WriterDuet for screenwriters. Both offer real-time co-writing; Laper adds character maps, AI visuals, refined UX. WriterDuet wins on price. **Start free.** Junior is free, no credit card required. Import a `.fdx`, test the character map and AI visuals on a real script, then decide whether the extra workflow is worth the higher price. [Start free on Laper](/login/?utm_source=alternatives&utm_medium=comparison&utm_campaign=writerduet_alternative) · [View pricing](/pricing/?utm_source=alternatives&utm_medium=comparison&utm_campaign=writerduet_alternative) --- ## Blog Articles (22) Long-form articles on AI screenwriting, screenplay craft, software comparisons, and industry trends. ### Three Act Structure Screenplay: The Complete Breakdown **URL**: https://laper.ai/blog/three-act-structure-screenplay/ **Date**: 2026-07-05 **Author**: chunxiang **Category**: Screenwriting Craft **Keywords**: three act structure screenplay, three act structure, screenplay structure, plot points screenplay, screenplay midpoint, act two confrontation, screenplay page count, screenplay outline **TL;DR**: The three act structure divides a screenplay into Setup (roughly the first quarter), Confrontation (the middle half, hinged on a midpoint), and Resolution (the final quarter). Two plot points and a midpoint carry the structural load. Learn the page math for 90-120 page scripts, see it working in Casablanca and A Christmas Carol, then translate it into a beat outline before you draft. Three act structure screenplay guide: setup, confrontation, resolution, plot points, midpoint, and page targets for 90-120 page scripts. --- ### Save the Cat Beat Sheet: All 15 Beats, Page by Page **URL**: https://laper.ai/blog/save-the-cat-beat-sheet/ **Date**: 2026-07-05 **Author**: chunxiang **Category**: Screenwriting Craft **Keywords**: save the cat beat sheet, Blake Snyder beat sheet, 15 beats screenplay, beat sheet template, screenplay beats, save the cat page numbers, screenplay outline method, beat sheet page count **TL;DR**: Blake Snyder's Save the Cat beat sheet maps a screenplay onto 15 beats pegged to a 110-page script - from Opening Image (p.1) through Catalyst (p.12), Midpoint (p.55), All Is Lost (p.75), to Final Image (p.110). This guide explains each beat's actual job, gives you percentage math to rescale the sheet for any length, shows how to map it onto a script you have already started, and names the misuses that turn a diagnostic tool into a formula factory. The Save the Cat beat sheet explained: all 15 Blake Snyder beats with page numbers, conversion math for any script length, and common misuses. --- ### Screenplay Format: The Complete Industry Guide (2026) **URL**: https://laper.ai/blog/screenplay-format-guide/ **Date**: 2026-07-05 **Author**: shizhi **Category**: Screenwriting Craft **Keywords**: screenplay format, script format, movie script format, screenplay formatting rules, scene heading, screenplay margins, screenplay font, how to format a screenplay, screenplay example, one page one minute **TL;DR**: Standard screenplay format is Courier 12pt on US Letter with a 1.5-inch left margin, built from six elements — scene heading, action, character, dialogue, parenthetical, transition — each at a fixed indentation. Done right, one page equals roughly one minute of screen time. Modern screenwriting software applies all of it automatically; your job is knowing the rules well enough to spot when a page is wrong. Screenplay format explained: margins, Courier 12pt, all six elements, the one-page-per-minute rule, formatted samples, and common mistakes to avoid. --- ### How to Write a Screenplay: Step-by-Step Guide (2026) **URL**: https://laper.ai/blog/how-to-write-a-screenplay/ **Date**: 2026-07-05 **Author**: shizhi **Category**: Screenwriting Craft **Keywords**: how to write a screenplay, how to write a movie script, screenplay writing for beginners, screenplay structure, three act structure, how to write a script, screenwriting guide, logline, screenplay outline **TL;DR**: Writing a screenplay is a nine-step process: test your concept, compress it into a logline, outline the beats, structure three acts, write scenes that earn their place, finish a fast first draft, rewrite in focused passes, format to industry standard, and submit strategically. Most of the work happens before page one and after the first draft. How to write a screenplay from concept to submission: logline, outline, three-act structure, scene writing, rewriting, format, and querying. --- ### Fountain Format vs .fdx Files: Screenplay Formats Explained **URL**: https://laper.ai/blog/fountain-format-vs-fdx-screenplay-files/ **Date**: 2026-07-05 **Author**: shizhi **Category**: Screenwriting Craft **Keywords**: fountain format, .fdx file, fountain screenplay format, fdx file format, convert fountain to fdx, screenplay file formats, final draft file format, fountain syntax, plain text screenwriting **TL;DR**: Fountain is a plain-text markup syntax any editor can read; .fdx is Final Draft's XML format and the de facto Hollywood delivery standard. Write in whichever format your software prefers, keep Fountain as your portable archive, and convert to .fdx at delivery via Highland or open-source Fountain tools. Fountain format vs .fdx files explained: plain-text markup syntax, Final Draft's XML standard, conversion paths, and which screenplay file format to use when. If you have ever emailed a script and gotten back "can you send that as a Final Draft file?", or opened a `.fountain` attachment and seen what looked like plain notes instead of a screenplay, this guide is for you. We'll cover what each format actually is, how Fountain's syntax works (with real examples), why `.fdx` occupies the position it does in the industry, when to use which, how to convert between them, and which major screenwriting editors support what. --- ### Laper Now Serves Screenwriting Professionals in More Than 65 Countries **URL**: https://laper.ai/blog/laper-serves-professional-screenwriters-in-65-countries/ **Date**: 2026-06-29 **Author**: shizhi **Category**: Product News **Keywords**: Laper, professional screenwriters, screenplay editor, AI screenplay software, screenwriting workflow, global screenwriters **TL;DR**: Laper now serves screenwriting professionals in more than 65 countries. Our product focus remains the same: a reliable screenplay editor, industry formatting, collaboration, structure, and AI that stays under the writer's control. Laper now serves screenwriting professionals in more than 65 countries. Here is what that means for the screenplay editor we are building. {/* [INPUT]: 依赖 Laper 公开产品定位与作者可核实的运营事实 [OUTPUT]: Laper 全球编剧服务声明文章 [POS]: content/blog 的品牌说明页，AI 能力只使用可验证 scope 表述 [PROTOCOL]: 变更时更新此头部，然后检查 CLAUDE.md */} Laper now serves screenwriting professionals in more than 65 countries. This is not a victory lap about a vanity metric. For us, it is a product signal. Writers working in different languages, production systems, budgets, and team sizes keep running into the same core problems. They need a screenplay editor they can trust. They need industry formatting to stay out of the way. They need teams to work from one script source. They need AI,... --- ### Final Draft vs Laper 2026: Honest Head-to-Head Review **URL**: https://laper.ai/blog/final-draft-vs-laper-honest-comparison/ **Date**: 2026-05-19 **Author**: shizhi **Category**: Comparisons **Keywords**: Final Draft vs Laper, Final Draft alternative, Laper vs Final Draft, AI screenwriting software comparison, real-time collaborative screenwriting, industry standard screenwriting software, screenwriting software **TL;DR**: Pick Final Draft if you deliver .fdx to Hollywood studios and want one-time pricing without AI. Pick Laper if you need real-time CRDT collaboration, full-script AI, or generate visual assets — Junior tier is free. Final Draft vs Laper for screenwriters. Six rounds: collaboration, AI, .fdx format, pricing, visual assets, platform. Honest verdict by persona. {/* [INPUT]: 依赖 Laper 当前功能/价格事实与 Final Draft 公开能力 [OUTPUT]: Final Draft 与 Laper 诚实比较文章 [POS]: content/blog 的 BOFU 比较页；承认竞品优势并明确 Laper 的实际边界 [PROTOCOL]: 变更时更新此头部，然后检查 CLAUDE.md */} --- ### AI Writing Assistants Compared: Novel AI vs Screenplay AI (2026) **URL**: https://laper.ai/blog/2025-11-02-best-ai-novel-writing-tools-2025/ **Date**: 2026-05-19 **Author**: shizhi **Category**: AI Writing Assistants **Keywords**: best AI writing assistants, AI novel writing software, AI screenwriting software, Sudowrite alternative, NovelAI vs Sudowrite, AI for novelists, AI for screenwriters, Laper vs Sudowrite **TL;DR**: Novel AI and screenplay AI solve different problems. Use Sudowrite or NovelAI for fiction prose; use Laper for structured screenplay editing, explicit AI read scopes, and real-time collaboration. Honest comparison of AI writing assistants. Novel AI (Sudowrite, NovelAI, Jasper) vs Screenplay AI (Final Draft, WriterDuet, Laper). Pick the right assistant for what you write. {/* [INPUT]: 依赖小说 AI 工具公开定位与 Laper 当前 screenplay AI scope 事实 [OUTPUT]: 小说 AI 与剧本 AI 工具选型文章 [POS]: content/blog 的跨品类比较页，区分 prose 与 structured screenplay 工作流 [PROTOCOL]: 变更时更新此头部，然后检查 CLAUDE.md */} --- ### Best Script Writing Software 2026: Complete Guide **URL**: https://laper.ai/blog/2026-05-15-best-script-writing-tools-2026/ **Date**: 2026-05-15 **Author**: shizhi **Category**: Screenwriting Software **Keywords**: best script writing software, script writing software 2026, screenwriting software 2026, script writing software, best screenwriting software, Final Draft alternative, Highland Pro, WriterDuet, Laper screenwriting **TL;DR**: Best script writing software 2026: Laper for AI + collaboration, Final Draft 13 for industry standard, Highland Pro for Mac minimalism, WriterDuet for writers' rooms. Best script writing software 2026 reviewed: Final Draft 13, Highland Pro, WriterDuet, Celtx, Fade In, Laper, and more. Pick the right software for your workflow. {/* [INPUT]: 依赖 Laper 当前 AI read scopes、Loro 同步边界与公开工具事实 [OUTPUT]: 2026 script writing tools 比较文章 [POS]: content/blog 的工具选型文章；Laper 技术能力使用可验证口径 [PROTOCOL]: 变更时更新此头部，然后检查 CLAUDE.md */} --- ### AI Screenwriting Software Comparison 2026: Best Software **URL**: https://laper.ai/blog/2026-05-14-ai-screenwriting-tools-comparison-2026/ **Date**: 2026-05-14 (updated 2026-05-15) **Author**: shizhi **Category**: AI Technology **Keywords**: AI screenwriting assistants 2026, Final Draft 13, Movie Magic Screenwriter, WriterDuet, Celtx, Fade In, Highland Pro, Laper, best screenwriting software 2026, AI screenplay generator **TL;DR**: In 2026, Laper leads with multimodal AI (script + storyboards + character art), Final Draft 13 added a real AI Beat Board, and Highland Pro launched. Sudowrite still leads prose. Honest 2026 comparison of AI screenwriting assistants: Final Draft 13, WriterDuet, Celtx, Fade In, Highland Pro vs Laper. See where each wins. The screenwriting software market in 2026 is split. On one side, the **established names** that the industry has run on for two or three decades — **Final Draft, Movie Magic Screenwriter, WriterDuet, Celtx, Fade In, Highland Pro**. On the other, a new generation built around AI, real-time collaboration, and multimodal generation. This piece is honest about both. Where the legacy software win — pagination correctness, FDX interop, production paperwork — we say so. Where they have not kept up — AI generation, real-time collaboration, image/audio/video output — we say that too. And we'll show wher... --- ### Best Screenwriting Software For Writers In 2026 **URL**: https://laper.ai/blog/2026-05-13-best-screenwriting-software-for-writers-2026/ **Date**: 2026-05-13 **Author**: chunxiang **Category**: Software & Comparison **Keywords**: best screenwriting software, best script writing software, best for script writing, best script writing, screenwriting software 2026, best screenwriting software for writers, screenplay software comparison, AI screenwriting assistant **TL;DR**: Best screenwriting software 2026: Laper for AI-assisted writing, Final Draft 13 for industry formatting, Highland Pro for clean writing, WriterDuet for collaboration. Best screenwriting software 2026: Laper, Final Draft, WriterDuet, Celtx compared on formatting, real-time collaboration, AI, and price. {/* [INPUT]: 依赖 Laper 当前功能/价格事实与各竞品公开能力 [OUTPUT]: 2026 screenwriting software 比较文章 [POS]: content/blog 的商业意图横评页；产品断言必须服从 seo/CLAUDE.md 红线 [PROTOCOL]: 变更时更新此头部，然后检查 CLAUDE.md */} Picking the **best screenwriting software** in 2026 is not the same problem it was five years ago. The bar moved. Industry-standard formatting is table stakes. What separates the **best script writing software** from the rest is now: **real-time collaboration that actually works**, **AI that understands story structure (not just autocomplete)**, and a **production pipeline** that follows your screenplay all the way ... --- ### Professional AI Screenplay Editor: Industry Standards 2025 **URL**: https://laper.ai/blog/2025-11-12-professional-ai-screenplay-editor-industry-standards/ **Date**: 2025-11-12 **Author**: chunxiang **Category**: Professional **Keywords**: professional AI screenplay editor, industry standard screenplay software, Hollywood screenplay format, production-ready screenplay, screenplay submission guidelines **TL;DR**: Professional AI screenplay editors must support WGA-standard formatting, .fdx import/export, and revision tracking — Laper meets all three while adding AI structure analysis. Discover professional AI screenplay editors that meet Hollywood industry standards. Learn formatting rules, production requirements, and submission guidelines. Hollywood has strict formatting rules. **Professional AI screenplay editors** automate industry standards so your script looks production-ready—not amateur. --- ### Online AI Screenplay Editor: Best Cloud-Based Software 2025 **URL**: https://laper.ai/blog/2025-11-11-online-ai-screenplay-editor-cloud-based-tools/ **Date**: 2025-11-11 **Author**: chunxiang **Category**: Software **Keywords**: online AI screenplay editor, cloud screenplay software, web-based screenwriting, online screenplay software, browser screenplay editor **TL;DR**: Cloud-based AI screenplay editors run fully in browser — Laper and WriterDuet lead, while Final Draft and Highland remain desktop-locked. Cloud is the 2026 default. Compare online AI screenplay editors for cloud-based writing. Write anywhere, sync automatically, collaborate in real-time without downloads. Desktop software died. **Online AI screenplay editors** let you write from any device, sync automatically, and collaborate in real-time—without installing anything. --- ### AI Screenplay Editor with Collaboration: Best Software 2025 **URL**: https://laper.ai/blog/2025-11-10-ai-screenplay-editor-with-collaboration-features/ **Date**: 2025-11-10 **Author**: chunxiang **Category**: Collaboration **Keywords**: AI screenplay editor collaboration, real-time screenplay editing, collaborative screenwriting software, remote screenwriting software, AI co-writing software **TL;DR**: AI + real-time collaboration unlocks writers' room AI co-writing — Laper combines CRDT-based editing with shared AI sessions, vs. WriterDuet (collab only) and Sudowrite (AI only). Discover AI screenplay editors with real-time collaboration. Compare features for remote teams, co-writers, and writers' rooms in 2025. Remote collaboration killed email attachments. AI screenplay editors with **real-time collaboration** let teams write together—from anywhere—with zero version conflicts. --- ### AI Screenplay Editor for Beginners: Complete Tutorial 2025 **URL**: https://laper.ai/blog/2025-11-09-ai-screenplay-editor-for-beginners-tutorial/ **Date**: 2025-11-09 **Author**: chunxiang **Category**: Tutorial **Keywords**: AI screenplay editor tutorial, how to use screenplay software, AI screenwriting for beginners, screenplay formatting guide, learn screenwriting software **TL;DR**: Beginners can write a first screenplay in 30 minutes with Laper: enter genre and premise, AI generates beats, then write scenes with formatting and structure feedback. Learn how to use AI screenplay editors as a beginner. Step-by-step guide covering setup, formatting, collaboration, and AI features to write your first script. Writing your first screenplay feels overwhelming. Traditional software has steep learning curves, but **AI screenplay editors** make it simple—even if you've never written a script before. This tutorial walks you through everything: setup, formatting, collaboration, and AI features. --- ### Free AI Screenplay Editor: Best Options for 2025 **URL**: https://laper.ai/blog/2025-11-08-free-ai-screenplay-editor-best-options-2025/ **Date**: 2025-11-08 **Author**: chunxiang **Category**: Software **Keywords**: free AI screenplay editor, free screenwriting software, AI screenplay editor no cost, free screenplay software 2025, budget screenwriting software **TL;DR**: Laper Junior is the most capable free AI screenplay editor in 2025 — full editor + AI credits + collaboration, vs. competitors that paywall AI behind subscriptions. Discover the best free AI screenplay editors in 2025. Compare features, limitations, and find the perfect software to start writing without spending a dime. Writing a screenplay shouldn't require a $250 upfront investment. **Free AI screenplay editors** now offer professional features that rival paid software—no credit card required. --- ### AI Screenplay Editor vs Traditional Software: 2025 Comparison **URL**: https://laper.ai/blog/2025-11-07-ai-screenplay-editor-vs-traditional-software/ **Date**: 2025-11-07 **Author**: chunxiang **Category**: Comparison **Keywords**: AI screenplay editor vs traditional, screenplay software comparison, AI vs Final Draft, best screenwriting software, AI writing assistants **TL;DR**: AI screenplay editors generate structured beats and analyze story; traditional software (Final Draft, Celtx) only handles formatting. The future is hybrid — Laper combines both. Compare AI screenplay editors with traditional screenwriting software. Discover which solution fits your workflow, budget, and creative needs in 2025. The screenwriting landscape has fundamentally shifted. Traditional software like Final Draft dominated for decades, but **AI screenplay editors** now offer capabilities that were impossible just two years ago. Should you stick with proven software or embrace AI? This comprehensive comparison reveals the truth. --- ### AI Screenplay Editor: Complete Guide for 2025 **URL**: https://laper.ai/blog/2025-11-06-ai-screenplay-editor-complete-guide-2025/ **Date**: 2025-11-06 **Author**: chunxiang **Category**: Guide **Keywords**: AI screenplay editor, screenplay software 2025, AI screenwriting assistants, best screenplay editor, AI writing assistant **TL;DR**: AI screenplay editors in 2025 use LLMs for structure analysis, beat generation, and character arc tracking — Laper leads the category as the only structure-first AI editor. Discover the best AI screenplay editors in 2025. Learn features, pricing, and how AI transforms screenwriting workflow for professional writers. Artificial intelligence is revolutionizing screenplay writing. AI screenplay editors now offer real-time collaboration, intelligent formatting, and creative suggestions that traditional software can't match. --- ### Best Collaborative Screenplay Software 2025: Remote Writers' Rooms **URL**: https://laper.ai/blog/2025-11-05-best-collaborative-screenplay-software-2025/ **Date**: 2025-11-05 **Author**: chunxiang **Category**: Collaboration **TL;DR**: WriterDuet remains the collaboration standard, Laper adds AI co-writing on top of CRDT-based real-time editing, and Final Draft 13 still requires paid add-ons. Best collaborative screenplay software 2025. Real-time co-writing software, cloud sync, team features for TV writers, indie teams, and co-authors. **Remote writers' rooms are the new normal.** Whether you're running a TV show, co-writing a feature, or workshopping with writing partners, you need **real-time collaborative screenplay software** that actually works. We tested every collaboration feature of **8 major screenwriting software** to find the best platforms for team writing in 2025. --- ### AI Screenwriting Software Comparison 2025: Best Software **URL**: https://laper.ai/blog/2025-11-04-ai-screenwriting-tools-comparison-2025/ **Date**: 2025-11-04 (updated 2026-05-15) **Author**: shizhi **Category**: AI Technology **Keywords**: AI screenwriting assistants, AI screenplay software comparison, best AI for screenwriting, AI script writing software 2025, artificial intelligence screenwriting, AI screenplay generator, machine learning screenwriting **TL;DR**: Only Laper offers true AI for screenplay structure (beat generation, arc tracking) in 2025 — Final Draft, WriterDuet, and Celtx market \"AI\" but ship only autocomplete. AI screenwriting software comparison 2025. How AI screenplay software uses ML for story generation, beat analysis, character development. Find the best. {/* [INPUT]: 依赖 Laper 当前结构化 AI 工具与竞品公开信息 [OUTPUT]: AI screenwriting tools 比较文章 [POS]: content/blog 的品类教育页，AI 上下文口径服从显式 scope 与 bounded full read [PROTOCOL]: 变更时更新此头部，然后检查 CLAUDE.md */} **AI is transforming screenwriting**—but not all "AI screenplay software" is created equal. Some software slap on basic autocomplete and call it "AI." Others use **advanced machine learning** to analyze story structure, character arcs, and dramatic pacing. We tested **every major AI screenwriting assistant** to reveal what they **actually do** versus what they **claim to do**. --- ### Best Free Screenplay Software 2025: Top 7 Software Compared **URL**: https://laper.ai/blog/2025-11-03-best-free-screenplay-software-2025/ **Date**: 2025-11-03 **Author**: chunxiang **Category**: Free Software **Keywords**: best free screenplay software, free screenwriting software 2025, free script writing software, no cost screenplay editor, free screenplay software with AI, best free scriptwriting app, free Final Draft alternative **TL;DR**: The best free screenplay software in 2025: Laper Junior (full editor + AI credits), KIT Scenarist (open-source, multi-platform), and Trelby (Linux-friendly). Best free screenplay software in 2025. Compare 7 free screenwriting software with pro formatting, AI features, and collaboration. No credit card needed. **You don't need to spend $249 on Final Draft** to write professional screenplays. In 2025, several **completely free screenplay software options** offer industry-standard formatting, AI features, and collaboration—without asking for a credit card. We tested every free screenwriting software available to find the **7 best options** that won't cost you a penny. --- ### Top 10 Best Screenplay Editors in 2025: Complete Rankings & Reviews **URL**: https://laper.ai/blog/2025-11-01-top-10-screenplay-editors-2025/ **Date**: 2025-11-01 **Author**: shizhi **Category**: Software Comparison **Keywords**: top 10 screenplay editors, best screenplay editors 2025, screenplay software comparison, top screenwriting software, best script editors, screenplay editor rankings 2025, professional screenwriting software **TL;DR**: Laper, Final Draft, WriterDuet lead the 2025 screenplay editor market — Laper for AI + collaboration, Final Draft for industry formatting, WriterDuet for writers' rooms. Top 10 best screenplay editors in 2025. Compare features, pricing, and AI capabilities of leading screenwriting software. Find your perfect software. Looking for the **best screenplay editor** in 2025? With over 30 screenwriting software on the market, choosing the right one can be overwhelming. We've tested **every major screenplay editor** to bring you definitive rankings based on features, usability, AI capabilities, and value. --- ## Featured Highlights (11) Curated short-form articles on screenwriting craft and AI assistance. ### Why AI Screenplay Editors Are Taking Over Hollywood in 2025 **URL**: https://laper.ai/recent-highlights/2025-11-16-why-ai-screenplay-editors-are-taking-over/ **Date**: 2025-11-16 **Author**: Laper Team **Category**: Industry Analysis **Keywords**: AI screenplay editor adoption, Hollywood AI assistance, why use AI screenplay editor, screenwriting technology shift Explore why AI screenplay editors are replacing traditional software in Hollywood. Discover the technological and cultural shifts driving mass adoption. Desktop software dominated screenwriting for 30 years. Then AI arrived—and **everything changed in 18 months**. By end of 2025, **71% of professional screenwriters use AI screenplay editors**. Here's why the shift happened so fast. --- ### AI Screenplay Editor Success Stories: Real Writers, Real Results **URL**: https://laper.ai/recent-highlights/2025-11-15-ai-screenplay-editor-success-stories/ **Date**: 2025-11-15 **Author**: Laper Team **Category**: Case Studies **Keywords**: AI screenplay editor success stories, screenplay software case studies, AI screenwriting results, professional screenplay software Discover how professional screenwriters use AI screenplay editors to accelerate their workflow, land deals, and win competitions in 2025. AI screenplay editors aren't hype—they're delivering real results. These are **true stories** of writers who used AI assistance (primarily Laper AI) to accelerate their careers in 2025. --- ### The Future of AI Screenplay Editors: 2026-2030 Predictions **URL**: https://laper.ai/recent-highlights/2025-11-14-ai-screenplay-editor-future-predictions/ **Date**: 2025-11-14 **Author**: Laper Team **Category**: Future Tech **Keywords**: AI screenplay editor future, screenwriting technology predictions, voice-to-script, VR writing rooms, future of screenwriting Explore future predictions for AI screenplay editors. Voice-to-script, VR writing rooms, multimodal AI, and what's next for screenwriting technology. AI screenplay editors transformed screenwriting in just 3 years. What's next? **Voice-to-script**, **VR collaboration**, **AI co-writers trained on your style**—and features we haven't imagined yet. --- ### AI Screenplay Editor Market Trends: 2025 Industry Report **URL**: https://laper.ai/recent-highlights/2025-11-13-ai-screenplay-editor-market-trends-2025/ **Date**: 2025-11-13 **Author**: Laper Team **Category**: Industry Trends **Keywords**: AI screenplay editor trends, screenwriting software market, AI adoption screenwriting, screenplay editor statistics 2025 Explore AI screenplay editor market growth, adoption rates, and future predictions for 2025. See how AI is transforming the screenwriting industry. The **AI screenplay editor market** exploded in 2024-2025. Cloud-based software now dominate, traditional desktop software is declining, and AI features are no longer optional—they're expected. --- ### AI Screenwriting Assistant vs Traditional AI: Why Assistants Win 2025 **URL**: https://laper.ai/recent-highlights/2025-10-13-ai-screenplay-agent-technology/ **Date**: 2025-10-13 **Author**: Laper Engineering Team **Category**: Technology Deep Dive **Keywords**: AI screenwriting assistant, AI assistant, screenplay AI technology, intelligent screenwriting assistant, AI assistant architecture, Claude Sonnet 4, AI vs generator, screenplay AI comparison AI screenwriting assistants vs traditional AI generators. Laper's assistant (Claude Sonnet 4) delivers creative assistance via perception, decision, and action. **Not all AI is created equal.** The difference between an **AI screenwriting assistant** and a traditional AI generator is like the difference between a chess grandmaster and a calculator—both use computation, but one *understands* the game while the other just follows rules. In 2025, the most advanced **screenplay AI assistants** (like Laper) use **assistant architectures** built on state-of-the-art models like **Claude Sonnet 4**. This guide explains why **AI assistants** are revolutionizing screenwriting, how they work, and what the future holds. --- --- ### AI Collaboration Software for Screenwriters: Real-Time 2025 **URL**: https://laper.ai/recent-highlights/2025-10-13-ai-collaboration-screenwriting/ **Date**: 2025-10-13 **Author**: Laper Technical Team **Category**: Collaboration **Keywords**: AI collaboration, screenplay collaboration, real-time collaboration, team screenwriting, collaborative writing, AI collaboration software, CRDT screenplay, remote screenwriting How AI collaboration software transform screenplay writing. CRDT tech, real-time sync, zero-conflict editing. Why Laper leads remote writing teams. **Screenwriting has always been collaborative**—but until now, the *software* weren't. Email chains, version confusion, and "Who saved last?" nightmares have plagued writing teams for decades. In 2025, **AI collaboration software** are finally solving this problem with **real-time synchronization**, **conflict-free editing**, and **intelligent assistance** that makes team writing feel effortless. This guide covers everything you need to know about modern **screenplay collaboration** technology, from the science behind **CRDT** to practical workflows for TV writers' rooms. --- --- ### Complete Guide to AI Screenplay Writing in 2025: From Beginner to Pro **URL**: https://laper.ai/recent-highlights/2025-10-13-ai-screenplay-writing-guide/ **Date**: 2025-10-13 **Author**: Laper Content Team **Category**: Tutorial **Keywords**: AI screenplay, AI screenplay writing, AI screenplay assistant, screenplay AI, AI screenwriting, how to write screenplay with AI, AI screenplay software, screenplay writing guide 2025 Master AI screenplay writing with our complete 2025 guide. How AI assistance work, step-by-step workflows, Hollywood tips, and mistakes to avoid. **AI screenplay writing is transforming Hollywood.** What used to take months can now be achieved in weeks—but only if you understand how to leverage AI assistance effectively. This comprehensive guide will take you from complete beginner to confident AI screenplay writer. --- --- ### Best AI Screenplay Software in 2025: Complete Comparison & Rankings **URL**: https://laper.ai/recent-highlights/2025-09-20-best-ai-screenplay-software/ **Date**: 2025-09-20 **Author**: Laper Research Team **Category**: Product Comparison **Keywords**: AI screenplay software, best screenwriting software 2025, AI script writing software, screenplay AI assistant, screenwriting software comparison, Laper vs Final Draft, AI screenwriting Top 7 AI-powered screenplay writing software in 2025 compared. Detailed feature analysis, pricing, and pros/cons for your workflow. **AI is revolutionizing screenwriting.** But with dozens of software claiming to be "AI-powered," which ones actually deliver? We tested **7 leading screenplay software platforms** to find the best options for professional writers in 2025. --- ### The AI Storytelling Revolution: ML Reshaping Screenplays **URL**: https://laper.ai/recent-highlights/2025-09-05-ai-storytelling-revolution/ **Date**: 2025-09-05 **Author**: Dr. Sarah Chen, Laper Research **Category**: Industry Insight **Keywords**: AI storytelling, machine learning, screenplay AI, creative technology, narrative AI Explore how AI-assisted software are transforming the creative process for screenwriters, from beat generation to character arc optimization. **Artificial intelligence** is no longer science fiction—it's now a **creative partner** in the screenwriting process. But can machines truly understand the nuances of human storytelling? --- ### The Ultimate Guide to Professional Screenplay Formatting **URL**: https://laper.ai/recent-highlights/2025-08-15-screenplay-formatting-guide/ **Date**: 2025-08-15 **Author**: Marcus Rodriguez, Script Consultant **Category**: Writing Tips **Keywords**: screenplay formatting, script writing, industry standards, Courier font, script margins Master the industry-standard screenplay formatting rules that will make your script stand out to producers and agents. **First impressions matter.** A poorly formatted screenplay signals **amateur hour** to Hollywood gatekeepers. Here's everything you need to know about industry-standard formatting. --- ### Collaborative Screenwriting: Writing Rooms in the Digital Age **URL**: https://laper.ai/recent-highlights/2025-07-22-collaborative-screenwriting/ **Date**: 2025-07-22 **Author**: Jennifer Park, TV Writer & Showrunner **Category**: Writing Tips **Keywords**: collaborative writing, writers room, TV writing, remote collaboration, screenwriting team Learn how modern TV writers' rooms leverage technology for remote collaboration while preserving the creative magic of traditional brainstorming. **The TV writers' room** is where the magic happens—or the chaos unfolds. In the age of remote work, how do teams maintain creative synergy when they're scattered across time zones? --- ## Product Changelog (6) Version history and feature releases for the Laper platform. ### Laper 0.4.1 - Design System Refinement **URL**: https://laper.ai/changelog/2026-01-09-v0-4-1/ **Date**: 2026-01-09 **Author**: Laper Product Team **Category**: Product Update **Keywords**: Laper 0.4.1, design system, typography, UI consistency, toolbar Unified typography system, streamlined toolbar actions, and consistent icon sizing across all components. This release focuses on design system consistency, unifying typography across all components and streamlining the toolbar experience for a cleaner interface. --- ### Laper 0.4.0 - Project Intelligence **URL**: https://laper.ai/changelog/2026-01-05-v0-4-0/ **Date**: 2026-01-05 **Author**: Laper Product Team **Category**: Product Update **Keywords**: Laper 0.4.0, ScriptToolPanel, Timeline, credits, project metadata, CRDT ScriptToolPanel v2.0 with LoroDoc data display, Timeline multi-track architecture, enhanced credits system, and project metadata insights. This release brings intelligent project insights with the redesigned ScriptToolPanel, professional-grade Timeline editing, and a refined credits system for AI-powered features. --- ### Laper 0.3.0 - Localization & Polish **URL**: https://laper.ai/changelog/2025-11-23-v0-3-0/ **Date**: 2025-11-23 **Author**: Laper Product Team **Category**: Product Update **Keywords**: Laper 0.3.0, localization, i18n, multilingual, design system, animations Complete 11-language localization across 33 namespaces, unified design system with theme colors, and stunning Landing Hero animations. This release brings Laper to a global audience with comprehensive localization support while polishing the visual experience with design system refinements and stunning animations. --- ### Laper 0.2.0 - WorkSpace Evolution **URL**: https://laper.ai/changelog/2025-11-15-v0-2-0/ **Date**: 2025-11-15 **Author**: Laper Product Team **Category**: Product Update **Keywords**: Laper 0.2.0, WorkSpace, MVVM, file import, SSE streaming, AI assistant WorkSpace output panel optimization, Create page MVVM architecture refactor, file import workflow, and SSE streaming enhancements. This release transforms the WorkSpace experience with a complete architectural refactor, intelligent file import capabilities, and enhanced AI-powered content creation. --- ### Laper 0.1.0 - Foundation **URL**: https://laper.ai/changelog/2025-11-10-v0-1-0/ **Date**: 2025-11-10 **Author**: Laper Product Team **Category**: Product Update **Keywords**: Laper 0.1.0, CRDT, TypeScript, WebSocket, real-time sync, performance CRDT TypeScript unified module, Loro WebSocket synchronization, GEB fractal documentation protocol, and comprehensive performance optimizations. This release establishes the architectural foundation for Laper's collaborative editing system, featuring a complete TypeScript rewrite of the CRDT layer and real-time WebSocket synchronization. --- ### Laper 0.0.1 - Initial Alpha Release **URL**: https://laper.ai/changelog/2025-10-06-v0-0-1/ **Date**: 2025-10-06 **Author**: Laper Product Team **Category**: Product Update **Keywords**: Laper 0.0.1, screenplay software, AI screenwriting, collaborative writing, alpha release The first alpha release of Laper, a professional AI-powered screenplay collaboration platform built for modern screenwriters. We're excited to introduce **Laper 0.0.1**, the first alpha release of our AI-powered screenplay collaboration platform. This release marks the beginning of our journey to revolutionize how screenwriters work together. --- ## Author Profiles (2) Biographies of Laper team members and contributors. ### Editorial Screenwriting Advisor **URL**: https://laper.ai/authors/chunxiang/ **Keywords**: screenwriting, story structure, dialogue, screenplay format, screenwriting craft Editorial Screenwriting Advisor at Laper. Working screenwriter contributing craft-side perspectives on story structure, dialogue, and screenplay format. **Editorial Screenwriting Advisor at [Laper](https://laper.ai)** — a working screenwriter who reviews and contributes to Laper's editorial coverage of screenwriting software, craft, and workflows. --- ### Founder, Laper **URL**: https://laper.ai/authors/shizhi/ **Keywords**: AI screenwriting assistant, CRDT collaboration, Plate.js, creative writing software, Laper founder Founder of Laper. Building an AI-native screenwriting assistant and screenplay editor for professional writers. {/* [INPUT]: 依赖当前 Laper 编辑器、AI scope、Loro 同步与公开作者资料事实 [OUTPUT]: Shizhi 作者实体正文与编辑原则 [POS]: content/authors 的创始人 E-E-A-T 资料页，被作者页与文章署名引用 [PROTOCOL]: 变更时更新此头部，然后检查 CLAUDE.md */} **Founder of [Laper](https://laper.ai)** — an AI-native screenwriting platform for professional writers, directors, and production teams. --- --- ## Generation Notes - **Generated**: 2026-10-14T01:31:39.345Z - **Total articles indexed**: 92 - **Source**: content/**/*.en.mdx plus Docs i18n/en.yaml ordered by catalog.yaml - **Update frequency**: Regenerated on every `bun run build` - **For shorter summary**: See [llms.txt](https://laper.ai/llms.txt) - **For full sitemap**: See [sitemap.xml](https://laper.ai/sitemap.xml)