- Turning raw supplier photos into Amazon-ready main images in one pass.
- Re-preparing an existing catalog for a second marketplace with different rules.
- Standardizing image prep so every listing goes through the same steps.
Catalog Studio Beta
Upload, set options, see the price before you run. Failed images are refunded automatically and files are deleted after 24 hours.
Sign in to run a job — your credits, history and downloads live in your account. Sign in
Drop images here
JPG, PNG or WebP · up to 20 at a time
What this will do
- 1 Clean up the background Background Cutout
- 2 Crop to the marketplace shape Smart Crop
- 3 Raise the resolution HD Upscale
- 4 Check it against the marketplace rules Product Image Audit
Settings
Estimated cost
—
Add files to see the price
Add files to see the price
0%
Failed images refunded
Deleted in 24h
Not used to train our models
Results
Getting one supplier photo ready for a marketplace is four separate jobs: clean the background, crop to the platform's shape, raise the resolution past the minimum, then check the result against the rules. Doing them one tool at a time means downloading and re-uploading between every step. Catalog Studio runs the whole path as one action: upload the photo, pick the marketplace, see every step and the total price, then start.
The pre-publish check runs last, on the finished image — not on your input, where half the findings would be things the earlier steps fix anyway. If a step fails, nothing is charged for that image and whatever finished before the failure is still yours to download.
- Steps: background cleanup → marketplace crop → upscale → pre-publish check
- You see every step and the total price before anything runs
- Failed images: fully refunded, earlier finished steps kept for download
- Price: the sum of the individual steps — no workflow surcharge
Frequently asked questions
Is the workflow cheaper than running the tools separately?
Same price — the total is exactly the sum of the steps, shown before you start. What it saves is the downloading, re-uploading, and remembering the right order in between.
What happens when a middle step fails?
The run stops, you are told exactly which step failed, nothing is charged for that image, and the output of the last successful step is still available to download. The costs already spent upstream are on us.
Why does the quality check run last instead of first?
Because it should judge the image you are about to publish. Checking the raw input would flag problems — busy background, low resolution — that the pipeline itself is about to fix.
Can I use it for several marketplaces?
Run it once per target marketplace — each run uses that platform's shape, size, and rule preset. The source photo can come straight from your asset library the second time.