OG:Image could not be processed as an image. It may be corrupted or may have an invalid format.

estimated reading time: 2 min

OG:Image could not be processed as an image. It may be corrupted or may have an invalid format.

8

All of the sudden clients started having incorrect images showing for their Facebook posts. When we run the URLs through the facbook debugger, we’re receiving this error message even though valid images are used for the og:image tag. I’m seeing it happen across multiple websites.

Corrupted Image Provided og:image URL, https://faithconnector.s3.amazonaws.com/3322/images/thumbs/announcements/37488198_10155892158683924_2420206705427087360_o_10155892158673924.jpg?t=261737 could not be processed as an image. It may be corrupted or may have an invalid format.

Open Graph

Adam

Asked

Tom

Having the exact same issue over the last few weeks across multiple sites. Happy to share the OG info if that will help anyone debug

February 6 at 2:31 AM

Selected Answer

1

I noticed that I had some empty og:image:height and og:image:width tags on some of my pages. I updated those pages with values and now I’m seeing images being pulled in.

So EITHER Facebook quickly fixed something, OR they put something in place that didn’t like empty image dimensions. The few tests I’ve run seem to show images again.

February 6 at 11:34 AM

Adam

Aamir

I don’t have empty image dimensions on my client site but still its not workig.

February 9 at 11:34 PM

1

I concur. This issue has been going on way too long. Facebook developers rely on these og: images to conduct campaigns and we have ceased all advertising on the platform until this issue is resolved. Our team has run an extensive diagnostic review of all meta tags associated with Facebook and conclude that it likely an overlap from their increase in censorship of political content.

February 12 at 4:59 PM

Steven C.

2

I have the same issue.

February 12 at 6:16 PM

Wayne

2

Does Facebook ever review these posts and provide solutions????

February 12 at 10:26 PM

Leslie

2

We have exactly the same issues on our domain.

Yesterday at 1:33 AM

Richard

Richard

https://developers.facebook.com/tools/debug/?q=https%3A%2F%2Ffr.gaultmillau.com%2Fnews%2Fgault-millau-le-magazine-le-numero-2-en-kiosque

Yesterday at 2:36 AM

3

Same, for some weeks now. Tried everything, sadly didn’t work. I still got the error and looks like there’s nothing I can do : (

February 8 at 3:46 AM

Ernesto

Ernesto

https://developers.facebook.com/tools/debug/?q=https%3A%2F%2Finmobiliaria-lapalma.com%2FE787

February 8 at 3:48 AM

9

Yes, same here. It just started happening.

February 6 at 8:22 AM

Mike