Choose the page format and review information before exporting. For a quick review sheet, Krita’s procedural rows, columns, or grid layouts may be enough. If the page needs a fixed paper structure, separate comment and sound areas, or shot-level metadata, use an SVG template and match its labels to the comment-track names in the Storyboard Docker. After moving scenes, review the exported page as a set of linked fields: image, shot number, duration, and notes.
Decide the sheet, then build it
Start with the recipient’s review task. If they only need to compare scene flow, choose a simple layout and a readable number of shots per page. If they must annotate dialogue separately from action, or use a specified paper size and orientation, define those areas before choosing a template. The export dialog supports page size and orientation; procedural layouts also expose rows or columns per page. Krita exports storyboards as PDF or SVG. See the Storyboard Docker export options.
Use this sequence:
- In the Storyboard Docker, settle the scene order, editable names, durations, and comment content. A scene thumbnail represents its first keyframe, while a scene can contain multiple keyframes over its duration. Its starting frame number is shown but cannot be edited.
- Configure the comment fields you need, such as
commentfor action andsoundfor dialogue or effects. Name and order them for the production team, then fill in the relevant fields on each scene. - Pick the export path. Use a procedural layout when its available arrangement and page controls meet the brief. Choose a custom SVG when you need controlled placement of images, notes, metadata, and page furniture.
- For a custom template, put placement rectangles in the SVG
layoutlayer. Treat the numeric suffix as a shared shot-position index: for the first position, pairimage0,shot0,time0, and each track rectangle such ascomment0andsound0; use suffix1for the second position, and continue consistently. Comment rectangle names must also match the Docker’s comment-field names. Includepage-numberandpage-timewhere needed. The label, not its color, identifies a rectangle’s role. The SVG template guide describes these mappings. - Export a review copy, then compare each printed field with its scene in Krita. Re-export after any reorder or timing change.
Hypothetical three-shot acceptance sheet
This is an author-recommended checking method, not a report of a completed export or a guarantee of Krita’s page-time calculation. Assume a project at 24 frames per second, scenes placed continuously with no gaps, and a timeline beginning at frame 1; the custom page is intended to hold three shots. The example durations are illustrative. Under these assumptions, the start frames below are arithmetic estimates; use the starting frame displayed by Krita for the actual project. At 24 fps, the listed frame counts correspond arithmetically to the listed durations.
| Page position | Scene after reorder | Start frame in Docker | Duration | Page running time | SVG fields to compare | Hypothetical observation and decision |
|---|---|---|---|---|---|---|
| 1 | B, moved before A | 1 | 2 s / 48 frames | 2 s | image0, shot0, time0, comment0, sound0 | Image B and both B notes appear with its shot and time; accept this row. |
| 2 | A | 49 | 3 s / 72 frames | 5 s | image1, shot1, time1, comment1, sound1 | If the A image is paired with B’s action note, reject and check comment labels and scene entries. |
| 3 | C | 121 | 1.5 s / 36 frames | 6.5 s | image2, shot2, time2, comment2, sound2 | Confirm C’s notes and timing together; compare the page total with the sum in this worksheet. |
Here, “page running time” is the worksheet’s cumulative sum in the displayed order, not a claim about how Krita calculates or prints page-time. The guide defines time as shot duration in Seconds + Frames format and page-time as the total duration of shots on a page. If the exported SVG’s labels or values do not match the intended rows, treat the mismatch as a failed association even if the artwork looks right.
Limits and next steps when it fails
A template label is a data contract: sound0 will not mean “sound” merely because its rectangle is drawn in a particular color. Check the actual label and its numeric suffix. Ensure each scene’s comment fields contain the intended text, and confirm the template’s comment-track labels match the Docker names. If text appears misplaced, the template guide notes that text transformations may render differently in other programs; it suggests converting affected text to paths in Inkscape. Test the revised template with a small export before relying on it for the full sheet.
If a thumbnail is wrong, inspect the scene’s canvas content and keyframe at that scene’s time; the thumbnail is not directly edited in the Docker. If timing or order is wrong, correct the scene data in Krita and export again. The documentation does not promise that every custom layout will fit arbitrary content legibly, nor does it define a universal page-time rounding rule. Check the resulting PDF or SVG at its intended reading size and verify totals using the project’s frame rate.
Sources and next step
- Storyboard Docker — Krita Manual 5.3.0 documentation
- SVG Storyboard Export Templates — Krita Manual 5.3.0 documentation
This guide interprets public documentation and uses explicitly hypothetical acceptance examples, not application tests. Controls and availability can change; verify the cited manual against your installed version.
Documentation and production boundary
LTX Studio: Script to Video is a vendor-specific workflow reference. The decision record above is our original manual review method. Use Imagild's current film planning workspace for supported planning steps and inspect the current interface before choosing an input or generation mode. Do not infer an available control from another vendor's documentation.