See every render on the Renders page

The Renders page lists every image and PDF made from your workspace’s templates, newest first. It shows where each render came from, the credits it used, its files, and the reason when one failed. In the sidebar, click Renders.

Credits at the top

Box	What it shows
Credits this period	Render credits your whole organization used in this billing period, out of your plan’s credits.
Remaining	Render credits left for this period, or Unlimited.
This workspace	Render credits this workspace used in this period.
Resets	The day the period ends and your credits start again.

To learn how credits work, see Credits.

Find a render

• Status: show All statuses, only Succeeded or only Failed renders.
• Template: show the renders of one template.
• Clear filters shows every render again.
• Refresh loads renders made since you opened the page.

The filters are kept in the page’s address, so you can bookmark a filtered list or send it to a teammate.

The page shows 25 renders at a time. Click Load more at the bottom to see older ones.

What each row shows

Column	What it shows
Preview	A small picture of the first image. Click it to open the image. A PDF shows a PDF icon.
Template	The template’s name, which opens it in the editor. Under it, where the render came from (below). Deleted template means the template was deleted after the render.
Format	PNG, JPG, WebP or PDF.
Pages	How many pages were rendered.
Credits	Render credits the render used.
Status	Succeeded or Failed.
Duration	How long the render took.
Created	How long ago it was made. Point at it to see the exact date and time.
Files	A link for each file: Image, Page 1, Page 2 and so on, or PDF.

Where a render came from

Label	Made by
API	A POST /v1/render call with an API key. See Render images and PDFs.
Editor test render	The Test render button. See Test render.
Signed URL	Opening a signed URL. See Signed URLs.
Dynamic URL	Opening a template’s dynamic URL. See Dynamic URLs.
Form	A visitor’s Generate on a form. See Forms.
Workflow	A row of a workflow run. See Workflows.

Images served again from a cache, by a dynamic URL, a signed URL or a form, are free and usually don’t add a row. You see them as counts on the Dynamic URL and Forms tabs instead. A row marked · cache hit was served from the cache and used no credits.

Failed renders

A failed render has a red Failed badge. Click it to open Why it failed, which shows the error message. Failed renders are free: “No credits were charged for this render.”

A common cause is an image URL that can’t be loaded, or an image server that answers too slowly. For fixes, see Troubleshooting.

Download files

• Click a file’s name to open it in a new tab.
• Click the download arrow next to it to save it with a readable name, such as summer-sale-4f2a9c.png.

A render made with base64 output has no stored files. Its preview says base64 and its files column shows a dash.

How long files last

The links on this page work for an hour. Click Refresh, or open the page again, to get fresh links.

The files themselves are kept for a limited time:

Where the render came from	Files are deleted after
Form	7 days
API, test render, workflow	8 days
Signed URL, dynamic URL	31 days

After that, the row stays on the page with its credits and status, but its files are gone. A dynamic URL or signed URL makes its image again the next time it’s opened. To keep a file, download it.

What next

• Read the same list from your code: Templates and renders.
• Learn what uses credits: Credits.
• Fix a failed render: Troubleshooting.