Otto Product Image Requirements: What Is Documented, What Is Not, and How to Plan Anyway

What Otto Requires From Product Images

With Otto the most honest answer is also the least satisfying: Otto does not publish its image requirements. Unlike Zalando, About You and Amazon, which document their specifications in publicly accessible partner material, the binding values for OTTO Market sit inside the partner area behind a login — and are maintained there partly per assortment.

This page does not invent a table out of that. It separates cleanly instead: what do several independent integration providers consistently report, what follows from that for production planning, and where is there no way around your own partner access?

Status: August 2026. The binding source is the documentation inside the OTTO partner area. The values below are not quotations from Otto documents but the overlap of what interface and feed software vendors tell their customers about OTTO Market. Otto's public partner site otto.market covers access, terms and onboarding — it does not publish an image specification. That is precisely the finding of this page: the binding requirements sit inside the partner area, behind the login (last checked 13 August 2026).

Why the Source Situation Differs Here

Researching this cluster, Otto was the only one of the four marketplaces for which no publicly accessible primary source could be found. The OTTO Market API developer documentation describes interfaces but no image specifications. The public seller pages cover legal form, VAT registration and assortment eligibility — not image rules.

What exists instead are help articles from certified integration partners: ERP and feed vendors who pass the requirements on to their customers because their software has to enforce them technically. These sources are largely consistent with each other, which speaks for their accuracy — but they are second-hand, and at least one value differs between them.

That is not a trifle for planning. Rely on a second-hand number, write it into a production specification for 300 articles, and you carry the risk yourself. Checking your own partner access takes half an hour.

What Is Consistently Reported

Requirement	Consistently reported value	Reliability
File format	JPG or PNG	Consistent across sources
Colour space	RGB only; CMYK is not processed	Consistent across sources, technically plausible
Minimum size	500 × 1000 px	Named repeatedly — one source states 480 × 960 px, another 1000 × 1000 px. Sources disagree here.
Maximum dimension	4500 px per side	Consistent across sources
Frame fill	Product fills roughly 85 % of the image area	Consistent across sources
Main image background	Light and neutral — white, light grey, off-white or light beige; cut-out preferred	Consistent across sources, but without an exact colour value
File name	No umlauts or special characters	Consistent across sources
Prohibited content	Seller logos, watermarks, quality seals and certificates, price information, promotional text	Consistent across sources
Number of images	No reliable public figure — a single source states a maximum of 10 per variant	Not reliable — check the partner area
Aspect ratio	No publicly documented mandatory format found	Unresolved — check the partner area
Model requirement for fashion	No publicly documented rule found	Unresolved — check the partner area

The disagreement over minimum size is where this table shows its limits. Three sources, three numbers — 480 × 960, 500 × 1000 and 1000 × 1000 px. They may describe different image types or different points in time. For production that means: stay above the highest figure named and you are safe either way.

Planning Without a Published Specification

The unclear source situation leads to a production rule that is the better one anyway: do not produce for Otto, produce for the strictest requirement in your channel mix and derive Otto from it.

Concretely: if you serve Zalando alongside Otto, produce to Zalando's specification at a minimum of 762 × 1100 px, preferably 1801 × 2600 px. That sits far above every reported Otto minimum and below the 4500 px maximum. If you serve About You alongside Otto, take their 1500 × 2000 px as the base — equally safe.

The three points you still have to check separately for Otto, because they cannot be derived from other marketplaces:

• The colour space. RGB rather than CMYK is where images from a print production fail. Reusing material from a catalogue or print process carries real risk here.
• The file names. Umlauts and special characters are a classic stumbling block for German assortments.
• The image slots for your own product group. Neither the count nor the ordering is publicly documented.

The comparison with the other three marketplaces is in the fashion marketplace image requirements overview; the detail pages are Zalando, Amazon and About You.

The Most Likely Sources of Error

Because Otto publishes no rejection documentation, this section is deliberately qualitative. What integration partners name in their help articles as recurring causes of images not appearing or not being processed:

