Ming Design-Layer splits a design into RGBA layers: Sume does not
Ming-Image-0.1-Design-Layer decomposes a flat design into RGBA PNG layers. Sume's Image API returns finished images, so build layers from transparent elements.

Sume has no layer-decomposition endpoint, so it cannot do what Ming-Image-0.1-Design-Layer does: split one flattened design into several RGBA layers. What it can do is generate each element as its own transparent PNG with background: "transparent" on GPT Image 2.5.
Ming facts are from its Hugging Face card; Sume facts from the Image API docs. Both read 2026-10-01.
What does Ming Design-Layer do?
Per its model card, it takes a flattened design image plus a layer plan (a prompt, or a requested layer count) and returns RGBA PNG layers. It is a 6B model under the MIT license, recommends 1024 (or 512) input, 12 steps and CFG 2.0, and expects an 80 GB GPU.
Does Sume return layers?
Not as a documented feature. The Image API docs describe text-to-image and reference-guided editing that return finished images; layers are not part of the request or response. Two earlier posts cover the same gap for Qwen layered output and Seedream layer decomposition.
| Item | Ming Design-Layer | Sume Image API |
|---|---|---|
| Output | RGBA PNG layers from a flattened design | Finished images |
| Transparency | Per layer | background: "transparent" on GPT Image 2.5, as png |
| Model size and license | 6B, MIT | Not applicable |
| Hardware | 80 GB GPU expected | Hosted |
How do I get separate elements?
Generate them one at a time. background accepts auto, transparent or opaque on GPT Image 2.5, and transparent needs a format that carries alpha, so ask for png. You then composite the PNGs in your own editor or renderer.
curl -X POST https://api.sume.com/v1/images \
-H "Authorization: Bearer $SUME_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"model": "openai/gpt-image-2.5",
"prompt": "A single red kettle icon, centered, no shadow, no text",
"image_size": "1024x1024",
"background": "transparent",
"output_format": "png"
}'What if I already have a flat image?
Sume's background removal tool takes a public HTTPS image_url and returns one subject cutout. That is one cut, not a stack of layers, and it does not recover what was hidden behind overlapping objects.
Sources
Related posts
More in Developers
- Ming-Image-0.1-Design on Sume: not in the catalog, use these
Ming-Image-0.1-Design is an open 6B design model. Sume's image catalog does not list it, so send a listed model id such as openai/gpt-image-2.5 for posters.
- MiniMax H3 first_frame and reference roles can't mix: Sume rule
MiniMax H3 treats first/last frames and reference roles as mutually exclusive. On Sume, frame_images takes precedence over input_references. Which to send.
- MiniMax H3 reference input limits: 30 MB, 50 MB, 64 MB request
MiniMax H3 caps images at 30 MB, reference video at 50 MB and the request at 64 MB, and says to use public URLs. A pre-flight list, and how Sume takes URLs.
- Modal 150-second web timeout and 303 redirect: Sume polling
Modal web endpoints return a 303 redirect after 150 seconds. Sume returns 202 with status_url and result_url, so a client polls and follows no redirects.
Written by Sume