share Open Graph & Twitter Card Generator star

How It Works

The Open Graph protocol was introduced by Facebook in 2010 so any web page could describe itself as a rich social object — what title, description, image and site name should appear when someone pastes the link into a feed or chat. This tool generates the four load-bearing tags (og:title, og:description, og:image, og:url) plus the matching twitter: set, and renders a live preview of the resulting card so you see what Facebook, LinkedIn, WhatsApp or X will actually show before you publish anything.

The og:type field (website, article, product...) isn't cosmetic — some platforms change the card's behavior based on it: an article type can surface an author/date line, a product type can trigger price display on platforms that support Open Graph commerce extensions. Concrete example: a recipe page set to og:type=article with a 1200×630 og:image gets a full-width photo card on X (via twitter:card=summary_large_image) and a matching preview on WhatsApp — set it wrong or leave og:image out, and most platforms fall back to guessing, usually picking the first image on the page or nothing at all.

Beyond the core four tags, a few optional fields fine-tune the result: og:site_name shows your brand next to the title on some platforms, og:locale sets the language/region (en_US, tr_TR) so multilingual sites render the right variant, and twitter:site attributes the card to an account handle on X. The twitter:card value itself has a third option beyond summary and summary_large_image — player — for embedding video or audio directly in the timeline, though it needs additional player-specific markup this generator doesn't cover. Cache duration also varies by platform: some debuggers refresh within a day of a fresh scrape, while other platforms can hold onto a stale preview for a week or more since they cache per-link rather than per-crawl, which is why a debugger-forced re-scrape is often the only fast fix.

Things to Know

• 1200×630px (a 1.91:1 ratio) is the safe universal image size across platforms; keep the file under roughly 1MB so it loads reliably, and always use an absolute URL (https://...) — relative paths silently fail.
• Caching is the most common complaint: once a platform has scraped a URL, it can keep showing the old title or image for days even after you fix the tags. Facebook's Sharing Debugger, LinkedIn's Post Inspector and similar tools force a fresh scrape.
• X mostly falls back to Open Graph values for title, description and image, but twitter:card is its own setting (summary vs. the full-width summary_large_image) and won't be inferred — set it explicitly.
• No tags at all doesn't mean no preview — the platform guesses from whatever it finds on the page, and that guess is rarely flattering.
• og:url should point to the canonical version of the page — pointing it at a tracking-parameter URL or a redirect target splits the share signal across two different addresses instead of consolidating it on one.
• Test on more than one platform before shipping: Facebook, LinkedIn and X each parse Open Graph slightly differently, and a card that looks right on one can crop the image or drop the description on another.