Skip to main content
Every template you upload lands here, whether it arrived through the browser or through the API. The library is where you find a UUID, rename a template that was named badly, and clear out what you no longer render.

​
Find a template

Search by name or by UUID. The grid and the list view show the same set, so pick whichever reads better for the number of templates you keep. Opening a template shows its details: the layers it exposes, the image settings it was saved with, and the UUID to copy into a render request. This is the fastest path from a picture of a template to the identifier the API wants.

​
Name your templates

A template uploaded over HTTP takes the name you sent with it. A template uploaded in the browser takes the file name. Renaming here changes what you see in both places, and it does not change the UUID, so a rename never breaks a render already in production.

​
Colours

A template can carry a named set of colours, so a colour a shopper picks in the editor has a label rather than a hex value. Every colour needs a name before the set will save.

​
Delete

Deleting is permanent and the confirmation says so. A deleted template cannot be restored, and a render request that still holds its UUID will answer 404.
Your plan sets how many PSD templates the account stores at once. At the ceiling, a new upload is refused with 403 and psd_limit_reached while every stored template keeps rendering. Delete one, or move to a plan with a higher limit.

​
Upload several at once

Drop a set of files on the library to register them in one pass rather than one at a time. Each file is checked on its own, so one rejected file does not take the batch with it.

Upload a PSD

The same registration step, written as an API call.