The Tool Desk
Outbyte Driver Updater FREEFix the driver behind crashes, sound loss and screen glitchesFind Drivers →Outbyte PC Repair FREEClear out junk files and repair common Windows errorsFree Scan →For a practical Open Graph image size, start with 1200 × 630 pixels—about a 1.91:1 aspect ratio. It is a useful general-purpose canvas, not a universal rule enforced by the Open Graph protocol. Platforms may crop the image, display it differently, or enforce their own file-size limits, so keep important content away from the edges and check the share preview where the image will appear.
Why 1200 × 630 pixels is a useful default
The Open Graph Protocol specifies metadata that describes a page, including the og:image URL. It does not require one universal pixel size. The image dimensions that work well depend in part on the service reading that metadata and how that service renders a preview.
A 1200 × 630 pixel canvas has an aspect ratio of approximately 1.91:1. That makes it a practical starting point for a general-purpose share image and brings it close to LinkedIn’s published sharing-module guidance. Treat it as a baseline to design and test—not a guarantee that every network will show the entire image without cropping.
Keep the title, logo, and any other essential details within a central safe area rather than touching the edges. A platform that crops the image can trim material near the perimeter. There is no single safe-margin measurement established for every platform, so preview the actual image on the services that matter to your audience.
Free tools Windows power users keep installed
One-click scans. No signup required.
Image dimensions and limits by platform
These figures distinguish platform-published guidance from a secondary cross-platform compilation. Confirm live requirements before a launch where a specific platform’s rendering is critical.
| Platform or layer | Image guidance | What to keep in mind |
|---|---|---|
| General Open Graph canvas | 1200 × 630 pixels; approximately 1.91:1. | A practical cross-platform starting point, not a dimension required by the protocol. The September 2026 cross-platform guide is secondary reporting. |
| LinkedIn sharing module | Minimum 1200 × 627 pixels; recommended aspect ratio 1.91:1; maximum file size 5 MB. Images narrower than 401 pixels display as thumbnails. | These are LinkedIn’s published help-page requirements. The page says it was last updated two years ago, so verify its current guidance before relying on it for a high-stakes launch. |
| X large-image card | A secondary guide describes a 2:1 card ratio and a slight crop when using 1200 × 630. | This is not an official specification in the cited guide. Check current X documentation where available and preview the image. |
| A secondary guide reports a file-size limit under 600 KB. | Optimize the file and test it in a share preview; treat the figure as secondary reporting, not a confirmed current official limit. | |
| Slack and Discord | The secondary guide says exact image dimensions are not publicly documented. | Do not assume a precise official size. Use the general canvas as a starting point and test the result in each service. |
The comparison is useful because image fit involves more than pixel dimensions: aspect ratio affects cropping, and file-size caps can affect whether an image is accepted or how reliably it loads. A secondary roundup can help identify what to test, but it is not a substitute for a platform’s own current documentation.
Open Graph metadata to set with the image
Providing a correctly sized image is only part of setting up a share preview. The Open Graph Protocol lists og:title, og:type, og:image, and og:url as required properties. Its structured image properties include width, height, MIME type, a secure URL, and alternative text. When a page specifies og:image, the protocol says it should also specify og:image:alt.
Add the metadata to the page’s HTML head and replace the example values with information for that specific page. The image URL should point to the image you want a service to use; the dimensions should describe the actual image file.
<meta property="og:title" content="Page title">
<meta property="og:type" content="article">
<meta property="og:url" content="https://example.com/page">
<meta property="og:image" content="https://example.com/images/share-card.jpg">
<meta property="og:image:width" content="1200">
<meta property="og:image:height" content="630">
<meta property="og:image:alt" content="Description of the share image">Use a concise, meaningful description for og:image:alt rather than treating it as a second headline. The title and image should describe the same page, and the URL should identify the page being shared. The protocol also documents og:image:type and og:image:secure_url as optional structured image properties when those details are relevant.
Design the image to survive different previews
Prioritize the central content
Design to the full 1200 × 630 canvas, but avoid placing essential words, faces, or logos flush to its border. The exact crop can vary by consuming platform, and the available evidence does not establish one universal crop or safe-zone size. A clean background and a focused subject make it easier to preserve meaning if some peripheral area is trimmed.
Keep the file suitable for its destinations
There is no single file-size cap established across the listed services. LinkedIn’s published help guidance gives a 5 MB maximum; the September 2026 secondary guide reports under 600 KB for WhatsApp. If you need to serve several platforms, balance visual quality against the strictest limit relevant to your audience and verify that the final image still looks clear at preview size.
Do not mistake metadata for a rendering guarantee
Correct metadata makes the intended image discoverable to services that read the page, but it does not force those services to select or display it identically. A service may crop the image, use a different card layout, or fail to reflect a recent change immediately. The practical test is the preview on the target service, not only the values in your HTML.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
A practical implementation and preview workflow
- Create the image: Export a 1200 × 630 pixel image as your starting canvas. Keep important details away from the edges.
- Publish it at the intended URL: Confirm that the image URL in the metadata points to the correct published file.
- Add page-specific metadata: Set the four required Open Graph properties and describe the image with
og:image:alt. Include width and height that match the image file. - Check the page itself: Inspect the published page’s HTML head to confirm that the final metadata is present and points to the right page and image.
- Preview on the destination services: Share or inspect the page using the services that matter. Check for cropping, legibility, and whether the intended image appears.
- Adjust and repeat: If a crop hides content or a file is too large, revise the artwork, export, metadata, or file size as appropriate, then check the preview again.
For a commercially important page, confirm platform requirements directly before launch. LinkedIn’s help page is marked as updated two years ago, while the broader platform comparisons cited here come from a secondary September 2026 guide.
Or skip the browser setup
If you want a screenshot of your published page to review its rendered appearance, ScreenshotNeo can return an image from one API request. That is a way to inspect the page itself; it does not replace checking how a social platform renders its share card.
curl -G "https://api.screenshotneo.com/v1/shot" -d access_key=YOUR_API_KEY --data-urlencode url=https://example.com/page -o shot.webpSee the ScreenshotNeo API documentation for request options. Cookie banners, popups, and chat widgets are removed before the shot; bot checks, blank pages, and failed loads are never billed. An MCP server lets AI agents take screenshots. The Free plan includes 1,000 screenshots a month with no card, and paid plans start at $5 for 3,000. ScreenshotNeo also supports PNG, JPEG, WebP, and PDF output.
Sign up for 1,000 free screenshots a month—no card required.
Recommended Free Tools
Troubleshooting Open Graph image problems
The preview shows the wrong image
Check that the published page’s og:image value points to the intended image and that you are testing the right page URL. If the metadata has changed, inspect the page again after publishing; the preview may not update immediately. Do not assume the protocol alone controls which image a service chooses.
The image is cropped or text is cut off
Review the preview on the target service. Move important content inward and test a revised image; a 1200 × 630 canvas is a starting ratio, not proof that every service displays the whole canvas.
The image appears as a small thumbnail on LinkedIn
Check its actual width. LinkedIn’s published help page says images narrower than 401 pixels display as thumbnails, and gives a 1200 × 627 pixel minimum for its sharing module. The page is marked as updated two years ago, so verify the current requirement if this matters to a launch.
The image is rejected or fails to load
Check the destination service’s current file-size rules and confirm that the image URL in the page metadata is the intended published asset. The sources summarized here establish different limits for some destinations, not one limit for all of them. Optimize the file where necessary and retest the resulting share preview.
The preview differs between services
That can happen because the protocol defines metadata rather than a universal presentation. Check each destination separately, and use current platform documentation for requirements that are not established by the protocol or that come only from a secondary guide.
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.
Frequently asked questions
Does the Open Graph Protocol require JPEG or WebP?
The protocol details cited here describe an image URL and optional image metadata, including a MIME-type property; they do not establish a required image format. Choose a format supported by your destination services and verify the published preview.
Does og:image:alt appear as text on the share card?
It is metadata describing the image, not a promise that a service will display that text visibly on its card. The consuming service controls how it uses page metadata.
Frequently Asked Questions
Does the Open Graph Protocol require JPEG or WebP?
The protocol details cited here describe an image URL and optional image metadata, including a MIME-type property; they do not establish a required image format. Choose a format supported by your destination services and verify the published preview.
Does og:image:alt appear as text on the share card?
It is metadata describing the image, not a promise that a service will display that text visibly on its card. The consuming service controls how it uses page metadata.
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.
