Free tools Windows power users keep installed
One-click scans. No signup required.
To get a preview card when you share a video link, publish a public webpage for the video, add Open Graph tags to that page’s HTML <head>, and share the page URL. Uploading a video file directly to a social platform is a separate workflow: it creates a native video post, not a preview of your website.
First decide what you want people to share
There are two different ways to put a video on social media. With a webpage link, you share a URL to a page on your site. The platform fetches that page and may show a card with its title, description, and image. With a native video post, you upload the video file through the platform’s own posting flow; any thumbnail is set using that platform’s video tools.
| Decision | Webpage link preview | Native social video upload |
|---|---|---|
| What you share | A URL to your video page | A video file uploaded to the platform |
| Where the preview image comes from | Page metadata such as og:image, fetched by the platform |
The platform’s native thumbnail selection or upload controls, where available |
| Who controls the destination | You control the website page and its canonical URL | The social platform hosts the post and video experience |
| Best fit | Send people to a watch page or article on your site | Publish a video directly in a platform’s feed |
| Main checks | Metadata, stable URL, public image access, and platform-specific image guidance | Current upload limits, thumbnail options, captions, and visibility settings |
For a LinkedIn URL post, the official Help page says the preview image is taken from the site being shared. LinkedIn documents native video upload separately. X also provides a native flow for selecting and posting a video file. If you want a card that leads to your own page, configure that page and share its URL; uploading the file alone does not add metadata to your site.
Add Open Graph metadata to the video page
The Open Graph protocol defines og:title, og:type, og:image, and og:url as its basic required properties. Add them to the HTML <head> of the public page you intend people to share. A description is useful too. The protocol also supports og:video as optional metadata, but that does not guarantee that any particular platform will show an inline player.
The Tool Desk
Outbyte Driver Updater FREEScan for outdated or missing drivers - takes under a minuteDriver Scan →Outbyte PC Repair FREEClear out junk files and repair common Windows errorsFree Scan →<!doctype html>
<html lang="en">
<head>
<meta charset="utf-8">
<title>How to Make Sourdough Bread</title>
<meta property="og:title" content="How to Make Sourdough Bread">
<meta property="og:type" content="video.other">
<meta property="og:url" content="https://example.com/watch/sourdough">
<meta property="og:image" content="https://example.com/images/sourdough-preview.jpg">
<meta property="og:description" content="A step-by-step video guide to baking sourdough at home.">
</head>
<body>
<h1>How to Make Sourdough Bread</h1>
<!-- Put the video player and page content here. -->
</body>
</html>- Replace both example URLs with the real, publicly accessible page and image URLs.
- Use
og:urlfor the page’s canonical URL: the stable address you want associated with that content. - Use
og:imagefor a representative thumbnail. It is an image URL, not the video file URL. video.otheris an example value, not a promise that a platform will render a playable video card. Platform behavior varies.
Open Graph describes the metadata that identifies a page as a rich object; it does not control every platform’s card design or guarantee that a card will appear. Whether a platform uses optional og:video for inline playback must be checked against that platform’s current behavior.
Make the thumbnail fetchable and fit the platform
The platform’s crawler must be able to retrieve the image. Serve the page and thumbnail publicly, without a login, expiring authorization, or a rule that blocks the crawler from the image path. A page can load normally for you while the preview image fails because a social platform cannot fetch the asset.
LinkedIn Help lists a minimum sharing-image size of 1200 × 627 pixels, a maximum file size of 5 MB, and a recommended 1.91:1 aspect ratio for its sharing module. These are LinkedIn’s stated specifications, not universal social-media rules. The reviewed Google video-search documentation does not state a universal social-preview image size, so do not assume LinkedIn’s dimensions apply to Google or another network.
- Choose an image that remains legible when displayed as a small card; avoid placing essential text at the extreme edges.
- Check that the image URL returns the intended image, not an error page or a page that requires a session.
- Use the image guidance for the platform and placement where you plan to share. Requirements can change.
Publish, share, and check the result
- Create a stable, public watch page for the video.
- Put the Open Graph tags in that page’s HTML
<head>, using the page’s canonical URL and a public thumbnail URL. - Confirm that the page and image can be fetched without a login or blocked access.
- Share the webpage URL using the platform’s link or URL-post flow, not its native video-upload flow.
- Inspect the rendered card on the platform. If it is wrong, check the HTML the crawler can read and the image it can fetch, then correct the page and inspect the result again.
A valid page in your browser is not enough by itself: the platform must be able to fetch the page and its image. The reviewed platform documentation does not establish one preview-cache expiry time or a universal refresh interval, so there is no reliable fixed wait time to promise.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
Google video Search is a separate concern
Social link cards and video features in Google Search have different requirements. Google’s video-search guidance says Google needs to crawl the video bytes, the video URL should be stable, and structured data should include contentURL. Both the page host and the streaming host need to be able to handle crawler traffic. Meeting those recommendations does not guarantee a social preview, and Open Graph tags alone do not establish Google video-search eligibility.
If the video plays in your browser but is absent from Google video features, check that Google can retrieve the actual video bytes, that the streaming URL does not expire or change unexpectedly, and that the video host can serve crawler requests. Treat those as Google Search checks, not as a universal checklist for social cards.
Or skip the browser setup
If you need a screenshot to visually inspect the published page, ScreenshotNeo can return a screenshot from one GET request. It does not create Open Graph tags or force a social platform to display a preview; it helps you capture the page itself. See the ScreenshotNeo API documentation.
curl -G "https://api.screenshotneo.com/v1/shot" -d access_key=YOUR_API_KEY --data-urlencode url=https://example.com/watch/sourdough -o shot.webpThe service can remove cookie banners, newsletter popups, and chat widgets before capture; those steps can be turned off. Bot checks, blank pages, timeouts, failed loads, and cache hits are not billed, and the response identifies page verdict and billing status in headers. Its MCP server provides take_screenshot, get_page_info, and capture_pdf tools for AI agents using Claude, Cursor, or another MCP client. The Free plan includes 1,000 shots per month with no card; paid plans start at $5 for 3,000 shots. Sign up for 1,000 free screenshots a month, with no card required.
Upload natively when you want a platform-hosted post
For a video that should play as a post in the platform’s feed, use its native video flow and set the thumbnail there where the platform offers that control. LinkedIn documents desktop and mobile video-upload steps, a native thumbnail option, caption controls, a maximum file size of 5 GB, and a maximum duration of 15 minutes. Its Help page is listed as updated one year before the research was verified on September 29, 2026; the exact publication year is not stated there. Check LinkedIn’s current interface and rules before uploading. X’s Help page also describes selecting a video file from a computer and posting it natively; check X for its current rules and controls.
These native upload limits are not limits for a webpage link preview. Conversely, setting page metadata does not upload a video file into a social feed.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Troubleshoot a missing or incorrect preview
No image appears
Confirm that the shared page has an og:image value pointing to the intended image, then check that the exact image URL is publicly fetchable and not blocked or protected. LinkedIn specifically notes that a protected or blocked image location can prevent it from appearing.
The wrong page or content appears
Check that the tags are in the HTML <head> of the page you actually shared and that og:url identifies the intended canonical page. Make sure you are sharing that URL rather than a different redirect, duplicate, or native post.
Do these 3 things before closing this tab:
1Fix the driver behind crashes, sound loss and screen glitches2Clear out junk files and repair common Windows errors3Scan for outdated or missing drivers - takes under a minuteThe video does not appear in Google video features
Check Google’s video-specific requirements separately: crawler access to the video bytes, a stable video URL, structured data with contentURL, and adequate crawler access at both the page and streaming hosts.
Best Value
The video went out as a file, not a website card
You used the native upload flow. To send users to your website, publish and share the watch-page URL through the platform’s link-post flow.
A metadata change is not visible yet
Inspect what the platform currently renders after you update the page. There is no fixed refresh interval established by the reviewed documentation; avoid assuming a particular cache lifetime.
Sources and changing specifications
The Open Graph Protocol defines the page metadata properties; LinkedIn Help describes its URL preview image and native video options; Google Search Central documents Google’s separate video requirements; and X Help documents native video posting. Platform interfaces, limits, and crawler behavior can change, so confirm the relevant platform’s current requirements when publishing.
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.
