The render lifecycle

What a render is

One render is one thing on one surface of one scene: a fabric on the sofa, a floor on the floor, a color on the walls. It makes one image, and costs 1 credit.

Create renders with Create renders and follow each one with Retrieve a render. Every render has its own id, even when it was sent in a batch.

Render statuses

How statuses change

• A render only moves forward, and a final status never changes.
• Every render reaches a final status. One that stops making progress for 10 minutes is marked failed and its credit given back, so a poll that waits for a final status always ends.
• A queued render can fail before it starts, for example if its product is removed from your catalog while it waits. Its credit is given back too.
• If an upscale fails, the render still completes, with the image as it was rendered. Its upscale_status says so. See Upscaling.

How long renders take

Once it starts, most renders finish in about 20 to 60 seconds. Times vary with the image and how busy the service is, so some take longer, and none is guaranteed.

Queue and order

• Each workspace’s renders run 3 at a time, shared by all of its keys.
• They start in the order they were sent, including the order inside a batch.
• So a full batch of 100 takes roughly 22 minutes or more. Plan for minutes, not seconds, and collect each image as it arrives.

Failed renders and refunds

A failed render costs nothing: its credit goes back to your workspace without you asking. Its error says what went wrong, in words you can show your team.

Cancelling

A queued render can be cancelled with Cancel a render, and its credit comes back, unless it was taken before your workspace’s credits last renewed. Once a render is rendering it runs to the end.

Renders in the app

Renders made through the API appear in your workspace’s gallery in Skip Shoot, marked as made by the API, so your team can see, share and download them like any other.