SEO guide

Open Graph Image Not Updating? How to Refresh a Link Preview

Open Graph image not updating? Why Facebook, LinkedIn, and Slack keep the old preview, and how to refresh it with a new image URL or the right tool.

A link preview card showing an old image with a refresh arrow pointing to a new image, next to a small cache box and a new file name

You have changed the picture that a page uses when someone shares it. The tag is right, the new image is on the server, and the page source shows the new address. You paste the link into a post and the old picture, or no picture at all, appears. Nothing is wrong with your tag. The platform is showing you a copy of the page that it saved earlier, and it is not going to look at the page again until something makes it do so.

This guide explains why the old image stays, how long each platform keeps it, what it takes to make the platform read the page again, and what else can stop a new image from showing. It draws on the Open Graph protocol, on Meta's documentation for webmasters, best practices, and its crawler, on two LinkedIn Help pages, and on Slack's page about its robots, all linked at the end. It also uses the work on the Open Graph preview tool on this site.

The short answer: use a new address for the new image, ask the platform to read the page again with its own tool, and wait for the chat apps that have no tool. A changed file under the same address is the most common cause of a preview that will not update.

Why the old image stays

The pictures on a link card are not loaded from your page when the card is drawn. When a link is first shared, the platform sends a program to your page. It reads the Open Graph tags in the head, fetches the image that og:image names, and saves what it found. The protocol describes og:image as an image URL which should represent your object within the graph, and the platforms keep their own copy of the result.

Meta's documentation on its crawler says the same in plain words. The crawler, which it calls FacebookExternalHit, gathers, caches, and displays information about the website such as its title, description, and thumbnail image. After that, the card comes from the copy. A change on your server does not change the copy, and no platform checks your server each time a link is shown.

Facebook: the image is cached by its address

Meta says it in a single sentence in the table of image tags: to update an image after it has been published, use a new URL for the new image, and images are cached based on the URL and will not be updated unless the URL changes. So if you replace the file but keep the name, from Facebook's side nothing has happened. If you give the new file a new address, it is a different image, and Facebook fetches it.

The Sharing Debugger is the tool for the rest. Meta's webmaster guide says that the debugger shows which meta tags the crawler scrapes, with any errors or warnings, and that it also triggers a scrape of your page, so you can use it to update your content. The best practices page adds that the debug tool refreshes any scraped content Meta has for your website, which is useful if you need to update more often than the standard 24 hour update period.

The same page recommends that you pre-cache your images by running the URL through the Sharing Debugger, and to do this again if you update the image for a piece of content. In practice, change the image address first, then run the debugger, and then share.

LinkedIn: the Post Inspector, and only for new posts

LinkedIn has a help page on this problem, and it describes it exactly. When you post, message, or write an article with a URL, the preview may show an old image that is cached, because if you have shared the same URL before, the image might already have been stored in the cache. LinkedIn's answer is the Post Inspector: enter the URL, and confirm that the preview shows the correct content.

The page has one more sentence that is easy to miss. The changes you make only affect the preview image and information for new posts that include the URL, and the preview of any existing posts with that URL remains the same. A post that has already been published will not change when you fix the page, so do not expect to repair it, and share the link again as a new post instead.

LinkedIn's help page does not say how long it keeps a preview. Several blogs give a number, but none of them is LinkedIn, so this guide does not repeat it. The honest advice is to inspect the URL and look at the result.

Slack: about thirty minutes, and no switch

Slack describes its link robot on a page of its own. It says that the robot fetches as little of the page as it can, using HTTP Range headers, to extract meta tags about the content, and that it looks for oEmbed and Twitter Card and Open Graph tags. If the tags refer to an image, video, or audio file, it fetches that file too. It also says that responses to these requests are cached globally across the service for around 30 minutes, and that you should not see more than one request for the same URL from it more often than that.

Of the three, Slack is the one that gives a clear number for its link previews, so for Slack, waiting about half an hour is a real answer. A second robot, the image proxy, fetches and caches images posted into channels, and Slack does not say how long it keeps them. Slack also says that it does not currently honor robots.txt files, so a block there will not stop it. If you want your site blocked from embeds, or want changes to how your embeds are displayed, Slack asks you to contact it.

What this guide cannot tell you

Other apps show cards too, among them WhatsApp, Telegram, Discord, and X. This guide leaves them out of the numbers, because the documentation that this research found did not state how they cache or how to refresh them. The dependable method is the same for all of them, and it does not depend on a rule that you have to know: give the new image a new address, and share the link again.

Treat any figure that you read elsewhere for the time a platform keeps a preview as a report and not as a rule, unless it comes from the platform. Platforms change their behavior without notice. Slack gives its thirty minutes for link previews. Meta mentions a standard 24 hour update period for scraped content, but it also says that an image is cached by its URL, so that period does not promise that a changed image under the same address will appear. LinkedIn gives no period at all.

The fix that works everywhere: a new image address

