An AI table read for pages that have never been spoken
A table read tells you what the page cannot: which lines land, which drag, which joke is three words too long. Render every scene in draft and listen to the whole script in order.
DMITRI
You film it, you forget you filmed it.
EZRA
That's not how cameras work.
RENDERS AS 9:16
Read-through in draft quality
The point of a table read is speed, not polish. Queue every scene at Draft quality, where a 5-second clip costs five credits and a 10-second clip ten, and let the queue work through the script. Cast members are described in words at this tier rather than matched by face, which is fine for hearing the lines.
When the renders complete, the rail shows them in script order. Play them top to bottom. You will hear pacing problems in minutes that take a week of silent rereading to notice.
Notes go straight back into the page
Because the clips sit beside the editor, a note becomes an edit immediately. Trim the line, move the beat, cut the scene. Re-render only the scenes you touched; the rest keep their clips. The script is saved as you go, so a read-through from last week can be reopened and compared with today's pass.
The co-writer can help here too. Give it the logline and a tone, let it draft alternatives for a scene that is not working, and keep what improves the read.
Graduate the keepers
Once the script reads well, the same scenes can be rendered at Standard or Cinematic quality with full cast references: likeness, wardrobe, props and sets. Nothing about the workflow changes, only the credit cost per scene and the fidelity of the result.
Keep the draft clips private, share the finished ones from their own pages, or download everything as MP4s.
What a read-through catches
Lines that are grammatical on paper but impossible to say in one breath. Two characters who sound identical. An exposition speech that should be three exchanges. A scene that ends a beat after it should. Hearing the pages performed, even roughly, surfaces all of these faster than any silent pass, and because the clips are right beside the text the fix is a keystroke away.
Sample scenes
Rendered from scripts like yours
Take nine
INT. RECORDING BOOTH - NIGHT
Level three
INT. UNDERGROUND CAR PARK - NIGHT
The ticket
INT. NIGHT DINER - 2 A.M.
Verdict
EXT. COURTHOUSE STEPS - MORNING
FAQ
Questions
How much does a draft table read cost?
Draft renders at 720p cost one credit per second. A ten-scene script at five seconds a scene is fifty credits, which fits inside the Draft monthly plan with room to re-render.
Do draft renders use my cast?
Draft quality describes each cast member in words rather than matching a reference image, so faces will differ between scenes. Standard and Cinematic quality match the library portrait.
Can I render the scenes in a different order?
Scenes render in the order you queue them but are listed in script order afterwards. Reordering the script itself is done in the editor by moving the headings.
Who owns the read-through clips?
You do. Anything the service renders at your direction is yours, as the Terms of Service set out. Copyright treatment varies by country; for a specific question, consult a lawyer.
Is there a limit on script length?
Scripts up to 40,000 characters and 40 scenes are supported. Up to twelve scenes can be queued in one go; queue again for the next batch.
Ready when the pages are
Sign in, paste a script or ask the co-writer for one, and render your first scene.