Polotno SDK is a creative editor SDK: an embeddable image and video editor, a programmatic API, and a renderer, all driven by one JSON schema. Add it to your product and users edit on a real canvas under your own brand, no separate account, no third-party UI in front of them.
Image and video editor
Create image and video content, by hand or from code, on one canvas.
White-label, built for B2B
Runs under your brand. No Polotno name, no separate account for your users.
Editor plus API
The same schema drives the interactive editor and programmatic generation.
CREATIVE EDITOR SDK – POLOTNO DEMO
A creative editor SDK for images and video
Most creative editor SDKs pick a lane: image-only, video-only, or a hosted account model where users design on someone else's domain. Polotno covers image and video editing on the same canvas, under one JSON schema, self-hosted by default. Import a video file or pull from a stock library, trim and layer it alongside text and images, and export from the editor your users already know, no second tool, no second integration.
ARYEO INTEGRATION DEMO
Creative editor SDK in use: Aryeo showcase
Watch how Aryeo uses this creative editor SDK to streamline content production for its real estate agents and win more business. Some of the features this integration includes:
- Templates, flyers, postcards, digital ads
- Programmatically generated content
Creative editor SDK, or build your own?
Every team evaluating a creative editor SDK has already run the build-it-yourself math once. A canvas engine, undo/redo, font handling, export pipelines, and template logic take real engineering months, and then keep taking maintenance time every release after that. That calculation is why most teams end up here in the first place.
“We didn't think about building our own thing at all. From the moment we started the company, bringing Polotno in was the natural next step.”
Anca Bujor
Co-Founder @ Boardssey
“Our only alternative would have been to implement our own cover design editor. That would have amounted to a lot of development time, a lot of maintenance, and would have missed huge features.”
Zack Bloom
Co-founder @ Heirloom
How Polotno compares to other creative editor SDKs
IMG.LY's CreativeEditor SDK is the other name that comes up in this search: a mature, cross-platform SDK covering web, iOS, Android, and desktop. If native mobile parity is the requirement, it's worth evaluating directly. Polotno takes a narrower, web-first bet: browser-based, self-hosted by default, open JSON schema for automation, and a flatter learning curve for teams that live in React. See the full comparison for the detailed breakdown.
Brand Ninja is a good example of the web-first case: an AI content platform that added automated image and video generation with Polotno and launched in under a week, without hiring additional engineers. Read the case study.
Trusted by 300+ paying businesses
Polotno is built on top of Konva.js, an open-source canvas library with over 11,000 stars on GitHub and production use at companies including Meta. Polotno SDK itself is used by 300+ paying businesses, from bootstrapped startups to enterprises like Amazon, BMW, and Expedia.
4.4 / 5
5 / 5
5 / 5
How Predis.ai leverages Polotno's creative editor SDK to serve 100k+ users monthly
30% users engaged
Launched in <2 weeks
4+ months of work saved
FAQs
What is a creative editor SDK?
A software development kit that adds a design editor, image, video, or both, directly into your product's UI, rather than sending users to a separate app. It typically ships an editor component, a data format for the designs it creates, and a way to render those designs to output files.
Is Polotno's creative editor SDK open source?
No. Polotno SDK is a commercial license starting at $249/mo, with a 60-day free trial for development. It's built on Konva.js, which is open source, but the editor, template system, and rendering pipeline are licensed.
Can I white-label a creative editor SDK?
With Polotno, yes, fully. The editor carries no Polotno branding, and your users never see a third-party name or create a third-party account. Not every creative editor SDK offers this; some, like hosted account-based tools, keep their own branding visible by design.
Does it handle video, or just images?
Both, on the same canvas and the same JSON schema. Video and image elements share layering, animation, and export, so adding video support later doesn't mean a second integration.
How is this different from building a canvas editor in-house?
Scope, mainly. A creative editor SDK gives you the canvas engine, undo/redo, font handling, template system, and export pipeline as a maintained product. Building it in-house means owning all of that, plus every browser and rendering edge case that shows up after launch. See build vs. buy for the fuller argument.
