Tabaix / workflow guide
A practical workflow for consistent product-photo dimensions, honest compression, SKU filenames and visual checks before upload.
Start with a master, then work on a copy
Keep the largest useful original outside your upload folder. A store-ready image is a delivery asset, not a replacement for the master. Separate the product, variant and view in your naming plan before processing a batch. For example, a SKU may have a front photograph and a detail photograph; those should not collapse into one output filename.
Choose framing before choosing quality
Suppose your source is 2400 × 1600 pixels and your layout needs a 1200 × 1200 square. Contain scales the full photograph to 1200 × 800 and leaves padding. Cover fills the square but crops the left and right edges. Stretch fills it by changing the proportions. Choose deliberately: a cropped product label and a stretched shoe are both problems even when the output has the right dimensions. Inspect one representative photograph before applying the same operation to other items.
Compress against a real destination
Resize first when the current dimensions are unnecessary; then compare JPG or WebP quality. A small file that hides product detail is not a good outcome. If an upload form requires 200 KB, check its unit and inspect the downloaded file size. The compressor treats KB as 1000 bytes. A target-size attempt can fail on a difficult image, so read the result instead of assuming that selecting a limit guarantees it. Fine print, jewellery edges and textured fabric deserve close inspection.
Pick the output format for the asset
JPG suits opaque photographs, while PNG or a compatible WebP workflow can preserve transparency. Converting a transparent logo to JPG needs a background colour. Changing the extension alone does not convert the encoding. Test the actual destination with the output before converting an entire catalogue. HEIC conversion is useful for supported phone still photos, but the converter does not preserve metadata or recreate a Live Photo.
Name files without breaking SKU data
Export a filename and sku mapping as UTF-8 CSV. Preserve a SKU such as 00124 as text in the spreadsheet so the leading zeros survive. Confirm that each input filename has a mapping and that output names are unique. Renaming changes the name, not the image quality. Download the mapping report with the ZIP so you can trace each delivery image back to its source.
Finish with a visual and catalogue check
Compare at normal display size and at full resolution. Check crop, orientation, transparent edges, filename, variant match and file size. Open the image on the store after uploading: the platform may transform it again. This workflow improves asset preparation; it does not promise a particular speed score or search ranking. Use original screenshots and measurements from your own store when documenting results.
Tools for this workflow
Putting this workflow into practice
A workflow only saves time when it becomes a habit: keep an unchanged source, work on a copy, check the result where it will actually be used, and write down the settings that worked so the next batch takes minutes instead of guesswork. The Tabaix image tools used in this guide run in your browser, so the same steps work wherever you are — no uploads and no sign-up.
Does the tool upload my images to a server?
No. The tools run in your browser, so your files stay on your device while they are processed.
Will processing reduce the quality of my photos?
Some operations change the file by design — for example compression trades a small amount of detail for a much smaller file. Compare the output with the source at normal viewing size before using it.
Continue with the image tools, or browse all 100 free browser tools on Tabaix.
