Use a 1200 × 630 pixel raster image as your starting Open Graph (OG) canvas. Publish it at an absolute, publicly reachable HTTPS URL, declare it with og:image, and add explicit dimensions plus descriptive alternative text. That 1.91:1 canvas works across many sharing surfaces, but it is not a universal guarantee: LinkedIn, X, Facebook and messaging apps can use different card ratios, limits and crops. Validate the preview on the platforms that matter before relying on it.
What an Open Graph image is
Open Graph is a metadata protocol that lets a page become a rich object when its URL is shared. The four basic properties are og:title, og:type, og:url and og:image. The image value is the URL of the picture representing that page in the social graph.
og:image:url is defined as an alias of og:image. Optional structured properties describe the selected file: og:image:secure_url, og:image:type, og:image:width, og:image:height and og:image:alt. Alt text should describe meaningful content in the image, not act as a caption.
The best OG image size
Start with 1200 × 630 pixels
A practical guide updated in July 2026 identifies 1200 × 630 (approximately 1.91:1) as a convenient cross-platform default. The same dimensions are listed for Facebook, iMessage, Slack, Discord, WhatsApp and Telegram. LinkedIn is listed at 1200 × 627, although 1200 × 630 is expected to behave similarly. X uses 1200 × 630 for a large image that may be cropped slightly toward a 2:1 presentation.
Windows Errors? Fix Them Before They Spread
Repair common Windows errors and clear accumulated junk for a smoother, more stable PC - no reinstall needed.Free scan · no reinstallOutdated Drivers Are Slowing You Down
One free scan finds every outdated or missing driver and matches the right update for your exact hardware.Free scan · exact hardware match#1 Best Overall
- HTML CSS Design and Build Web Sites
- Comes with secure packaging
- It can be a gift option
Treat those dimensions as a production default rather than a promise that every card will show the entire rectangle. Card type, application version, device and platform changes can alter the visible crop.
Keep a safe central area
Put headlines, logos and faces well inside the center of the canvas. Let only nonessential background decoration reach the edges. A service may trim the top, bottom or sides when it converts your image to its own card ratio, so edge-positioned text is the first thing to disappear.
Platform limits are not interchangeable
Published comparison tables disagree on some details, which is a reason to verify important destinations against their current owner documentation. Examples reported by the practical guide and community compilation include:
| Destination or card | Reported dimensions or ratio | Reported file guidance | Qualification |
|---|---|---|---|
| 1200 × 630 recommended; at least 200 × 200 listed as a minimum | Up to 8 MB in the guide | Images under 600 pixels wide may become a small square thumbnail; another table recommends at least 600 × 314. | |
| 1200 × 627 or 1200 × 630 | Up to 5 MB | Values differ by reference table and card context. | |
| X large summary | 1200 × 630 commonly used; one table lists a 1:1 requirement for a different card interpretation | Under 5 MB in one compilation; 5 MB limit in the guide, with 4096 × 4096 maximum | Confirm which X card type your metadata requests. |
| 1200 × 630 listed | Guide recommends under 600 KB | Recommendation, not a universal protocol limit. |
These figures are useful planning signals, not substitutes for current platform specifications. If a campaign depends on one network, design and test for that network’s exact card type.
Metadata to put in the page head
Use an absolute HTTPS URL that a crawler can fetch without authentication, a VPN or a session cookie. Relative paths can fail on some platforms. Declare the dimensions you actually generated and make the MIME type agree with the file.
<meta property="og:title" content="A clear page title">
<meta property="og:type" content="website">
<meta property="og:url" content="https://example.com/article">
<meta property="og:image" content="https://example.com/social-preview.png">
<meta property="og:image:secure_url" content="https://example.com/social-preview.png">
<meta property="og:image:type" content="image/png">
<meta property="og:image:width" content="1200">
<meta property="og:image:height" content="630">
<meta property="og:image:alt" content="A blue dashboard showing monthly sales trends">The protocol does not require width and height, but they make the asset explicit and can help a service prepare its preview. If you provide og:image:secure_url, it should identify the same HTTPS asset.
Using more than one image
Multiple og:image declarations form an array. The first image is preferred when a consumer must choose between them. Put each image’s structured properties immediately after its root image tag; when the next root tag appears, following properties belong to that new image.
<meta property="og:image" content="https://example.com/primary.jpg">
<meta property="og:image:width" content="1200">
<meta property="og:image:height" content="630">
<meta property="og:image:alt" content="Primary article illustration">
<meta property="og:image" content="https://example.com/alternate.jpg">
<meta property="og:image:width" content="1200">
<meta property="og:image:height" content="630">
<meta property="og:image:alt" content="Alternate product photograph">Do not assume every platform will expose a picker. If one image is the real default, list it first.
Recommended Free Tools
Rank #3
Choosing a file format and preparing the artwork
JPEG, PNG and WebP
- JPEG: a sensible choice for photographs and gradients where smaller files matter.
- PNG: preferable for flat artwork, screenshots, sharp text and transparency.
- WebP: broadly supported, but PNG or JPEG is safer when an obscure crawler or older integration is important.
SVG is not suitable for all crawlers discussed by the practical guide, and animated GIF previews commonly show only the first frame. Use a raster fallback for dependable sharing.
Compression and readability
Export at 1200 × 630, inspect the result at small card size, and compress until text remains legible without creating halos or blocking. Keep the headline short, use strong contrast, and avoid placing essential details near any edge. A platform may recompress the file, so do not rely on subtle color differences or hairline type.
How to implement and verify an OG image
- Create the canvas: export a PNG or JPEG at 1200 × 630 unless a target platform requires another ratio.
- Publish the file: place it at a stable HTTPS URL that returns the image directly, not an HTML error page or an access-controlled redirect.
- Add metadata: insert the tags in the document’s
<head>, using the exact absolute URL and actual width, height and MIME type. - Inspect rendered HTML: view the deployed page, not only a template source, and confirm that the intended values are present.
- Fetch the asset independently: request the image URL without login and check that the response is the expected raster file.
- Use destination previews: paste the live URL into each platform’s current preview or debugger. The Open Graph project identifies Facebook Object Debugger as Facebook’s parser and debugger.
- Check the final crop: look for clipped titles, logos, faces and important contrast at the size users will see.
Why an OG image is missing, wrong or stale
No image appears
- Confirm the page contains
og:image, not only a theme-specific social-image setting. - Replace relative, HTTP or malformed URLs with an absolute HTTPS URL.
- Make sure the image is publicly fetchable and does not require cookies, a referer, a token or JavaScript.
- Check that the server returns the image bytes and a matching MIME type rather than a 404 page, redirect loop or HTML challenge.
The wrong image appears
- Inspect every
og:image; the first is preferred when several are present. - Ensure structured width, height and alt tags follow the correct root image, rather than the next one.
- Check CMS templates, inherited defaults and duplicate tags in rendered HTML.
The old image remains
Social services cache fetched previews. There is no universal cache lifetime or one fix for every service. Verify that the URL now points to the intended file, then use the destination’s debugger or refresh workflow. If you replace an image while keeping the same URL, a service may continue serving its cached copy; a deliberate versioned filename can help when your publishing system permits it.
The image is cropped badly
Move essential content inward, create a destination-specific variant, or choose a card ratio supported by that platform. Do not enlarge a tiny source merely to reach 1200 pixels; it will remain soft and may be rejected for quality or size.
Do these 3 things before closing this tab:
1Repair Windows errors before they cause bigger problems2Scan for outdated or missing drivers - takes under a minute3Clear out junk files and repair common Windows errorsRank #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
Or skip the browser setup
If you need a clean screenshot of a live page to use as an OG asset, ScreenshotNeo provides a website screenshot API and MCP server. Its capture steps accept cookie and consent banners and remove more than 60 known consent platforms, newsletter popups and chat widgets before the shot; each step can be disabled. Bot checks and CAPTCHAs, blank pages, timeouts, failed loads and cache hits are not billed, and the response identifies the page verdict and billing status in headers.
One request returns PNG, JPEG or WebP (or a PDF), so you can generate a source image without maintaining browser automation:
Read the ScreenshotNeo API documentation.
curl -G "https://api.screenshotneo.com/v1/shot" -d access_key=YOUR_API_KEY --data-urlencode url=https://stripe.com -o shot.webpimport requests
r = requests.get("https://api.screenshotneo.com/v1/shot", params={"access_key": "YOUR_API_KEY", "url": "https://stripe.com"}, timeout=90)
open("shot.webp", "wb").write(r.content)const q = new URLSearchParams({ access_key: 'YOUR_API_KEY', url: 'https://stripe.com' });
const res = await fetch(`https://api.screenshotneo.com/v1/shot?${q}`);For AI workflows, its MCP server exposes take_screenshot, get_page_info and capture_pdf to Claude, Cursor and other MCP clients. The service includes full-page capture, selector capture, device and retina settings, custom CSS or JavaScript, waits, request blocking, authentication headers and cookies, resizing, caching, signed links, asynchronous jobs, bulk calls and a usage API.
The Free plan includes 1,000 screenshots per month with no card. Paid plans start at $5 for 3,000 shots; every feature is available on every plan. Create a free ScreenshotNeo account.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
A compact launch checklist
- Canvas is 1200 × 630 or intentionally tailored to a target card.
- Text and logos sit inside a central safe area.
- File is PNG or JPEG when maximum crawler compatibility matters.
og:imageis absolute, HTTPS and publicly fetchable.- Width, height, MIME type and alt describe the actual file.
- The first image is deliberately the preferred fallback.
- Rendered HTML contains no duplicate or stale CMS tags.
- Each important platform has been previewed after deployment.
Frequently Asked Questions
Does an OG image have to be exactly 1200 × 630?
No. It is a practical cross-platform starting point. Card ratios and limits vary, so use the destination’s current specification when one platform is critical.
Is og:image:alt the same as a caption?
No. It should describe meaningful visual content for accessibility and metadata consumers; it is not a visible caption.
Can I use a relative image URL?
Use an absolute HTTPS URL instead. Some platforms fail to resolve relative paths reliably.
Why did changing the file not change the shared preview?
The platform may be serving a cached scrape. Confirm the live metadata and use that platform’s current debugger or refresh process.
The Tool Desk
Outbyte PC Repair FREEClear out junk files and repair common Windows errorsFree Scan →Outbyte Driver Updater FREEScan for outdated or missing drivers - takes under a minuteDriver Scan →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.
