Skip to main content
Every template 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.

​
Template management

The library holds everything the Create page produces: Photoshop templates, mockups built from a product photo, and scenes you generated. One shelf, one search field, one set of actions, and the shelf belongs to the organization rather than to the person who uploaded, so every member opens the same set. The saved mockup library in grid view, each card showing the template name and its type. Over HTTP that one shelf reads as two collections, because the two kinds of mockup answer to different routes: list PSD mockups and list photo mockups. Each kind carries its own read, update and delete route, and the UUID you copy in the browser is the identifier every one of them takes.
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.

​
Find a template

Search by name or by UUID; the grid and the list view show the same set. The PSD list endpoint takes the same handles: name matches a fragment rather than the whole string and ignores case, created_after and created_before narrow the window, and sort accepts name, created_at or updated_at with order set to asc or desc. Either list is walked with limit and offset, which Pagination covers in full.

​
View template details

Opening a template shows what the upload found in it: the canvas size, the thumbnails generated from it, the image settings it was saved with, and the UUID to copy into a render request. A Photoshop template lists three kinds of layer, each carrying its own UUID that a render can address:
  • smart_objects: the design areas artwork lands in, covered by Smart objects.
  • text_layers: the wording a render can replace, with the font, size and colour it is set in, covered by Text layers.
  • group_layers: outlines that can be recoloured as a set, so everything inside the group follows the change.
A layer hidden in Photoshop is not offered here, and Hidden layers explains which kinds are still reachable. A mockup built from a product photo lists print areas instead of layers.

​
Rename a template

A template uploaded over HTTP takes the name you sent with it, an upload that sent no name is given one, and a template uploaded in the browser takes the file name. The name is what search matches and what the API hands back in name. Renaming changes both places and does not change the UUID, so it never breaks a render already in production. Over HTTP the same edit is update a PSD mockup or update a photo mockup.

​
Name a template’s colours

A template can carry a named set of colours, so a shopper picks a label in the editor and a render asks for blue jean where it would otherwise send a hex code. Every colour needs a name before the set will save. Setting the colours over HTTP replaces the whole set rather than adding to it, so send every colour you mean to keep, and send an empty list to clear the set entirely.

​
Upload several at once

Drop a set of files on the library to register them in one pass. Each file is checked on its own, so one rejected file does not take the batch with it, and each arrives as its own template with its own UUID, renamed or deleted on its own afterwards. The API registers one file per call. Upload a PSD covers that call and the background mode, which hands back a job to poll instead of holding the connection open while a large file is read.

​
Delete a template

Deleting is permanent and cannot be undone, and the confirmation says so. The template and the files that belong to it go together, and a render request that still holds its UUID answers 404. Deleting frees a slot against the stored template ceiling. Over HTTP the same removal is remove a PSD mockup or remove a photo mockup.

​
API reference

For the full contract behind this page, see the PSD endpoints from Retrieve a single PSD mockup and the photo endpoints from Retrieve a single photo mockup. Errors lists every code these routes can answer with.