Free tools Windows power users keep installed
One-click scans. No signup required.
For a general-purpose Open Graph image, use 1200 × 630 pixels (about 1.91:1). It is a practical cross-platform default, not a size mandated by the Open Graph Protocol. LinkedIn’s published link-sharing minimum is 1200 × 627 pixels, nearly the same shape. File limits and preview behavior vary by platform, so compress the image, make it publicly fetchable, and test the published page where it will be shared.
Recommended Open Graph image size
Create a 1200 × 630 px image as your default. Wix recommends this canvas, and a July 2026 guide describes it as a cross-platform default. It is approximately 1.91:1, a ratio close to LinkedIn’s published requirement. Use the same dimensions for a single image intended to work across several destinations, then inspect previews on the platforms that matter to your audience.
The Open Graph Protocol specifies metadata fields, not a universal image canvas or a single rendering rule for every social platform. Its documentation supports properties such as image width, height, type, secure URL and alt text. The dimensions below are platform guidance, not a guarantee that every feed will display the image identically.
Platform dimensions and file-size guidance
| Destination | Dimensions and ratio | File-size guidance | What the evidence establishes |
|---|---|---|---|
| General-purpose Open Graph image | 1200 × 630 px; about 1.91:1 | Check the destination’s limit; see the platform notes below | Wix recommends this canvas; a July 2026 guide describes it as a cross-platform default. |
| LinkedIn sharing module | 1200 × 627 px minimum; 1.91:1 | 5 MB maximum | LinkedIn Help publishes these requirements. Its page reported an update age of two years as of September 29, 2026, so check it again before relying on the limits. |
| Facebook-oriented guidance relayed by Wix | 1200 × 630 px recommendation; 200 × 200 px stated minimum; 600 × 315 px recommended practical minimum | 8 MB maximum | Wix relays Facebook Sharing Best Practices; this is not a direct check of Meta’s page. Wix says images below 600 × 315 appear small. |
| WhatsApp, as relayed by Wix | No separate pixel size established here | Under 300 KB for image preview display | Wix states this threshold. Because third-party guides give looser figures, use conservative compression and verify the live preview. |
| X (formerly Twitter) | Secondary guides describe a 2:1 large-card presentation and slight top/bottom cropping for 1200 × 630; another suggests 1200 × 600 | Not stated in the reviewed sources | No current exact size was verified against official X documentation. Check its current developer guidance and test the card if pixel-exact rendering matters. |
| Slack and Discord | No public numeric embed dimensions found in the reviewed guide | Not stated in the reviewed sources | Use the general default and inspect actual previews; do not treat a secondary estimate as an official specification. |
A 1200 × 630 image is six pixels taller than LinkedIn’s stated 1200 × 627 minimum and has nearly the same ratio. The published materials support it as a practical near-match, but do not establish identical rendering everywhere.
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 glitches#1 Best Overall
Prepare the image and metadata
Use an absolute, publicly reachable image URL
Set og:image to an absolute HTTPS URL, not a root-relative path such as /images/share.jpg. A preview crawler must be able to fetch both the page and the image without signing in. Avoid access controls or bot protections that block the crawler. These implementation points are described in the technical guides from OG Image Design and URLpipe.
Put the tags in the HTML returned to crawlers
Include the Open Graph tags in the HTML response for the page. A tag added only after client-side JavaScript runs may not be seen by a preview bot. If your site renders metadata dynamically, confirm that the crawler receives the completed tags in the page source.
Rank #2
Declare image dimensions and descriptive alt text
The Protocol defines structured image properties, including og:image:width and og:image:height. Set them to the actual pixel dimensions of the declared image. It also says: “If the page specifies an og:image it should specify og:image:alt.” Write alt text that describes the image’s content; do not use it as a caption or repeat the page title without describing the visual.
Example HTML
Replace the example domain, image URL and description with values for your page. This example declares a 1200 × 630 image and provides corresponding structured metadata.
Rank #3
<meta property="og:image" content="https://example.com/images/article-share.jpg">
<meta property="og:image:width" content="1200">
<meta property="og:image:height" content="630">
<meta property="og:image:alt" content="A blue map with marked walking routes through the city center">
If you publish multiple og:image values, the Protocol says the first takes precedence in a conflict. Put your preferred image first and keep its structured properties adjacent to the matching image declaration.
Compress for the strictest destination
Choose an output format and compression level that keep the image visually clear while meeting the smallest file limit among your target platforms. The guidance summarized above includes a 5 MB LinkedIn limit, an 8 MB Facebook-oriented limit relayed by Wix, and a Wix-reported under-300-KB WhatsApp threshold. If WhatsApp preview display matters, the smaller target is the practical constraint. Recheck current platform guidance because limits and preview behavior can change.
Rank #4
Do not rely on dimensions alone. A correctly sized image can still fail to appear if it is too large for a destination, inaccessible to crawlers, or served from a URL the crawler cannot retrieve. Conversely, shrinking below a platform’s useful display dimensions can make the preview look small or soft.
Publish, inspect and refresh previews
- Check the page source: verify that the published HTML contains the expected Open Graph tags and that the image URL is absolute HTTPS.
- Open the image URL without signing in: confirm it returns the intended image and is not blocked by authentication or a crawler restriction.
- Inspect a real destination preview: use Facebook’s debugger or LinkedIn’s Post Inspector where appropriate. Wix points to these tools for checking and refreshing previews.
- Refresh after a change: preview caches can preserve an old image. Use the platform’s inspector or debugger to request a refresh; where appropriate, a changed image URL can help distinguish the updated file.
- Check each important platform: Slack and Discord do not have public numeric embed dimensions established in the reviewed guide, so inspect their actual link previews rather than assuming a precise crop.
Common preview problems and fixes
The preview shows no image
- Confirm the image URL is absolute, uses HTTPS, and is accessible without a login.
- Check that the crawler is not blocked by a bot rule, firewall, or other access control.
- Make sure the metadata appears in the HTML response, rather than being inserted only after JavaScript runs.
- Use the destination’s preview inspector or debugger to refresh a cached result.
The preview displays an old image
Many preview systems cache page data. Request a refresh through the available platform inspector or debugger. If the updated image is at a new URL, use that URL in the metadata so it can be fetched as a distinct asset.
The Tool Desk
Outbyte Driver Updater FREEFix the driver behind crashes, sound loss and screen glitchesFind Drivers →Outbyte PC Repair FREERepair Windows errors before they cause bigger problemsFix Now →Best Value
- 1. Custom Nail art Tray: Show off your nails with our personalized nail art tray Photo Prop! This 4-inch disk is made of strong acrylic. It's great for anyone who loves nail art, works as a nail tech, or wants to promote their nail design. We laser engrave names and social media handles, then fill them with resin for a smooth look. Perfect for showing off your nails or promoting your nail business online.
- 2. Material: Crafted from 5mm thick, high-quality acrylic,it provides a comfortable and secure grip, making it easy to hold while displaying your nail art. The glossy, smooth acrylic surface offers a perfect backdrop for your designs.
- 3. Design: Sleek round acrylic disc with a cut-out notch for easy handling during photos.NOTE: Black will be prone to showing finger prints and dust/scratches easily.
- 4. Ideal for Social Media and Business Promotion: Consistent use of the nailfie disk builds a cohesive, professional brand image, setting you apart from the competition. Whether you're attracting new clients or showcasing your talent, the nail art display plate is essential for promoting your business online.
- 5. Perfect Gift for Nail Technicians: Personalized nail art tray disk is an ideal gift for any nail technician or artist.Whether for a friend, colleague, or even yourself, the nail art display plate is a gift that every nail professional will value and use frequently.
The image looks cropped or unexpectedly small
Check the destination’s display shape and the actual image dimensions. LinkedIn’s published minimum is 1200 × 627, while the general 1200 × 630 canvas is only three pixels shorter in width terms? Both have a near-identical 1.91:1 ratio, but platform rendering can still differ. For Facebook-oriented guidance, Wix says images below 600 × 315 appear small. Preview the page on the destination rather than treating the source image dimensions as proof of its final appearance.
The image works on one platform but not another
Platforms apply different size limits and preview rules. Check the strictest file limit relevant to the failing destination, verify that it can fetch the URL, and test with that platform’s inspector where one is available. Do not assume a behavior reported by a secondary guide is an official current requirement.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Or skip the browser setup
If you need a screenshot of a page for a workflow or an image asset, ScreenshotNeo offers a website screenshot API and MCP server. It is not a replacement for setting correct Open Graph metadata or validating a social preview; it can capture a page without you setting up a browser automation flow.
One GET request returns a screenshot in PNG, JPEG or WebP, or a PDF. For example, save a screenshot of the target page as WebP with cURL:
curl -G "https://api.screenshotneo.com/v1/shot" -d access_key=YOUR_API_KEY --data-urlencode url=https://example.com -o shot.webp
See the ScreenshotNeo documentation for the API details. Cookie banners are accepted and removed before the shot, along with known newsletter popups and chat widgets. Bot checks, blank pages, failed loads and cache hits are not billed; the response includes page-verdict and billing headers. An MCP server lets AI agents use screenshot tools, and 1,000 screenshots a month are free with no card; paid plans start at $5 for 3,000. Sign up for the free plan.
Choose dimensions by the job
- One image for broad sharing: start with 1200 × 630 px and test on the destinations your readers use.
- LinkedIn is the key destination: meet LinkedIn Help’s published 1200 × 627 px minimum and 5 MB maximum, and recheck its guidance because the help page’s reported update age is two years as of September 29, 2026.
- WhatsApp preview display is important: use Wix’s under-300-KB threshold as conservative guidance, then confirm the live result.
- Exact X, Slack or Discord rendering matters: consult current platform guidance where available and test the preview; the reviewed sources do not establish a verified numeric official size for these cases.
The image is only one part of a working preview: the tags must reach the crawler, the image must be fetchable, and the destination must be allowed to refresh or re-fetch its cached preview.
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.




