The Canva Button, the embed that let your users design in a Canva overlay and hand the result back to your app, was discontinued for partners outside China after December 30, 2025. If it powered a feature in your product, you're replacing infrastructure a vendor switched off. This page covers your options.
Quick disclosure: you can guess why this page exists. We ship the Polotno Button, the same script-plus-button integration shape the Canva Button had, so we think the closest like-for-like replacement is ours. But a useful guide still has to tell you when a different path fits better, so this one does.
The short answer
Like-for-like embed
Users live in Canva
Background generation
What happened to the Canva Button
The Canva Button was a JavaScript snippet: your user clicked the button, an overlay opened Canva's editor, and the finished export came back to your app through a callback. It made Canva's editor a feature of your product, so SaaS tools, website builders, and internal platforms wired it in.
Canva discontinued the Button for partners outside China after December 30, 2025, and suggests its other APIs instead, such as the REST APIs. For your rebuild, the lesson is practical: the Button sat on someone else's roadmap, and that vendor could turn it off. Make the replacement decision once, on terms you hold a contract for.
Why REST APIs aren't a drop-in replacement
The REST APIs are real and well-built, but they are a different product shape with different integration assumptions.
Users need Canva accounts
The Button asked users to log in or sign up, but it did that in a modal without leaving your app. The REST APIs act on a Canva user's account, so every user of your feature grants your app OAuth access and then edits on canva.com.
Editing happens on canva.com
There is no embedded editor in the REST APIs. Your app can create designs, read them, export them, and send users to the Canva editor on canva.com, with Canva's branding, outside your product.
Designs live in Canva's cloud
The design data belongs to the user's Canva account, in Canva's format. Your product orchestrates around it; it doesn't own it.
The workflow breaks in the middle
The Button's loop was: click, design, export, done, all inside your app. The REST API loop is: authorize, redirect to canva.com, return through Canva's Return button. Some products can accept that. A design feature that drives your funnel usually can't.
If your users are agencies and marketing teams who already live in Canva, the REST APIs are a good fit. Meet them where their assets are. If your users came to your product to design something, the redirect is where you'll lose them.
What a like-for-like replacement needs
Measured against what the Button did, and what it could not:
This is the shape of an embeddable editor. Polotno ships it at two levels, and the first one is deliberately shaped like the thing you just lost.
The drop-in replacement: Polotno Button
The Polotno Button is the same integration contract as the Canva Button: add a script, wire a button, get an editor overlay, receive the export in a callback. A Canva Button integration maps onto it almost line for line:
<script src="https://embed.polotno.com/button-v1.js"></script>
<button id="polotno-button">Open editor</button>
<script>
document.getElementById('polotno-button').addEventListener('click', () => {
window.createPolotnoEditor({
key: 'YOUR_API_KEY',
// size, templates, and visible panels are configurable
onPublish: ({ dataURL, json }) => {
// the rendered image – same job as the Canva Button callback
// plus the design JSON: store it and reopen the design later
},
});
});
</script>The differences are the ones that caused this migration in the first place: no third-party accounts for your users, your choice of visible panels and templates, and onPublish hands you the design JSON alongside the image, so designs become re-editable data in your database instead of artifacts in someone else's cloud. Polotno hosts the Button's editor at embed.polotno.com, so you still depend on a vendor's service, and our support SLA covers only the self-hosted SDK. The SDK removes that dependency.
When the button outgrows itself (you want the editor as a page in your app rather than an overlay, custom side panels, or programmatic design generation), the same JSON moves to the full Polotno SDK: composable React components, an open schema, and rendering that runs client-side, on your servers, or through an optional cloud API. Polotno has been in market since 2020, with 300+ businesses in production, including Amazon and BMW.
Migrating from the Button: the practical path
1. Inventory the Button's job
What did users design, at what sizes, from which entry points, and what format did your callback consume? That list is your integration spec.
2. Swap the script
Replace the Canva Button script with the Polotno Button script and move your callback logic into onPublish. This is the like-for-like step, same entry point, same overlay flow, same "here's your image" hand-back.
3. Replace templates
Your users lose Canva's template and stock library along with the Button. With Polotno you supply templates as JSON (jsonUrl on the Button, or your own template picker on the SDK). To carry a design across, export it from Canva as PDF and import it as editable layers.
4. Keep the JSON from day one
Store the design JSON that comes back with every export. The Canva Button could reopen a design by ID, but only inside Canva's cloud. With the JSON, your users reopen past designs in your product, you can re-render them server-side, and the same data moves to the full SDK later.
Other options, honestly
Adobe Express Embed SDK, the closest thing to "another Button": Adobe's hosted editor in an iframe. Access needs Adobe's business approval, users need an Adobe ID to save, and projects live in their Adobe Express account. If you're comfortable re-creating the same dependency with a different logo, it's a real option. See our detailed comparison.
Picsart Editor SDK: embeddable editing with a photo-editing center of gravity. Worth evaluating if your Button usage was mostly image touch-up rather than layout design.
Render APIs (Templated, Bannerbear, Placid): built for generating images from templates, with hosted or embedded template editors on some plans. If your Button flow had degenerated into "apply template, change one line of text, export," a render API may be the honest replacement. See Polotno SDK vs Templated.
Build in-house on Fabric.js or Konva.js: full control, no license fee, and a year of editor engineering before feature parity with what the Button did on day one. We maintain Konva; we say this with affection. The build-vs-buy breakdown runs the numbers.
FAQ
Is the Canva Button coming back?
Canva's developer docs say it has no plans to offer the Button outside China.
Can I keep designs my users made through the Button?
Exports you already received are yours. The underlying designs live in Canva's ecosystem, one more argument for owning design data in the next integration.
How close is Polotno to what the Button did?
The Polotno Button is the same integration shape (script, button, editor overlay, export callback) so the user-facing loop is identical. The differences sit on your side: your branding on a paid key, your design JSON, no third-party account for your users, and a paid license you hold.
How long does the migration take?
The script swap is the small part. Template creation and export wiring take most of the time. Evaluate it on the 30-day free trial.
