Your title here
Your description here
<meta property="og:title" content="" /> <meta property="og:type" content="website" />
How to use
01
Auto-fill from an existing page
Paste the address into the URL box and click Auto-fill. The tool reads any og:* tags already on the page, falling back to the plain title and description when they're absent.
02
Adjust the six og fields
Edit og:title, og:description, og:url, og:image, og:type, and og:site_name. The social-card preview below updates live, cropping your image to the 1.91:1 ratio platforms use.
03
Copy the OG tags block
When the preview looks right, use the copy button on the OG tags panel and paste the block into your page's head, above any script tags if possible.
Why Open Graph Generator
- Auto-reads existing og:* tags as a starting point.
- Live preview shows the social-card style render.
- Outputs spec-compliant OG markup.
Common questions
Which og tags does the generator output?
Up to six: og:title and og:type always, plus og:description, og:url, og:image, and og:site_name whenever you've filled them. As an og meta tags generator it skips empty fields entirely rather than emitting blank content attributes, so the output stays clean.
What size should the og:image URL point to?
1200 by 630 pixels is the safe answer, which is the 1.91:1 ratio the preview here crops to. Facebook and LinkedIn both render that shape, and larger images scale down fine. Below about 600 pixels wide some platforms demote your card to a small thumbnail layout.
Does the open graph generator read tags my page already has?
Yes. Auto-fill prefers existing og values, then falls back to the page's title tag and meta description when the og versions are missing. That means you can use it to upgrade a half-tagged page: the good values carry over and you only write what's absent.
Can it work as a social preview tags generator for X as well?
Partly. X reads og:title, og:description, and og:image as fallbacks, so the block from this tool gives you a working card there. What og markup can't express is the twitter:card type, which controls the layout. For that, the Twitter Card Generator on this site builds the twitter:* set.
Why does og:type default to website?
Because that's correct for most pages: homepages, landing pages, product pages, tools. Change it to article for blog posts and news stories, which lets platforms attach publish metadata. The field is free text, so profile, video.other, and the rarer types work too.
Is the social-card preview pixel-identical to Facebook's render?
It's a close approximation, not a screenshot of Facebook. Fonts, spacing, and title clamping differ slightly per platform and per device. The preview's job is catching the big problems, a cropped image or an overlong og:title, before you ship. For a per-platform view of a live URL, use the Open Graph Inspector.
What happens if I leave og:site_name or og:description empty?
Those lines simply don't appear in the output block. Both tags are optional in the spec. Platforms fall back to showing your domain instead of a site name, and some cards render with no description at all, which looks sparse but works.