Remotion and Polotno SDK both produce video, but they're built around opposite mental models. Remotion treats video as React: every frame is a component, every animation is a function, version-controlled like any other code. Polotno treats video as design: a visual editor your users open and manipulate, with a JSON schema underneath. One question decides it: who makes the video, your developers in code or your users in an editor?
Pick the one that matches your team and product
Pick Remotion if…
- Your team is React-fluent and wants to write video as code. Remotion is built for that job, and it does it well.
- Your video logic is a differentiator and needs full code expression. Complex per-frame computation, custom rendering logic, and bespoke programmatic timing are awkward to express in JSON and natural in React.
- You qualify for the Free License, or you want the source in front of you. Remotion is source-available and free for individuals, teams of up to 3, and non-profits, commercial use included. Larger companies need a Company License.
- Your code makes the videos and your users never touch a timeline. That is Remotion's core use. If you want an end-user editor later, it sells Editor Starter, a React template you fork.
Pick Polotno SDK if…
- Your users need to design or edit videos themselves and aren't React developers. Polotno ships a finished visual editor for non-coders. Remotion's route is a starter template your developers fork and finish.
- You want one design format for image, video, and print. Polotno's unified JSON schema covers image, video, PDF, and GIF in one editor.
- You want managed rendering. Polotno's Cloud Render API runs renders for you. Remotion's terms say it does not provide a rendering service, so you render in your own cloud or in the browser.
- You'd rather author templates as JSON than as TSX components. JSON is easier to generate from data, edit by non-engineers, store in a database, and serialize across systems.
How Remotion and Polotno differ
1. What a "template" is
In Remotion, a template is a React component. You write TSX, compose Remotion's primitives with normal React patterns, and the resulting file is your template. Data flows in through props, which you can describe with optional typed schemas and adjust visually in Remotion Studio. Changing the template itself means changing code, and you commit it to git.
In Polotno, a template is a JSON file. You design it visually or generate it in code, and you save the resulting JSON. Editing a template means opening it in the editor or changing the JSON. Your code sets values in that JSON, and the same file drives manual editing in the browser and batch generation from a backend job.
A React component is for developers. A JSON file also works for your designer, your user, and an AI agent generating templates from prompts.
2. Editor surface
Remotion's core has no end-user editor. Remotion calls Studio "a preview tool", aimed at developers. For end users it sells Editor Starter, a boilerplate with a timeline, canvas, font picker and asset uploads, plus a paid Timeline component. Editor Starter is a template: you fork it, extend it, and own it from then on. It assumes React 19, Tailwind v4, and TypeScript. If you want to own every line of a React video editor, Editor Starter is a fair place to start.
Polotno SDK's editor is a finished JavaScript component you mount inside your application, and your end-users (including non-developers) open and operate it. Drag, type, upload, position. You configure it and update it through the package.
3. Format scope
Remotion renders from React code: video in six codecs including H.264, H.265 and ProRes, plus GIF, audio, image sequences, and stills as PNG, JPEG, WebP, or PDF. Its core has no design document, so a still is one more composition in code.
Polotno covers image, video, PDF, and GIF in one schema, with one editor and one render API. If you need specific video codecs, Remotion's output goes further.
4. Render infrastructure
Remotion's terms state that "Remotion does not provide a rendering service", so you render in your own cloud or in the browser. Its comparison page covers Lambda, Vercel Sandbox, Cloud Run (in alpha), Node.js or Bun servers, and Cloudflare Containers, and recommends Lambda for most people. Lambda is fast to set up, and it renders fastest because it splits a video across many functions. Its compute costs more than the alternatives, and a long-running server has the cheapest compute. Remotion also renders in the browser, with a subset of tags and CSS.
Polotno renders in three places: via the managed Cloud Render API with webhook callbacks, on your own servers, or in the browser using the user's device (zero backend). All three use the same schema. The managed path is the quickest route: you send JSON and get files back, billed per use at $0.03 per video minute, with nothing to deploy.
Side by side
| Polotno SDK | Remotion | |
|---|---|---|
| Authoring | Visual editor or JSON | React code |
| Template format | JSON file | React component |
| End-user editor | Finished component you configure | Editor Starter, a paid template you fork and maintain |
| Per-frame control | Presets, easing, and timing per element | Anything you can code in React |
| Video output | MP4, GIF | Six codecs including H.264, H.265 and ProRes, plus GIF and audio |
| Design output | PNG, JPEG, SVG, HTML, PPTX, print PDF | Stills as PNG, JPEG, WebP, PDF |
| Managed rendering | Cloud Render API, billed per use | None, by its terms |
| Self-hosted rendering | Browser, your servers, AWS Lambda | Browser, Lambda with distributed rendering, Vercel Sandbox, your servers |
| Licensing | Fixed license fee by custom quote, no per-render fee when self-hosted, Cloud Render billed per use | Source-available. Free up to 3 people, then a Company License per seat or per render |
| Trial | 30-day free trial, no credit card | Free to evaluate, with no feature limits |
When Remotion is the right call
If your team is React-fluent and your video logic is sophisticated enough that you want it in code (version-controlled, testable, composed from reusable components, expressive at the frame level), Remotion fits that shape better than any JSON schema can. Individuals, teams of up to 3, and non-profits get the full product free, commercial use included. Lambda splits long renders across functions for speed, and you can render in the browser with no backend. Larger companies pay for a Company License, and those prices are published. For a video tool where the rendering logic is the product, Remotion is usually the right call.
The point of departure is the finished editor. If your users need to design videos themselves and they aren't React developers, Remotion gives you Editor Starter and a Timeline component to build from, and you own that editor and its roadmap. Polotno ships the editor as a maintained component.
A reasonable rule: if you'd describe your video work as "we write video logic," Remotion fits. If you'd describe it as "our users design videos," Polotno fits, and you can test it with the 30-day free trial, no credit card needed.
FAQ
Does Polotno render programmatically without an editor, like Remotion?
Yes. The Cloud Render API accepts a JSON template and returns a finished MP4, PNG, JPEG, PDF, or GIF. You need no editor at runtime. You can use Polotno purely as a render API, designing templates once (visually or programmatically) and generating media from data after that.
Can I version-control Polotno templates the way I version-control Remotion compositions?
Yes, Polotno templates are JSON files that commit to git cleanly, diff predictably, and merge like any other JSON resource.
Why pay for Polotno when Remotion has a free license?
Remotion is source-available, and its vendor says it is not open source. A company of more than 3 people needs a Company License, charged per seat or, for automations such as video editors, per render. So a for-profit company past 3 people pays for either product.
With Polotno, you're paying for the embeddable editor and its rendering. If you don't need the editor (your team writes video as code, you render on Lambda), Remotion is the right choice and we'd say so.
Can I render Polotno on AWS Lambda the way Remotion does?
Yes. Self-hosted rendering comes with every license, and it runs on AWS Lambda as well as on a long-running server. The function carries a headless browser, so raise the memory, timeout and ephemeral-storage limits above the Lambda defaults. Your renders and your AWS account stay yours, as with Remotion. Remotion's Lambda path also splits one video across many functions for speed.
Does Polotno support complex programmatic animation like Remotion?
Less expressively. Polotno's animation schema covers common patterns: enter, exit and loop presets, easing curves, text animated by letter, word or line, and per-element timing, alongside audio tracks on the timeline. For video where the differentiator is bespoke per-frame logic or computational effects, Remotion's React model is more flexible than what JSON can express. If your videos are built from common patterns and visual composition, Polotno's schema is sufficient and easier to author.
What about Remotion Player vs Polotno's editor?
Remotion Player is a React component that runs a Remotion composition live in your app, and your code can change its content at runtime. It's not an editor. To let users modify a video, you build that interaction on top of Player, or start from Remotion's paid Timeline component or Editor Starter. Polotno's SDK ships the editor itself: drag, type, change, save, render.
