Maximum practical square at 1600×1600
Sixteen-hundred-pixel squares show up when teams want one large square from which smaller icons are derived. Upscaling a soft 400×400 cannot invent detail. Prefer a larger original, resize to 1600×1600 here, verify the measured box, then generate smaller siblings from that download offline or with other tools.
Source masters that survive downscaling to 1600×1600
Start from a larger master when possible; upscaling a tiny source makes edges fuzzy even if pixels match. Prefer a clean master with more pixels than you need when downscaling; upscaling tiny sources cannot invent detail. Temporary server copies are cleaned on a schedule; treat downloads as your durable copy. Start from the original export whenever you still have it, not a chat-compressed copy. Temporary processing is not archival storage, save the download you intend to submit.
Sixteen-hundred-pixel squares for large retina tiles
Apple-style retina grids and high-DPI storefronts cite 1600×1600 for crisp square merchandise art. Match the published width×height first when both rules appear, then return for weight targeting if needed. If rejection continues, re-read the help text for a second hidden rule. Temporary processing is not archival storage, save the download you intend to submit.
Merchandise framing inside 1600×1600 boxes
Products with shadows need margin so fill cropping does not clip packaging corners. A second hidden rule (pixels, PNG-only, DPI) often explains “file still rejected” after a successful size pass. Nearby tools cover adjacent size and format rules when this page is not the match. When format or pixel rules sit outside this page, finish those steps on the related tools linked nearby.
JPEG storefront art at 1600×1600
Default JPEG output keeps bytes practical for photo content. Gradients in lifestyle shots band if quality drops too low during downscale. Keep naming clean, odd double extensions confuse some intake scripts. Avoid screenshotting the preview pane, download the generated file instead. Temporary processing is not archival storage, save the download you intend to submit.
Storefront byte limits after 1600×1600 fit
Some commerce APIs cap two-megabyte JPEGs separately from pixel validation, read API docs. Keep an uncompressed master until the destination accepts the file. Start from the original export whenever you still have it, not a chat-compressed copy. Being under the cap is the real pass condition; exact byte matching is uncommon.
Batch seasonal squares at sixteen-hundred pixels
Holiday variants need per-SKU preview for color accuracy at large square size. Match the published width×height first when both rules appear, then return for weight targeting if needed. Open the download once before you close the tab. If the result looks too soft, tighten framing before lowering quality again.
Commerce API upload check for 1600×1600
Confirm measured bytes and pixels on the result card match marketplace API validation messages. Read the rejection wording carefully, error toasts sometimes omit format details that still block you. If the published rule shifts, switch to the sibling tool that matches the new number. If the result looks too soft, tighten framing before lowering quality again.
How the resize is applied
Output is written at 1600×1600 pixels. The preview and download use that raster. File weight still depends on subject detail and the output format, not only the pixel box.
Resize checks
Exact-size tools are checked by measuring the output width and height after processing. A pass means those pixels match the named box. File size is reported separately. Reviewed 5 October 2026.
Technical reference
Everyday “JPEG” files follow the JFIF interchange pattern on top of JPEG compression. MDN summarizes the type, MIME value image/jpeg, and common extensions: MDN image file type guide.
Frequently asked questions
1600×1600 for storefront retina tiles?
When commerce APIs cite sixteen-hundred-pixel squares, read output dimensions. Open the download once on your submission device before retrying the portal. If softness is unacceptable, crop tighter or ask whether a higher official limit exists.
1600×1600 satisfy API byte limits?
Marketplace APIs may cap two-megabyte JPEGs separately from pixels. Batch mode still shows per-file previews. Review each result before submitting a set.
Upscale merchandise to 1600×1600?
Packaging detail softens, shoot square masters at high resolution. Neighboring tools exist for nearby sizes; switching is better than forcing the wrong ceiling.
Storefront orientation at 1600×1600?
Preview on the commerce admin grid; EXIF may not match listing crop. Neighboring tools exist for nearby sizes; switching is better than forcing the wrong ceiling.
Batch seasonal SKUs at 1600×1600?
Each variant previews independently before API upload. If softness is unacceptable, crop tighter or ask whether a higher official limit exists. Neighboring tools exist for nearby sizes; switching is better than forcing the wrong ceiling.
Why 1600×1600 instead of generic resize?
Generic resize works broadly, this page names the exact box so search intent matches the checklist. Neighboring tools exist for nearby sizes; switching is better than forcing the wrong ceiling.