If a social link preview shows a tiny image, first check the exact image URL in the page’s <head>, confirm the image’s real pixel dimensions, and see whether an earlier og:image tag is taking priority. A practical wide-image target is 1200 × 630 pixels; for LinkedIn, its guidance specifies a minimum of 1200 × 627 pixels, a recommended 1.91:1 ratio, and a 5 MB maximum. After updating the page or image, inspect the preview with the relevant platform’s debugger.
Why an Open Graph image can look too small
An Open Graph preview uses metadata in the page’s HTML to identify the image. The protocol defines og:image as a basic required property: its value is a URL for the image representing the page. A preview may be small because the file itself has too few pixels, the page points to the wrong asset, or the platform is selecting a different image than expected.
As an Amazon Associate I earn from qualifying purchases.
Dimensions are not the only possible cause. LinkedIn notes that an image may fail to appear if its crawler cannot retrieve the page or if the image is in a protected directory or site. A stale preview is also something to check after changes, rather than proof that dimensions are wrong.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
Check the image dimensions against the platform
There is no single size guarantee for every social service. Use the requirements for the platform where the preview looks wrong, and treat the broader 1200 × 630 target as a practical starting point for a wide card.
#1 Best Overall
- HTML CSS Design and Build Web Sites
- Comes with secure packaging
- It can be a gift option
| Platform or source | Published guidance | How to apply it |
|---|---|---|
| Facebook guidance summarized by Wix | Wix recommends 1200 × 630 pixels at a 1.91:1 ratio, reports a 200 × 200 pixel minimum, and says images below 600 × 315 pixels appear as small previews. | Use 1200 × 630 as a practical wide-image target. These figures are Wix’s summary of Facebook Sharing Best Practices, not a direct Meta source. |
| LinkedIn sharing module | Minimum 1200 × 627 pixels; recommended 1.91:1 ratio; maximum file size 5 MB. LinkedIn says images under 401 pixels wide display as thumbnails. | For LinkedIn, meet its stated minimum and file-size limit; do not assume a smaller image will render as a large preview. |
These are technical recommendations and thresholds, not a guarantee that each platform will render the same image identically. If you publish for several services, a 1200 × 630 landscape image is close to the recommended wide ratio, but check each target platform’s current guidance when requirements matter.
Fix the metadata and asset in order
- Inspect the delivered HTML. View the page source or fetch the HTML that a crawler receives, then find the
<head>and confirm there is anog:imagetag pointing to the intended image URL. - Open the exact image URL and check its pixel dimensions. Do not rely on how large it looks in your CMS or on a desktop screen. For LinkedIn, check the 1200 × 627 minimum, 1.91:1 recommended ratio, and 5 MB maximum against LinkedIn’s guidance.
- Look for duplicate image tags. If the page declares several
og:imagevalues, inspect their order and URLs. The Open Graph protocol says the first value takes preference in conflicts, so put the intended asset first. - Update the metadata for the chosen asset. Alongside
og:image, provide accurateog:image:widthandog:image:heightvalues. The protocol recommendsog:image:altwhenog:imageis specified. These describe the asset; they do not make an undersized file larger. - Make sure the crawler can fetch it. Confirm the image URL is publicly accessible and not behind authentication, access controls, or a site-level restriction that blocks the platform’s crawler.
- Recheck the platform’s parsed preview. Use the relevant debugger or inspector after the HTML and image have been updated so you can see what that service fetched.
Validate what the platform sees
The Open Graph protocol site identifies Facebook’s Object Debugger as its official parser and debugger. Wix also recommends Facebook’s debugger after image updates. For LinkedIn, use its Post Inspector. A preview inspector can reveal whether the crawler sees the new metadata and image URL, rather than merely confirming what is in your local source file.
If the inspector still reports the old image, revisit the delivered HTML, duplicate tags, exact asset URL, and crawler access before assuming the platform has accepted the change. The available guidance does not establish one universal refresh delay or a cause for every stale preview.
Troubleshooting common cases
- The file is below the relevant dimensions: export a larger image at the platform’s recommended wide ratio, replace the asset, and update the metadata URL if the filename changes.
- The source looks correct but the wrong image appears: inspect all
og:imageentries in document order; make the preferred image first and remove obsolete duplicates if they are no longer needed. - The image dimensions are adequate but no image appears: check whether the platform crawler can retrieve both the page and image. LinkedIn specifically flags crawler blocking and protected image locations as potential barriers.
- The platform shows an old preview after a change: run the updated URL through the platform’s debugger or inspector and verify the fetched HTML and asset URL. Do not treat the old card alone as evidence that the new file is too small.
- The metadata includes width and height but the preview remains tiny: confirm the underlying file’s actual dimensions. Structured metadata describes the image; it does not enlarge or replace the file.
Or skip the browser setup
You can inspect the page with a screenshot without setting up a browser automation stack. ScreenshotNeo is a website screenshot API and MCP server; its request accepts a URL and returns an image or PDF. For example, this cURL request saves a WebP capture of the page:
Rank #3
curl -G "https://api.screenshotneo.com/v1/shot" -d access_key=YOUR_API_KEY --data-urlencode url=https://stripe.com -o shot.webpReplace the target URL with the page you are checking. See the ScreenshotNeo API documentation for request options. ScreenshotNeo removes cookie banners, newsletter popups, and chat widgets before a shot; bot checks, blank pages, and failed loads are never billed. Its MCP server lets AI agents take screenshots, and 1,000 screenshots a month are free with no card; paid plans start at $5 for 3,000. Sign up for ScreenshotNeo’s free plan.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Frequently Asked Questions
Which Open Graph tag identifies the preview image?
Use og:image with the URL of the image that should represent the page.
Does adding og:image:width and og:image:height enlarge the image?
No. Those structured properties describe the asset; the image file itself must have suitable pixel dimensions.
Do these 3 things before closing this tab:
1Clear out junk files and repair common Windows errors2Scan for outdated or missing drivers - takes under a minute3Repair Windows errors before they cause bigger problemsQuick Recap
Rank #4
- Brand: Wiley
- Set of 2 Volumes
- A handy two-book set that uniquely combines related technologies Highly visual format and accessible language makes these books highly effective learning tools Perfect for beginning web designers and front-end developers
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.
