Open Graph Image Cache: Why Share Previews Don't Update

PublishedToolOpen Graph & Twitter Card Generator

Contents
  1. The problem: you changed the image, but the share preview didn't budge
  2. The fix: refresh each platform's cache, or bypass it
  3. Common sticking points
  4. The takeaway
  5. FAQ

You swap in a new image for og:image, deploy, and share the link on KakaoTalk or Facebook — and the old image still shows up. The short version: your code isn't broken. Social platforms cache the og data from the first time that URL was shared, and they keep reusing it.

This post covers why that cache exists, how to force a refresh on each platform, and how to skip the cache entirely.

Summary ① The cause isn't a code bug. The sharing platform caches the URL's og data exactly as it looked the first time it crawled the page. ② Facebook and KakaoTalk each run their own crawler and cache, so refreshing one has no effect on the other. ③ The most reliable workaround is to add a version value to the image URL, so the platform treats it as a brand-new URL.

The problem: you changed the image, but the share preview didn't budge

You point og:image at a new file and finish deploying. Then you send the link to a friend on KakaoTalk or Facebook Messenger, and the old thumbnail is still there. Plenty of people run into this.

The usual mistake is to suspect the meta tag code again. You recheck the og:image path, clear your browser cache, even redeploy — and the preview stays the same. The cause isn't your server or your code. It's on the sharing platform's side.

Platforms like KakaoTalk and Facebook crawl the head of a URL once, at the moment the link is first shared, and store the title, description, and image on their servers as a cache. When the same URL gets shared again, they don't re-crawl it. They just serve what they saved. So even if the live page's og:image changed, the preview doesn't reflect it.

The fix: refresh each platform's cache, or bypass it

Start by confirming that the deployed page's og tags actually point at the new image. Open the page in your browser and check the og:image value inside <head> with View Source (or your dev tools).

If the source already shows the new image, then code isn't the problem — the platform cache is. You have two ways to handle that.

First, Facebook offers an official sharing debugger. Put the URL into developers.facebook.com/tools/debug and run it again with "Scrape Again," and Facebook re-crawls the URL and overwrites the cache with the new image.

Second, KakaoTalk runs its own crawler and cache, separate from Facebook's. You need to submit the same URL separately through Kakao's Open Graph cache refresh tool on the Kakao Developers site. Refreshing on one platform doesn't refresh the other.

If neither works, or you need a sure result right now, the most reliable option is to append a version query string like ?v=2 to the end of the image URL. Crawlers treat the whole string, query string included, as a single URL. Change the value and they see a completely new image, so they pull the new thumbnail right away with no cache refresh needed.

Along the way, if the meta tag fundamentals are shaky — the og:image path isn't absolute (https://), the aspect ratio is off from the recommended value — the preview won't render properly no matter how many times you refresh the cache. It helps to build the tags yourself with our tool and check them there.

Open Graph & Twitter Card Generator

Free · No sign-up · Enter a title and image URL to get og and Twitter meta tags plus a share card preview instantly

Enter a title, description, page URL, and representative image URL, and the tool builds your meta tags live, setting og:image to 1200×630 automatically. From the same screen you can check a Facebook-style card, a Kakao-style card, and a Twitter (X) card preview side by side. Before you deploy, this is where you verify the tag values are what you intended.

Common sticking points

SituationCauseHow to check
You swapped the image and deployed, but the old thumbnail staysThe sharing platform cached the og data from the first crawl and reuses itResubmit the URL to each platform's cache refresh tool
The cache refresh tool runs, but nothing changesog:image is a relative path or an unreachable URL, so the crawler can't read itCompare the absolute-path (https://) tag from the tool against your actual source
It only fails to update on KakaoTalkFacebook and Kakao run separate crawlers and cachesRun Kakao's cache refresh tool separately
You get a small thumbnail card instead of a large imagetwitter:card is set to summary, not summary_large_imageSwitch the card type to the large image and regenerate the tags

The takeaway

If your share preview doesn't change after you update og:image, it's almost always the platform's stored cache, not your code. Facebook and Kakao each manage their own cache, so you have to run the refresh tool on each platform — and if that still isn't reliable, adding a version value to the image URL and making it a new URL is faster. Build the tags with the tool and compare them against your source first, and you'll immediately know whether the problem is in your code or in the cache.

Open Graph & Twitter Card Generator

Free · No sign-up · Enter a title and image URL to get og and Twitter meta tags plus a share card preview instantly

FAQ

I refreshed the Facebook cache. Why is the KakaoTalk preview still the same?

Facebook and KakaoTalk each run their own bot for crawling shared links and their own cache storage. Refreshing the cache on one platform doesn't pass along to the other, so you have to refresh the cache separately on every platform where you share the link.

Does the cache clear on its own after a while?

No platform publishes an official retention period for its cache. Rather than waiting to see when it clears, if you need the update to land now, use the platform's cache refresh tool or change the image URL itself — that's the sure route.

Is it safe to add a question mark and version value to an og:image URL?

Yes, it's safe. Crawlers read the whole string, query string included, as a single URL, so changing the value makes it a new image. Just make sure the original image file stays at the same path, or the link will break.

I want to save the og:image from another site, not my own

Sometimes you need to pull just the representative image out of an arbitrary URL and save it — to reference a competitor's card design, or to capture a broken link before it disappears. The tool in this post is for building your own meta tags. If you want the opposite — paste any URL and download the original og:image file — use the OG Image Downloader tool.

This article was adapted from our Korean original. Read the Korean original

Related articles

  1. Pinterest Image Ratio 2:3: Why Instagram Sizes Get CroppedPinterest's 2:3 ratio vs Instagram's 4:5 and 1:1: see how much padding or cropping an off-ratio image gets, and how to check the math yourself.
  2. Why Cropping a Profile Photo at High Zoom Looks BlurrySee why zooming in and cropping a profile picture lowers image quality, and how to check a photo's pixel size to predict it before you upload.
  3. Blog reading time calculation: why sites show different minutesBlog reading time is an estimate, not a measurement. See the formulas sites use, why the minutes differ, and how to check the math by hand in seconds.
  4. Shorts & Reels Safe Zone: Where Captions Get CoveredSee which UI covers your captions on YouTube Shorts, Instagram Reels, and TikTok, plus the exact safe-zone ratios and how to check before you post.
  5. Instagram Link in Bio CSS Builder: Mobile Landing Page CodeLearn the card-size formula and HTML/CSS behind a multi-link landing page for your Instagram bio, plus how to export the code without writing it.
  6. Social Media Image Compression Guide: Size Limits by PlatformWhy Instagram, YouTube, and X recompress your images, how to measure the damage, and the resolution and file size limits to check before you upload.

Related tools