Smartmockups API: Status and a Reliable Alternative

#TL;DR

• Smartmockups never shipped an API. It sat at "Coming soon" for years, then Canva acquired the company and shut the standalone platform down on September 27, 2024.
• If you are still searching for it, the real question is not "where did the API go" but "what rendering engine can I build a business on for the next five years." That is a question about fidelity, reliability, and control, not a coupon hunt.
• SudoMock renders your own PSD pixel-for-pixel, has served over 2 billion renders at 99.99% uptime, ships signed render-complete webhooks, and is fully white-label. The per-render cost is low too, and we cover that honestly below. But it is one advantage in the stack, not the headline.

#The Smartmockups timeline: from startup to shutdown

Smartmockups launched in 2016 out of Liberec, Czech Republic. Founded by Lukas Zajic and Andrew Nekvinda, it built a solid reputation for quick, browser-based mockup creation. Upload a design, pick a template, export. Simple, and genuinely good at what it did.

By 2020, over 3 million mockups had been created on the platform, used by everyone from Etsy sellers to Fortune 500 marketing teams. Then Canva came knocking. In February 2021, Canva acquired Smartmockups (alongside the parent company behind remove.bg) to fold mockup capabilities into its design ecosystem.

For three years Smartmockups kept running as a standalone product. But on September 27, 2024, Canva pulled the plug. The smartmockups.com domain now redirects to Canva, user data was deleted, and saved projects did not transfer. And that API? Still "Coming soon" when the lights went off.

#Why Smartmockups never shipped an API

This is not just a Smartmockups story. It is an architecture story, and it is the most useful part of this page if you are choosing an engine to build on.

Template-based mockup tools composite your design onto a pre-rendered scene, usually in the browser. The mockup is essentially a finished photograph with a designated drop zone, and the placement happens client-side with basic image manipulation. That model is fast to ship for a UI. It is the wrong foundation for a programmatic engine, because a real API has to:

1. Run the full compositing pipeline server-side, deterministically, without a browser in the loop
2. Handle real concurrency: queues, retries, and throughput under burst load
3. Reproduce the full range of layer behavior (blend modes, masks, smart filters) rather than a flat drop zone
4. Hold response times steady while traffic climbs

An API-first product needs that foundation from day one. You cannot bolt it onto a browser compositor later without essentially rebuilding the thing. After the acquisition, Smartmockups engineering went toward Canva integration rather than new server infrastructure, and the promised API never had a foundation to stand on. The lesson for buyers is simple: a tool that demos beautifully in a browser tells you nothing about whether it can survive as an API.

#What the searcher actually needs: a reliable rendering engine

If you typed "smartmockups api" you do not want a template gallery. You want an engine that returns the right image, every time, at the volume your catalog demands. Here is what that engine looks like, and where SudoMock has spent its engineering.

Verified Adobe-grade fidelity. SudoMock renders your PSD against Photoshop's own output and measures the difference. Mean per-pixel error sits at 0.24, effectively pixel-for-pixel. It supports all 27 blend modes, smart filters including Perspective Warp, Curves, and Gaussian Blur, nested smart objects, masks, and adjustment layers. A fabric fold warps correctly, a drop shadow lands where Photoshop would put it. That is the difference between a mockup a customer trusts and one that looks subtly wrong.

Your own PSD, not a shared catalog. This is the part that quietly matters most for sellers. A generic shared template library is a liability, not a feature. If your store runs the same stock scenes as thousands of other shops, your listings look interchangeable, and marketplaces have little reason to favor duplicate imagery. A mockup should be yours, rendered from the PSD your designer built, so your catalog looks like nobody else's. SudoMock is built around that: you upload your own templates and swap designs into them programmatically.

Print-ready resolution. Renders go up to 10,000px with no forced downscaling, so the same call that feeds your web listing can feed a print file.

Battle-tested reliability. Over 2 billion renders served as of June 2026, 99.99% uptime backed by a public status page, and sub-second average render times. Every render can fire an HMAC-signed completion webhook with automatic retries and a replay dashboard, plus full position metadata so your downstream system knows exactly where the design landed. That is the boring infrastructure a real automation pipeline lives or dies on.

Fully white-label. Serve every render from your own domain with zero SudoMock branding, and embed the editor directly in your product. Your customers never see a third party.

