01

Start a project

There are two doors into Hamlet.

  • From ScriptHooks: every script result has a Create this in Hamlet action. One click opens Hamlet, creates the project, and loads your script word for word, along with the shot direction ScriptHooks wrote for it.
  • From Hamlet directly: at hamlet.video, pick a template (Cinematic Trailer, Anime Scene, Product Ad, UGC, and more) or a Blank project, then describe a story or paste a script. Templates preset the style, engine, format, music, and narration voice, so you just bring the story.
Pro Tip

For shot-for-shot control, generate your script in ScriptHooks with the Film / Director's Spec script type. It writes a timecoded shooting document that Hamlet follows exactly: your beats, your camera moves, your cuts.

02

Generate the plan

In 01_Scripting, hit Generate plan (or Re-plan). Hamlet decomposes your story into a shot list: each shot gets a visual description, framing, a camera move, a duration, the characters in it, and any dialogue attributed to its speaker. Narration is split across shots so every line lands where it belongs.

If your script came from ScriptHooks with timecoded visual direction, the shot list is built from that direction rather than invented. Every shot stays editable: click any row to change its description, framing, camera, or timing.

03

Lock your look with key art

Before storyboarding, generate the key art: one reference image that defines the film's whole visual world. Every storyboard frame anchors to it, which is what keeps shot one and shot twelve looking like the same movie. You can generate it from your plan, restyle an uploaded image, or regenerate variations until the look is right.

04

Cast your characters and their voices

In 02_Cast & World, every character gets a canonical portrait, minted in your film's style. That portrait is the identity anchor for every board and every render. To strengthen it, add extra angles (generated or real photos: real photos are strongest), define wardrobe looks for different story stages, and use Lock character to train a dedicated identity model for a character you will reuse.

Each character also gets their own voice, picked automatically and changeable with a click (with previews). Dialogue written as NAME: line in your script is always spoken in that character's voice, in every shot.

05

Storyboard

Hit Storyboard and Hamlet generates a still for every shot: the exact first frame the video will animate from. Boards chain to each other so continuity carries forward, and a quality check regenerates boards that drift off model before you spend render credits.

Fix any board by editing the shot's text and hitting Reframe, or upload your own frame for full control.

06

Animate

Render per shot or run the whole episode. Each shot routes to the right engine (Seedance, Kling, or Veo) automatically, and every render shows its exact credit cost before you confirm. Rendered takes keep a history, so re-rolling a shot never loses the previous version: you can always revert.

07

Edit and export

Finished shots land on a real timeline in 04_Editing: reorder, trim, and mix. Voiceover is laid per shot in each character's locked voice, music and ambient sound come from 05_Scoring, and lip-sync passes put dialogue on faces. Export a finished MP4 when the cut is right.

Frequently Asked Questions

No. Hamlet shares accounts with ScriptHooks. Sign in at hamlet.video with the same login and everything just works.

Planning is free: you can write, generate a shot plan, and build the project structure without paying. Generating images (key art, character portraits, storyboards) and rendering video costs credits.

Credits are sold in one-time packs, from 900 credits for $10 up to 10,000 credits for $100. No subscription is required and credits never expire. Every generation shows its exact credit cost before you run it, and there is no free video tier: video is genuinely expensive to run, so we price it honestly instead of faking an unlimited plan.

Yes. ScriptHooks members get 25% off their first credit pack with the code TRYHAMLET at checkout, valid through August 5, 2026.

Storyboards are generated with Google's Gemini image models. Video renders route between ByteDance Seedance 2.0, Kling, and Google Veo 3.1, chosen per shot automatically, and you can force a specific engine per project or per shot.

Some video engines refuse photoreal human faces as a safety measure. When that happens, use Retry on Kling on that shot: Kling handles photoreal people reliably, and Hamlet routes crowd and human-heavy shots there automatically in most cases.

Yes. When you use Create this in Hamlet, your script arrives word for word, and the timecoded visual direction that ScriptHooks writes becomes Hamlet's shot list: your framing, camera moves, and timing. For full shot-for-shot control, generate the script with the Film / Director's Spec type.

Every character gets a canonical portrait that all storyboards and renders anchor to, plus optional extra angles and real photo uploads. Each character also gets their own voice that stays consistent across every line of dialogue. For the strongest lock, use Lock character to train a per-character identity model.

Individual shots render at roughly 4 to 15 seconds depending on the engine. Projects assemble any number of shots on the timeline, so finished cuts of several minutes are normal. Trailers and shorts of 15 to 90 seconds are the sweet spot.

Yes. Upload your own key art, character photos, and storyboard frames, and bring your own audio through the media library to use as the score. Real photos are the strongest identity anchor for characters.