Should I refresh on a schedule?

No. Update on triggers. A clean, accurate, compliant image does not stop working because it is two years old.

What is the strongest trigger?

The product changing. Once the image no longer represents what ships, it is a correctness problem rather than a styling one.

What about marketplace rule changes?

They are a real trigger, and they can put a whole catalogue out of compliance overnight when a minimum changes.

How do I know if imagery is underperforming?

Analytics and return reasons. Both point at a specific unanswered question, which is usually one added image rather than a reshoot.

Can I update only some products?

You can, but match the existing recipe. A partial refresh in a different style leaves a grid looking worse than before.

Does a rebrand require new imagery?

Often, since a new site design can make an older catalogue look inconsistent even when each image is individually fine.

Is old imagery a ranking problem?

Age itself is not the issue. Compliance, resolution and whether the image answers buyer questions are what matter.

Is the free generation really free?

Yes. One per day, watermarked and capped at 1024px. Signing up gives you 20 credits and clean full-resolution files with full commercial rights.

How Often Should You Update Product Photos?

On a trigger, not on a schedule.

One free generation a day. No account, no card.

How it works

1. Check what actually changed
A changed product or channel requirement is a real trigger; the calendar is not.
2. Regenerate only what needs it
Consistency matters, so match the existing recipe rather than starting fresh.
3. Generate and download
One free watermarked result. Sign up for the clean, full-resolution file.

Why this is worth getting right

Refreshing product imagery on a schedule is a way to spend money without a reason, and the better rule is to update when something specific has changed. Five triggers genuinely warrant it. The first and most important is that the product itself changed — a revised colourway, new packaging, a construction change — because at that point the existing image is no longer an accurate representation of what ships, which is a correctness problem rather than an aesthetic one. The second is a channel requirement changing, such as a marketplace raising its minimum resolution or altering its background rules, which can put an entire catalogue out of compliance overnight. The third is a diagnosed conversion problem, where analytics or return reasons point at a specific unanswered question and the fix is an added image rather than a wholesale reshoot. The fourth is a brand or design change that makes the old catalogue look inconsistent with the new site. The fifth is inherited inconsistency, where a catalogue grew product by product and the accumulated drift in backgrounds and framing now makes the store look unfinished. What does not warrant a refresh is age alone. A clean, accurate, compliant image that answers the buyer questions does not become less effective because it is two years old, and replacing it consumes budget that would do more work elsewhere. Consistency is the constraint on any partial refresh, since updating some products leaves a grid that looks worse than before.

Tips that actually help

Update when the product itself changed, since an image that no longer matches what ships is a correctness problem.
Watch for channel requirement changes, which can put a whole catalogue out of compliance without warning.
Let analytics and return reasons drive targeted additions rather than reshooting everything.
Match the existing recipe on a partial refresh, because updating some products leaves a worse-looking grid than before.
Do not refresh on age alone, as an accurate compliant image that answers buyer questions does not expire.

Who uses this

Packaging changes: Where the shipped product no longer matches the listing image.
Marketplace rule changes: Compliance shifts that can affect an entire catalogue at once.
Rebrands: Where a new site design makes the existing catalogue look inconsistent.
Legacy catalogue drift: Stores that accumulated inconsistency product by product over years.

Najczęstsze pytania

Should I refresh on a schedule?: No. Update on triggers. A clean, accurate, compliant image does not stop working because it is two years old.
What is the strongest trigger?: The product changing. Once the image no longer represents what ships, it is a correctness problem rather than a styling one.
What about marketplace rule changes?: They are a real trigger, and they can put a whole catalogue out of compliance overnight when a minimum changes.
How do I know if imagery is underperforming?: Analytics and return reasons. Both point at a specific unanswered question, which is usually one added image rather than a reshoot.
Can I update only some products?: You can, but match the existing recipe. A partial refresh in a different style leaves a grid looking worse than before.
Does a rebrand require new imagery?: Often, since a new site design can make an older catalogue look inconsistent even when each image is individually fine.
Is old imagery a ranking problem?: Age itself is not the issue. Compliance, resolution and whether the image answers buyer questions are what matter.
Is the free generation really free?: Yes. One per day, watermarked and capped at 1024px. Signing up gives you 20 credits and clean full-resolution files with full commercial rights.

Related tools

Open the full studio →

Want more than one a day?

A free account gives you 20 credits, clean full-resolution files and full commercial rights. No card needed.

Zacznij za darmo