TINT uses a service called Embedly to extract images from websites. For Twitter, if a Tweet does not contain an image, but contains a link, we have logic in place that will search the linked page for an image. If you’re seeing what you believe to be the wrong picture associated with a Tweet or website, it’s likely because of how Embedly is extracting the image.
To test out the Embedly Extract API click here. Simply copy and paste the desired URL and click the "Play" button.
Embedly looks at the following attributes of the page and then ranks and scores the images.
- The url of the oEmbed object (if the oEmbed type is a photo)
- The thumbnail_url of the oEmbed object (if the oEmbed type is not a photo)
- The Open Graph og:image property
- The meta image_src tag
- Any images found in the API response
- Images ranked and pulled from the body of the page
If you’re having the wrong image returned, and have you have access to modify the website, you may look at inserting a new og:image. The og:image is what is returned to TINT in the majority of cases.
If only a few posts are returning the wrong images you can simply edit the images in the TINT Editor. Simply click “Moderate” on the left-hand side of the screen, hover over the right-hand side of the post, click “Edit”, and then change the URL of the image.
Upon initial connection of a hashtag or account, you may notice that Tweets containing gifs will actually just pull in still images instead. This is currently a limitation of the Twitter API. However, once a connection has been made, if any new Tweets containing gifs populate your TINT they will properly play the gif.
If you think that TINT is displaying the wrong image for a post for reasons that are not outlined here please don’t hesitate to contact Technical Support at email@example.com.