Template ID vs Render ID

Understanding the difference between these two important identifiers.

Template ID

What it is: Unique identifier for a template (your design blueprint)

Format: UUID like 9dcf568e-26b3-4ef4-aa8c-075cdf9f4066

Where to find it:

• Templates page → three dots menu → Copy Template ID
• Editor URL: app.templated.io/editor/{TEMPLATE_ID}
• API: GET /v1/templates

Used for:

• Creating renders
• Opening templates in Editor
• Playground testing
• API integrations

Example:

{
  "template": "9dcf568e-26b3-4ef4-aa8c-075cdf9f4066",
  "layers": { ... }
}

Render ID

What it is: Unique identifier for a specific render (generated output)

Format: UUID like a1b2c3d4-e5f6-7890-abcd-ef1234567890

Where to find it:

• API response after creating a render
• Render history in dashboard
• Webhook payload

Used for:

• Fetching render details
• Loading renders for editing
• Tracking generated outputs

Example response:

{
  "id": "a1b2c3d4-e5f6-7890-abcd-ef1234567890",
  "url": "https://templated-assets.s3.amazonaws.com/renders/...",
  "templateId": "9dcf568e-26b3-4ef4-aa8c-075cdf9f4066"
}

Key Differences

Common Mistakes

❌ Wrong: Using render ID to create new renders

{ "template": "RENDER_ID" }  // Won't work!

✅ Correct: Using template ID

{ "template": "TEMPLATE_ID" }

Quick Reference

• Creating a render? → Use Template ID
• Fetching render result? → Use Render ID
• Opening in Editor? → Use Template ID
• Editing existing render? → Use &render=RENDER_ID parameter

Updated on: 11/01/2026