Take the 2-minute tour ×


  • linter reports that specified og:image is too small. Image is 628x464.
  • linter instead picks a random image from the page which is 380x214, smaller than the og:image!

What the linter shows me:



We have been happily using 130x110 og:images without problems for the last 9 months. I noticed in the last couple of weeks that pages were no longer sharing the correct image. Using the linter it seems that Facebook recently decided og:images should be at least 200x200. So I have been replacing our og:images with larger examples but the linter still says they are too small.

Any ideas how I can fix this, or is it a Facebook problem? Thanks.

share|improve this question
I had this. Basically, it won't work (and this bug is status wontfix) if the URL results in a redirect. Also the debug tool somehow seems slow/delayed and does seem to cache some stuff. Hit the button a few times and you get different results, even without changing the site. –  artfulrobot Apr 30 '13 at 11:59

5 Answers 5

Did you change how big the image file at http://www.futuremark.com/images/facebook/futuremark-logo.png is without changing the URL specified in the og:image meta tag?

The image itself will be cached if the URL didn't change, so you need to change the URL (or add a cash-busting parameter like ?v=1 to the end)

share|improve this answer
Thanks for the reply. The URL is the same but the image is different. The image is used for many pages on the site so I didn't want to have to go and change the URL on every page. I thought the act of using the linter was supposed to clear the cache? –  James Feb 22 '13 at 9:40
Update: I tried adding ?v=1 to the image URL. Same problem, linter says og:image is too small: developers.facebook.com/tools/debug/og/… –  James Feb 22 '13 at 10:05
There's a bug report here: ( developers.facebook.com/bugs/338739036234971 ) saying that if the image URL returns a HTTP 301 redirect to a different URL that the size isn't corrected - does that sound like the issue here –  Igy Feb 22 '13 at 17:16
Yes, that could be the issue. I'll check with our developers. Thanks again for your help. –  James Feb 26 '13 at 7:13

Now I guess that Facebook does not find tags for height and width and considers them null. In my case, next tags fixed this issue:

<meta property="og:image:width" content="1280" />
<meta property="og:image:height" content="855" />
share|improve this answer

I ran into this same issue, for me the problem was with the URL defined in the og:image not matching the URL being checked

for example my og:image tag had

<meta property="og:image" content="http://www.soundfuse.co.uk/public/images/logo_300px.png"/>

And the URL I was actually checking against was


Notice the missing www. on the TLD? This caused a 301 redirect to occur from soundfuse.co.uk to www.soundfuse.co.uk, but once I matched both primary URL's up it worked as expected.

share|improve this answer

This issue is also triggered if you're enforcing no trailing slashes with .htaccess [301]. Facebook infers this slash if no og:url is present.

share|improve this answer

There is a useful workaround for this issue. If you use a URL shortener to create a new URL, the image seems to load without error.

For example, paste your Youtube URL into bitly.com's URL shortener, then paste the shortened URL into Facebook. The thumbnail image will then be displayed as intended.

share|improve this answer

Your Answer


