The Tool Desk
Outbyte PC Repair FREEClear out junk files and repair common Windows errorsFree Scan →Outbyte Driver Updater FREEFix the driver behind crashes, sound loss and screen glitchesFind Drivers →To change the thumbnail that appears when a website link is shared, set that page’s Open Graph og:image tag to a publicly reachable image. Put the tag in the page’s <head>, or use your CMS or SEO plugin’s social-image field. For a single LinkedIn Page post, an administrator can replace the preview image in LinkedIn’s post composer without changing the website.
Choose the kind of change you need
There are two different controls that are often confused:
| Route | What it changes | Best use | Access required |
|---|---|---|---|
| Website Open Graph metadata | The default image platforms discover when the URL is shared | A durable, page-level change across sharing services | CMS settings, plugin settings, or website source access |
| Social post composer override | The image displayed in one particular post | A campaign, announcement, or one-off correction | Features and permissions of the target platform |
Changing a post’s preview does not necessarily alter the metadata on your site. Conversely, changing og:image may affect future shares but not a preview already cached by a platform.
Set the page’s Open Graph image
Use your CMS or SEO plugin first
- Open the editor for the exact page or post.
- Find a panel labelled Social, Open Graph, Social sharing image, or similar.
- Upload or select the image you want associated with that URL. If the panel offers both a site-wide default and a page-specific image, choose the page-specific override.
- Save or publish the page, then inspect the rendered HTML to confirm that the intended image URL is emitted.
Many WordPress SEO plugins can use the featured image as an Open Graph source and also provide a manual image-selection field. The exact labels depend on the plugin and version, so verify the generated source rather than relying only on the editor preview.
#1 Best Overall
Edit the HTML when no CMS control exists
Open Graph metadata belongs in the document head. A minimal set for a page is:
<meta property="og:title" content="Example page title">
<meta property="og:type" content="website">
<meta property="og:url" content="https://example.com/article">
<meta property="og:image" content="https://example.com/images/article-share.jpg">
<meta property="og:description" content="A concise description for link previews.">The Open Graph Protocol describes og:title, og:type, og:image, and og:url as basic properties; og:description is optional but useful. The image URL must be publicly reachable by the service fetching the page, not a path that works only inside your admin area or local network.
Add image details when appropriate
Open Graph also supports image dimensions and alternative text. Supplying accurate values can help consumers process the image:
<meta property="og:image:width" content="1200">
<meta property="og:image:height" content="627">
<meta property="og:image:alt" content="Description of the shared page image">Only publish dimensions that match the actual file. Keep the image URL stable where possible; replacing the file at the same URL is generally easier to manage than changing many metadata references.
Do these 3 things before closing this tab:
1Scan for outdated or missing drivers - takes under a minute2Clear out junk files and repair common Windows errors3Fix the driver behind crashes, sound loss and screen glitchesPick an image that survives platform requirements
Design the source image for the services where your links will appear. Avoid placing essential text at the extreme edges, because cards can be cropped differently. Use a high-quality file at the dimensions recommended by the target service, and ensure the server returns the image without authentication, an interstitial, or a bot challenge.
For LinkedIn, the help documentation recommends a 1.91:1 image such as 1200×627 pixels for a Page-post preview and specifies a minimum of 1200×627 pixels for website sharing. These are LinkedIn specifications, not universal rules for every network. Check the current requirements of each destination before standardizing one template.
Change the thumbnail for one LinkedIn Page post
LinkedIn documents a per-post workflow for Page super admins and content admins:
- Switch to the Page’s admin or content-admin view.
- Paste the website URL into Start a post.
- Choose Edit below the text box.
- Select the image icon and choose the replacement image. If available, edit the article title as well.
- Set the audience and publish.
This changes the preview attached to that LinkedIn post. It is separate from editing the page’s og:image, so update the website metadata too if future shares should use the same image.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
Verify what platforms can actually read
- Request the public page as an unauthenticated visitor and view its source, not only the CMS editor.
- Search for one, and preferably only one,
og:imagevalue in the head. Confirm that it is the intended absolute HTTPS URL. - Open the image URL directly. Check that it returns the image with a successful response and does not require cookies, a login, or JavaScript.
- Check
og:title,og:description, andog:urlfor the same page so the card is internally consistent. - Use the destination platform’s current sharing debugger or post inspector, when available, to fetch the URL again.
A browser’s visual preview is not proof that every crawler will see the same content. Server-side rendering, access rules, redirects, and cache layers can produce different results.
When the old thumbnail keeps appearing
Confirm the source before blaming a cache
Inspect the live HTML and the image URL first. Common causes are an unchanged page template, a page-level override taking precedence over the site default, multiple conflicting og:image tags, or an image URL that redirects to an old file.
Ask the platform to fetch again
Social services can cache page metadata and images aggressively. Use the relevant debugger or inspector to request a fresh fetch, then share a new test post. Cache duration and refresh behavior differ by platform; there is no universal waiting period or guaranteed instant update.
Use a new URL only as a last resort
Appending a query string or renaming the image can make a platform treat it as a new resource, but it also creates another URL to maintain. Prefer correcting the metadata and refreshing the platform cache first.
Troubleshooting checklist
- No image appears: Confirm
og:imageis in the server-rendered<head>, not inserted only after page load by client-side JavaScript. - The wrong image appears: Remove duplicate tags, check plugin precedence, and inspect redirects from the declared image URL.
- The image is rejected: Test the URL without logging in, check HTTPS and response headers, and meet the destination’s minimum dimensions.
- LinkedIn shows an older title or description: Recheck all Open Graph fields, then run LinkedIn’s current sharing inspection flow and create a fresh post.
- The CMS setting has no effect: Clear your site’s page cache and CDN cache, purge the generated HTML, and verify the final source.
- Only some platforms update: Each service fetches and caches independently. Validate the page separately on each destination.
- Images are cropped badly: Recompose for the target aspect ratio, keeping logos and text inside a safe central area.
Performance, security, and maintenance considerations
Serve the social image from a reliable HTTPS endpoint and keep its dimensions and file type appropriate for the destination. A very large source increases fetch time; excessive compression makes text illegible. Do not put private data in an image URL, because crawlers and anyone with the URL may request it. If you change a brand or article image, update the page metadata, any CMS override, and platform-specific post overrides as separate tasks.
For sites with templates, generate Open Graph values from the canonical page record so title, URL, and image cannot drift. For individual editorial pages, retain a manual override for campaigns or pages that need a custom illustration.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Or skip the browser setup
If your goal is to obtain a clean screenshot of the page itself for a preview workflow, ScreenshotNeo makes the capture a single API request. It accepts cookie or consent banners before capture and removes more than 60 known consent platforms, newsletter popups, and chat widgets; each step can be disabled. Bot checks, CAPTCHAs, blank pages, timeouts, failed loads, and cache hits are not billed, and response headers identify the page verdict and billing status. Its MCP server provides take_screenshot, get_page_info, and capture_pdf tools for Claude, Cursor, and other MCP clients.
See the ScreenshotNeo documentation for authentication and options. A basic cURL request is:
Recommended Free Tools
curl -G "https://api.screenshotneo.com/v1/shot" -d access_key=YOUR_API_KEY --data-urlencode url=https://stripe.com -o shot.webpPython:
import requests
r = requests.get("https://api.screenshotneo.com/v1/shot", params={"access_key": "YOUR_API_KEY", "url": "https://stripe.com"}, timeout=90)
open("shot.webp", "wb").write(r.content)Node.js:
const q = new URLSearchParams({ access_key: 'YOUR_API_KEY', url: 'https://stripe.com' });
const res = await fetch(`https://api.screenshotneo.com/v1/shot?${q}`);The API supports full-page captures with lazy images loaded, CSS-selector element capture, dark mode, device presets and custom viewports, retina scale, PDF output, custom CSS and JavaScript, pre-capture clicks, hidden selectors, selector/delay/network-idle waits, request and resource blocking, custom headers, cookies, user agents and authorization, timezone and geolocation, transparent backgrounds, resizing, chosen cache TTLs, signed image links, asynchronous jobs with signed webhooks, bulk capture of up to 100 URLs per call, usage reporting, and an OpenAPI specification. Parameter names used by other screenshot APIs also work, which can simplify migration.
Best Value
Every feature is included on every plan: Free provides 1,000 shots per month with no card; Starter is $5 for 3,000; Growth $15 for 15,000; Pro $39 for 60,000; Scale $99 for 250,000; and Business $249 for 1,000,000. Yearly billing gives two months free. Create a free ScreenshotNeo account to get 1,000 screenshots a month with no card.
Frequently Asked Questions
Does changing the featured image always change a link thumbnail?
No. It changes the thumbnail only when your CMS or plugin uses the featured image as its Open Graph image. Verify the rendered og:image tag.
Can I use a relative image path in og:image?
Use an absolute, publicly reachable URL such as https://example.com/image.jpg so external crawlers can request it reliably.
Free tools Windows power users keep installed
One-click scans. No signup required.
Will a new thumbnail update old social posts?
Usually not. Existing posts can retain their stored preview; update the post or use the platform’s documented editing and inspection tools.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
