Orshot is a hosted API for generating images, PDFs, and video from templates. You design templates in Orshot Studio or import them from Canva or Figma, render through its API, integrations, or MCP server, and can embed the Studio editor in your app as an iframe. Polotno SDK is a design editor SDK you ship in your own bundle, with designs stored as JSON and rendering that can run on your servers. One question decides it: should the editor, the templates, and the rendering run on Orshot, or on your side?
Pick the one that matches what you're building
Pick Orshot if…
- You want generation running with little or no code: build a template, then render from the REST API, a URL, a spreadsheet, or tools such as Zapier, Make, and n8n.
- AI agents run your pipeline: Orshot's MCP server lets an agent create templates and render them, signed in through OAuth.
- Your designs start in Canva or Figma: Orshot imports a public Canva share link, a Figma file, or JSON from its Figma plugin.
- You want an editor in your app with nothing to run: Orshot Embed is the Studio editor in an iframe. Orshot hosts the editor, stores the templates, and renders the output.
Pick Polotno SDK if…
- The editor is part of your product's UI: you compose it from React components, replace panels, and add your own controls. Orshot describes its embed as an iframe whose source you cannot fork.
- You need editing and rendering on your side: every Polotno license includes self-hosted editing and rendering. We found no self-hosted option on Orshot's site as of November 2026.
- You want your templates as files: designs are JSON you store, version, and diff in your own systems.
- Your users bring PowerPoint, PDF, or Photoshop files: Polotno imports PPTX, PDF, PSD, IDML, and SVG as editable elements, and exports PPTX and SVG.
How Orshot and Polotno differ
Both products generate images, PDFs, and video from templates, and both can put an editor in front of your users. They differ in who runs the editor, how far you can change it, who keeps the templates, and where the render happens.
1. Where the editor runs
Orshot Embed places the Orshot Studio editor in your page as an iframe, with optional React and Vue wrappers. The editor loads from Orshot and works only on the domains you allow. It needs a paid plan, and the higher plans give each of your users a private template library behind a signed session. Orshot's own comparison post says the editor and its storage run on Orshot, and that you cannot fork the source or run it offline.
Polotno SDK is a package you install and ship in your own bundle. The editor mounts as components in your app and loads from your servers.
The hosted iframe leaves you less to run, and your editor depends on Orshot's service. The SDK leaves you more to integrate, and you choose when to upgrade.
2. How far you can change the editor
Orshot configures the embed from its dashboard: a title, icon, and accent color, switches for features such as multi-page templates and the templates sidebar, and removal of Orshot branding on higher plans. Higher plans add editor events and webhooks, and the top plan adds your own toolbar buttons and asset picker. We found no way to add your own panels in its docs.
Polotno ships React components you lay out inside your own UI. You can replace side panels, add controls, and connect your own asset libraries. For governance, you get per-element locks, admin, user, and viewer roles, a font allowlist, and a brand kit panel. Customizing the editor needs React.
If branding, switches, and a few buttons cover your product, Orshot gets you there with less code. If the editor has to work like the rest of your app, you need access at the component level.
3. Who keeps the templates
Orshot templates live in your Orshot workspace. Its public template endpoint returns a summary of each page without the layers, and the endpoints that create and update templates are limited to the Enterprise plan and to Orshot's own clients, such as its MCP server. We found no documented template export as of November 2026, so ask Orshot how you would take templates with you.
Polotno templates are JSON files you store, version, and migrate yourself. Your code or a language model writes the JSON, and the same file drives the editor, batch jobs, and rendering.
Orshot lists a Polotno importer in its import docs, so a move from Polotno to Orshot has a documented path. We found none in the other direction.
4. Where rendering runs
Orshot renders through its API. Paid plans can send each render to your own storage, such as Amazon S3 or Cloudflare R2, and its Enterprise page mentions dedicated cloud instances and data residency on request. We found no self-hosted or on-premise renderer on its site as of November 2026.
Polotno SDK renders in three places: through the Cloud Render API, on your own servers, or in the user's browser. The quickest route is Cloud Render: you send the JSON and get the file back, with no servers to run. Self-hosting stays an option when your data has to stay on your side. On your own servers, PNG, JPEG, and vector PDF render in Node.js with no headless browser, and GIF and MP4 render through a package that runs headless Chromium. Those servers are yours to operate.
5. AI agents
Orshot's MCP server gives an agent tools to render templates, create and edit template designs, and manage brand assets, and it lists clients such as Claude, ChatGPT, Cursor, and VS Code. The agent signs in through OAuth and needs no API key.
Polotno SDK has no MCP server that renders. Its skills and documentation MCP server help an agent write Polotno JSON and SDK code, and the agent then renders by running a Node.js package or calling the Cloud Render API. See Polotno for AI agents. Polotno App, a separate desktop editor, has a built-in MCP server for designs on your own computer.
If you want an agent to produce images through a hosted tool with no code, Orshot has that today. If the agent works inside your codebase and the output must stay an editable design in your systems, Polotno fits.
Orshot and Polotno side by side
| Polotno SDK | Orshot | |
|---|---|---|
| What it is | Design editor SDK you ship in your bundle | Hosted generation API with an embeddable editor |
| Editor in your app | React components in your bundle | Hosted iframe, with React and Vue wrappers, on paid plans |
| Customization | Replace panels, add controls, theme | Title, icon, accent color, feature switches, toolbar buttons and asset picker on higher plans |
| Time to a working editor | Integration work in your codebase | An embed created in the dashboard and an iframe |
| Templates | JSON files you store | In your Orshot workspace, full template API on Enterprise |
| Template import | PPTX, PDF, PSD, IDML, SVG, and Figma through SVG | Canva, Figma, and importers for other template tools, Polotno included |
| Self-hosting | Editing and rendering, with every license, unlimited under fair use | None found, dedicated cloud instances on Enterprise |
| Rendering | Cloud Render API, your servers, or the browser | Orshot's API, delivery to your own storage on paid plans |
| Design data | Reaches Polotno servers only with Cloud Render or AI features | Stored and rendered on Orshot |
| Output | PNG, JPEG, PDF, SVG, HTML, PPTX, GIF, MP4, through Cloud Render or locally. Print: CMYK, bleed, crop marks, PDF/X-1a, PDF/X-4 | PNG, JPEG, WebP, AVIF, PDF, MP4, with WebM and GIF for video; HTML through Embed on Grow/Scale |
| No-code integrations | None: you call the API from your code | Zapier, Make, n8n, Pipedream, Google Sheets, Airtable, Notion, and more |
| Render links | You build them | Dynamic URLs and signed URLs |
| AI agents | Skills help agents write design JSON and SDK code; render through Cloud Render or Node | MCP server that creates templates and renders |
| Server SDKs | JavaScript and TypeScript, REST for Cloud Render | Node.js, Python, PHP, and Ruby, plus REST |
| Pricing model | Fixed license fee by custom quote, no per-render fee when self-hosted, Cloud Render billed per use | Monthly plans with credits, one credit per image, PDF page, or second of video |
| Evaluation | 30-day free trial, no credit card | Free plan with monthly credits, no credit card, no embed |
When Orshot is the right call
If you generate templated images, PDFs, or short videos as part of running your business, Orshot gets you there with a template and an API call, and Polotno SDK would be more than you need. Its integrations, spreadsheet runs, and signed links cover jobs an SDK leaves to you, and you operate no render servers. A free plan with monthly credits lets you test before you pay.
Orshot also fits product teams that want an editor in their SaaS with hosting, per-user template storage, and rendering handled for them, when an iframe with their branding is enough. And if your users or your own team work through AI agents, its MCP server renders and edits templates with no code on your side.
A reasonable rule: if a hosted editor passes both your product review and your security review, start with Orshot. If either one says no, evaluate Polotno with the 30-day free trial, no credit card needed.
FAQ
How does Orshot's pricing work?
Orshot sells monthly plans with included credits. One credit is one image, one PDF page, or one second of video. Unused credits do not roll over, and rendering pauses when you run out until the allowance resets. The embed starts on a paid plan, and its features grow with the plan. Check Orshot's pricing page and request a Polotno quote to compare the two models at your volume.
Does Polotno have a server renderer?
Yes. The quickest route is the Cloud Render API, with no servers to run. On your own servers, PNG, JPEG, and vector PDF render in Node.js with no headless browser, and a second package runs headless Chromium for GIF and MP4.
Can I move templates between Orshot and Polotno?
Orshot documents an importer for Polotno JSON, and its migration notes list what does not convert. We found no export from Orshot to Polotno, so that direction means rebuilding templates.
