You replaced the image on your server. Your browser shows the new version. The README, the email sitting in your inbox, the Slack message and the LinkedIn preview all still show the old one, and a hard refresh changes nothing.
Your browser was never involved. When an image appears inside someone else's product, the reader almost never asks your server for it. A proxy run by Google, Apple, GitHub, Slack or Meta fetches it once and hands its copy to everyone who looks. The proxy decides when to ask you again, and several of them never read your Cache-Control header.
We first published this on the HTML to Image blog as Why your image won't update: how Gmail, Apple Mail, GitHub and Slack cache images . This is the same guide: the per-platform cheat sheet, the header measurements and the two URL patterns that fix it.
Two minutes or thirty days
The spread is what catches people out.
The blue bars are clocks somebody chose.…