Free tools Windows power users keep installed
One-click scans. No signup required.
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 a 1200 × 630 pixel image (about a 1.91:1 ratio) as your practical Open Graph default. It is close to LinkedIn’s 1200 × 627 minimum and recommended ratio, while leaving enough resolution for most social previews. It is not a protocol-mandated size: each platform can crop, resize, or limit files differently. Keep important text and logos inside a generous safe area, publish the correct Open Graph metadata, and inspect the real preview after deployment.
Why 1200 × 630 is the usual Open Graph canvas
Open Graph defines metadata that describes a page; it does not require one universal image dimension. The og:image property points to the image representing the page, while the service displaying the link decides how that image is rendered.
A 1200 × 630 canvas is approximately 1.91:1. That makes it a useful cross-platform starting point and keeps the image close to LinkedIn’s stated 1.91:1 recommendation. Treat it as a practical default rather than a guarantee that every network will show the entire image.
What the ratio means
The ratio is calculated as width divided by height: 1200 ÷ 630 ≈ 1.90. A platform using a slightly different crop can remove pixels from the sides or top and bottom. Design with that possibility in mind instead of placing critical content against an edge.
Platform dimensions, crops, and file limits
Platform requirements change, and some published guidance is secondary rather than an official specification. Use the following as planning guidance and verify the live rules before an important launch.
| Platform or layer | Guidance | Qualification |
|---|---|---|
| General Open Graph canvas | 1200 × 630 pixels; approximately 1.91:1 | Practical cross-platform default, not enforced by the protocol. |
| LinkedIn sharing module | 1200 × 627 pixel minimum; 1.91:1 recommended; 5 MB maximum | Official LinkedIn help guidance. Images narrower than 401 pixels are displayed as thumbnails. The page indicates it was last updated two years ago, so confirm the current requirements. |
| X large-image card | A secondary September 2026 guide describes a 2:1 card and a slight crop when using 1200 × 630. | Secondary reporting; check current X documentation for a production decision. |
| The same secondary guide reports a file-size limit under 600 KB. | Secondary reporting. Optimize and test the actual share preview. | |
| Slack and Discord | No exact public dimensions are listed in that guide. | Do not present a precise size as an official requirement. |
When a single image must serve several services, 1200 × 630 is the sensible baseline. If one channel is commercially critical, create a channel-specific variant after checking its current documentation.
Open Graph metadata you must publish
The protocol identifies four required properties for a basic object: og:title, og:type, og:image, and og:url. The image URL should be absolute and publicly reachable over HTTPS. Add structured image properties so consumers know the dimensions and alternative text.
Recommended Free Tools
<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">The protocol says that a page specifying og:image should specify og:image:alt as well. You may also provide og:image:type (such as image/jpeg), og:image:secure_url, and additional image details where supported.
Make the URL and page identity consistent
- Use the canonical page URL in
og:url, not a tracking URL or a shortener. - Make the image URL stable; changing the path can leave old previews cached.
- Use
og:type="article"for an article page and choose a title that makes sense when shown without the page’s headline. - Keep the image publicly fetchable. Login walls, robots restrictions, or a URL that expires before a crawler fetches it can produce a missing preview.
Designing a share image that survives cropping
Keep a safe area
Leave visible padding around headlines, logos, and calls to action. A platform may trim the outer edges, and link cards may display the image at different sizes. Center the primary message and avoid placing small type in the corners.
Use readable type and contrast
Social previews are often shown as small cards on phones. Use a short headline, strong contrast, and a simple visual hierarchy. Check the image at the approximate size users will see rather than judging only a full-resolution file.
Choose a format deliberately
- JPEG: useful for photographs and gradients; adjust quality to stay within platform limits.
- PNG: useful for sharp text, diagrams, or transparency, but can be much larger.
- WebP: often reduces size, but verify that every target service accepts it before making it your only asset.
LinkedIn’s stated maximum is 5 MB. The secondary guide’s WhatsApp figure is under 600 KB, so a heavily compressed, optimized variant may be necessary for that channel. Do not assume that a file accepted by one service will meet another service’s cap.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
A reliable implementation workflow
- Create the master: start at 1200 × 630 pixels and keep essential elements away from the edges.
- Export and optimize: select an appropriate format, remove unnecessary metadata, and check the resulting byte size against your target platforms.
- Publish the asset: host it at a stable HTTPS URL that does not require authentication.
- Add metadata: place the four core properties and image dimensions in the document’s
<head>; includeog:image:alt. - Deploy the page: ensure the production HTML, rather than a client-side-only placeholder, contains the tags when crawlers request it.
- Inspect previews: share the live URL on each important platform and look for cropping, stale images, missing text, or a file rejection.
- Revise safely: if you replace an image at the same URL, a service may continue showing a cached copy. A versioned filename can help, but update the metadata and retest the final URL.
Troubleshooting Open Graph image problems
The preview has no image
Check that og:image is present in the server-rendered HTML, uses an absolute HTTPS URL, and returns the image without a login, redirect loop, or access block. Confirm the URL directly in an unauthenticated browser session.
The wrong image appears
Look for multiple og:image tags, plugin-generated metadata, or stale platform caching. Keep one deliberate primary image, then republish or use the platform’s current preview refresh mechanism.
The image is cropped badly
Move text and logos inward, shorten the headline, and test a 1200 × 630 master against the platform’s card shape. X’s reported 2:1 presentation can trim a 1200 × 630 image slightly; do not rely on edge content.
LinkedIn shows a thumbnail
LinkedIn states that images narrower than 401 pixels display as thumbnails. Verify the delivered image width and that the image URL is not being replaced by a small fallback asset.
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 glitchesThe file is rejected or loads slowly
Measure the encoded file, not just its pixel dimensions. Compress photographs, remove unused metadata, and consider a JPEG or WebP variant where accepted. Keep a higher-quality source file separately so you can re-export without repeated degradation.
Updates do not appear
Social crawlers cache fetched images. Confirm that the HTML now points to the intended URL, wait for the service to refetch it, and use a new versioned asset URL when a time-sensitive correction must be visible.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Or skip the browser setup
If you need to inspect how a published page renders before sharing it, ScreenshotNeo can return a screenshot from one GET request. It accepts the page URL and can produce PNG, JPEG, WebP, or PDF output. Cookie and consent banners, newsletter popups, and chat widgets are removed before the shot; bot checks, blank pages, timeouts, failed loads, and cache hits are not billed, and the response identifies the page verdict and billing status in headers. Its MCP server provides take_screenshot, get_page_info, and capture_pdf tools for Claude, Cursor, and other MCP clients.
Use the ScreenshotNeo documentation for all parameters. A basic capture of an article page is:
curl -G "https://api.screenshotneo.com/v1/shot" -d access_key=YOUR_API_KEY --data-urlencode url=https://example.com/article -o preview.webpPython:
import requests
r = requests.get("https://api.screenshotneo.com/v1/shot", params={"access_key": "YOUR_API_KEY", "url": "https://example.com/article"}, timeout=90)
open("preview.webp", "wb").write(r.content)Node.js:
const q = new URLSearchParams({ access_key: 'YOUR_API_KEY', url: 'https://example.com/article' });
const res = await fetch(`https://api.screenshotneo.com/v1/shot?${q}`);ScreenshotNeo includes full-page capture, device presets, custom viewport and retina scale, waits for selectors or network idle, custom CSS and JavaScript, hidden selectors, request blocking, cookies and headers, caching with a chosen TTL, signed links, asynchronous jobs, bulk capture for up to 100 URLs per call, usage reporting, and an OpenAPI specification. Its parameter names match those used by other screenshot APIs, which can simplify migration.
| Plan | Included shots | Price |
|---|---|---|
| Free | 1,000 per month | $0, no card |
| Starter | 3,000 | $5 |
| Growth | 15,000 | $15 |
| Pro | 60,000 | $39 |
| Scale | 250,000 | $99 |
| Business | 1,000,000 | $249 |
Yearly billing gives two months free, and every feature is available on every plan. Start with 1,000 free screenshots a month—no card required.
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.
Final checklist
- Master image is 1200 × 630 pixels unless a channel-specific asset is required.
- Critical content has a safe margin from every edge.
og:title,og:type,og:image, andog:urlare present.og:image:width,og:image:height, andog:image:altdescribe the asset.- The image URL is absolute, HTTPS, stable, public, and within the target file-size limit.
- Previews have been checked on the platforms that matter to your audience.
Frequently Asked Questions
Is 1200 × 630 an official Open Graph requirement?
No. Open Graph defines metadata properties, not a universal pixel dimension. 1200 × 630 is a practical cross-platform default.
Should I create a separate image for every social network?
Use one 1200 × 630 master for broad compatibility, then create channel-specific variants when a platform’s crop or file limit materially affects the result.
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 reinstallCrashes, No Sound, or Screen Glitches?
Random freezes, missing sound and display glitches usually trace back to one bad driver. Find and replace yours safely.Free scan · under a minuteDo Open Graph images need alternative text?
The protocol says pages specifying og:image should also specify og:image:alt; provide concise text describing the image.
Why can a correct image still look different after sharing?
The consuming service controls its card layout, crop, resizing, and caching. A standards-compliant tag set does not force identical rendering everywhere.
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.
