Open Graph Meta Generator

Web

Build Open Graph and Twitter Card meta tags with a live preview, so you can see exactly how share cards render before you ship the page. Copy the tags.

Open Graph + Twitter Card · social-ready meta tags
Configure
HTMLGenerated tags
<!-- Open Graph -->
<meta property="og:title" content="My Amazing Article" />
<meta property="og:description" content="A short, compelling description shown when this page is shared on social media platforms." />
<meta property="og:url" content="https://example.com/articles/my-article" />
<meta property="og:image" content="https://oltool.net/banner.png" />
<meta property="og:site_name" content="Example Site" />
<meta property="og:type" content="article" />
<meta property="og:locale" content="en_US" />

<!-- Twitter Card -->
<meta name="twitter:card" content="summary_large_image" />
<meta name="twitter:site" content="@example" />
<meta name="twitter:title" content="My Amazing Article" />
<meta name="twitter:description" content="A short, compelling description shown when this page is shared on social media platforms." />
<meta name="twitter:image" content="https://oltool.net/banner.png" />
Social preview
example.com
My Amazing Article
A short, compelling description shown when this page is shared on social media platforms.

About Open Graph Meta Generator

Whether a link shows a title, description, and large image when shared to WeChat, Twitter, LinkedIn, or Slack depends on the Open Graph tags in the page head. This tool generates a complete set of og: and twitter: meta tags locally in your browser from the title, description, image, URL, and type you enter, ready to paste into the head. It focuses on the Open Graph protocol (distinct from a general Meta Tag generator) to help you craft attractive social share cards, assembling everything on your machine with nothing uploaded. The card shown when a page is shared into a chat app or social platform is decided by a set of metadata tags: title, description, thumbnail and page address. How complete those tags are determines whether the card is something worth opening or a bare link nobody touches, which makes this a small effort with an immediate payoff in content operations. Several constraints are hard requirements. The address must be absolute, since relative ones fail to resolve on most platforms; the image needs a publicly reachable absolute URL matching the platform's dimension and format rules, or it gets cropped, stretched or omitted entirely. And title and description must stay inside the truncation range, because an overlong description is cut into a semantically incomplete half sentence that lowers click intent. None of this concerns the quality of the page copy, it is pure technical requirement. Practical notes: Set tags per language rather than hoping the platform translates. When one piece of content is reachable at several addresses, give each its own canonical address or a platform may treat them as duplicates and merge the display, so a shared card points somewhere else. Do not rely on an editor preview, but send the link to the target platform and look, because platforms read the same tags with different priority and only a real share reveals the outcome. Limits: These tags do not affect search ranking, and treating them as a ranking lever is a misunderstanding; they influence click-through in sharing contexts. Platforms also change their parsing, ignoring certain tags in favour of their own heuristics, so never depend on one tag for the final result and make sure title and image each stand alone. The content is also public in the page source, so never put internal addresses or authenticated parameters in it. Data and privacy: metadata is public by nature, but the image URL used during generation may point at an unreleased asset store, so confirm it is publicly reachable first. This tool assembles the tag text in the browser, uploads nothing and works offline. A common misuse is previewing only in an editor rather than actually sharing: platforms read the same tags with different priority, and only a real share reveals the outcome. Another is unmet image requirements — an unreachable URL, a wrong ratio, or a platform-cached old version — which leaves the card without a thumbnail; after a change you must refetch or test a different link.

How It Works Internally

The card is decided by head tags, so three hard constraints decide success: the address must be absolutely reachable, the image must be publicly fetchable and match expected dimensions and ratio, and title and description must fall inside the truncation range. Platforms also cache what they fetched, so after a change you must refetch or test a different link or you keep seeing the old card.

InputOne tag set reused across several pages
OutputPlatforms key uniqueness on the address and may merge duplicates, so sharing page A shows the title of page B

Measured on This Page

