How are images processed and resized?

Image handling uses ImageSharp. When an image is uploaded (for a product, category, variant, etc.) it is processed into multiple stored sizes — typically a full/large version and a thumbnail — so list views can load small images quickly while detail pages show the large one. Images are represented as polymorphic MediaAsset records that reference an owner (e.g. a Product or a Variant) and…

Image handling uses ImageSharp. When an image is uploaded (for a product, category, variant, etc.) it is processed into multiple stored sizes — typically a full/large version and a thumbnail — so list views can load small images quickly while detail pages show the large one. Images are represented as polymorphic MediaAsset records that reference an owner (e.g. a Product or a Variant) and a role (Main, Gallery, and so on) with a sort order, so a single product can have a main image plus an ordered gallery. If a product has no image, the system falls back to an automatically generated placeholder so listings never break. During catalogue import, images can also be fetched from URLs in a separate, safety-hardened step.