RenderScript Studio logo

Screenplay in. RenderPackage out.

Example RenderPackage

Build a RenderPackage

RenderScript packages one screenplay scene into a RenderPackage - a practical workflow for AI video generation.

The output is a downloadable .zip file containing a structured production kit: shot planning files, provider-ready prompts, a Keeper Sheet, and audio post-production guides.

  1. Upload a screenplay in .fountain format. Fountain is a plain-text screenplay format that is easy to read, version, and convert from common script tools.
  2. Select the scene you want to package. If the script contains only one scene, scene 1 is selected automatically.
  3. Choose your prompt packs and build the RenderPackage.
Accepted screenplay format: .fountain (also supports .fnt). Single-scene scripts default to scene 1.
Builds a RenderPackage .zip for one scene.
Use the package in your chosen AI video workflow.

For Creators

RenderScript is designed for writer-directors and small teams exploring AI filmmaking.

Instead of treating each generation as a one-off prompt, RenderScript creates a repeatable production workflow built around shots, takes, keepers, and editing.

The system follows a picture-first approach: generate visuals first, then handle dialogue, sound effects, and mix in post.

This mirrors real production workflows and helps maintain visual continuity while working with AI video tools.

The result is fewer random rerolls, clearer creative decisions, and a smoother path from screenplay scene to rough cut.

For Developers

RenderScript is not just a UI tool. It is a programmable packaging layer between screenplay text and downstream AI video workflows. Creators will usually use the Studio UI. Developers will use the CLI and GitHub when they need automation, integration, adapters, and pipeline control.

Why use the CLI

Use the CLI when package generation needs to be repeatable and scriptable. That includes generating packages programmatically, batch processing scenes or scripts, integrating RenderScript into CI, validating screenplay inputs automatically, and running QA on generated shot plans before anyone starts generation work.

What developers can build

  • Provider adapters for specific AI video workflows
  • Validation and QA checks around screenplay and package outputs
  • Internal tools that wrap RenderPackage generation
  • Pipeline integrations for studio or cloud workflows
  • Downstream orchestration systems built around RenderPackage

Why RenderPackage exists

RenderPackage exists to remove ambiguity between screenplay text and generation workflows.

Screenplays are written for humans and can be interpreted in many ways. RenderScript converts one scene into a deterministic generation plan: a shot list, reference bindings, prompt blocks, and a machine-readable package contract.

This means downstream tools do not need to parse screenplay text or infer shot structure. They can operate directly on the structured package data.

The package is designed so that:

  • Creators work in screenplay language
  • The package provides a stable handoff format
  • Developers can build automation, validation, or adapters around the package without modifying the creator workflow

The machine-readable contract for the package lives in:

dev/rpack.json

Core package contract

RenderPackage is designed to be machine-consumable. Creator-facing files are included for workflow use, but developer tooling should rely on the machine-readable contract in dev/rpack.json. The format is export-first, portable, and intentionally structured to support adapters, validation, and downstream orchestration.

CLI quick start

  • python3 -m pip install -e .
  • renderscript package path/to/script.fountain --scene 1 --provider universal -o ./out/package.zip
  • renderscript package path/to/script.fountain --scene 1 --provider universal --add-pack grok.imagine -o ./out/package.zip

Provider options

  • Universal → universal
  • Runway Gen-4 References → runway.gen4_image_refs
  • Grok Imagine → grok.imagine

Where to go next

  • Studio UI
    renderscript.studio
  • GitHub
    https://github.com/ioioioan/renderscript

About RenderScript

RenderScript prepares screenplay scenes for AI video production.

It converts a scene into a RenderPackage: a structured toolkit containing shot planning files, prompt packs, asset bindings, and post-production guides.

The goal is simple - make screenplay structure usable in AI video workflows.

RenderScript does not generate video. It builds a production package that creators run in their chosen AI video tools.