---
title: "Open Graph Preview & Debugger"
description: "Preview how a link looks when shared on Facebook, X, LinkedIn, Discord, Slack and WhatsApp, and check its Open Graph and Twitter Card meta tags."
url: https://findutils.com/seo/open-graph-preview/
category: seo
---

# Open Graph Preview & Debugger

Preview how a link looks when shared on Facebook, X, LinkedIn, Discord, Slack and WhatsApp, and check its Open Graph and Twitter Card meta tags.

**Use this tool:** [Open Graph Preview & Debugger](https://findutils.com/seo/open-graph-preview/)

## Programmatic access

- REST id `open-graph-preview`: POST https://api.findutils.com/api/tools/open-graph-preview/execute (reference: https://findutils.com/api/open-graph-preview/)
- MCP tool `open_graph_preview` on https://mcp.findutils.com (reference: https://findutils.com/mcp/open-graph-preview/)

## Why Use Open Graph Preview?

See exactly how your links will appear on Facebook, Twitter/X, LinkedIn, Discord, Slack, and WhatsApp before publishing. Catch missing images, truncated titles, and broken tags instantly with real-time validation and multi-platform previews, all without deploying your page or sharing it publicly.

## Open Graph Optimization Tips

- Always use absolute URLs for og:image. Relative paths like /images/hero.jpg will fail on most platforms. Include the full URL with https:// protocol.
- Keep og:title under 60 characters and og:description under 155 characters. Facebook and LinkedIn truncate longer text, and the cut-off point varies by device and platform.
- Use og:image dimensions of exactly 1200x630 pixels with a 1.91:1 aspect ratio. This is the universal safe size that renders well on Facebook, LinkedIn, Twitter, Discord, and Slack without cropping.
- Set a unique og:image for each page rather than reusing your site logo. Pages with custom social images get significantly more engagement than those with generic fallback images.
- Add both og:title and twitter:title separately. While Twitter falls back to OG tags, setting dedicated Twitter Card tags lets you craft platform-specific messaging, like shorter titles that work better in Twitter's card layout.

## Frequently Asked Questions

### Does this Open Graph Preview tool require a signup?

No. This Open Graph Preview tool is available with no account required, no usage limits, and no feature restrictions. You can preview social cards across all six platforms, validate your meta tags, generate HTML markup, and copy the output as many times as needed. The entire tool runs locally in your browser, which means your HTML source code and meta tag content never leave your device. This makes it safe for testing pre-launch pages, client projects, and confidential content that you would not want to share with external services. Unlike Facebook Sharing Debugger or Twitter Card Validator that require your page to be publicly live, this tool works with raw HTML or manually entered values before anything is deployed. There are no premium tiers or paid upgrades. Every feature visible on the page is fully functional for all users without limitations or time-restricted trials.

### What is the recommended Open Graph image size for social sharing?

The universally recommended Open Graph image size is twelve hundred by six hundred thirty pixels with a one-point-nine-one to one aspect ratio. This dimension works well across Facebook, LinkedIn, Discord, Slack, and WhatsApp without significant cropping on any platform. Twitter summary large image cards use a similar twelve hundred by six hundred twenty-eight pixel size, which is close enough that a single twelve hundred by six hundred thirty image works for both protocols. The minimum acceptable size is six hundred by three hundred fifteen pixels, though images below the recommended dimensions may appear pixelated or improperly cropped on high-resolution displays. Always use JPEG or PNG format with file sizes under eight megabytes, as larger files may timeout during social platform scraping. Place important text and visual elements in the center of the image, keeping a safe margin of about ten percent from all edges to account for different cropping behaviors across platforms.

### Why does my shared link show the wrong image or old title?

Social media platforms cache Open Graph metadata aggressively to reduce server load when links are shared frequently. Facebook caches scraped data for approximately twenty-four hours, Twitter retains cached cards for around seven days, and LinkedIn caches for a similar duration. When you update your Open Graph tags, the platforms continue serving the old cached version until the cache expires or you manually force a refresh. To clear Facebook cache, use the Facebook Sharing Debugger and click the Scrape Again button for your URL. For Twitter, use the Card Validator tool to trigger a fresh scrape. LinkedIn provides a Post Inspector that re-fetches your page metadata on demand. Also verify that your og:image URL uses an absolute path with the full https protocol included, as relative image paths are a common cause of missing images across all platforms.

### Do I need both Open Graph tags and Twitter Card tags on my page?

You do not strictly need both, but adding them gives you maximum control over how your content appears on each platform. Twitter and X will fall back to reading your Open Graph tags when dedicated Twitter Card meta tags are absent, so your links will still generate preview cards with just og:title, og:description, and og:image. However, Twitter Cards support features that Open Graph does not cover, including player cards for embedding video directly in the timeline, app install cards for promoting mobile applications, and summary cards with differently formatted layouts. Adding dedicated twitter:title and twitter:description tags also lets you craft platform-specific messaging, such as shorter titles optimized for Twitter character constraints or descriptions with different calls to action. The performance cost is negligible since meta tags add only a few bytes to your HTML head section, and the SEO benefit of complete social markup is well documented.
