
Transfer the CSV exposure sheet together with its matching .frames directory. In Krita's documented animation CSV format, the CSV describes the project and timing while the companion directory contains image files. Sending the small spreadsheet-like file alone does not send the drawings.
Key Takeaways
- Keep the CSV and its same-name
.framesdirectory together at the same path level.- Open the CSV as a document; it is not an image sequence for Import Animation Frames.
- Check supported color and layer features before promising an editable cross-application exchange.
Treat the CSV and folder as one package
Krita's CSV documentation describes an animation exchange based on an exposure sheet and image files. The companion folder uses the CSV's base name followed by .frames. A CSV named gesture.csv therefore travels with gesture.frames beside it.
Preserve that relationship when creating an archive or moving the files to another machine. Avoid renaming just the CSV after collecting the folder. Before uploading a handoff, open the archive's contents and confirm that the two items remain siblings rather than one being nested inside an extra folder level.
Keep a native KRA master too. An exchange file serves a different purpose from a full native backup. The format documentation describes restrictions around features such as groups and masks and recommends an 8-bit sRGB workflow for TVPaint exchange. A document containing sophisticated layer structures needs a deliberate simplified exchange version, not an assumption that the other application will recreate every native feature.
Use document opening rather than frame import
The documented workflow uses normal document loading and saving. Import Animation Frames consumes image files; it is not the operation that reads this CSV exposure sheet. Likewise, Render Animation produces rendered output rather than the editable timing exchange described here.
Open the packaged CSV in a separate session and examine the timeline. If timing appears but pictures are absent, inspect the companion directory's location and filenames before changing document FPS. A missing-resource fault and an incorrectly paced animation can look related while requiring different fixes.
Do not assume that any application capable of opening a CSV table supports this particular animation format. Confirm compatibility with the receiving artist and application first. Reading cells as text is not the same as reconstructing layers, drawings and holds.
Compare exposure changes after exchange
Suppose a hypothetical shot contains a held anticipation pose, a quick action and a held finishing pose. The handoff should reproduce when each new drawing begins, not merely contain the same number of image files. This format can describe one drawing held across several timeline frames, so unique image count alone is an unsuitable acceptance test.
Ask the receiver to check the first exposure, an agreed action change and the last held interval. Compare project FPS and the intended range. If a correction changes timing, use the timeline spacing workflow before exporting again. If it changes one drawing independently, review clone versus duplicate behavior in the native source.
Include a short handoff note with the CSV filename, companion directory, project rate, expected duration and any simplified layers. Keep the original package until the recipient confirms both drawings and timing. A successful archive upload verifies transport; reopening and comparing the exposures verifies the animation exchange.
Related tasks
- When to Clone or Duplicate an AI Keyframe in Krita
- How to Insert Time Across Visible Layers in Krita’s Timeline
- How to Render and Verify a Repaired Frame Range in Krita
Sources and scope
- *.csv: Layered animation exchange consists of a CSV exposure sheet plus a same-name .frames directory at the same path.; Use document load/save rather than Import Animation Frames and Render Animation for this format.; Groups and layer masks are not supported; 8-bit sRGB is recommended for TVPaint exchange.
Documentation-based workflow. The example describes a proposed check, not a reported test result.
Prepared by Imagild Editorial, the company editorial team responsible for these guides. AI assisted research and drafting. This is documentation-based guidance with proposed examples, not a claim of hands-on testing or an independent product review. Report a correction.
Cover: AI-generated conceptual editorial illustration; not a real application screenshot, observed output or before-and-after test.