Product listings need delivery copies, not camera originals
1 rejected product photo can delay a marketplace listing, catalog update, or buyer support reply. An iPhone 15 may save a sharp product shot as HEIC because Apple has used HEIF/HEIC as the default camera format since iOS 11 in 2017, but listing systems still tend to ask for JPG or PNG. Start with the flagship HEIC to JPG converter when the platform accepts JPG, then add resizing, compression, or metadata cleanup only when the listing rules require it.
HEIC is a compact image container that commonly stores iPhone photos with HEVC compression. JPG is a delivery image format built for broad compatibility across browsers, catalogs, help desks, and seller dashboards. Apple explains the modern iPhone format in its HEIF and HEVC support guide, while the older JPEG format remains the safer upload choice for storefronts that validate files by extension.
Set listing outputs before editing
A product workflow should protect the original while creating a predictable web copy. Do not switch every iPhone photo to Most Compatible just because one marketplace rejects HEIC; create JPG exports for the listings that need them.
Use JPG for ordinary product photos
Use JPG for shoes, tools, books, furniture, handmade items, packaging, and serial-number evidence when the image is a normal camera photo. A 90% JPG export is a practical first pass because it keeps surface detail visible without producing a huge file. If the marketplace caps uploads at 5 MB, resize the long edge to 2000 px with the image resizer before dropping below 82% quality. For a stricter size workflow, use the image compressor after conversion instead of repeatedly exporting the same file.
Use PNG only for text-heavy product evidence
Use PNG when the image is a label, barcode, spec plate, invoice, app screenshot, or diagram where small text must stay crisp. PNG can become 2x to 5x larger than JPG, so it is not the default for ordinary catalog photos. The format tradeoff is covered in When HEIC to PNG Is Better Than JPG, and a wider JPG setting guide is available in Best JPG Quality After HEIC Conversion.
How browser-local product photo conversion works
Browser-local conversion reads the selected HEIC through the browser File API, decodes the HEIF container and HEVC-compressed image data with native support or a WebAssembly codec such as libheif, draws the decoded pixels into a Canvas-style bitmap, and exports a JPEG blob at the selected quality. The W3C File API defines the browser layer that lets a page read a local file selected by the user. That mechanism matters because conversion fixes the rejected .heic extension, resizing fixes excessive dimensions, compression fixes a 2 MB, 5 MB, or 10 MB cap, and EXIF cleanup fixes hidden device or location data.
A clean marketplace photo workflow
Use one folder for originals and one folder for listing-ready copies. That keeps the HEIC archive intact while giving the storefront a consistent JPG set.
- Keep original HEIC files in Photos, Files, or your archive drive.
- Convert selected product photos through / at about
90%JPG quality. - Use the batch converter for 20 or more listing photos.
- Resize long edges to
2000 pxor2400 pxwhen the platform only displays web previews. - Compress only the files that still exceed the marketplace limit.
- Remove metadata with the EXIF remover before publishing photos from a home, warehouse, workshop, or customer site.
Windows can complicate handoff without changing the upload rule. A Windows 11 23H2 PC on build 22631 may preview HEIC after codec support is installed, but the seller dashboard can still reject the same file because it only allows .jpg, .jpeg, or .png. If the issue is cloud upload friction, compare the local workflow with better than Convertio or the free alternative to CloudConvert.
FAQ
What JPG quality should I use for product listings?
Start at 90% quality. For most web storefronts, 88% to 92% keeps product texture, color edges, and labels clean while avoiding oversized exports.
Should I resize iPhone product photos before uploading?
Yes when the original is a full-resolution 12 MP or 48 MP iPhone photo and the platform displays a web gallery. A 2000 px long edge is often enough for listings with a 5 MB cap.
Does converting HEIC to JPG remove GPS data?
Not reliably. Format conversion and metadata cleanup are separate steps, so use EXIF removal before publishing images shot at a home address, warehouse, workshop, or customer location.
Is browser-local conversion better than a cloud converter for listings?
It removes the upload step for the original files, which matters when a batch includes 30 private inventory photos or customer-site images. Cloud tools can still help with unusual formats, but normal HEIC-to-JPG listing work does not need a remote queue.
Bottom line
Product listings need compatible, consistent delivery images. Keep HEIC as the original, convert selected photos locally to JPG, resize against the platform display size, compress only against a real byte cap, and remove EXIF before the listing goes public.