og fieldsSix of the seven og:* fields verified one by one, values equal to the inputs
og:image &An image URL with ?p=1&q=2 escapes & to &amp;, which scrapers restore
Twitter blocktwitter:card=summary_large_image, twitter:site=@handle and title synced with og:title
Round-tripA title containing quotes, &, < and > parses back identical to the original
DefaultsThe sample image defaults to an on-site asset (avoiding third-party image-host timeouts), type defaults to article

Open Graph and Twitter Card are the two sharing-card protocols: Facebook/WeChat/DingTalk read og:*, X/Twitter prefers twitter:* and falls back to og:*. This page emits both blocks with synced fields. Three practical points: og:image should be 1200x630 and an absolute URL (most scrapers ignore relative paths); og:url should be the canonical address, consistent with <link rel=canonical>, or share counts split; and after changing tags re-scrape with each platform's debugger (Sharing Debugger / Card Validator) or the cached old card persists for days.

How this was measured: Same method as meta-tag: special-character inputs plus html.parser tag-by-tag comparison across og:title/description/url/image/site_name and twitter:card/title — seven checks; URLs carry query strings to verify & preservation. · Measured 2026-10-30

How to Use

  1. Open "Open Graph Meta Generator"
  2. Enter the title, description, page URL and image
  3. Add site name, type, locale and Twitter card style
  4. Compare the result in the social preview card
  5. Copy the generated OG and Twitter tags

Use Cases

  • Share cards — Generate og tags for an article or landing page so links show a big-image title preview on social platforms.
  • Twitter large image — Set twitter:card to summary_large_image so tweets display a striking banner card.
  • Multilingual sites — Generate tags with og:locale per language page to improve sharing abroad.
  • E-commerce products — Use og:type product so product links carry an image and title when shared.
  • Bulk templating — Produce one standard template, then swap title and image fields to apply it across pages fast.
  • Social preview debug — Generate og tags with placeholder values and test how the preview renders on a social sharing debugger.
  • Video/article embeds — Configure og:video or og:audio tags so media links show inline players on supported platforms.

FAQ

How do Open Graph tags differ from ordinary meta tags?

Open Graph is a protocol from Facebook, widely adopted by social platforms, using property="og:*" to control share previews; our Meta Tag generator leans toward SEO tags like description, keywords, and viewport — different purposes.

What size should og:image be?

Use 1200x630 (about 1.91:1); most platforms crop to it, and too-small images may be ignored or shown small. Prefer an absolute URL and make sure crawlers can access the image publicly.

Why does sharing still show old content after I changed the tags?

Social platforms cache crawl results; use the matching debugger (Facebook Sharing Debugger, Twitter Card Validator) to re-scrape and refresh the cache before new content appears.

Are twitter: tags required?

Not required, but they give X/Twitter a nicer card style. Twitter falls back to og: tags when twitter: tags are missing, so providing both is safest.

What should og:url contain?

The page's canonical absolute address (with https) as the content's unique identifier, so multiple URLs with tracking parameters are not treated as different pages and share counts aggregate correctly.

The card differs between a chat app and another platform. Do I need separate tags?

Yes. Platforms read slightly different tag sets, some preferring one social group and some the other, and some apply their own post-processing. Write both sets with matching content and test on each target platform. Configuring one set and expecting identical results everywhere typically fails on at least one of them.

What happens if the title is too long or too short?

An overlong title is truncated by the platform at a point you do not control, sometimes mid-keyword, which lowers click intent; a very short one carries too little information for a reader to judge whether to open it. Aim for the display width of each target platform and put the essential words first, because truncation always happens at the tail. The same applies to the description, where leading key points beat trailing flourish.

OG tags are set but shares still show no image?

In order: the image URL must be an absolute, publicly reachable address (relative paths fail); platforms enforce minimum sizes (WeChat from 300×300, Facebook recommends 1200×630); and platforms cache aggressively, so wait for expiry or trigger a re-scrape.