Shopify's invisible AI watermark vs generating images with Sume
Shopify puts an invisible watermark on generated images and says commercial use is not restricted. It edits backgrounds; Sume's Image API makes new images.
Shopify says: "An invisible watermark is applied to all generated images, which doesn't restrict commercial use." So images from Shopify's media generation can be used commercially, and merchants keep ownership. That tool is built for background work. The Sume Image API is a different tool: it generates whole images from text and references, and its docs do not describe any watermark.
Side by side
Shopify facts are from its Help Center page; Sume facts are from the Image API docs.
| Topic | Shopify media generation | Sume Image API |
|---|---|---|
| What it does | Color Background and Generate, plus outpainting | Text-to-image and reference-guided editing across a model catalog |
| Watermark | Invisible watermark on all generated images | Docs do not mention one |
| Commercial use | Not restricted by the watermark; merchants keep ownership | See each model's terms in the catalog; docs here do not state a rule |
| Default size | About 1 megapixel by aspect ratio | Your image_size or preset |
| Where it runs | Shopify admin file editor, Basic to Plus plans; free in the file editor on all plans for a limited time | API call, billed per the endpoint pricing |
| Count per call | Not stated | n is up to 10 per call in the docs; per-model ceilings are lower (the Seedream 4.5 example shows 1-4) |
What the watermark means
The page does not say how a watermark is detected, what reads it, or whether it survives a crop or re-export. Do not describe it to a client beyond what Shopify wrote: it is invisible and does not restrict commercial use.
On the Sume side, absence of a documented watermark is not a statement that no marking exists anywhere. It means the docs are silent, so check the model terms in the catalog and your own platform's AI rules before publishing.
Which to use
Use Shopify's tool when the job is swapping or extending the background of an existing product photo inside the admin. Use the Image API when you need a new scene, a new angle from references or several variants. Using n for variants costs more per call, so read per-endpoint pricing from /v1/images/models/{model_id}/endpoints first.
A common flow is to generate the lifestyle scene with Sume, then bring it into Shopify as a file. Check the upload limits on the Shopify page (20 MB, 25 MP, JPEG, PNG, WEBP, HEIC or GIF) before uploading.
Sources
Related posts
More in Comparisons
- Shortest clip each platform accepts: Spotlight, Reels, Kick
Instagram Reels API needs 3 seconds, Snapchat Spotlight 5, Kick clips 10. Sume trim and Timeline go down to 0.2 seconds. The table shows which floor decides.
- Sora API shutdown Sept 24, 2026: what Omni 1.1 Flash covers on Sume
OpenAI lists the Videos API and sora-2 models for removal on Sept 24, 2026, with no replacement named. Omni 1.1 Flash on Sume: 3-10 s, 4K, edit, end frame.
- Spatius client-side Gaussian splatting avatar vs a finished MP4
Spatius renders avatars on the client with 3D Gaussian splatting and needs its SDK to show them. A finished Sume MP4 plays in any video element, no SDK needed.
- Speech-to-text price per hour, ranked: nine rates and Sume STT
Nine STT rates in dollars per audio hour, from Cloudflare's $0.03 to Sume STT 1.0 at $0.60, each read from the vendor's own page with the conversion shown.
Written by Sume