Open Graph Tag Generator

Create Open Graph meta tags for perfect social media previews on Facebook, Twitter, and LinkedIn.

How to Use Open Graph Tag Generator

1

Enter page details

Fill in the title, description, image URL, and page URL.
2

Choose OG type

Select website, article, product, or another Open Graph type.
3

Preview the card

See how your link will appear when shared on social media.
4

Copy the meta tags

Click copy to grab the Open Graph meta tag HTML code.

Tested tool guide Tested browser tools Checked August 16, 2026

What Open Graph Tag Generator does, with a checked example

Fill in a page title, description, image URL and canonical address, and this tool returns the <meta> tags that social platforms read when your link is shared. Each value becomes a property/content pair following the Open Graph protocol, with Twitter card equivalents alongside. The thing most people get wrong: og:image must be an absolute URL the platform's crawler can fetch publicly - a relative path or a localhost URL silently produces a share with no picture. And because every major platform caches scraped pages, corrections never appear the moment you save them.

Worked example

A concrete input and expected output from the current implementation.

Input

Page URL: https://bee2.io/pricing/
Site name: Bee2
Title: Bee2 Pricing
Description: Simple cloud backup for small teams. From $5 per month.
Image: https://bee2.io/img/og-pricing.jpg

Expected output

<meta property="og:title" content="Bee2 Pricing">
<meta property="og:type" content="website">
<meta property="og:url" content="https://bee2.io/pricing/">
<meta property="og:image" content="https://bee2.io/img/og-pricing.jpg">
<meta property="og:description" content="Simple cloud backup for small teams. From $5 per month.">
<meta property="og:site_name" content="Bee2">

Each field maps one-to-one onto a property/content pair, so the tags mirror exactly what you entered. og:type defaults to "website" when left blank, and og:url fixes the canonical address that platforms use as the permanent ID of the object, so shares from any page path collapse into one.

How the result is produced

Field to tag mapping

Each form field maps directly to one meta tag: the title becomes og:title and twitter:title, the description becomes og:description and twitter:description, the image URL becomes og:image and twitter:image, and the page URL becomes og:url. The generator does not analyze your page or fetch anything - it wraps exactly what you type into property/content pairs, so the resulting preview is only as accurate as the values you supply.

What happens after you paste

The generated tags sit inert in your HTML until a platform's crawler fetches the page, which happens when someone shares the link. Facebook, X, LinkedIn, Slack and messaging apps each scrape the head, read the og: and twitter: properties, and cache the result - Facebook for roughly 24 hours or until you force a rescrape through its debugger. The generator cannot see or change that cached card.

Good uses

Publishing a new blog post or product page: generate the tags once, paste them into the head, and the first person to share the link gets the intended headline and image instead of whatever text the crawler scrapes.
After a redesign or a URL move: regenerate og:url and og:image so shares point at the new canonical address instead of an old, broken thumbnail.
Debugging a bad share card: re-enter the page's current values to review which tags exist and which are missing - usually the image - before using a platform debugger to rescrape.

Limits and checks

Nothing is verified at generation time. A typo in the image URL or a missing https produces valid-looking tags and a broken card. Confirm every URL resolves before publishing, because the platforms will not tell you.
A tag generator cannot fix stale previews. Every platform caches scraped pages for hours or longer, and old shares keep their old card. Editing the tags only affects future scrapes, not anything already shared.
Dimension and length limits are invisible in the output. Titles beyond roughly 95 characters truncate on Facebook, images under 200x200 pixels are rejected, and anything far from the recommended 1200x630 crops awkwardly. The generated tags look identical either way.

Common questions

Will my links work on WhatsApp, Slack and iMessage too?

Mostly yes. WhatsApp, Slack, Discord, Telegram and iMessage all read Open Graph tags and render a card with your title, description and image. The catch is that these apps cache aggressively and each has quirks - WhatsApp will sometimes drop the image or fall back to a plain link, and X prefers its twitter: tags over og:. Test a real share on each network you care about before relying on it.

Why does my image still not show after I added the tags?

Three usual causes: the image URL is relative or behind a login, so the crawler cannot fetch it; the image is smaller than 200x200 pixels or larger than 8MB, which Facebook rejects; or the platform is showing a cached scrape from before your edit. Force a fresh fetch with Facebook's Sharing Debugger before assuming the tags themselves are wrong.

References and verification

The example and behavioral notes were checked against the browser implementation. Standards and primary references below define the relevant format, formula, or platform behavior.