Developer experience. API-first, with Python and Node SDKs, a public MCP server, and native Shopify, WooCommerce, n8n, Zapier, and Make integrations. You are not gluing a UI tool to a cron job. Compare the broader field on our mockup tool alternatives page.

#And the cost: an honest comparison

Price is not the reason to pick an engine, but it is not nothing either, so here are the real numbers without the marketing math.

Adobe's Photoshop API is powerful and handles operations well beyond mockups, but it has been documented at about $0.15 per call, which suits teams already standardized on Adobe. SudoMock is from $0.002 per render. The free tier is 500 credits with no card, and paid plans start at $25/mo. We deliberately do not publish a tangle of per-tier render math here; the current plans live on the pricing page.

Run the same workload through each and the gap is obvious, but do the multiplication yourself rather than trusting a slogan. The point is not that one is cheap. It is that once you have chosen the engine on fidelity and reliability, the cost should not be what stops you from scaling it. For a full side-by-side across providers, see our mockup API pricing comparison, and for the Adobe case specifically, SudoMock vs Adobe Photoshop API.

#From Smartmockups to a working API: a migration path

If you were waiting on the Smartmockups API, here is how to get to real automation in an afternoon.

Step 1: Prepare your PSD. Build or open a Photoshop template with smart object layers, and name each one descriptively, like "Chest Design" or "Front Print." Lighting, angle, and brand are baked into your own file, which is the whole point.

Step 2: Get an API key. Sign up and grab your key from the dashboard. About thirty seconds.

Step 3: Upload your template. Push the PSD through the dashboard or the upload endpoint. The response returns your mockup UUID and the list of smart objects with their dimensions. The quickstart guide walks the whole setup.

Step 4: Render your first mockup.

curl -X POST https://api.sudomock.com/api/v1/renders \
  -H "x-api-key: sm_your_api_key" \
  -H "Content-Type: application/json" \
  -d '{
    "mockup_uuid": "c315f78f-d2c7-4541-b240-a9372842de94",
    "smart_objects": [{
"uuid": "128394ee-6758-4f2f-aa36-e2b19b152bd9",
"asset": { "url": "https://your-cdn.com/design.png", "fit": "cover" }
    }],
    "export_options": { "image_format": "webp", "image_size": 4000, "quality": 95 }
  }'

You get back a CDN URL with the finished render, and a signed webhook fires on completion so your system never has to poll.

Step 5: Scale it. Wire the render call to n8n, Zapier, or Make so a new Google Drive file, a new Shopify product, or an Airtable row triggers a batch automatically. Upload once, render thousands of variations, no browser tabs and no "Coming soon" that never comes.

#The honest-broker close

You do not have to take any of this on faith. Smartmockups is gone, but the engine you replace it with is a five-year decision, so test it like one. Render your own PSD through both free tiers, put the output next to Photoshop's, and compare the fidelity, the warp, and the response times under your real load. The engine that holds up is the one to build on.

Start free with 500 SudoMock credits, no credit card required, and run your own template through the API today.

#FAQ

Does Smartmockups have an API?

No. Smartmockups never released an API. It was listed as "Coming soon" throughout the product's life. After Canva acquired and shut down Smartmockups in September 2024, no API was added to the Canva mockup integration either.

Is Smartmockups still available?

The standalone smartmockups.com platform shut down on September 27, 2024. The template library lives on inside Canva as "Canva Mockups" for Canva Pro subscribers, but the original platform, user accounts, and saved projects are gone permanently.

What should I use instead of the Smartmockups API?

Use an engine that was built API-first. SudoMock renders your own PSD with verified Adobe-grade fidelity, has served over 2 billion renders at 99.99% uptime, ships signed webhooks, and is fully white-label. Compare options on the alternatives page.

Can I use my own PSD files with a mockup API?

Yes, and you should. Rendering from your own PSD gives you control over lighting, angle, and brand, and keeps your listings from looking identical to every other store running a shared template library. SudoMock is built around uploading and rendering your own templates.

How do I automate mockups without Smartmockups?

Upload your PSD template once, then call the render endpoint with each new design. Connect n8n, Zapier, or Make for hands-off triggers. A 500-product catalog that took 40 hours by hand can finish in minutes through the API.

Did Canva keep the Smartmockups API plans?

No. Canva's mockup feature is UI-only, with no API access, no bulk generation, and no automation hooks. For programmatic rendering you need a dedicated mockup API.