I had read that images associated with a given URL in the Facebook open graph had to be greater than 50 x 50
However, when we ran the Facebook Object debugger - we g
From your post it seems you want to share the post using the OG concept to facebook.For this the minimum size of the image should be 200px(x)200px. This is a standard dimension by FB and if there is no specific size image is available it will take next image in your page which has the same dimension.
Minimum Image Size The minimum image size is 200 x 200 pixels. If you try to use an image smaller than this you will see an error in the URL Debugger.Please check with this Link>>
Today I had a much clearer answer to this question (from the Open Graph debugger tool):
Small og:image: All the images referenced by og:image should be at least 200px in both dimensions, with 1500x1500 preferred. (Maximum image size is 5MB.) Please check all the images with tag og:image in the given url and ensure that it meets the recommended specification.
og:image should be larger: Provided og:image is not big enough. Please use an image that's at least 200x200 and preferably 1500x1500. (Maximum image size is 5MB.) Image ... will be used instead.
So, YES, you have to convert your open graph images to at least 200x200 pixels, and it seems that the larger, the better.
If your image is smaller than 200x200, Facebook will try to use a larger image (if) available on the page.
The same information returned by the debugger can be found on the open graph documentation, on "Maximizing Distribution for Media Content" topic, item 3: tags
Looks to be a bug in the specification. A work-around solution is to make your images 200px but clip what you do not want to see, or shrink them if you have large enough originals. For example, if your image is 25x25 pixels you can add 175px to both dimensions and then nest that image inside of a div that has an overflow:hidden css property and width/height of 25x25. Not the cleanest, but it would work.
I've opened a bug ticket with Facebook to address the question of poor documentation and uncover if this is an actual spec or bug. http://developers.facebook.com/bugs/210269722417284