What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
Yes. An og:image URL can point to a WebP file. The Open Graph protocol defines the value as an image URL and provides an optional og:image:type MIME property, but it does not promise that every social crawler can decode or display every image format. If a preview must work across several networks, publish a WebP candidate only with a tested JPEG or PNG fallback, then validate the actual shared URL on each destination.
What the Open Graph specification actually requires
The core Open Graph properties are og:title, og:type, og:image, and og:url. The protocol describes og:image as the image URL representing the page or object; it does not publish a complete allow-list of encodings. See the Open Graph protocol reference.
You can describe the candidate with optional structured properties:
og:image:type— the MIME type, such asimage/webp,image/jpeg, orimage/png.og:image:widthandog:image:height— the pixel dimensions.og:image:alt— meaningful alternative text.
A minimal WebP declaration therefore looks like this:
#1 Best Overall
<meta property="og:title" content="Example article">
<meta property="og:type" content="article">
<meta property="og:url" content="https://example.com/article">
<meta property="og:image" content="https://example.com/images/article.webp">
<meta property="og:image:type" content="image/webp">
<meta property="og:image:width" content="1200">
<meta property="og:image:height" content="630">
<meta property="og:image:alt" content="Illustration for the example article">The MIME declaration describes what you supplied; it cannot make a crawler with no WebP decoder accept the file. Serve the URL publicly over HTTPS, return the actual image bytes, and send a sensible response header such as Content-Type: image/webp. Avoid requiring cookies, a browser challenge, or JavaScript before the bytes are available.
Why browser WebP support does not answer the social-preview question
Web browsers commonly negotiate image formats with an Accept request header. A server can send WebP to clients that advertise support and a legacy format to others. Google’s WebP guidance states: “You’ll want to serve WebP images only to clients that can display them properly, and fall back to legacy formats for clients that can’t.” Read the Google WebP FAQ.
A social preview fetcher is a separate HTTP client. Its request headers, redirect handling, cache, maximum dimensions, and decoder may differ from a browser. Consequently, a WebP that renders perfectly in Chrome can still produce no preview on a particular network. Conversely, a crawler may support WebP even when its public upload documentation does not mention it. Treat each destination as an independent compatibility test, not as an extension of browser support.
How to provide a reliable WebP implementation
Use an absolute, stable URL
Put an absolute URL in og:image, keep it reachable without authentication, and return an image rather than an HTML error page. Check redirects and make sure the final response still has the correct content type. A cacheable URL is preferable to one that changes on every request.
Rank #2
- HTML CSS Design and Build Web Sites
- Comes with secure packaging
- It can be a gift option
Add dimensions and useful metadata
Declare the real width and height and write useful alt text. These properties help consumers understand the candidate, but they are not decoder instructions. Do not claim that image/webp guarantees acceptance.
Publish a fallback when reach matters
For several social destinations, retain a JPEG or PNG version at a second URL. Open Graph permits multiple og:image declarations; when values conflict, the protocol gives preference to the first one. Put your preferred, tested candidate first and include the fallback deliberately:
<meta property="og:image" content="https://example.com/images/article.webp">
<meta property="og:image:type" content="image/webp">
<meta property="og:image:width" content="1200">
<meta property="og:image:height" content="630">
<meta property="og:image" content="https://example.com/images/article.jpg">
<meta property="og:image:type" content="image/jpeg">
<meta property="og:image:width" content="1200">
<meta property="og:image:height" content="630">The protocol does not fully specify how every consumer chooses among an array. Some services may use only the first value, some may select another, and some may ignore unsupported candidates. If a particular network is business-critical, making JPEG or PNG the first candidate is the conservative choice; otherwise test the order you intend to deploy.
Do not use browser-only content negotiation blindly
If one image URL negotiates WebP based on Accept, verify what each crawler sends. A crawler that does not advertise WebP should receive a fallback, while a crawler that sends a broad or unusual header may receive an unexpected format. Separate, explicit URLs are easier to diagnose and cache.
Free tools Windows power users keep installed
One-click scans. No signup required.
Rank #3
What platform documentation does—and does not—tell you
LinkedIn’s current Images API documentation lists JPG, GIF, and PNG for uploaded image assets and says images must contain fewer than 36,152,320 pixels. That is an upload-API rule. It is not conclusive evidence that LinkedIn’s crawler will reject a WebP URL found in a page’s og:image metadata. Keep those two workflows separate when making a compatibility decision.
Facebook and other networks
The accessible Open Graph specification and Google’s WebP documentation do not establish a current, universal rule for every Meta preview fetch, response header, dimension, or debugger path. Online anecdotes report both successful and failed WebP previews, but they cannot prove a platform-wide policy. Avoid statements such as “Facebook always supports WebP” or “Facebook never supports WebP.” Test the exact URL and account for cache refresh behavior.
Protocol maintenance versus platform guarantees
The Open Graph protocol is maintained in a Facebook Open Source repository (repository mirror), but a protocol description is not a service-level commitment from every company that consumes the tags. The WebP format is also formally specified in IETF RFC 9649 (November 2024); standardization still does not require a social crawler to implement it.
A practical test procedure before publishing
- Inspect the HTML. Fetch the public page without logging in and confirm one or more
og:imagetags contain the intended absolute URLs. - Fetch each image directly. Check the status, redirects,
Content-Type, dimensions, and that the body begins with valid image bytes. Test from outside your office network if access controls are involved. - Test both candidates. Open the WebP and JPEG/PNG URLs independently. Confirm that resizing, transparent backgrounds, or animation have not produced an unexpected file.
- Use each network’s current preview tool. Submit the page URL, inspect the selected image, and force a refresh after changing tags. A previously cached result may persist even when your server is correct.
- Share a real post. A debugger result and a production share can use different caches or processing paths. Verify the final card on every destination that matters.
Record the date, URL, selected candidate, and any error. Recheck after changing CDN rules, image URLs, or metadata.
The Tool Desk
Outbyte PC Repair FREERepair Windows errors before they cause bigger problemsFix Now →Outbyte Driver Updater FREEFix the driver behind crashes, sound loss and screen glitchesFind Drivers →Rank #4
- Brand: Wiley
- Set of 2 Volumes
- A handy two-book set that uniquely combines related technologies Highly visual format and accessible language makes these books highly effective learning tools Perfect for beginning web designers and front-end developers
Common failure modes and fixes
| Symptom | Likely cause | Fix |
|---|---|---|
| No image or an old image | Social cache still holds the earlier response. | Use the platform’s refresh/debug function, then share the canonical URL again. Changing the asset URL is a last-resort cache break. |
| WebP works in a browser but not in a card | The crawler or its image pipeline lacks WebP decoding, or received a different response. | Place a tested JPEG/PNG fallback in the tag array; inspect crawler-facing headers and redirects. |
| Image URL returns an error | Authentication, robots/WAF rules, hotlink protection, rate limiting, or a JavaScript challenge. | Allow the relevant fetch, remove browser-only gating for the asset, and verify an unauthenticated request. |
| Preview is blank or cropped | Dimensions, aspect ratio, pixel ceiling, or unsupported features such as unusual animation. | Use a conventional social-card size, provide declared dimensions, and test a static JPEG/PNG alternative. |
| Wrong image selected | Multiple og:image values are ordered differently than expected or a consumer chooses its own candidate. |
Put the preferred candidate first, keep metadata consistent, and test the deployed order. |
| Upload API rejects WebP | The API’s accepted formats differ from metadata scraping. | Convert the upload to a documented format; do not infer the rule for og:image URLs from that API error. |
Performance, quality, and format trade-offs
WebP can reduce transfer size. Google’s FAQ summarizes an average compression advantage of about 30% over JPEG without loss of image quality, based on the study it links; that is a general summary, not a guarantee for your artwork or a social crawler. Smaller files can improve fetch time, but a failed decode gives you no preview at all. For a critical share card, successful retrieval and decoding are more important than saving a few kilobytes.
Keep the source image within the target network’s practical limits, avoid needlessly huge pixel counts, and generate a deterministic fallback from the same artwork. The LinkedIn threshold cited above is specifically for its Images API and is strictly “less than” 36,152,320 pixels; it should not be presented as a universal Open Graph limit.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Or skip the browser setup
When you need to verify what a public page actually looks like to a remote fetcher, ScreenshotNeo can capture the page through one API request. It removes cookie banners, newsletter popups, and chat widgets before the shot; bot checks, blank pages, failed loads, and cache hits are not billed, and the response identifies the page verdict and billing status in headers. Its MCP server lets Claude, Cursor, or another MCP client use take_screenshot, get_page_info, and capture_pdf.
For a quick visual check of your page after changing its Open Graph tags:
curl -G "https://api.screenshotneo.com/v1/shot" -d access_key=YOUR_API_KEY --data-urlencode url=https://example.com/article -o shot.webpSee the ScreenshotNeo documentation for the full parameter set, including device, full-page, wait, and output options. The free plan includes 1,000 shots per month with no card; paid plans start at $5 for 3,000 shots. Create a free ScreenshotNeo account.
FAQ
Does og:image:type make WebP mandatory?
No. It describes the candidate’s MIME type; the consumer still decides whether and how to decode it.
Should the JPEG fallback come before WebP?
If maximum cross-platform predictability matters, put the tested JPEG or PNG first. If WebP is your preferred candidate, put it first only after testing the destinations that matter.
Can I infer preview support from an image-upload API?
No. Upload APIs and page-metadata crawlers are different ingestion paths with different format rules.
Is WebP standardized?
Yes. WebP is described in IETF RFC 9649, published in November 2024. Standardization does not require every social service to support it.
Frequently Asked Questions
Does a CDN that negotiates WebP solve social-preview compatibility?
Not by itself. Confirm the format returned to each crawler, or use explicit WebP and JPEG/PNG URLs with a tested order.
Are animated WebP files a safe Open Graph choice?
Do not assume so. A static, conventional social-card image is easier for preview pipelines to process; test any animation on every target.
The Bottom Line
WebP is valid in an og:image URL, but compatibility belongs to each crawler, not to the protocol alone. Serve a real public image, declare accurate metadata, keep a JPEG or PNG fallback, and test the deployed page on every network where the preview matters.
Quick wins for a faster PC:
Repair Windows errors before they cause bigger problemsFix Now →Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →Clear out junk files and repair common Windows errorsFree Scan →Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
