How it works
The workflow, examples and limits behind every tool.
Shot editor ↗
Each shot stores a title, shot size, duration, action, dialogue and optional resized image.
Example: Create a 5-second wide shot, followed by a 3-second close-up.
Up to 24 shots. JPEG, PNG and WebP inputs up to 12 MiB are resized locally to at most 640 × 360 JPEG.
Shot order ↗
Reordering moves the whole shot, including its image and timing. IDs remain stable.
Example: Move the final close-up before the wide shot without re-entering its dialogue.
This is a local storyboard, without shared editing, automatic generation or video rendering.
Timing sheet ↗
Each start is the sum of preceding durations; the final end is the total running time.
Example: Durations of 5 and 3 seconds produce spans 0–5 and 5–8 seconds.
No overlaps or transitions are modeled. Timing is a planning estimate, not a rendered movie timeline.
Print & backup ↗
JSON includes resized images. CSV contains text and times; printing uses the browser’s PDF dialog.
Example: Export a JSON project to move your storyboard, including images, to a second browser.
Images and notes autosave locally. Storage space can fill; export a backup if saving fails.
Local work, explicit limits
Each workspace reports its input and file limits. Imports validate the supported format before asking to replace saved work. Plain text is displayed as text, never executed as markup. Both languages use the same tools; the root address always opens in English, with Chinese under /zh/.