Rendering is the final step in the Polotno workflow — turning a JSON project into a ready-to-use image, video, or document. Every Polotno design can be rendered in three ways: directly in the user’s browser, on your own server, or through the Polotno Cloud Render API. All three options use the same schema and produce identical visual output; the difference lies in scale, control, and infrastructure.
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, JPG, PDF, 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. 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
Cons
Requires DevOps setup and monitoring
Higher maintenance cost compared to the cloud
ㅤ
Cloud rendering API
The Polotno Cloud Render API handles rendering on managed infrastructure. You send a project JSON and receive a rendered image, video, or PDF through API callback or URL. 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)
Limited by credit or pricing tiers
ㅤ
Choosing the right rendering mode
In general:
Client-side is best for interactive editing and individual user exports.
Self-hosted is best for teams that need strict data control or run custom workflows.
Cloud API is best for automated, high-volume rendering and when you want scalability without infrastructure overhead.
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 — browser-based for simplicity, self-hosted for total control, or cloud for scale. Whichever mode you choose, the same schema and editor power every render, keeping your creative pipeline consistent from design to export.