---
title: "Render from Studio Template"
method: POST
path: "/studio/render"
tags: ["Generation & Templates"]
---

# Render from Studio Template

`POST /studio/render`

Render any template you've designed in Orshot Studio by making a POST request — as an image, PDF, or video, at any size, and optionally publish it.

## Request body

- object
  - `templateId` number, required — Your template's ID — shown on the template's page and in the playground.
  - `modifications` object — Your dynamic values, keyed by parameter ID. Multi-page templates prefix keys with the page, e.g. `page2@title`. You can also set [style parameters](/docs/orshot-studio/style-parameters) to change layer styles at render time.
  - `response` object — What to render and how to return it (format, type, size, …). See below.
  - `pdfOptions` object — PDF-only output controls (document title, margins, DPI, color mode, page range). See [Render as a PDF](#render-as-a-pdf).
  - `videoOptions` object — Video-only output controls (fps, trim, audio, subtitles, page transitions). See [Render as a video](#render-as-a-video).
  - `publish` object — Publish the render to connected social accounts. See [Publish to social](#publish-to-social).

## Response `200`

Successful response

- object

## Other responses

- `400` — The request was malformed or a parameter was invalid.
- `401` — Authentication is required and was not supplied.
- `403` — The API key is missing, invalid, or not permitted to perform this action.
- `404` — The requested route or resource does not exist.
- `429` — The workspace rate limit was exceeded. Retry after the interval given by the Retry-After header.
- `500` — An unexpected error occurred on our side.

---

[API](https://skmtc.dev/orshot/apis/orshot-api.md) · [All operations](https://skmtc.dev/orshot/apis/orshot-api/llms.txt) · [OpenAPI document](https://skmtc-service-production.skmtc.workers.dev/v1/apis/orshot/orshot-api/revisions/7c4d4e1c76fc/schema)