I say believe here, because when I did this, it seems like I had to do it a couple of times before it “took”, but I believe this was the step that got my images displaying properly.

So the next question is, if this image data is getting cached server side, can we do anything about it, or are we hosed? Ananda’s post provides a nice tool that I believe fixes this problem. This Medium post has some nice diagrams showing these two types of caching: Cache Me Outside (oh, programmer puns). So if I am correct here, you wouldn’t expect clearing your local cache to fix this. I don’t know if this actually helped, but there’s a chance it may have, and more importantly, I think it’s nice to know how to clear you cache for a specific website, so here’s a link to a how to: How to Clear Chrome Cache for Specific Website Only (3 Steps)Īfter initially trying to clear the cache locally, I realized that besides client side caching, there is also server-side caching, and I think this is what is happening with LinkedIn preview images / the caching that Ananda Kannan is alluding to here in this post. So I googled how to clear my cache for LinkedIn specifically, so that the rest of my browser’s cache wouldn’t be affected. After I did this for my projects, I assumed that client side caching of the images would prevent me from seeing if I’d actually fixed this problem on LinkedIn.

Linkedin website link