• Wrong colour space. CMYK files are not processed — and the image is then simply missing, without comment.
• Special characters or umlauts in the file name. The file is not fetched.
• Updating an image without changing the name. Replacing an image under the same file name and URL risks the new version not being reloaded. Integration partners therefore recommend either changing the file name or making a simultaneous change to the product data.
• Exceeding the maximum dimension. Very large master files from production are quickly above 4500 px.
• Logos, seals and price information in the image. The most common content violation, especially with material originally built for your own shop.

A Shot List on the Safe Side

1. Main image: article cut out or against a light, neutral background, product filling roughly 85 % of the frame.
2. Front view on model — drape and proportion.
3. Back view — the most effective lever against orders placed only to check what the garment looks like from behind.
4. Side or three-quarter view.
5. Fabric close-up.
6. Construction detail — seam, fastening, lining or print.
7. Optional: styled or context shot.

Trousers benefit from an additional side view, shoes from several angles including the sole. How many images actually carry per product group is covered in How Many Product Photos Per SKU.

Producing the Views Without a Shoot

Positions 2 through 4 are on-model views of the same garment and can be generated from an existing product photo. GridShot returns 16 to 25 pose variations per run in 5 to 15 minutes; billing is one US dollar per published image plus the compute actually consumed, a few cents. New accounts start with USD 10 in credit.

For Otto the same honest caveats apply as everywhere in this cluster, plus one more:

• The cut-out main image stays a camera job. Position 1 is conventional product photography; what gets generated are the views after it.
• Colour space, file name, dimensions and crop are export work in your own image pipeline, downstream of generation — not part of the generation step.
• And the Otto-specific point: without the binding specification from the partner area, no claim of "requirement met" can be made here. What this page can offer is a production that very probably sits above the requirements. Confirmation comes from a test article in onboarding, not from this text.

Products come in by URL import, larger catalogues by CSV import. What conventional production of the same volume costs is in Product Photography Pricing.

Otto Checklist

1. Binding image rules for your own product group read in the OTTO partner area — this page does not replace that.
2. Colour space of all files verified as RGB, especially for material from print production.
3. File names without umlauts and special characters.
4. Resolution above the highest reported minimum, dimensions below 4500 px.
5. Main image cut out or against a light, neutral background; product filling roughly 85 % of the frame.
6. No logos, seals, certificates, price information or promotional text in the image.
7. When replacing an image, file name or product data changed alongside it so the new version loads.
8. One test article fully imported and checked on the live product page before the catalogue follows.

Frequently Asked Questions

What image requirements does Otto have?

Otto does not publish its image requirements; the partner area is binding. Integration software vendors consistently report: JPG or PNG, RGB colour space only, a minimum size in the region of 500 × 1000 px, a maximum of 4500 px per side, a product filling roughly 85 percent of the frame, and a light, neutral background for the main image. Status: August 2026.

Why are the Otto image guidelines not published?

Because they are not published. The OTTO Market API developer documentation describes interfaces but no image specifications, and the public seller pages cover eligibility rather than image rules. The binding values sit in the partner area behind a login and differ partly by assortment.

What minimum resolution does Otto require?

The available figures disagree: 480 × 960 px, 500 × 1000 px and 1000 × 1000 px are all cited. Because none of them comes from a public Otto source, the safe approach is to produce above the highest figure named and to read the binding number in the partner area.

Does Otto require model images for fashion?

No publicly documented model requirement could be found. Independently of that, the same logic applies as everywhere in fashion e-commerce: drape, length and proportion cannot be conveyed without showing the garment on a body. Whether Otto formally requires it is a question for the partner area; that it helps the sale is not in doubt.

Why is my updated image not showing on Otto?

A recurring note from integration partners: if an image is replaced under the same file name and URL, the new version may not be reloaded. The recommendation is to either change the file name or make a simultaneous change to the product data so the update gets processed.