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 →Use 1200 × 630 pixels (about a 1.91:1 aspect ratio) as the practical default for a general-purpose Open Graph image. That canvas works well when one image must travel across several sharing surfaces. It is a recommendation, not a size required by the Open Graph protocol. If LinkedIn is your exact target, its sharing guidance specifies a 1200 × 627 pixel frame at the same 1.91:1 ratio. Always treat a platform’s current documentation as the final authority.
What “OG image size” actually means
An Open Graph (OG) image is the preview image a site declares with the og:image metadata property. Social networks and other link-preview clients can fetch that URL and use the image when someone shares the page. The Open Graph protocol also defines optional og:image:width and og:image:height properties, but it does not prescribe one universal pixel canvas for every platform. See the Open Graph protocol reference.
That distinction matters: a protocol-level metadata definition and a platform’s display or upload rule are different things. Saying that “Open Graph requires 1200 × 630” is too strong. The more accurate statement is that 1200 × 630 is a broadly useful design default.
Recommended dimensions at a glance
| Use case | Width × height | Aspect ratio | What the evidence supports |
|---|---|---|---|
| General-purpose OG image | 1200 × 630 px | About 1.91:1 | A practical cross-platform recommendation from OG Image Design’s July 2026 guide. |
| LinkedIn website-sharing preview | 1200 × 627 px | 1.91:1 | LinkedIn’s own sharing guidance; the page also lists a 5 MB maximum and thumbnail behavior below 401 px wide. See LinkedIn Help. |
| Open Graph protocol | Not specified | Not specified | The protocol defines image metadata, not one required canvas. See ogp.me. |
The two common canvases differ by only three pixels in height. At normal preview sizes, that difference is unlikely to be visible, but use 1200 × 627 when LinkedIn’s exact guidance is the requirement and 1200 × 630 when you need one broadly reusable asset.
Recommended Free Tools
#1 Best Overall
Why 1200 × 630 is a sensible default
It preserves a common wide shape
A 1200 × 630 canvas is approximately 1.91:1, a wide format that leaves room for a headline, brand mark and a simple visual without making the text microscopic. Designing to that ratio also reduces the chance that a platform must aggressively crop the sides or bottom.
It gives you enough working pixels
At 1200 pixels wide, large type and high-contrast shapes remain legible after a preview is reduced. The source is still compact enough to optimize as a web image. The exact file size depends on the artwork and encoding, so dimensions alone do not guarantee a small file.
It is a convention, not a compatibility promise
Different services can apply their own crop, file-size, or preview rules. The cited guidance establishes LinkedIn’s numeric requirements, but it does not establish a universal specification for every network. Check the current documentation for any platform that is especially important to your publishing workflow.
How to create an OG image that survives cropping
- Start a 1200 × 630 px document. If LinkedIn is the sole target and exact compliance matters, start at 1200 × 627 px instead.
- Place essential content in a safe center area. Keep the title, logo and critical labels away from the outer edges so a tighter preview crop does not remove them.
- Use one clear message. A short page title is easier to read than a paragraph. Use strong contrast between text and background.
- Export to a web-friendly format. Use the format your publishing system supports, then check the resulting file size against the target platform’s limit. LinkedIn’s cited guidance lists 5 MB for website-sharing images.
- Keep the image URL stable. Put the final file at a publicly reachable HTTPS URL. Avoid a URL that requires a login, a session cookie or a browser interaction.
- Match the metadata to the file. If you publish
og:image:widthandog:image:height, use the actual dimensions of the file, as described by the protocol.
Metadata implementation
Put the tags in the page’s <head>. Replace the example URL and text with the values for the page being shared:
<meta property="og:title" content="How to Configure Backups">
<meta property="og:description" content="A practical guide to reliable backups.">
<meta property="og:type" content="article">
<meta property="og:url" content="https://example.com/guides/backups">
<meta property="og:image" content="https://example.com/images/backups-og-1200x630.jpg">
<meta property="og:image:width" content="1200">
<meta property="og:image:height" content="630">
<meta property="og:image:alt" content="A backup workflow diagram">The protocol reference defines the image and optional dimension metadata. The dimensions in your tags should describe the file you actually serve; do not leave 1200 × 630 in the tags after replacing the asset with a differently sized image.
Rank #2
Choosing between 1200 × 630 and 1200 × 627
Choose 1200 × 630 for a shared default
Use this when your CMS creates one OG asset for many destinations, or when you want a simple design specification for writers and designers. It is the practical general-purpose recommendation cited above.
Choose 1200 × 627 for LinkedIn-specific production
LinkedIn’s help page specifies “1200 (w) x 627 (h) pixels” for the preview frame and lists a 5 MB maximum. It also says images narrower than 401 pixels display as thumbnails. Those are LinkedIn details, not Open Graph protocol rules.
Keep a source file if you need both
Because the dimensions are so close, you can maintain a master design and export two crops. Check text alignment and edge spacing in both exports rather than simply stretching one file.
Quick wins for a faster PC:
Scan for outdated or missing drivers - takes under a minuteDriver Scan →Repair Windows errors before they cause bigger problemsFix Now →Validation checklist before publishing
- Confirm the final pixel dimensions in an image editor or build step.
- Confirm the file is below the target platform’s documented size ceiling; for LinkedIn, the cited limit is 5 MB.
- Open the exact
og:imageURL in a private browser window to verify that it is publicly retrievable. - Inspect the rendered HTML, not only a CMS preview, and verify that the tag is in the document head.
- Check that
og:image:widthandog:image:heightmatch the served file. - Look at the image at a small preview size. If the title cannot be read there, shorten it or increase contrast.
- Review the outer edges for logos, dates or words that a crop could remove.
Common failures and fixes
The preview shows no image
Likely causes: the image URL is private, returns an error, redirects through a blocked login, or the tag is missing from the rendered HTML. Fix: request the image URL without an authenticated session, check its HTTP response, and inspect the page source for a correctly formed og:image tag.
The wrong image appears
Likely cause: a cached preview client still has an earlier image. Fix: verify the current tag and URL first. If the tag is correct, allow for the platform’s cache behavior or publish a new, versioned image URL when your workflow permits it.
The image is cropped awkwardly
Likely cause: essential content sits too close to an edge or the destination uses a different preview frame. Fix: redesign with a centered safe area and test the 1200 × 630 and 1200 × 627 exports separately.
LinkedIn shows a thumbnail instead of a large preview
Likely cause: the image is narrower than 401 pixels. Fix: provide a larger image; LinkedIn’s cited guidance specifically identifies that threshold.
PC Slower Than It Used to Be?
A free scan shows the junk files, broken settings and background clutter dragging Windows down - then fixes them in one click.Free scan · Windows 10 & 11Outdated 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 matchThe upload is rejected for size
Likely cause: the encoded file exceeds the destination’s limit. Fix: remove unnecessary metadata, choose an appropriate compression setting, or export a more efficient file while retaining the intended dimensions. For LinkedIn, compare the result with its 5 MB maximum.
Previewing the finished page without manual browser setup
If you need a rendered screenshot of the page to check the OG design in context, you can use a browser automation workflow. For a repeatable API call, ScreenshotNeo returns PNG, JPEG, WebP or PDF captures from one GET request. It is useful for visual QA because it accepts cookie or consent banners before capture and removes more than 60 known consent platforms, newsletter popups and chat widgets; each step can be disabled. Only clean shots are billed, while bot checks or CAPTCHAs, blank pages, timeouts, failed loads and cache hits are not billed, and the response identifies the result with X-Page-Verdict and X-Billed headers.
Or skip the browser setup:
Use the API documented at ScreenshotNeo’s documentation:
curl -G "https://api.screenshotneo.com/v1/shot" -d access_key=YOUR_API_KEY --data-urlencode url=https://example.com/guides/backups -o og-preview.webpimport requests
r = requests.get("https://api.screenshotneo.com/v1/shot", params={"access_key": "YOUR_API_KEY", "url": "https://example.com/guides/backups"}, timeout=90)
open("og-preview.webp", "wb").write(r.content)const q = new URLSearchParams({ access_key: 'YOUR_API_KEY', url: 'https://example.com/guides/backups' });
const res = await fetch(`https://api.screenshotneo.com/v1/shot?${q}`);You can set a viewport, wait for a selector or network idle, hide selectors, use a device preset, or capture a specific element when checking an OG layout. ScreenshotNeo also offers an MCP server with take_screenshot, get_page_info and capture_pdf tools for Claude, Cursor and other MCP clients. The Free plan includes 1,000 screenshots per month with no card; paid plans start at $5 for 3,000 shots. Create a free ScreenshotNeo account.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
Rank #4
Performance, reliability and cost considerations
Optimize the asset, not just the canvas
A 1200 × 630 image can still be heavy if it contains photographic detail or excessive metadata. Compress the exported file, serve it from a reliable public host and avoid redirects that add latency. Keep the dimensions intact while tuning encoding quality.
Automate checks in your publishing pipeline
For sites that generate pages programmatically, validate that every page emits one reachable og:image URL and matching dimensions. A screenshot service can provide a visual regression step after deployment; an API response that distinguishes clean, failed and cached captures helps you separate rendering problems from billing events.
Budget for the work you actually perform
Image hosting and social preview fetching are separate from screenshot testing. ScreenshotNeo’s Free plan provides 1,000 shots each month without a card; listed paid plans are Starter $5 for 3,000, Growth $15 for 15,000, Pro $39 for 60,000, Scale $99 for 250,000 and Business $249 for 1,000,000. Yearly billing gives two months free, and every feature is included on every plan.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Does the Open Graph protocol mandate a particular OG image size?
No. The protocol defines properties such as og:image and optional width and height metadata, but the cited protocol reference does not require a universal pixel size. Use 1200 × 630 as a practical default, then follow a destination’s own current guidance when exact compliance matters.
FAQ
Is 1200 × 630 better than 1200 × 627?
Neither is universally “better.” 1200 × 630 is the broad default; 1200 × 627 is LinkedIn’s specified frame. Select according to whether you need one reusable asset or LinkedIn-specific output.
Best Value
Can an OG image be smaller?
It can be, but smaller dimensions provide less room for readable type and may trigger thumbnail treatment. LinkedIn’s cited guidance says images under 401 pixels wide display as thumbnails.
Should the metadata dimensions be included?
They are optional protocol properties, but when you include them they should match the actual file dimensions. This gives consumers accurate metadata without claiming a size the file does not have.
Frequently Asked Questions
What is the safest single OG image size for a CMS?
Set the default export to 1200 × 630 pixels and keep essential content inside a centered safe area.
Free tools Windows power users keep installed
One-click scans. No signup required.
What file-size limit does LinkedIn list?
The cited LinkedIn Help page lists a 5 MB maximum for website-sharing images.
How can I check an OG image after deployment?
Inspect the rendered head tags, request the image URL without authentication, and use a screenshot of the live page to verify the visual result.
The Bottom Line
Use 1200 × 630 pixels as the practical general-purpose OG image size. Use LinkedIn’s 1200 × 627 specification for LinkedIn-specific work, and remember that neither number is a universal Open Graph protocol requirement.
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.
