A white-label design editor, inside your product.
Your users design in your app, in your chrome, under your logo. One script tag and one mount call — and on Scale, nothing in the experience mentions Pixy at all. Stop planning the two quarters it would take to build an editor of your own.
Embed on Growth · fully unbranded on Scale
- Templates
- Text
- Images
- Elements
- Draw
- Uploads
- Brand kit
- Background
Your users’ design
8
Panels you control
3
Export formats
1,500+
Templates included
0
Mentions of Pixy on Scale
Your logo · your accent colour · your domains · your export formats
Who embeds it
Products that need a design surface, and a roadmap for other things.
If your users are currently making artwork somewhere else and uploading it to you, this is the gap. Pixy fills it without adding an editor to your backlog.
Print on demand
Customers design the mug, the shirt or the poster inside your storefront, and you receive the print-ready file.
Site and store builders
Give your users a real editor for banners, product images and social assets without leaving the builder.
Marketing and CRM suites
Let the person writing the campaign make the creative for it in the same session, in your chrome.
Marketplaces and classifieds
Sellers produce listing images that actually match your layout, because the template is yours.
Learning and certification
Course builders design certificates and lesson covers inside the platform they already live in.
Signage and print shops
Take an order and the artwork in one step, and get an export at the size the press needs.
Build or buy
Two quarters of engineering, or an afternoon.
Everybody underestimates the design editor. It is not the canvas that takes the time — it is fonts, undo, snapping, crop, export fidelity, and every one of them is a bug report the week after you ship.
| Building it yourself | Pixy | |
|---|---|---|
| Time to a working editor | Two engineers, two quarters | An afternoon |
| Fonts, kerning and export fidelity | Yours to get right, forever | Ours |
| Undo, layers, snapping, crop | Every one of them, by hand | Already there |
| A template library on day one | Commission or build it | 1,500+ included |
| AI tools inside the editor | A second roadmap | Six, included |
| Whose product it looks like | Yours | Yours — your logo, your colour, no Pixy on Scale |
The control surface
Your chrome, your rules, your domain.
Configure it once in the Pixy dashboard and every launch of the editor obeys it. Nothing about the integration changes when you change your mind about a panel.
- It looks like your product
- Your wordmark in the editor chrome, your hex value on every button and accent. On Scale, nothing in the experience mentions Pixy at all.
- It does only what you allow
- Switch the eight sidebar panels on or off — templates, text, images, elements, draw, uploads, brand kit, background — and choose which export formats a user can leave with.
- It opens where you want it
- Mount it inline inside a page, or open it as a modal from a button. You choose the save button’s label and whether users can rename a design.
- It is locked to your domains
- An embed key works only on the origins you list, so the editor cannot be lifted onto somebody else’s site.
<script src="https://app.pixy.art/embed/sdk"></script><div id="pixy" style="width: 100%; height: 900px;"></div><script> window.Pixy.mount('#pixy', { embedKey: 'YOUR_EMBED_KEY', designId: 'YOUR_TEMPLATE_DESIGN_ID', openAsCopy: true, onExport: (result) => { console.log(result.designId) console.log(result.files) }, })</script>Launch with a design id to reopen a saved project, add openAsCopy to treat it as a template, or pass width and height for a blank canvas. onExport hands you back the design id and the exported files.
Integration
Three steps, and one of them is pasting a script tag.
No infrastructure to run, no fonts to host, no export pipeline to maintain. The editor is ours; the product it appears in is yours.
- 01Dashboard
Create an embed key
In the Pixy dashboard, list the domains that may load the editor and set your logo, accent colour, panels and export formats.
- 02SDK
Drop in the SDK
One script tag and one mount call. Pass the embed key and either a design to open, a template to copy, or the dimensions for a blank canvas.
- 03onExport
Handle what comes back
Your onExport callback receives the design id and the exported file URLs, so your app can store the result and reopen it later.
Pricing
The plan that removes every trace of us.
Embed is included on Growth and Scale. Scale is the white-label one — it is the plan that takes Pixy branding out of the embedded editor entirely.
Starter
For solo creators getting started with regular usage.
$49/ month
Get startedWhat’s included
- Members
- 1
- Credits
- 1,000 / month
- Overages
- $0.03 / credit
- API
- Embed
Growth
For growing teams with active API and embed usage.
$149/ month
Get startedWhat’s included
- Members
- 3
- Credits
- 10,000 / month
- Overages
- $0.02 / credit
- API
- Embed
Scale
Best fitFor high-volume teams that need the embeddable Pixy image editor.
$299/ month
Book a demoWhat’s included
- Members
- 10
- Credits
- 50,000 / month
- Overages
- $0.01 / credit
- API
- Embed
Image exports cost 1 credit per page · PDF costs 1 credit
FAQ
The questions we get most.
Is this really white-label?
On Scale, yes — your logo sits in the editor chrome, your accent colour is on every control, and nothing in the experience mentions Pixy. Growth includes embed with Pixy branding left in place.
Which plans include embed?
Growth and Scale. Scale is the plan built for putting the editor inside your own product, because it is the one that removes Pixy branding entirely.
How long does integration take?
One script tag and one mount call. You create an embed key in the dashboard, list your allowed domains, and pass the key to the SDK — most teams have it running the same day.
Can my users start from a template?
Yes. Launch with a design id and openAsCopy, and each user gets their own copy of your template while the original stays untouched. All 1,500+ Pixy templates are available, or you can use your own.
Who can load my embedded editor?
Only the origins you list against the embed key. It will not run on a domain you have not allowed.
Do my users need a Pixy account?
No. They are your users, working inside your product. The editor runs against your embed key, not against individual Pixy logins.
Can I turn the AI tools on or off for my users?
Yes. The AI prompt window is a configuration flag on the embed, alongside the eight sidebar panels, so you decide how much of the editor your users see.
Start here
See it in your colours.
Twenty minutes, your logo and your hex value, and you will know whether this replaces the editor on your roadmap. Or start free and mount it yourself this afternoon.
8 panels · inline or modal · domain-locked · 1,500+ templates