AI Design Files: What Remains Editable After Export?

Ask what your team must change next, then inspect whether the delivered file supports that edit. An attractive preview is not evidence that its headline is editable text, its illustration is a vector object or its layout can adapt to another size.

This reference defines editability through twelve acceptance checks. It covers two-dimensional design deliverables from AI-assisted work, not a ranking of design tools. The examples and worksheet are proposed methods; no conversion benchmark or editor compatibility test was performed.

Start with an ordinary request: change the headline without repainting the background, replace the photograph without disturbing its mask, or widen a panel while preserving its spacing. Each request defines an observable capability. A contract that says only editable leaves all of these questions open.

Pixels can be edited, but that does not make the pictured objects independently editable. A person can paint over a word in a flattened image; that is different from selecting the text and typing a replacement. Likewise, moving an entire screenshot is different from moving a button inside the design.

Choose the editing environment before acceptance. Native project features may depend on the application and version that created them. A successful preview in another viewer proves appearance in that viewer, not a lossless editing round trip. For broader output checks, see the file deliverable reference.

The table groups twelve proposed checks into visible edits, structural edits and dependencies. The final column is the action to attempt in the agreed editor. Apply only the checks required by the brief, but retain failed and unknown items rather than silently removing them.

A result is pass only when the delivered package supports the requested operation. Mark fail when the operation cannot be completed as agreed, unknown when it has not been checked, and not applicable when the brief does not require it. A screenshot of the original design cannot substitute for evidence of the edited result.

The SVG 2 embedded-content specification permits image resources inside an SVG document. An SVG file can therefore contain a bitmap rather than the independent paths a buyer expected. Inspect the object structure before accepting the file as editable vector artwork.

The SVG text specification describes text as a distinct kind of content. Converting letters to paths can preserve their appearance while losing convenient character-level editing. Whether that tradeoff is acceptable depends on the requested revision: a fixed logo and frequently translated campaign copy have different needs.

Layer count is equally incomplete evidence. A project with separate background and foreground layers may still bake every headline into the foreground. Ask for a semantic operation, not a large layer total. The useful question is whether the next editor can make the agreed change without reconstructing the design.

The GIMP 3.0 manual, Getting Images out of GIMP, distinguishes saving its native XCF project from exporting another format. It explains that XCF preserves its image information except undo history, while other formats preserve subsets. This is a concrete example of why an export is not necessarily the full working project.

It also describes an imported PNG or JPEG as a new project. Saving that import under a native extension does not recover the original design decisions or object separation. A file can be valid in the editor and still contain only the flattened picture you started with.

For an AI-generated deliverable, request the source that actually contains the promised structure, a preview of the intended appearance and any required assets. The 3D asset delivery reference handles a different medium; this guide deliberately stays with text, layers, shapes and layout in two dimensions.

Use a copy of the delivery package. Change the headline to a longer phrase, replace one image and adjust a dimension that matters to the brief. Save, close and reopen the copy. This can reveal missing fonts, broken asset paths and changes that were visible in memory but not preserved in the saved file.

Inspect the revised preview as well as the editable structure. A text layer can remain editable while the replacement font changes the line breaks. A mask can remain present while the exported crop differs. These are separate findings and should lead to separate corrections.

Choose acceptance criteria before the test. If the brief allows manual adjustment at another size, record that. If it promises automatic layout behavior, demonstrate that behavior. Do not silently lower the requirement because the first export looks convincing. The design input guide addresses what to give an AI builder before it starts.

A file can depend on resources outside its folder: fonts, linked images, component libraries or application-specific effects. Identify which are included, which need separate access and which have a permitted substitute. Avoid promising ownership of a dependency merely because its rendered appearance is visible.

The recipient should open the package using their own access and environment. A creator's cached font or private asset path can hide a missing dependency. If the recipient cannot perform that check yet, preserve the status as unknown and agree who will resolve it.

Keep the acceptance record beside the source package. It should state the edits supported, any known conversion losses and the environment used for verification. A web development handover can apply the same principle to components and source code: the next maintainer needs working structure, not only a polished preview.

Download the blank acceptance worksheet. The reference rows are filled; observed status, evidence and checked date are deliberately empty. Record pass, fail, unknown or not applicable only after inspecting the relevant artifact or claim.