OGP Tag Generator (Auto Output for og:title, og:image, and More)

Enter URL, title, description, and image URL. Generate Open Graph and Twitter Card meta tags in one place.

Copy and paste ready Built-in preview Image and cache guidance

How to use

  1. Open the tool and enter canonical URL, title, and image URL.
  2. Optionally add description, site name, and Twitter settings.
  3. Copy the generated meta tags and paste them into your page head.
  4. Check preview and notices, then adjust image ratio or cache strategy if needed.

What is OGP?

Open Graph Protocol (OGP) is metadata used by social platforms and chat apps to render link previews.

By setting og:title, og:description, og:image, and related tags, you can influence how shared URLs appear.

Combining OGP with Twitter Card tags helps keep preview behavior more consistent across platforms.

Image size guidance (for more stable preview rendering)

Meta platforms guidance (reference)

  • Minimum reference: 200×200.
  • Often stable: 1200×630 or larger, at least 600×315.
  • Target aspect ratio around 1.91:1.
  • Image file size guidance includes 8MB or less.

X card guidance (reference)

  • summary_large_image generally targets about 2:1 ratio.
  • Reference range: minimum 300×157, maximum 4096×4096.
  • File size guidance includes less than 5MB.
  • Use JPG/PNG/WEBP/GIF where supported.

When updates do not appear (cache and re-scrape)

  • Social crawlers may cache fetched metadata. Use each platform's debugger/inspector to request re-scrape.
  • If image replacement does not appear, changing the image URL can help (filename update or query string).
  • Setting og:image:width and og:image:height may improve rendering stability in some cases.

FAQ

Can this generate Twitter Card tags too?

Yes. It can output twitter:card and related tags together. A minimal mode is also available.

What image size should I use?

Use practical guidance by destination. Meta-oriented previews often use around 1.91:1 (for example 1200×630), while X summary_large_image often uses around 2:1 (for example 1200×600).

Why are changes not reflected?

Most cases are cache-related. Re-scrape via platform tools and consider changing image URL after replacement.

Related tools