eMAG main product image standard and what to ask Sume for
eMAG Marketplace's main-image standard (whole product, centred, about 85% of the image, white or grey background) and the Sume request that fits.

What is eMAG's main product image standard?
eMAG's Marketplace Academy page says the main image must display the product entirely and be clear, with the product centred and occupying as much of the image surface as possible, approximately 85%. It recommends a white or gray background, and allows environmental backgrounds for certain categories if professionally taken.
The rest of that article sits behind an eMAG Marketplace account, so pixel dimensions, file formats and file size are not stated here. Read them in your seller account before you set sizes.
| Rule | What the visible page says |
|---|---|
| Product visibility | Displayed entirely, clear |
| Position and fill | Centred, approximately 85% of the image surface |
| Background | White or gray recommended |
| Environmental backgrounds | Allowed for certain categories if professionally taken |
| Pixels, formats, file size | Behind login, not read |
What do you ask Sume for?
The rule is about composition, not pixels, which suits a prompt. Use openai/gpt-image-2.5 with your packshot as a reference, background: opaque and a prompt that names the white or grey backdrop and the 85% fill. Choose the aspect ratio your eMAG category needs from the Image API list, which for this model is 1:1, 4:3, 3:4, 5:4, 9:8, 4:5, 16:9, 9:16 or auto.
Quality is auto|low|medium|high|xhigh|max; omitted defaults to high.
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": "Same product, unchanged, entire product visible and centred, filling about 85 percent of the frame, plain light grey background, no text, no logo",
"input_references": [{"type": "image_url", "image_url": {"url": "https://example.com/packshot.png"}}],
"aspect_ratio": "1:1",
"quality": "high",
"background": "opaque"
}'How do the rules map to request fields?
Fill and centring come from the prompt; ratio and tier come from fields. Sume lists what it accepts per model, and a field the model does not list returns 400 unsupported_parameter, so read GET /v1/images/models first.
| eMAG rule | Sume field | Value |
|---|---|---|
| Whole product, clear | input_references, quality | Your packshot, high |
| Centred, about 85% | Prompt | State both |
| White or gray background | background plus prompt | opaque, name the colour |
| Aspect ratio of your category | aspect_ratio | One from the model's list |
What to check before you upload?
Estimate the fill by eye on the output; a model may leave more margin than you asked for. If the product changes shape or colour from your packshot, regenerate with a stricter 'unchanged' prompt. Then compare the file against the pixel and size limits in your eMAG account.
Sources
Related posts
More in Use cases
- Reel end card: trim the last 3 s, then overlay a still
Sume timeline-compose holds a still for the whole clip, so an end card on the last 3 seconds needs a trim first. Trim, compose, then join in Timeline.
- Open episode 2 on episode 1's last frame: video_frames, frame_images
Pull the closing still with POST /v1/video-frames, then send it as first_frame to POST /v1/videos so the next episode starts where the last cut ended.
- Estimated tax reminder videos for freelancers: an accounting firm plan
The IRS says sole proprietors and others generally pay estimated tax if they expect to owe $1,000. Plan short avatar clips that send clients to the IRS page.
- Eventbrite event video: 24-hour review and a 2:1 cover image
Eventbrite reviews uploaded event video for up to 24 hours and prefers 2:1 images. Build the clip and cover early with Sume so review is not your deadline.
Written by Sume