OXID eShop is a shop system from Germany, and its user documentation is published in English and German. Unlike many shop systems, it sets a hard upload limit for product images, and it generates the smaller sizes for you. This page collects what the OXID docs say about product pictures, with the date we checked them, and turns it into settings for clothing photos. We make NotShot, an AI on-model photo tool, so we also cover where on-model images fit.
The Pictures tab page of the OXID eShop docs (checked by us on 1 November 2026) gives a standard limit for product pictures: max. 2 MB per file and max. 1500 × 1500 pixels. The same limit is listed for custom thumbnails and icons. The docs warn that exceeding these values may cause memory issues while thumbnails and icons are generated. If needed, the upload_max_filesize and memory_limit values in php.ini can be raised.
For clothing, 1500 pixels on the long side is the safe target. A typical portrait shot in a 2:3 ratio then comes out at 1000 × 1500 pixels.
A product can have up to twelve pictures, shown in the product's detail view. The Pictures tab has upload fields #1 to #7. To use more than seven, the docs say to upload via FTP or customize the Admin panel template. After saving, OXID creates a thumbnail and an icon automatically. You can replace either with your own file under Custom pictures, and the trash icon deletes an image from the tab and the web server.
The result, per the docs: the product detail view shows the uploaded picture, product lists show the thumbnail and the shopping cart shows the icon.
Under Extensions » Themes » Settings » Images, the OXID images configuration page (checked 1 November 2026) lists the sizes OXID generates. The defaults include:
The docs add a hint: use different product picture sizes with caution, because pictures of different sizes can make the product presentation look unprofessional. For clothing, keep one size and one ratio for every picture of a product.
They also note that the size you set is the maximum the browser downloads, while the displayed size comes from your theme's CSS. In the demo store a subcategory image is downloaded at 300 × 300 pixels and shown at 62 × 62.
Under Master Settings » Core Settings » System » Pictures, Picture Quality sets the quality of the generated images. The default is 75, which the docs call a good compromise between quality and file size. Much lower values cause blurring and compression artifacts, and higher values mean larger files and longer loading times. The same section has an option to convert images to WebP automatically.
For clothing, check knits, fine prints and dark fabrics at your chosen quality before you change it for the whole shop.
The APEX theme offers three zoom types: hover zoom, modal zoom and a magnifying glass. You set one for the whole shop under Extensions » Themes » APEX » Settings » Product detail page. For a single product, enter the matching template in the Alternative Template field on the product's Settings tab. The docs say zoom templates can't be applied at category level.
Zoom is where shoppers check fabric, stitching and fit, so your uploads should be close to the 1500 pixel limit rather than near the 500 pixel thumbnail size.
Running another shop system too? Compare Shopware product image size for clothing, Gambio product image size for clothing and JTL-Shop product image size for clothing. For lighting and backdrops, see our clothing product photography guide.
The OXID docs set no rule against models in product pictures, so an on-model photo can sit next to your packshots in the twelve picture slots. Check each marketplace's own rules before you export there. NotShot renders your garment on your own model from the product photo you already have, and every render is checked by an AI judge that compares it with your upload for color, print and cut. Renders below the quality bar are refunded automatically, so you pay for photos that pass the check, not for attempts. Plans are on the pricing page.
