There are two ways to control the image LinkedIn shows for a website link. For a single post from a LinkedIn Page, paste the URL into the Page composer and use Edit to upload a replacement image. To set the normal preview for future shares, add Open Graph (OGP) tags—especially og:image—to the web page and make sure LinkedIn can fetch that image.
The instructions below separate those methods, explain the exact image requirements, and show what to check when LinkedIn displays an old or missing preview.
Choose the method that matches your goal
| Goal | Method | Access needed | Scope |
|---|---|---|---|
| Use a different image on one LinkedIn Page post | Page composer’s Edit control | LinkedIn Page super admin or content admin | That post only |
| Set the default image whenever people share a page URL | Open Graph metadata in the page source | Website source, CMS template, or developer | Future link previews for that page |
A Page-post upload does not rewrite your website’s metadata. Conversely, changing og:image does not retroactively replace an image already selected for a particular Page post.
Set a custom image for one LinkedIn Page post
This option is for an eligible LinkedIn Page administrator who needs a specific image immediately, without changing the website template.
Recommended Free Tools
- Open the LinkedIn Page while signed in as a super admin or content admin.
- In Start a post, paste the complete website URL. Wait a few seconds for LinkedIn to generate the link preview.
- Click Edit beneath the text box.
- Use the image control to choose the replacement file from your computer. If the headline is also wrong, choose Edit article title and enter the intended title.
- Confirm the audience setting, review the preview, and publish.
Image dimensions for a Page-post upload
LinkedIn recommends a 1.91:1 aspect ratio, commonly 1200 × 627 pixels. Its Page-post guidance says an image must be more than 200 pixels wide to appear in the large-image format; narrower artwork is shown as a thumbnail on the left. On mobile, LinkedIn does not crop the image: other aspect ratios appear in full with subtle white padding.
These dimensions describe the Page composer’s custom-image treatment. The website metadata requirements below are separate and should not be substituted for this workflow.
Set the website’s default LinkedIn preview image with Open Graph
If you own the site or can edit its CMS template, put the following tags in the target page’s <head>. LinkedIn identifies these as the key fields for website sharing:
<meta property="og:title" content="Title of the article">
<meta property="og:image" content="https://example.com/path/image.jpg">
<meta property="og:description" content="Description that will show in the preview">
<meta property="og:url" content="https://example.com/article">What each tag controls
og:title: the headline associated with the shared URL.og:image: the absolute image address LinkedIn should retrieve.og:description: the summary displayed with the link.og:url: the canonical URL represented by the share.
LinkedIn says its share box uses oEmbeds and/or Open Graph Protocol (OGP) to obtain accurate title, description, and image data. If your CMS already emits OGP tags, edit the existing values rather than adding conflicting duplicates.
Free tools Windows power users keep installed
One-click scans. No signup required.
Prepare an image that LinkedIn can use
- For website sharing, LinkedIn specifies at least 1200 × 627 pixels.
- The file must be 5 MB or smaller.
- A 1.91:1 ratio is recommended.
- The URL in
og:imagemust be reachable by LinkedIn without a login, HTTP authentication, or an access-controlled directory.
An image can meet the pixel and file-size rules yet still disappear if a firewall, robots policy, hotlink protection, or other server rule blocks LinkedIn’s retrieval request. Use a stable HTTPS URL and return the image with a normal successful response.
Verify the page before sharing
- View the published page source, not only the CMS editor, and confirm the four
og:properties are present in the HTML head. - Open the exact
og:imageURL in a private browser window. It should load without a session cookie. - Check that the URL contains no accidental spaces, line breaks, or characters introduced by a template.
- Confirm the image is at least 1200 × 627 pixels and no larger than 5 MB for the website-sharing method.
- Paste the page URL into LinkedIn’s composer and wait for the generated card before publishing.
When you change tags, LinkedIn may continue showing a previously fetched version. LinkedIn’s troubleshooting guidance says to allow up to 48 hours after the URL was shared or the metadata changed for stale preview information to update.
Common problems and precise fixes
No preview appears after pasting
Wait a few seconds for generation, then check that the URL is valid and contains no whitespace. LinkedIn specifically identifies spaces in a URL as an error cause. If the card still does not load, inspect the page source for malformed or missing OGP tags.
The title, description, or image is wrong
Compare the live page’s og:title, og:description, and og:image values with the content you expect. Check oEmbed output as well when your CMS provides it. Correct the source, then allow the stated cache period before judging the result.
The Tool Desk
Outbyte Driver Updater FREEScan for outdated or missing drivers - takes under a minuteDriver Scan →Outbyte PC Repair FREERepair Windows errors before they cause bigger problemsFix Now →Rank #3
The image meets the specifications but is absent
Test the image URL without being logged in. Remove HTTP authentication and directory permissions that prevent an external fetch. Also check CDN, firewall, bot-management, and hotlink-blocking rules for requests from LinkedIn. A protected image directory can prevent retrieval even when dimensions and file size are correct.
An old image remains after a correction
LinkedIn advises waiting 48 hours from the latest share or metadata update. During that interval, make sure the corrected tags are deployed consistently on the canonical URL and that redirects do not lead to a different page.
You need a different image immediately
If you are a Page super or content admin, use the composer’s Edit control and upload the intended image for that post. This is a post-level override; it does not change the website’s default tags.
LinkedIn cannot retrieve any preview image
The link itself can still be shared. LinkedIn states that a URL remains shareable even when it cannot retrieve a preview image, so publish the link while you repair the page metadata or image access.
Design and implementation details that prevent surprises
Keep important content inside the safe area
Although 1.91:1 is the recommended ratio, mobile presentations can include white padding rather than a crop. Put logos, faces, and text away from the extreme edges so they remain legible in both large-card and mobile layouts.
Use one canonical image per page
Templates that output several competing og:image tags can produce inconsistent results. Keep the intended image first and remove obsolete entries when changing a template.
Separate source artwork from the delivered file
Keep an editable master, then export a web-ready JPEG, PNG, or WebP within the 5 MB limit. Resizing or recompressing is acceptable as long as the delivered file still meets the website-sharing minimum dimensions.
Or skip the browser setup
ScreenshotNeo can create a clean screenshot asset from a URL that you can then host and reference in og:image. It removes cookie/consent banners, newsletter popups, and chat widgets before capture; bot checks, blank pages, failed loads, timeouts, and cache hits are not billed, and each response reports the page verdict and billing status in headers. Its MCP server provides take_screenshot, get_page_info, and capture_pdf tools for Claude, Cursor, and other MCP clients.
Windows Errors? Fix Them Before They Spread
Repair common Windows errors and clear accumulated junk for a smoother, more stable PC - no reinstall needed.Free scan · no reinstallCrashes, No Sound, or Screen Glitches?
Random freezes, missing sound and display glitches usually trace back to one bad driver. Find and replace yours safely.Free scan · under a minuteUse the API documentation at https://screenshotneo.com/docs/ for all options. Replace the example target with the page you want to represent, save the returned image, and publish it at a publicly reachable HTTPS URL before placing that URL in og:image.
cURL
curl -G "https://api.screenshotneo.com/v1/shot" -d access_key=YOUR_API_KEY --data-urlencode url=https://example.com/article -o shot.webpPython
import requests
r = requests.get("https://api.screenshotneo.com/v1/shot", params={"access_key": "YOUR_API_KEY", "url": "https://example.com/article"}, timeout=90)
r.raise_for_status()
open("shot.webp", "wb").write(r.content)Node.js
const q = new URLSearchParams({ access_key: 'YOUR_API_KEY', url: 'https://example.com/article' });
const res = await fetch(`https://api.screenshotneo.com/v1/shot?${q}`);
if (!res.ok) throw new Error(`Screenshot failed: ${res.status}`);
const image = Buffer.from(await res.arrayBuffer());
await import('node:fs/promises').then(fs => fs.writeFile('shot.webp', image));ScreenshotNeo includes every feature on every plan. The Free plan provides 1,000 shots per month with no card; paid plans start at $5 for 3,000 shots. Create a free ScreenshotNeo account to get started.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Cost, caching, and reliability considerations
- LinkedIn preview generation and cache refresh are controlled by LinkedIn, not by your web host. The documented allowance for stale data is up to 48 hours.
- Changing an image file while keeping the same URL can leave an old cached asset in circulation. A new, versioned filename is a practical way to distinguish a materially different asset, while still allowing LinkedIn’s cache window to pass.
- Do not place the image behind expiring signed URLs unless LinkedIn can fetch it during the preview request. A stable public URL is safer for social sharing.
- For Page-post overrides, check the final card before publishing. For metadata changes, validate the deployed source and image URL first, then wait for cache refresh rather than repeatedly reposting the same URL.
Quick decision checklist
- Need one special image on one Page update? Use Edit in the Page composer.
- Need the same default behavior for future shares? Set
og:imageand the other OGP tags in the page template. - Using website metadata? Deliver an image at least 1200 × 627 pixels, 5 MB or less, preferably 1.91:1.
- Image missing? Test public retrieval and remove access controls or blocking rules.
- Preview still old? Allow up to 48 hours after the last share or metadata change.
Frequently Asked Questions
Can I set a custom preview image from an ordinary personal LinkedIn profile?
The reviewed LinkedIn customization guidance describes the upload control for LinkedIn Page super admins and content admins. For a personal-profile share, use the website’s Open Graph metadata rather than assuming the Page-only control is available.
Does changing og:image alter a Page post that is already published?
No. A Page-post upload is attached to that post. Metadata changes affect subsequent link-preview retrieval and do not rewrite an image already selected for a published update.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
Can I use a protocol-relative image URL in og:image?
LinkedIn’s example uses a protocol-relative form, but an absolute HTTPS image URL is clearer and avoids ambiguity across clients.
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.
