SEO6 min read·Updated

How to Migrate a Site to WebP Without Breaking Links

A full-site WebP migration is a content operation. Convert in batches of 100, update references, 301 the old image URLs if they were indexed or embedded, and leave `og:image` as JPEG. Do not rewrite the entire media library in one untested night.

URLs are the risk

HTML pages keep their URLs. Images often change extension. Any inbound image link (newsletters, PDFs, partners) needs a redirect or a same-path replace.

Why it matters

  • Google Images URLs can 404.
  • Email archives point at old JPEGs.
  • CDNs cache the old object.

How to do it

  1. Inventory top templates. Convert those images first.
  2. Prefer replacing the file in the CMS so the HTML URL updates in one place.
  3. If the public URL must stay photo.jpg, some servers can still serve WebP via content negotiation — that is harder. Simpler: new .webp + 301.
  4. Purge CDN. Submit updated sitemaps.

Settings that work

Same visual settings as a normal convert. Migration is about process, not a special quality number.

Convert a batch in your browser. Nothing is uploaded.
Open the converter

Put it into practice

Convert your images to WebP right now, free and privately in your browser.

Open the converter

Frequently asked questions

Only if a partner requires JPEG. Otherwise redirect and delete after logs go quiet.

Old image URLs may. Redirects handle it.

Keep reading

SEO6 min read

Google Images + WebP

Google indexes WebP. Use crawlable img URLs, good alt, and do not hide images behind scripts.

Read more
SEO6 min read

Image sitemaps

If you maintain image sitemaps, list the WebP URLs you actually embed. Do not list leftover JPEGs.

Read more
Performance6 min read

Next-gen formats audit

The Lighthouse next-gen formats audit wants WebP or AVIF. Convert the listed JPEGs and PNGs in your browser.

Read more