Version the image. Instead of replacing og-image.png, save the new picture under a new name, such as og-image-2.png, or a name that includes a short hash of the file. Then change og:image in the page to the new address, and change any other tag that names the same picture, such as og:image:secure_url or twitter:image, so that the tags agree.

Leave og:url alone. The protocol describes it as the canonical URL of the object, used as its permanent ID in the graph, so it identifies the page and should not change when the picture does. A new address for the image is a new picture. A new address for the page would be a different object in the graph.

A query string at the end of the image address, such as a version number, also changes the address, and many people use it. Meta states that images are cached on the URL, but it does not say how it treats a changed query string, so test it in the debugger instead of assuming. A new file name is the clearer way.

Make the platform read the page again

Once the page has the new tags and the new address, ask each platform to read it. Use the Sharing Debugger for Facebook and the Post Inspector for LinkedIn, which are the platforms' own tools for this. Enter the page address, look at the tags that were found, and look at the image that is shown. If the old image is still there, the platform has not read your new tags yet, or the page that it received is not the page that you think.

Then check the result the way a viewer sees it, by sharing the link in a private post or a message to yourself. For Slack, paste the link in a private channel and wait up to half an hour if it shows the old card. Remember that posts that already exist keep their old preview, at least on LinkedIn, so test with a new post.

  • Change the image to a new address, and update every tag that names it.
  • Keep og:url the same.
  • Run the URL through the Sharing Debugger, and through the LinkedIn Post Inspector.
  • Share the link as a new post, since LinkedIn leaves existing posts as they were.
  • Wait about half an hour for Slack, and test again.
  • Look at the tags that the tool found, not only at the picture.

If the new image still does not show

Sometimes the cache is not the problem. The platform read the page again and the image is still wrong, or missing. These are the causes that are worth checking, and most of them come straight from the platforms' documentation. Each is quick to check.

  • The page that the crawler gets is old. A page cache, a plugin, or a CDN may serve the old HTML to the crawler, so check what the page returns to an outside request, not what your browser shows you.
  • The image address is not absolute. Use a full address that starts with https and names the host.
  • The crawler cannot reach the image. LinkedIn says on its help page that if the image meets the requirements but still does not appear, the website may be blocking it from pulling the image, or the image may be in a protected directory or on a protected website.
  • Your firewall or host blocks the crawler. Meta asks you to add the user agents or the IP addresses of its crawler to your allow list.
  • The page is slow. Meta says the content must be crawlable within a few seconds, or it cannot display it.
  • The tags are too far down the page. Meta says the Open Graph properties must be listed before the first 1 MB of the page, and Slack says it fetches as little of the page as it can.
  • The image is too small for the card. LinkedIn asks for at least 1200 by 627 pixels, a ratio of 1.91 to 1, and a size under 5 MB, and shows an image under 401 pixels wide as a thumbnail.
  • The type is wrong. Meta lists image/jpeg, image/gif, and image/png as the image types for the og:image tags, so an SVG is not one of them.
  • The tag is missing the size. Meta says to give og:image:width and og:image:height so that the image loads properly the first time it is shared.

A first share that is blank

Not every missing image is an old image. Meta explains that if you give the dimensions of the image in the tags, the crawler can render it immediately without having to download and process it asynchronously. Without them, the first share can be the one where the image is missing.

That is why the advice from Meta to run the address through the debugger before you share it is more than a courtesy. It makes the first public share the one that looks right.

How to avoid it the next time

Decide the image before the page is first shared. The copy that a platform keeps on the first share is the one that is kept, and every fix after that costs you a new address, a debugger run, and a new post. A page that was checked before it was published has none of those costs.

The Open Graph preview on this site reads the text of a page, which you paste, and shows every tag, with the cards of a few platforms drawn in an approximate way, so you can check the title, the description, and the image address before the page goes live. It does not look at your live page, and it cannot tell you what a platform has saved, so it is a check for the tags and not for the cache. After the page is live, use the debugger of each platform that matters to you, and use a versioned image name whenever the picture changes.

Practical checklist

  • Give a changed image a new address, and do not replace a file under the same name.
  • Update every tag that names the image, and keep og:url the same.
  • Run the page through the Sharing Debugger for Facebook and the Post Inspector for LinkedIn.
  • Share the link as a new post, because LinkedIn does not change existing previews.
  • Wait about half an hour for Slack, which caches link previews for around that long.
  • Check that the crawler receives the new HTML, and that it can reach the image.
  • Give the image an absolute address, a supported type, and the width and height in the tags.
  • Test the tags before the first share, with a preview tool and with the platform tools.

Research and references

This guide was prepared from the authoritative references below.

  1. The Open Graph protocol
  2. Meta for Developers: Guide to sharing for webmasters
  3. Meta for Developers: Sharing best practices
  4. Meta for Developers: Meta web crawlers
  5. LinkedIn Help: Use Post Inspector to refresh URL
  6. LinkedIn Help: Make your website shareable on LinkedIn
  7. Slack: Slack robots