Recommended Free Tools
To test an Open Graph image, check the page’s served HTML for the intended og:image URL, confirm that image is publicly retrievable and meets the destination’s requirements, then use that platform’s preview or inspector to see what it actually fetched. For LinkedIn, use Post Inspector; checking the tags alone cannot tell you whether LinkedIn can retrieve the image or is showing cached data.
What an Open Graph image test needs to prove
There are three separate checks: the page declares the right image, the image can be fetched by the destination platform, and the platform’s own preview displays the expected result. Passing one check does not guarantee passing the next. A correct og:image tag may point to an image that is blocked, protected, or unsuitable for the platform; a valid and accessible image may still not appear immediately if the platform has cached an earlier preview.
The Open Graph Protocol identifies og:title, og:type, og:image, and og:url as its four required properties. The protocol also permits structured image properties, including a MIME type, dimensions, a secure URL, and alt text. See the Open Graph Protocol specification for the property definitions.
Use the platform’s own inspection workflow for the final check. This article gives LinkedIn as the operational example because its published image requirements and cache-refresh steps are documented. Do not assume LinkedIn’s dimensions or file-size limit apply to other social platforms.
Quick wins for a faster PC:
Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →Clear out junk files and repair common Windows errorsFree Scan →#1 Best Overall
Test the page’s Open Graph tags
Inspect the HTML the page actually serves
- Open the public page in a browser and view its page source, or request the page HTML with a browser developer tool or HTTP client.
- Search the document’s
<head>forog:title,og:type,og:image, andog:url. - Check that
og:imageis the URL of the intended image, not a page URL, an outdated asset, or an unintended default image. - Check that the title and canonical page URL match the content you intend people to share. Confirm that the image belongs to this page and not another page’s metadata.
A representative set of tags looks like this; replace the example values with the actual page and image:
<meta property="og:title" content="Example page title">
<meta property="og:type" content="website">
<meta property="og:url" content="https://example.com/page">
<meta property="og:image" content="https://example.com/images/share.jpg">
<meta property="og:image:type" content="image/jpeg">
<meta property="og:image:width" content="1200">
<meta property="og:image:height" content="627">
<meta property="og:image:alt" content="A concise description of the image">The example includes optional image properties as well as the four required Open Graph properties. The values in your page must describe its actual image; declaring dimensions or a MIME type does not resize or convert the image file.
Check the served version, not only your CMS settings
A CMS or SEO plugin may show one value in its editing screen while the public page serves something else. Inspect the HTML returned for the page URL you intend to share. If a page varies by locale, device, or URL, check the exact public URL that will be shared. If the metadata is injected by client-side JavaScript, verify that the destination platform receives it in the form it can parse; the platform’s inspector is the practical confirmation.
Check the image URL and LinkedIn’s requirements
Open the exact URL found in og:image. Confirm that it loads the intended image without requiring a login, a special browser session, or access to a protected location. A successful load in your own browser does not prove that LinkedIn can retrieve it. LinkedIn says image retrieval can be blocked by a website or by a protected directory or website; its guidance is at Make your website shareable on LinkedIn.
The Tool Desk
Outbyte PC Repair FREERepair Windows errors before they cause bigger problemsFix Now →Outbyte Driver Updater FREEFix the driver behind crashes, sound loss and screen glitchesFind Drivers →| LinkedIn sharing-module check | Published specification | What to verify |
|---|---|---|
| Maximum file size | 5 MB | The image file is no larger than the stated maximum. |
| Minimum dimensions | 1200 × 627 pixels | The actual image dimensions meet the minimum. |
| Recommended aspect ratio | 1.91:1 | The image is close to the recommended landscape ratio. |
These are LinkedIn sharing-module specifications, not universal requirements for social previews. LinkedIn Help’s page was last updated two years before 2026-09-29; consult LinkedIn’s current guidance when exact compliance matters. File dimensions and ratio are distinct checks: an image can have enough pixels but still use a different composition, or have the recommended ratio but be too small.
- Check the image file itself rather than relying only on numbers in metadata.
- Make sure the image is publicly reachable by the platform and is not served only to signed-in users or visitors with a special cookie.
- Confirm that the image URL returns the image you expect, rather than an error page or an unexpected redirect destination.
- Keep important text and subjects within the image area; a platform preview may crop or display the image differently from a full-size browser view.
Use LinkedIn Post Inspector to see the fetched preview
- Open LinkedIn’s Post Inspector guidance and enter the page URL you plan to share.
- Review the preview LinkedIn returns. Confirm that the title and image are the intended ones, not merely that the page source contains an
og:imagetag. - If the preview is wrong, compare the URL and image shown in the inspector with the page’s served metadata and the image URL you checked directly.
- After correcting the page or image, inspect the URL again and use the refreshed preview for a future post.
The inspector answers a different question from viewing source: it shows what LinkedIn has picked up for its preview workflow. LinkedIn’s instructions describe Post Inspector as the way to refresh the preview used by new posts. It does not change the preview on posts that already exist.
Allow for caching after changes
If you have corrected an image or updated tags but LinkedIn still shows the old preview, the change may not be visible immediately. LinkedIn’s troubleshooting guidance says to allow 48 hours after a URL was shared or its tags were updated; that page was last updated three years before 2026-09-29. See Troubleshooting issues sharing URLs. Run the URL through Post Inspector to refresh the preview used for new posts. Existing posts keep their old preview, so refreshing the inspector is not a way to rewrite an already-published post.
When debugging a stale preview, work in this order: confirm that the current public HTML now contains the corrected value, confirm that the corrected image URL loads, then inspect the page URL again. Otherwise, it is easy to mistake an unchanged page response for a cache problem. If the inspected preview is correct but an old post remains unchanged, the old post’s behavior is consistent with LinkedIn’s stated limitation.
Free tools Windows power users keep installed
One-click scans. No signup required.
Best Value
Or skip the browser setup: capture the page with ScreenshotNeo
A screenshot can help you check how a page looks in a browser, but it does not replace checking its Open Graph tags or LinkedIn’s fetched preview. For those checks, use page source and Post Inspector. If you also want a clean visual capture of the page, ScreenshotNeo offers a one-request website screenshot API and an MCP server for AI agents. Its clean-shot options accept consent banners and remove more than 60 known consent platforms, newsletter popups, and chat widgets before capture; each step can be turned off. Bot checks, blank pages, failed loads, timeouts, and cache hits are not billed, and response headers identify the page verdict and billing status.
Use your own API key and substitute the page URL you want to capture. This cURL request saves a WebP screenshot:
curl -G "https://api.screenshotneo.com/v1/shot" -d access_key=YOUR_API_KEY --data-urlencode url=https://example.com/page -o shot.webpFor the supported parameters and response details, see the ScreenshotNeo API documentation. The service also has an MCP server with take_screenshot, get_page_info, and capture_pdf tools for Claude, Cursor, and other MCP clients. The free plan includes 1,000 shots per month without a card; paid plans start at $5 for 3,000 shots.
Sign up for ScreenshotNeo’s free plan: 1,000 screenshots a month, no card required.
Troubleshoot common Open Graph image failures
| What you see | Likely check | What to do |
|---|---|---|
| The preview shows the wrong image | The served og:image may still point to an old or default image, or the platform may have an older preview. |
Inspect the public HTML, verify the image URL, and then use Post Inspector to refresh the preview for future posts. |
| No image appears | The image may be inaccessible to LinkedIn, or hosted in a protected directory or website. | Make the intended image publicly retrievable and inspect the URL again in Post Inspector. |
| The image URL opens for you but fails in the preview | Your browser may have access that the platform’s crawler does not. | Check for access controls or other restrictions on retrieval; LinkedIn explicitly identifies blocked retrieval and protected locations as possible causes. |
| The new image appears in the inspector but not on an existing post | LinkedIn says refreshed preview data applies to future posts; existing posts keep their old preview. | Use the refreshed preview when creating a new post. Do not expect the inspector to alter the existing post. |
| The old image remains after updating tags | The change may not have propagated to LinkedIn’s preview yet. | Check the current HTML and image first, then allow for LinkedIn’s stated 48-hour window and inspect the URL again. |
| The image is rejected or not displayed as expected | It may exceed LinkedIn’s file-size maximum or fall below its minimum dimensions. | Check the actual file against LinkedIn’s 5 MB maximum and 1200 × 627 pixel minimum; treat the 1.91:1 ratio as LinkedIn’s recommendation. |
Testing a different social platform
The same diagnostic sequence is useful in principle: inspect the page metadata, verify the image URL is retrievable, compare the image with that destination’s own current specifications, and use its preview or inspector. But LinkedIn’s 5 MB limit, dimensions, ratio, and Post Inspector workflow should not be presented as requirements or tooling for Facebook, X, or any other destination. Check the destination’s official documentation for its current rules before adapting the image.
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.
