My Three-Step Image Handoff Before Every Shopify Upload
I used to treat product-image prep as a last-minute admin task. Someone would hand me a phone photo, I would drag it into Shopify, and then I would discover the crop looked awkward on mobile, the file was heavier than it needed to be, or I had no idea what metadata I had just passed along.
That is not a creative problem. It is a handoff problem. Now, before an image goes anywhere near a product page, I run the same three-step pass: make the crop intentional, remove hidden metadata, then make the file web-ready. It takes a few minutes and avoids the usual back-and-forth later.
I use Tiny Online Tools for this because the tools are focused, free, and designed for browser-based work without an account. The useful part is not having another giant media app in the stack. It is having the exact small tool ready when I need it.
1. Decide the crop before you resize
The first question is not “what dimensions should I type?” It is “where will this image have to work?” A product card, a collection grid, a product-page gallery, and a mobile view do not all reward the same crop.
I start with one approved source image and check two things:
- Is the product still obvious in a narrow mobile crop?
- Does the surrounding space feel intentional rather than like an accidental trim?
Then I use Resize Image to set the target dimensions. It supports custom pixel dimensions and an aspect-ratio lock, which is the setting I care about most. I would rather choose a crop deliberately than stretch a bag, garment, or bottle into a shape it was never meant to have.
For a Shopify workflow, I keep the original untouched and export the working version separately. That gives me room to create a square collection-card version and a taller product-detail version from the same approved source. The goal is consistency, not forcing one file to solve every placement.
This is the same operational discipline I use when turning one approved image into a broader asset plan. I also make a simple photo direction card before lifestyle work, then use a product-photo QA pass before anything ships. In that context, a reusable shot list is much easier to maintain when the source image has a clear job.
2. Clean hidden metadata before you share the file
A storefront photo can look perfectly normal and still carry information that does not belong in a vendor handoff, support ticket, or shared folder. Camera details, timestamps, and location data are not useful to a shopper, and I do not want to make assumptions about where a file will travel after I send it.
That is why I run Remove Image Metadata on the files that leave my working folder. The tool says it strips EXIF, GPS, camera information, and other embedded metadata from JPEG and PNG files directly in the browser, with batch processing available when I have a small set.
This is not an argument for making everything complicated. It is a small hygiene step that is especially sensible for phone-shot samples, supplier-provided photos, or images I am sending to a contractor. I keep the original safely in my asset library; the cleaned copy is the one I share and upload.
If you are already doing a pre-publish catalog check, treat image cleanup as one line on the same list. I use a similar “verify before connecting” mindset for marketplace data in my Etsy product-feed check: a five-minute review is cheaper than finding the problem after it is public.
3. Export the web-ready version, then check the trade-off
The last pass is about delivery. A beautiful product image is not helping much if it makes a collection page sluggish, especially on a phone connection. I do not chase a magic file-size number; I check the image at the size a customer will actually see.
For a PNG that does not need to stay PNG, I use PNG to WebP. It can convert one or multiple PNGs and offers a quality setting, so I can compare a lighter export with the source rather than guessing. If I already have a JPEG or WebP and simply need to reduce its weight, Compress Image gives me an adjustable quality control and shows the byte savings before I download.
My practical test is simple:
- Open the exported file at product-page size.
- Check edges, texture, and any type or label detail.
- Compare the file weight against the source.
- Keep the lighter version only if the product still looks trustworthy.
Do not optimize away the detail that helps someone buy. Fine stitching, ingredient labels, and material texture are not decoration; they are proof.
Keep the handoff boring
The best image-prep workflow is the one no one has to think about twice. Mine is: save the original, resize for the actual placement, strip metadata from the shareable copy, convert or compress it, and give the resulting file a sensible name.
That keeps the product team moving without adding another subscription or upload destination. It also leaves a cleaner trail for the next person who has to refresh an image, build a collection page, or review a catalog export. If a product’s image work is getting messy, start with one asset this week and run it through the three steps above. Bookmark Tiny Online Tools and make the handoff repeatable before the next upload rush.