Open Graph Previewer - Facebook/Twitter/LinkedIn Card Preview
Online Open Graph previewer. Enter OG tag content and preview how your page looks when shared on Facebook, Twitter, and LinkedIn.
TL;DR: Free online Open Graph previewer. Enter OG tag content and instantly preview share cards on Facebook, Twitter, and LinkedIn to catch truncation and image ratio issues. Local processing only.
For local tools, open DevTools → Network and search your input — it should not appear in requests.
Usage Guide
The card shown when you share a link into WeChat, X, Slack or Telegram reads the Open Graph (og:) and Twitter tags from the page head. This tool previews that card live — confirm title, description and image before shipping instead of discovering a broken image after.
1. Preview a share card
- Fill in the page URL, og:title, og:description, og:image and site name.
- Check the card: is the title truncated, the description complete, the image ratio right?
- Update the matching tags in your page head (this is a previewer — it does not modify your site).
2. Three frequent share-card problems
- Broken or blank image: og:image must be an absolute, publicly reachable URL — relative paths, intranet addresses and login-walled images all fail to fetch.
- Wrong ratio: platforms differ on the ideal og:image ratio (commonly 1.91:1); mismatches get cropped or padded.
- Changes not taking effect: platforms cache their crawls — force a re-scrape with each platform's debugger (Facebook Sharing Debugger, Twitter Card Validator, etc.).
3. The tags that actually drive click-through
Four tags carry nearly all the weight: og:title, og:description, og:image, and og:url. Everything else is edge-case plumbing. The image is where most posts lose the click: 1200x630 is the safe aspect (1.91:1), text under roughly 48px becomes unreadable in feed thumbnails, and center-crop assumptions differ across platforms — LinkedIn crops tighter than Twitter. After editing tags, use the platform debuggers (they force a re-scrape) or your shares keep showing the cached old card for days, which makes correct tags look broken.
FAQ
No. Share cards are rendered locally in your browser, and what you type stays on your machine.
Facebook, Twitter (X), and LinkedIn card styles. WeChat, Slack, and Telegram read the same og: and twitter tags when they build their share cards.
Platforms cache what they crawl, so an outdated card may linger after you change the tags. Once published, force a refresh with each platform's debugger tool.
Not necessarily. Hotlink protection and login walls can block platform crawlers — a passing preview doesn't prove your image host is reachable, so confirm the image URL is publicly accessible first.
For important campaign pages, prepare a common size like 1200×630 and keep key content inside a crop-safe area. Wrong aspect ratios get cropped, and an overlong title or empty description leaves the card short on information.
This tool handles how your link looks when shared on social platforms; pixel-level truncation of titles and descriptions in Google results is the meta-tag-pixel-checker's job. Share cards and search results are two separate chains — verify each.
Related Tools
Related Articles
Chinese Cryptographic Assessment (Miping) Self-Check Checklist: GB/T 39786, Layer by Layer
A pre-assessment framework for commercial cryptography application security evaluation: the four technical layers (physical, network, device, application) plus management, the quantitative red lines (algorithm/product/key compliance), the most common findings, and a remediation order ranked by points-per-effort.
SM2/SM3/SM4 in Practice: Choosing, Integrating, and Debugging Chinese National Cryptography
A field guide to Chinese national crypto: SM4 vs SM3 vs SM2, plus the integration traps that dominate real work — C1C3C2 vs C1C2C3, hex vs Base64, CBC IVs — with browser-local tools for known-answer checks.
Chinese National Cryptography (SM2/SM3/SM4/SM9/ZUC): A Developer's Introduction
Introduction to China's commercial cryptography: what SM2, SM3, SM4, SM9 and ZUC each do, how they map to RSA/SHA/AES, a selection decision tree, TLCP vs RFC 8998 boundaries, compliance drivers, and what browser tools can and cannot verify.