X / Twitter
Large summary card
Turn a real product screen into a polished 1200×630 card for LinkedIn, X, Facebook, Slack, and Discord—then carry the same visual direction across your launch.
Loved by 3,000+ creators

Designed at 1200×630. Pick a template, add your screenshot and export a static social card.
Study original Screenhance outputs for product crops, editorial splits, metrics, quotes, photography, and interface galleries—with the layout decision behind every example.
An OG image is the 1200×630 preview people see before they visit. Keep the product recognizable, the headline readable, and the important content away from cropped edges.

Make the benefit readable before the click.
Large summary card
Article and post preview
Link unfurl
Embedded link card
Paste a public URL to inspect the image metadata it exposes. Platform previews can still differ, so test the published URL on the services that matter to you.
See how your link looks when shared
Paste any page URL. We fetch its Open Graph tags and show the exact preview that appears on X, LinkedIn, Slack, and Facebook, then flag what is off.
Just want the checker? Open the OG image checker.
Exporting a card is only the design step. Put the file at a public HTTPS URL and add og:image to the page. The Open Graph protocol also defines optional image type, width, height and alt properties. Supplying them gives crawlers clear image details when they inspect the page.
Relative paths cannot be resolved reliably by an external crawler.
Do not require a cookie, login or browser-only script to fetch the file.
Add og:image:alt with a concise description of the meaningful visual content.
Inspect the published URL, not a local file or an unpublished preview.
The Open Graph specification defines image metadata but does not prescribe one universal pixel size. Screenhance uses 1200×630 as a practical 1.91:1 starting point. LinkedIn's current guidance uses the closely related 1200×627 size for Page link previews.
Keep important text away from the edges, make the main idea legible at a small size, and preview the finished card across the destinations that matter to your audience. That one careful composition gives supported Open Graph previews a clear, recognizable identity.
If LinkedIn shows stale metadata, its official Post Inspector can re-inspect the URL for new shares. Other services refresh on their own schedules, so version the image URL when practical.
The right workflow depends on how often the page changes and how many unique previews you need. The image metadata is the same; the difference is how the final image gets produced and maintained.
Design and export a dedicated image for a homepage, pricing page, launch page, or major feature. Static cards give you direct control over the crop, typography, product screen, and final file.
Generate images from page data when a blog, directory, documentation site, or marketplace has too many URLs to design one by one. Use a stable layout and keep the generated headline within predictable bounds.
Use designed static cards for the pages that define the product, then a simpler generated system for frequently published content. Shared type, color, and image treatment can keep both approaches recognizably yours.
Read the practical dynamic OG image guide or follow the step-by-step guide to creating OG images.
A social preview is often shown much smaller than the exported file. Make one idea dominant: a short headline, a clear product screen, or a recognizable brand mark. Supporting detail should stay secondary rather than compete with the reason to open the link.
Keep essential text and UI away from the outer edge because services may crop or resize the image differently. If the screenshot contains tiny controls, crop to the part that proves the headline instead of shrinking an entire dashboard into the card.
Preview the published URL after deployment. A correct export cannot fix a missing og:image, an inaccessible asset, or cached metadata. The page, image URL, metadata, and visual need to work as one delivery chain.
1200×630 is a practical 1.91:1 working size for a shared Open Graph image. The Open Graph protocol itself does not mandate a pixel size, and each service controls its own final preview, so test the published URL on the destinations that matter to you.
Publish an absolute HTTPS URL in og:image. The Open Graph protocol also supports og:image:type, og:image:width, og:image:height and og:image:alt. Include a useful alt description and make sure social crawlers can fetch the image without signing in.
Yes. Screenhance can place a screenshot in an iPhone, Pixel, MacBook or browser frame, then combine it with editable text and a background. Keep the interface large enough to understand when the card is shown as a small preview.
The free plan includes three watermarked PNG exports per month. The one-time Launch Pass removes the watermark from its included image exports; Pro adds ongoing clean exports, higher scales and the full paid export options.
Link-preview services cache the metadata and image they fetch. Confirm that the live page contains the new absolute image URL, then use a platform inspection tool where one is available. LinkedIn provides Post Inspector for refreshing and checking new shares.
Shipping a product? Generate matching App Store, Play Store, and Product Hunt visuals from the same brief. Upload your screenshots once and Launch Kit generates them all, on-brand and matching.
Turn the same product story into a post, share card, or launch gallery.
Sponsored feed, lead, app-install, and Story ad previews
Start creatingPolished LinkedIn post visuals
Start creatingMulti-page product launches, frameworks, changelogs, and case studies
Start creatingProduct launches, feature threads, proof, and updates for X
Start creatingLaunch, update, and proof templates for Instagram, LinkedIn, and X
Start creatingLaunch-ready PH gallery images
Start creatingStart with a polished 1200×630 template, add your product screen and brand, then export a consistent social card for links and destinations that support Open Graph previews.