File handoff · Reviewed 2026-10-18
ArtCraft file compatibility: import, editing & round trips
Read published file-format claims correctly, then verify editable structure, final exports and the receiving workflow.
There are three different compatibility questions
Import asks whether an application can read the source. Editing asks whether the elements you need can still be changed. A round trip asks what survives after saving and opening the result somewhere else. Record the answer to each question for the exact sample and build you use.
A final image can satisfy a delivery requirement while leaving editable layers unavailable. Likewise, a video can play correctly while its project timeline cannot be transferred. Decide which kind of handoff the recipient expects before reading a format list.
Published formats and the boundary to test
| App | Publisher describes | Your separate handoff question |
|---|---|---|
| PhotoCraft | PSD/PSB opening and saving | Do the layers, type and masks you need survive? |
| VectorCraft | SVG/PDF import and export | Do paths, text and effects remain usable downstream? |
| FilmCraft | Codecs including H.264, HEVC and ProRes | Does the exact media work, and how will the editable project move? |
| LightCraft | Raw families including DNG, CR2, ARW and NEF | Does your camera variant decode, and what happens to catalogue information? |
Sources: Photocraft publisher page · Vectorcraft publisher page · Filmcraft publisher page · Lightcraft publisher page
An extension does not describe the whole file
A layered image can contain text, masks, profiles and linked objects. A vector document can rely on fonts, clipping and effects. Two files with the same extension can therefore exercise different parts of an editor.
With video, keep the media container, encoded streams and editing project distinct in your notes. With raw photography, record the camera model and raw mode as well as the extension. These details make a failed sample useful to investigate.
Make an evidence table for your own files
| Record | Example of a useful entry |
|---|---|
| Sample | A duplicate of the client poster with live text and a clipped gradient |
| Environment | The exact app build, operating system and receiving editor |
| Required edit | Change a word without flattening the text |
| Saved output | A new layered file and a separate reference image |
| Observed result | Text reopens but a line wraps differently |
| Decision | Accept final image output; keep editable source in the current workflow |
Handle uncertainty without losing the result
Mark a requirement untested when you have not exercised it. Mark it failed when you observed a mismatch, and attach the stage where that mismatch first appeared. A passed check should name the file and the condition under which it passed.
Do not generalize one successful sample to every file in an archive. Add a second sample when it introduces a new dependency, such as a different camera, a font or a linked asset. Repeat only the affected checks after a change so the evaluation stays manageable.