Rendering turns a JSON project into an image, video, or document. Render through the Polotno Cloud Render API, on your own server, or in the user's browser. These options share the design schema, with different format support, scale, and infrastructure requirements. Match fonts, assets, and export settings, and test representative designs when changing renderers.
Cloud rendering API
The Polotno Cloud Render API handles rendering on managed infrastructure. You send a project JSON and receive a PNG, JPEG, PDF, SVG, HTML, PPTX, GIF, or MP4 file through API callback or URL. To make one copy per record, send a template and one record, and the job fills its template variables before it renders. It’s optimized for performance, concurrency, and stability across high-volume workloads.
Best use cases
- SaaS products generating images or videos automatically
- AI systems or templating engines outputting hundreds of creatives
- Businesses needing on-demand, high-throughput rendering without managing servers
Pros
- Zero maintenance and automatic scaling
- Optimized for large queues and batch jobs
- Pay-as-you-go pricing model
Cons
- External dependency (requires API connectivity)
- Billed per use
ㅤ
Client-side rendering
Client-side rendering runs entirely in the browser using the user’s device resources. It’s the simplest and fastest way to preview and export designs without additional setup. The output (PNG, JPEG, PDF, SVG, HTML, PPTX, GIF, or MP4) is generated in real time, matching what users see in the editor.
Best use cases
- Small-to-medium-scale SaaS tools and design apps
- Interactive previews and instant downloads
- Educational, marketing, or eCommerce editors
Pros
- Zero backend setup
- Instant export and preview
- Ideal for real-time design feedback
Cons
- Dependent on user hardware performance
- Not suitable for high-volume automation or large render batches
ㅤ
Self-hosted rendering
Description
Self-hosted rendering moves the export process to your own servers. You run Polotno’s Node.js renderer within your environment, typically a containerized or scalable backend service. PNG and JPEG images can also render on your servers without a headless browser, through @polotno/image-export. In Polotno's measurements it is 2–5× faster than the browser-based renderer on photo templates and about 15× faster on simple layouts, with a 280 MB memory peak against 700 MB. It does not draw video frames or Lottie animations, so designs that contain them, and GIF and MP4 output, stay on the browser-based renderer. This gives full control over privacy, queue management, and rendering performance.
Best use cases
- Enterprise or regulated environments requiring private data processing
- Internal creative systems with automated export pipelines
- Platforms running high-resolution print or video exports at scale
Pros
- Full data control and compliance
- Scalable infrastructure under your management
- No external dependency or API limits
- Container-ready with fast startup
- Cloud-metadata endpoints blocked by default, private networks blockable
Cons
- Requires DevOps setup and monitoring
- Higher maintenance cost compared to the cloud
Built for containers
The renderer is designed to run in a container, not a workstation: fast startup, configurable browser binary and timeouts, network access restricted by default against SSRF, and automatic retries for remote assets that fail with a transient error before the render is failed. See the Node.js rendering docs for setup details.
ㅤ
Choosing the right rendering mode
In general:
- Cloud API is the default for automated rendering: you run no servers, and it scales on its own.
- Self-hosted is best for teams that need strict data control or run custom workflows.
- Client-side is best for interactive editing and individual user exports.
All modes can coexist in one product. For example, live previews can render in the browser while final outputs are processed through self-hosted or cloud rendering for higher fidelity or throughput.
ㅤ
Summary
Polotno SDK’s rendering system adapts to your architecture: cloud for scale with no servers to run, self-hosted for total control, or browser-based for simplicity. Whichever mode you choose, the same schema and editor power every render, keeping your creative pipeline consistent from design to export.
Related reading
- Self-hosted vs cloud vs client-side rendering: how to choose: decision guide by volume, latency, and cost.
- Batch rendering at scale: production patterns for high-volume rendering.
- PDF generation: rendering a document from a template and a data row.
See it without writing code
Each of these runs the same pipeline client-side, on your own file:
- PDF to PNG and PDF to JPG: raster output at a selected resolution.
- PDF to SVG: vector output, one file per page.
- SVG to PDF: the reverse trip, including print-ready PDF/X.
