Server SDKs
Server-side support for the image editor: what is available now and what is in development.
The image editor runs in the browser. Your server works with it through files and HTTP requests. Server SDKs for the image editor are in development.
Available now
Your server can do these things today, with no server SDK:
| Task | How | Page |
|---|---|---|
| Receive the finished design | The browser uploads the file from onExport. | Export |
| Store and list templates | The editor calls onSaveTemplate and onGetTemplates, and your code talks to your server. | Saving and loading |
| Store pictures in your own storage | The editor calls onUploadAsset, and your code uploads the file. | Asset storage |
| Answer AI requests | The editor sends AI requests to your endpointUrl. | Custom AI endpoint |
| Search stock photos with your own keys | The editor sends searches to your stock proxy. | Stock media |
| Remove picture backgrounds | The editor sends the picture to {mediaApiUrl}/remove-image-background. | Images |
Every framework guide shows an upload endpoint for the exported file, for example in Next.js and Laravel.
In development
Server SDKs for the image editor are in development. They are not available yet.
Beta program
The beta program is not open yet. This page will say how to join when it opens.