https://damaheritage.com/Product-image workflows for online sellers, platform references and reproducible browser tests.enhttps://damaheritage.com/guides/fit-vs-fill/https://damaheritage.com/guides/fit-vs-fill/Mon, 07 Sep 2026 00:00:00 GMTChoose whether to preserve the entire product photo or fill a frame by cropping, based on what the listing image must keep visible. Updated 2026-09-23. A whole source photo fitted inside a frame with padding, compared with a fill that removes the overflow. Choose by risk, not by preset Fit keeps the whole source photo inside the output frame and may leave padding. Use it when a product edge, accessory, label or included-piece count must remain visible. Fill covers the frame and removes overflow; use it only when the removed area is expendable and the remaining photo still represents the product accurately. Neither mode recognizes the product or removes its background. A margin adds space around the full source photo, not around the product itself. If the original already contains a wide empty border, Fit preserves that border too. Make the decision with one representative image Do not decide from a single easy-to-crop product. Test one image with a detail near an edge and one image whose whole silhouette matters. Preview at the small size where a shopper will see it; a crop can preserve the object yet make a thin or small item hard to recognize. Use a short review routine Image Prep's preview shows illustrative center crops. It does not know which area of your image is important and is not a recreation of Etsy's interface. The downloaded file remains the prepared image; the small crop cards are checks, not alternate exports. 1. Name the details that must stay visible: full silhouette, text, accessories or quantity. 2. Prepare one copy with Fit and one with Fill; change no other setting during the comparison. 3. Inspect each complete export, then use Check crops to spot likely clipping. 4. If Fill cuts something important, use Fit, choose another source composition or adjust it in an editor with manual crop controls. 5. Check Etsy's own thumbnail editor and the final listing preview before publishing. This is an editorial explanation of a documented workflow, not a claim of first-hand selling experience. Examples are illustrative or reproducible; browser output and marketplace presentation can vary. Reference: Canvas drawImage: destination size and image scaling — https://developer.mozilla.org/en-US/docs/Web/API/CanvasRenderingContext2D/drawImagehttps://damaheritage.com/guides/thumbnail-crop-checklist/https://damaheritage.com/guides/thumbnail-crop-checklist/Mon, 07 Sep 2026 00:00:00 GMTA practical crop-review sequence for Etsy listing photos: inspect product edges, meaning and the actual thumbnail before publishing. Updated 2026-09-23. Square, landscape and portrait thumbnail frames shown with their 1:1, 4:3 and 3:4 aspect ratios. Use local previews as a warning, not a platform guarantee Image Prep shows center-crop examples in square, landscape and portrait frames. These previews help identify a risky edge; they do not predict every Etsy search, collection or shop placement and do not change the exported file. Etsy's own thumbnail editor is the decisive check for its current listing flow. The separate Etsy image reference lists the current official requirements and sources. Review the image in three layers A source image, a marketplace thumbnail and a small search result are not interchangeable views. A product can look complete when enlarged but become ambiguous when reduced. Check the actual Etsy preview rather than assuming a square or landscape canvas dictates its display everywhere. 1. Inspect the full source and identify its outermost meaningful detail. 2. Open the Image Prep crop cards to find obvious edge risks. 3. Use Etsy's thumbnail adjustment tool and inspect each preview it currently offers. 4. Check the saved draft at small display size before publishing. Check that the crop keeps the listing truthful A crop is not merely a composition choice if it changes what a shopper thinks is included. A handle, cable, matching piece or packaging can establish product identity or quantity. Do not remove such context just to make a thumbnail more dramatic. Small text may be unreadable in a thumbnail even when no pixels are cropped. Keep the main image understandable at small size and use separate detail photos for close-up information. When the thumbnail does not work If the subject is clipped, do not solve it by blindly adding output pixels. Try a less aggressive crop, add breathing room to the original composition or choose a different hero photo. If the subject becomes too small when fully preserved, create a closer source image while keeping enough context to represent the item accurately. 1. Return to Fit when preserving the whole photograph matters more than filling the frame. 2. Use a source with more space around the object when the current edge is too tight. 3. Separate the primary product view from detail or scale-reference views. 4. Reopen Etsy's own preview after any image or crop adjustment. This is an editorial explanation of a documented workflow, not a claim of first-hand selling experience. Examples are illustrative or reproducible; browser output and marketplace presentation can vary. Reference: Etsy: image requirements and thumbnail best practices — https://help.etsy.com/hc/en-us/articles/115015663347-Requirements-and-Best-Practices-for-Images-in-Your-Etsy-Shophttps://damaheritage.com/guides/consistent-product-grid/https://damaheritage.com/guides/consistent-product-grid/Mon, 07 Sep 2026 00:00:00 GMTUnderstand Shopify's current image limits, when a 2048-pixel square is useful, and why a consistent image frame still needs a theme preview. Updated 2026-09-24. Three equal square canvases form a consistent grid while the objects inside retain different apparent sizes. What Shopify currently recommends Shopify's product-media page, checked September 24, 2026, says product and collection images can be up to 5000 × 5000 pixels or 25 megapixels, with a file size under 20 MB. It says 2048 × 2048 pixels usually displays best for square product images; that is a starting recommendation, not a mandatory upload size. The same page lists PNG as the best type for most product images, followed by JPEG, and says Shopify's Imagery service selects a format supported by a customer's web client. This site's browser tools accept JPG, PNG and static WebP only. Shopify accepting another type does not mean Image Prep can process it. Choose one featured-image ratio for a collection Shopify notes that featured images with a consistent aspect ratio can appear the same size beside one another on collection pages. It also says themes can request consistent image sizes from Shopify's CDN, and that Shopify creates different image sizes for different theme areas. This means a matching source ratio can help a collection grid, but it does not control every display crop or resolution. Choose a ratio that fits the product family and inspect it in the actual theme. Do not stretch a portrait image into a square: Image Prep preserves proportions and uses padding or cropping instead. A square canvas also cannot make two products appear equally large if one source includes much more empty space. Worked example: portrait photo on a square canvas A 1600 × 2400 portrait fitted inside a 2048 × 2048 square at zero margin scales to about 1365 × 2048. That leaves about 341 pixels of canvas at each side. With a 5% inner margin, the usable square is 1843 × 1843; the portrait scales to about 1229 × 1843, leaving about 410 pixels per side. These are geometric calculations from the source dimensions and fit rule, not a Shopify preview. Fill would crop the top and bottom to cover the square. If the source is smaller than the target and enlarging is disabled, Fit will preserve its original pixel size rather than invent detail. Check the theme, then check the file limit The platform allows up to 5000 pixels on an edge and 25 megapixels, but Image Prep is intentionally more conservative: dimensions top out at 4096 pixels per edge and 12 megapixels per output. A file can be valid for Shopify and still exceed this tool's limits. Use another trusted editor for a larger output rather than repeatedly retrying it here. 1. Choose the featured-image ratio used by the product family or theme; do not assume square is always best. 2. Prepare one portrait and one landscape source with Fit before trying any crop. 3. Compare the complete exports side by side and check whether empty margins—not canvas dimensions—explain uneven product scale. 4. Upload representative files and inspect the collection page at both phone and desktop widths. 5. Check the image's actual uploaded type, pixel dimensions and byte size against Shopify's current requirements. 6. Revisit Shopify's official media page when its published limits or supported types change. This is an editorial explanation of a documented workflow, not a claim of first-hand selling experience. Examples are illustrative or reproducible; browser output and marketplace presentation can vary. Reference: Shopify: product media types, image requirements and presentation — https://help.shopify.com/en/manual/products/product-media/product-media-typeshttps://damaheritage.com/guides/file-size-and-quality/https://damaheritage.com/guides/file-size-and-quality/Mon, 07 Sep 2026 00:00:00 GMTChoose output dimensions and JPG, PNG or WebP using a repeatable comparison instead of a promised file-size target. Updated 2026-09-24. Dimensions, encoding quality and output format are three separate controls; the final file size must be measured. Dimensions are not a file-size promise Dimensions describe the pixel grid. A 2000 × 2000 image contains four million pixels regardless of whether its encoded file occupies 300 KB or 3 MB. File size also depends on the content, format and encoder. A detailed fabric photograph can need more bytes than a plain background at the same quality setting. The quality percentage is an encoder input, not a visual quality score. An 85% setting does not guarantee a specific number of kilobytes or identical results in every browser. Image Prep displays the actual output file size after preparation; it does not promise a hard KB target. Choose a format with the image in mind JPG is a practical starting point for photographs when the destination accepts it. WebP may provide smaller files, but confirm destination support before choosing it. PNG is lossless at the encoding stage and can be useful for sharp graphics, although photo files can be much larger. The PNG quality slider is disabled because the canvas PNG encoder ignores that parameter. All Image Prep exports are composited onto the selected background. This includes transparent PNG and WebP inputs; the tool currently does not preserve transparent backgrounds. Compare your own product photos consistently This workflow is for choosing settings for your own source image. Keep its dimensions and source unchanged while comparing compression, then inspect the actual exports. The local format-comparison tool encodes your image in the current browser and records its actual output MIME type and byte count. For a separate controlled reference-encoder benchmark, see the fixed-fixture experiment; its byte counts are not predictions for your photos. 1. Use the local format-comparison tool to encode one original as JPG, PNG and WebP at the same target dimensions. 2. Record the actual format and byte count returned by your browser; a browser may fall back to a different MIME type. 3. Inspect text, fine texture, diagonals and high-contrast edges at normal viewing size and at 100%. 4. Repeat with a second source that differs in texture, text or transparency; one file does not establish a general winner. 5. If edge artifacts or smearing become visible, use a less compressed output and verify the destination accepts that format. 6. Only then prepare a batch; check more than one result and the real listing preview. What re-encoding can change Re-encoding a compressed source can compound visible damage. Keep originals separately and start each new variation from them. Enlargement adds pixels, not detail; it cannot recover a blurry label. Canvas creates a new encoded image rather than copying the original metadata container. Original EXIF/IPTC metadata and color-profile behavior are not preserved as an archival workflow. Browser decoding, color management and interpolation can differ, so compare important product colors against the original. If a browser cannot encode the chosen format and returns PNG, the download uses the actual .png extension and displays a fallback notice. Do not rename a .png file to .webp to make it acceptable to a platform. This is an editorial explanation of a documented workflow, not a claim of first-hand selling experience. Examples are illustrative or reproducible; browser output and marketplace presentation can vary. Reference: Canvas toBlob: formats, quality and browser fallback — https://developer.mozilla.org/en-US/docs/Web/API/HTMLCanvasElement/toBlobhttps://damaheritage.com/guides/product-photo-workflow/https://damaheritage.com/guides/product-photo-workflow/Mon, 07 Sep 2026 00:00:00 GMTSet a product-code naming pattern, review every export and reuse browser-saved settings for your next listing. Updated 2026-09-08. Three camera filenames map to the sequential product filenames MUG-042-001.jpg, MUG-042-002.jpg and MUG-042-003.jpg. One product, one batch Choose a stable identifier such as MUG-042 before adding photos. Image Prep uses one shared filename prefix per batch, so separating products prevents unrelated images from receiving the same code. Keep your original folder unchanged. Files receive sequence numbers in the order shown in the workspace. If order matters, add files in the desired order; operating-system file pickers may return their own ordering. Image Prep does not currently offer drag-to-reorder. Check and arrange image order inside the marketplace after uploading. Make a small test export first Add one landscape image, one portrait image and a detail photo. Choose dimensions, fit, background and format. A convenient default is a square canvas with Fit and a small margin, but review your destination rather than treating the preset as a requirement. After Prepare images, compare the actual byte sizes, check crops and save a result. Open the downloaded copy to verify appearance. A successful export only means the browser created a file; it does not guarantee that a marketplace will accept it. Naming rules you can predict With prefix MUG-042 and first number 1, the first file becomes MUG-042-001.jpg when exported as JPG. Numbers are padded to at least three digits. Prefix characters outside letters A–Z, digits, hyphens and underscores are replaced with hyphens. Empty prefixes become product. The preview shows the final sanitized prefix, including adjustments for reserved filenames. Each input keeps its assigned position during processing. If the second image fails, successful exports may be numbered 001 and 003. The gap is useful evidence of a failed file: review the error list and archive contents. Remove a failed file and prepare again if you need a continuous sequence. Sequence numbers help organize files; they do not guarantee search rankings or storefront order. Never rely on filenames alone to select a listing’s primary photo. Close the batch deliberately 1. Confirm that the number of prepared images matches the number you expect. 2. Download the ZIP or save individual successful images. ZIP is an archive, not extra image compression. 3. Extract the archive and inspect names, dimensions and appearance. 4. Upload to your platform and check the actual listing preview. 5. Save settings for next time. The prefix is saved too, so change the product code for a new item. 6. Clear the batch when finished. Clearing removes selected files and results from the workspace but leaves your controls and optional saved settings unchanged. What comes back next visit Saved settings belong to this browser profile on this device. They do not sync with another phone or computer, and clearing site data can remove them. Photos and ZIP files are not saved in a cloud library. Use “Forget saved settings” to delete the stored recipe without changing the controls currently on screen. Source name | Export name IMG_1048.jpg | MUG-042-001.jpg IMG_1051.jpg | MUG-042-002.jpg detail-final.png | MUG-042-003.jpg This is an editorial explanation of a documented workflow, not a claim of first-hand selling experience. Examples are illustrative or reproducible; browser output and marketplace presentation can vary. Reference: Browser localStorage: persistence and limitations — https://developer.mozilla.org/en-US/docs/Web/API/Window/localStoragehttps://damaheritage.com/guides/browser-image-troubleshooting/https://damaheritage.com/guides/browser-image-troubleshooting/Mon, 07 Sep 2026 00:00:00 GMTResolve unsupported formats, large images, memory pressure, failed ZIP downloads and blocked browser settings storage. Updated 2026-09-23. A 4000 by 3000 pixel image expands to a roughly 48 MB RGBA buffer before browser overhead, even if its compressed file is small. Separate memory pressure from the file's download size The compressed file size does not tell you how much working memory the browser needs after decoding. This page focuses on recovery steps; the separate browser-limits experiment shows the pixel-buffer estimate and explains why it is not a device guarantee. Image Prep processes images sequentially and limits inputs to 24 megapixels, 20 MB per file, 20 images and 100 MB total. Outputs are capped at 12 megapixels per image and 100 MB per batch. These are product safeguards, not a guarantee that every low-memory device can handle a full batch. If a file is rejected before preparation The tool checks image headers rather than trusting a filename extension. Renaming picture.heic to picture.jpg does not convert it. Open the original in a trusted editor and export JPG, PNG or static WebP. GIF, SVG, HEIC and animated PNG/WebP are outside the supported scope. A damaged or incomplete file may have a familiar extension but lack valid image data. Try opening it outside the browser. If it cannot be opened there, recover the original rather than repeatedly trying the same broken export. If processing slows or stops 1. Cancel the run; cancellation takes effect after the current decode or encode operation finishes. 2. Keep or download any successful outputs, then try fewer photos. 3. Reduce output dimensions and close other memory-heavy tabs. 4. Test the failing file by itself. Large pixel dimensions matter even if the compressed size is small. 5. Try a current browser with image bitmap and canvas support. 6. Keep originals outside the browser. An open tab is not a backup. If the ZIP is missing A browser may block a download or ask where to save it. Check its downloads list first. Image Prep says “download requested” because a web page cannot verify that you saved and extracted a file. If building an archive fails, use Save image on individual results or prepare a smaller batch. PNG outputs can become large; a suitable JPG or WebP may reduce memory use when your destination supports it. The 100 MB output limit is checked as results are created, so some files can succeed and later files can fail. If saved settings do not return Private browsing, storage restrictions, cleared site data, a different browser profile, or a different device can explain missing settings. The workspace should still function with defaults. A failed save displays a message instead of silently promising persistence. Do not rely on browser navigation to preserve or clear a batch. Use Clear batch when finished, and keep originals separately. Browser and operating-system caches are outside Image Prep's control; local processing is not a promise of secure erasure of every trace. This is an editorial explanation of a documented workflow, not a claim of first-hand selling experience. Examples are illustrative or reproducible; browser output and marketplace presentation can vary. Reference: Canvas image data and pixel buffers — https://developer.mozilla.org/en-US/docs/Web/API/ImageDatahttps://damaheritage.com/marketplace/etsy/https://damaheritage.com/marketplace/etsy/Tue, 22 Sep 2026 00:00:00 GMTCheck Etsy's supported photo types, pixel recommendations, upload-size warnings and thumbnail workflow using directly linked Etsy help sources. Last checked 2026-09-23. Check the file type before exporting Etsy's current image guidance lists JPG, GIF, PNG, SVG and HEIC. It does not list WebP, even though Image Prep can export WebP and Image QA can inspect it. For an Etsy upload, choose JPG or PNG in this tool and confirm the file type in the listing draft. Renaming a WebP file does not convert it. Etsy says animated GIFs and transparent PNGs are not supported as expected; transparent areas may appear black. Image Prep composites transparent inputs onto the selected background, so choose that background deliberately. Check Etsy's linked requirements again if its supported formats change. Treat pixel dimensions as guidance, not a magic threshold Etsy recommends listing images at least 2000 pixels wide and high. Its image guidance also says the first photo should be at least 635 pixels in both dimensions to avoid reduced search appearance. The Search Visibility page separately recommends a 2000 × 2000 main photo. These are platform recommendations; meeting a pixel count alone does not guarantee search placement, acceptance or a sharp result. The guidance allows a landscape or square first image and recommends leaving room around the subject for thumbnail treatment. Do not enlarge a small original just to hit a number: added canvas pixels cannot restore missing detail. Use Etsy's own thumbnail adjustment tool to inspect the actual crop. Upload size advice is not one universal cap Etsy's image-requirements page warns that files over 1 MB may not finish uploading, especially on a slow connection. Its listing-creation help page separately says images over 300 KB may time out. Those statements are not the same as a single guaranteed file-size limit; connection conditions and the upload flow matter. If an upload stalls, test one image on a stable connection, then reduce dimensions or JPG quality in small steps and compare the result. Keep text, texture and product edges legible. Check the draft listing rather than treating a particular kilobyte target as a platform rule. Check composition, color and the final listing Etsy may compress images after upload, which can make them look less sharp. Etsy also converts images to sRGB; if colors shift, convert the source to sRGB before uploading and compare the listing preview with the original. The Search Visibility page checks more than image dimensions: it also calls out a clear main photo of one finished product rather than a collage, at least one listing photo, category details and shop/customer-service signals. Treat the page as a diagnostic checklist, not a ranking promise. Image optimization cannot replace accurate listing information or a useful product offer. A repeatable pre-publish check Use representative images that expose different risks: the main product view, an edge-sensitive detail and an image containing small text or transparency. A crop preview catches some framing problems, but only Etsy's own draft and thumbnail previews show how the platform currently presents the upload. 1. Confirm that the export type is supported by Etsy; use JPG or PNG from Image Prep. 2. Check the source dimensions and composition without enlarging a low-detail original to chase a number. 3. Inspect the exported file at normal size and at 100%, including edges, text and important color. 4. Upload one representative file to a draft and inspect Etsy's thumbnail adjustment and listing preview. 5. If an upload times out, test one file and adjust dimensions or compression gradually instead of assuming a universal size cap. 6. Record the official source and checked date when you reuse this workflow. Known limits Image QA can identify a file type and dimensions; Image Prep can create local exports. Neither tool checks Etsy account status, listing policy, image attractiveness, accurate product representation or the exact crop on every search and collection surface. A correct export is one technical check, not a promise of visibility or sales. Reference: Etsy: Requirements and Best Practices for Images in Your Etsy Shop — https://help.etsy.com/hc/en-us/articles/115015663347-Requirements-and-Best-Practices-for-Images-in-Your-Etsy-Shop Reference: Etsy: How to Use the Search Visibility Page — https://help.etsy.com/hc/en-gb/articles/25869947521175-How-to-Use-the-Etsy-Search-Visibility-Page Reference: Etsy: How to Create a Listing — https://help.etsy.com/hc/en-us/articles/115015628707-How-to-Create-a-Listinghttps://damaheritage.com/marketplace/shopify/https://damaheritage.com/marketplace/shopify/Tue, 22 Sep 2026 00:00:00 GMTCurrent Shopify image limits, format guidance and collection-image behavior, with a practical check that accounts for theme crops and this site's tool limits. Last checked 2026-09-24. Current image limits and accepted formats Shopify's product-media documentation, checked September 24, 2026, says product and collection images can be up to 5000 × 5000 pixels or 25 megapixels, and must be smaller than 20 MB. It lists PNG as the preferred format for most product images, followed by JPEG; it also lists PSD, TIFF, BMP, GIF, SVG, HEIC and WebP. Shopify's image service selects a format supported by each customer's web client. The 2048 × 2048 square recommendation applies to square product images that usually display best; it is not a universal upload requirement. Use the current linked help page if a platform rule matters to your workflow, because requirements can change. Why the collection can still look uneven Shopify says consistent aspect ratios for featured images can help collection images appear the same size side by side. It also notes that themes can request consistent sizes from Shopify's CDN and that different image sizes are created for different theme areas. A matching source ratio can improve consistency, but theme crops and responsive layouts still affect the final display. Equal output canvases do not equalize the size of the objects inside them. If one source product fills 80% of its frame and another fills 40%, fitting both into the same square preserves the apparent-size difference. Added padding surrounds the source rectangle; it does not detect or trim empty background around a product. 1. Choose the featured-image ratio used by the product family or theme, rather than assuming square is always best. 2. Use Fit to preserve all source edges. Use Fill only if the part removed by cropping is genuinely expendable. 3. Compare one portrait and one landscape product at the same output dimensions; note whether empty source margins cause unequal object scale. 4. Upload representative images and inspect both the collection grid and product page on phone and desktop. Shopify limits versus Image Prep limits Shopify allows images up to 5000 pixels per edge and 25 megapixels. Image Prep is deliberately smaller: it limits each output to 4096 pixels per edge and 12 megapixels. Shopify may accept file types this tool cannot open; Image Prep supports JPG, PNG and static WebP. A platform-valid file is not automatically within this browser tool's limits. Seller Operations Lab cannot see your store theme, its custom image settings or Shopify's final CDN response. Use the live theme preview as the presentation check; use this reference for the linked platform facts and the tool pages for local file checks. Reference: Shopify: Product media types — https://help.shopify.com/en/manual/products/product-media/product-media-typeshttps://damaheritage.com/experiments/jpg-png-webp/https://damaheritage.com/experiments/jpg-png-webp/Tue, 22 Sep 2026 00:00:00 GMTA reproducible reference-encoder comparison of image formats, with a clear record of what varies by encoder and source image. Last checked 2026-09-22. Hold the variables still A fair format comparison changes one encoding choice at a time. Start from the original for every export; re-encoding a previously compressed file can add artifacts that obscure the result. 1. Use the same source image and target dimensions for every output. 2. Record the actual output MIME type and byte count, not only the selected extension. 3. Inspect fine texture, text, diagonal edges and flat color at normal viewing size. 4. Repeat with a second image whose texture and background differ. Interpret the result carefully A smaller file is not automatically a better file. A product label that becomes unreadable or a color that shifts in a way your storefront cannot tolerate may outweigh the byte reduction. PNG can be appropriate for crisp graphics, but it is not a promise of small photographs. Question: Which output format gives a useful starting point for a product photograph? Method: Rasterize one deterministic 1600 × 1200 fixture with the repository's sharp reference encoder. Export the same pixels as JPG and WebP at quality 85 and as PNG, then compare the actual bytes. The browser tool can produce different numbers and is tested separately. Result: On the checked fixture, JPG was 34,980 bytes, PNG was 64,198 bytes and WebP at quality 85 was 14,846 bytes. This single fixture demonstrates why format choice changes bytes; it does not establish a universal winner or prove marketplace acceptance. Limitation: This is a repeatable reference-encoder comparison, not a universal compression benchmark. It does not test every browser, color profile or marketplace pipeline; run the browser workflow separately before relying on a result. Reference: Seller Operations Lab: deterministic format fixture script — https://github.com/huynjuunn-glitch/Milo/blob/main/scripts/measure-format-fixture.mjs Reference: MDN: HTMLCanvasElement.toBlob() — https://developer.mozilla.org/en-US/docs/Web/API/HTMLCanvasElement/toBlobhttps://damaheritage.com/experiments/crop-geometry/https://damaheritage.com/experiments/crop-geometry/Tue, 22 Sep 2026 00:00:00 GMTUse transparent calculations and controlled frames to see what centered 1:1, 4:3 and 3:4 crops remove from the same source. Last checked 2026-09-22. The geometry A centered crop keeps the smaller dimension and trims the larger one. On a 2000 × 2000 source, a 4:3 frame is 2000 × 1500, so 500 vertical pixels are removed in total. A 3:4 frame is 1500 × 2000, so 500 horizontal pixels are removed in total. Those pixels are not inherently unimportant. A handle, label or accessory near the edge can be more valuable than empty background in the center. The visual check Use a crop preview after preparing the image, then inspect it at approximately the size a customer will see. A centered crop is useful for identifying risk, not for claiming that a marketplace uses the same frame. 1. Mark the full product boundary before choosing a crop. 2. Compare square, landscape and portrait frames. 3. Move the source composition or add margin when a meaningful edge is clipped. 4. Verify the final listing preview after upload. Question: What content is removed when one image is shown in different aspect ratios? Method: Render the same prepared image into centered square, landscape and portrait canvases. Calculate the retained source rectangle before checking the visual result. Result: For a 2000 × 2000 square, a centered 4:3 crop removes 250 pixels from the top and bottom, while a centered 3:4 crop removes 250 pixels from each side. The calculation changes with every source ratio. Limitation: These frames illustrate geometry only. A real storefront may use a different crop position, focal point or responsive container. Reference: MDN: CanvasRenderingContext2D.drawImage() — https://developer.mozilla.org/en-US/docs/Web/API/CanvasRenderingContext2D/drawImagehttps://damaheritage.com/experiments/browser-limits/https://damaheritage.com/experiments/browser-limits/Tue, 22 Sep 2026 00:00:00 GMTA reproducible explanation of pixel buffers, browser limits and why local processing still needs conservative batch sizes. Last checked 2026-09-22. Compressed bytes are not decoded memory A JPG may occupy only a few megabytes on disk while expanding into millions of pixels in memory. The browser needs decoded data to draw a canvas, create a thumbnail and encode a new result. The Image Prep tool limits files to 24 megapixels, 20 MB per input, 20 files and 100 MB total input. The limits reduce risk; they cannot guarantee a successful run on every phone or low-memory device. A safer batch routine 1. Test one landscape and one portrait image first. 2. Process smaller batches when the device becomes slow. 3. Reduce output dimensions before assuming a format change will solve memory pressure. 4. Keep originals outside the browser and inspect every downloaded result. Question: Why can an apparently small image make a browser tab slow or fail? Method: Compare compressed file bytes with the decoded pixel count. A basic RGBA buffer uses roughly four bytes per pixel before canvases, thumbnails and browser overhead. Result: A 4000 × 3000 image contains 12 million pixels and needs roughly 48 MB for one raw RGBA buffer. Several copies can exist during decode, preview and export. Limitation: The estimate is a teaching model, not a device memory guarantee. Browser implementations, color depth and concurrent tabs vary. Reference: MDN: ImageData and pixel data — https://developer.mozilla.org/en-US/docs/Web/API/ImageData Reference: MDN: createImageBitmap() — https://developer.mozilla.org/en-US/docs/Web/API/Window/createImageBitmap