Recommended Free Tools
Some links on this page are affiliate links: if you buy through them we may earn a commission, at no extra cost to you.
Use an Open Graph image that is 1200 × 630 pixels (about 1.91:1) as your practical default. This matches Facebook-derived sizing guidance cited by Wix. It is a platform recommendation, not a size required by the Open Graph protocol; different services can crop or limit images differently.
Why 1200 × 630 pixels is the practical default
A 1200 × 630 image gives a link-preview card enough resolution for a wide landscape image while matching the proportions recommended in Wix’s Facebook-derived guidance. The ratio is approximately 1.91:1. If you are making one image for a page that will be shared on several services, this is a reasonable place to start rather than designing to an assumed universal rule. Wix Help Center’s recommended OG image guidance also says images smaller than 600 × 315 pixels can appear as small images in link previews.
That does not mean every service will display the whole image at the same size or in the same way. The final card depends on the sharing service and its rendering behavior. Treat 1200 × 630 as a strong default, then check the actual preview on the platforms that matter to your audience.
Is 1200 × 630 required by Open Graph?
No. The Open Graph protocol defines og:image as a URL representing the page or object. Its basic properties also include og:title, og:type and og:url. The protocol provides structured fields for image information, but it does not prescribe one universal pixel width and height.
This distinction matters: protocol markup tells a crawler which image to use and can describe it; platform guidance tells publishers what dimensions are likely to work well in a particular preview. The 1200 × 630 recommendation comes from practical platform guidance, not a requirement in the protocol specification. A service can apply its own minimum dimensions, file-size limit, crop or cache behavior.
Design for crops, not just the canvas
A 1200 × 630 file can still lose important material if a service displays it in a differently proportioned card. A 2026 cross-platform summary from urlpipe.dev says X’s large-image card may use a 2:1 crop, trimming a 1.91:1 image slightly. That is a secondary guide’s rendering note, not a guarantee about every X display or future interface. Check the guide and the current preview for your target service if the exact crop matters.
- Keep the most important words, logo and subject away from the outer edges. A crop can remove edge content even when the source image is correctly sized.
- Make the image understandable when reduced to a small card. Avoid relying on fine print or tiny decorative details.
- If one artwork must serve several networks or messaging apps, use a central safe area for essential content and preview it in each destination.
- If a platform is especially important, use its current official guidance and preview tool rather than assuming the cross-platform default overrides its rules.
There is no single safe-area measurement established by the sources cited here. The practical test is whether the essential content survives the previews your audience will actually see.
Add the image to your page’s Open Graph metadata
Place the Open Graph tags in the page’s HTML head, and make sure the image URL identifies the image you intend crawlers to fetch. The following example declares dimensions and MIME type as well as alt text; replace the example URL and description with values appropriate to your 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:type" content="image/jpeg" />
<meta property="og:image:alt" content="A concise description of the image contents" />The protocol describes og:image:width and og:image:height as image dimensions, og:image:type as its MIME type, and og:image:secure_url as an alternative secure image URL. These are structured properties that describe the image; adding dimensions in metadata does not resize or repair the image file itself.
Write useful image alt text
The protocol says a page specifying og:image should specify og:image:alt. Alt text should describe what the image contains, not serve as a caption or repeat promotional copy. For example, describe the visible subject or illustration in a concise way that makes sense without seeing the image.
If you declare more than one image
The protocol allows multiple og:image values. When values conflict, it gives preference to the first image declared. Put your intended primary preview image first instead of assuming a crawler will choose the last or most recently added one. If you need different images for different services, verify how those services interpret the page rather than relying on ordering to create platform-specific behavior.
Free tools Windows power users keep installed
One-click scans. No signup required.
File size and platform-specific limits
File-size limits are not universal. Wix Help Center’s cited guidance says the image should not exceed 8 MB, and separately says a WhatsApp link-preview image must be under 300 KB to display. Those are figures in that guidance, not a claim that all platforms share either limit. Confirm the current limit for the service you are targeting, since limits and rendering behavior can change. Wix’s guidance also covers the image-size recommendations and preview checks.
If an image meets the 8 MB figure but is intended for a WhatsApp preview, it may still fail the under-300 KB condition described by Wix. If you compress an image to meet a service limit, check that the result remains visually clear at the small preview size. The cited sources do not establish a universal preferred file format or compression setting, so choose a format accepted by the target platform and ensure the declared MIME type matches the actual image.
Check the preview after publishing
Do not judge the result only from the image file or the HTML source. A preview check can reveal an old cached image, missing metadata, an unexpected crop or a crawler that cannot access the image URL. Wix recommends refreshing a changed image through Facebook’s debugger and advises checking updated previews with platform tools. Tool names, cache behavior and availability can change, so consult the relevant platform’s current documentation if a preview still appears stale.
- Open the published page and inspect its rendered source or head markup. Confirm that
og:imagepoints to the intended image and that any declared dimensions and MIME type match the file. - Check the image URL itself in a browser. Confirm it loads the intended image rather than a page, an error response or an obsolete file.
- Use the target platform’s current preview or debugging tool to inspect the card. Check both whether the image appears and whether important content is cropped.
- If the image was recently changed, refresh or re-scrape it with the platform’s tool where available. A page or image that was previously fetched can continue to show an older preview until the service updates its stored copy.
- Repeat the check in the actual sharing destinations that matter. One service’s successful preview does not establish that another will use the same crop, limits or cached image.
Troubleshoot common Open Graph image problems
The preview uses the wrong image
Check for multiple og:image tags and confirm that the intended primary image is first. Then check whether the page has changed since the platform last fetched it; use the platform’s available refresh or debugger tool to request an updated preview. The Open Graph protocol gives preference to the first image when several values conflict.
The image does not appear, or appears very small
Verify that the metadata points to the image itself and that the URL loads the expected file. Compare its dimensions with Wix’s cited guidance: the recommended default is 1200 × 630 pixels, while images smaller than 600 × 315 may appear as small preview images. Wix’s help guidance also lists a 200 × 200-pixel minimum; treat that as guidance in that source, not as a universal guarantee across platforms. Check the target service’s own requirements if the image is still absent.
The card is cropped differently than the artwork
Keep key content farther from the edges and inspect the card in the destination service. A slightly different aspect ratio can trim an image; urlpipe.dev’s 2026 summary, for example, describes a possible slight trim for X’s 2:1 large-image card when using a 1.91:1 image. Avoid treating that secondary guide as a promise of identical rendering in every feed or app.
The image is stale after an update
The page may have been fetched before the new image was published. Refresh the platform preview where possible, as Wix advises for Facebook’s debugger, and check the live page’s tags and image URL before assuming the updated asset has been picked up. Preview tools and cache behavior are service-specific and may change.
The file is rejected or absent on one service only
Check that service’s current file-size and image requirements. The Wix guidance’s 8 MB advice and under-300 KB WhatsApp condition are not interchangeable universal ceilings. A file can satisfy one service’s guidance and exceed another’s.
Quick wins for a faster PC:
Scan for outdated or missing drivers - takes under a minuteDriver Scan →Clear out junk files and repair common Windows errorsFree Scan →Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →Or skip the browser setup
If you need to inspect how a published page looks in a browser, ScreenshotNeo can return a screenshot or PDF from one API request. It does not create an Open Graph image or guarantee how a social network will render one; use the target platform’s preview tool to validate the actual share card. ScreenshotNeo is useful for capturing the page itself, including after you have updated its tags or artwork.
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.
For example, this cURL request captures a page as a WebP image. Replace the example target URL and API key with your own values. See the ScreenshotNeo API documentation for request options.
curl -G "https://api.screenshotneo.com/v1/shot" -d access_key=YOUR_API_KEY --data-urlencode url=https://example.com/article -o shot.webp- ScreenshotNeo accepts cookie or consent banners like a visitor and removes more than 60 known consent platforms, newsletter popups and chat widgets before capture; each of these steps can be turned off.
- Bot checks or CAPTCHAs, blank pages, timeouts, failed loads and cache hits are not billed. Response headers identify the page verdict and billing status.
- An MCP server provides
take_screenshot,get_page_infoandcapture_pdftools for AI agents, including Claude, Cursor and other MCP clients. - The Free plan includes 1,000 screenshots a month without a card; paid plans start at $5 for 3,000 screenshots.
Sign up for ScreenshotNeo’s free plan to get 1,000 screenshots a month with no card.
Use a platform preview as the final check
For most pages, make a 1200 × 630 image, put its URL in og:image, add accurate image metadata and alt text, then inspect the rendered card in the services where it will be shared. The dimensions give you a practical starting point; the preview is the check that matters for a live page.
Do these 3 things before closing this tab:
1Clear out junk files and repair common Windows errors2Fix the driver behind crashes, sound loss and screen glitches3Repair Windows errors before they cause bigger problemsQuick 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.
