How to check your own file
Create a mockup from a PSD returns every slot the template holds. Each design area you meant to address should be insmart_objects, under the name you gave it in Photoshop, and each
live type layer in text_layers beside the signals that decide what you can
change on it.
A template you registered earlier needs no second upload.
Retrieve a single PSD mockup
returns the same arrays for a mockup UUID you already hold.
Read the warnings on a render
A render that succeeds still tells you what it had to work around. Itswarnings array names each one with a stable code, so your integration
branches on the code rather than on message text. TEXT_WARP_BAKED, for one,
means the layer uses one of the remaining warp styles and kept its original
appearance. The full list is on Text layers, the error
codes are in Errors, and
Render a PSD mockup shows
where the array sits.
Where a feature is not rendered
Nothing leaves you at a dead end. Geometric effects rebuild as a warp on the smart object, tonal effects rebuild as adjustment layers, and decorative or random textures rasterise into a static layer, which costs nothing because they were never going to change per render. Every row has its own route on PSD compatibility. Type that is not editable in this version still renders. Rasterise it when it never changes, or place it as an image in a smart object slot when it does, sending that slot anasset the way any other design area takes one.
If a feature still is not rendering
- Find the layer’s row on PSD compatibility. An unsupported row names what to send instead.
- Re-read the upload response. A slot absent there will not appear in a render.
- Read the
warningsarray. A supported feature that changed appearance names itself. - Walk the file through Preparing a PSD, the checklist that keeps every text layer taking overrides.
- Contact support with the mockup UUID and the layer name.