Workflow6 min read·Updated

Open Graph Images and WebP: What Scrapers Accept

Your article can be all WebP and still use a JPEG `og:image`. That split is normal in 2026. Convert on-page images to WebP; export one 1200×630 JPEG (under 1 MB, ideally <300 KB) for cards.

Two files, two jobs

LCP images are for browsers. OG images are for Slack, iMessage, LinkedIn, X. Those crawlers have lagged on WebP. Do not sacrifice share previews to be fashionable.

Why it matters

  • Marketing cares about unfurls.
  • A 2 MB PNG OG file is still too big for some crawlers.
  • The page itself should not use that PNG as the hero.

How to do it

  1. Design 1200×630. Export JPEG quality 80 (or convert a PNG to JPEG in your editor).
  2. Convert the in-article images to WebP separately.
  3. Point og:image at the JPEG URL.

When WebP OG works

Some platforms now accept WebP. If you control the audience (internal Slack only), test a WebP card. For public PR, JPEG is still the boring, correct choice.

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

Support has changed over time. JPEG/PNG remains the safe pair.

This tool outputs WebP. For OG, export JPEG from the design tool, or use the WebP on-page only.

Keep reading

SEO6 min read

OG tags and WebP

Use JPEG or PNG for og:image if you need reliable unfurls. Use WebP for on-page images.

Read more
Workflow6 min read

WebP in email

Many email clients still prefer JPEG/PNG. When WebP works, when it fails, and how to convert campaign images anyway for the web versions.

Read more
Tutorial6 min read

picture element + WebP

Use <picture> to serve WebP with a JPEG fallback. When you still need it in 2026, and how to generate both files in one workflow.

Read more