Open Graph Tag Generator
Fill in the form and watch the share card render the way Facebook and LinkedIn will draw it. The tool checks your image dimensions against the 1200 by 630 standard and outputs a copy-paste tag block.
Recommended 1200 × 630
How the preview works
The card mimics the link preview Facebook and LinkedIn render: image on top, domain in uppercase, then your bold title and gray description. When you paste an image URL, the tool loads it in your browser, reads the actual pixel dimensions, and flags anything below 1200 by 630 (small) or 600 by 315 (will render as a thumbnail, not a card). Nothing is uploaded; the image loads straight from its URL into your browser.
Getting og: tags right
- Absolute URLs only. og:url and og:image must be full URLs with the scheme. Relative paths are the most common reason a card fails to render.
- Match og:url to your canonical. Share counts consolidate on og:url the way ranking signals consolidate on the canonical.
- Pick the right og:type. Use article for posts so platforms can show author and date, website for everything page-like, and product or profile when the page genuinely is one.
- Rescrape after changes. Platforms cache cards aggressively. Use Facebook's Sharing Debugger or LinkedIn's Post Inspector to force a refresh.
Frequently asked questions
What size should my og:image be?
1200 by 630 pixels is the standard, a 1.91:1 ratio. Facebook's hard minimum is 200 by 200, but anything under 600 by 315 renders as a small thumbnail instead of a full-width card. Stay at 1200 by 630 or larger at the same ratio and keep the file under 8 MB.
Why isn't Facebook showing my image?
Almost always caching. Facebook scrapes a URL once and serves the cached card for weeks, so changes to your tags do not show up on their own. Paste your URL into Facebook's Sharing Debugger and hit Scrape Again to force a refresh. Also check that the image URL is absolute, publicly reachable, and not blocked by robots rules.
Should og:url match my canonical URL?
Yes, in nearly every case. og:url tells social platforms which URL identifies the content, so likes and share counts consolidate on it the same way a canonical consolidates ranking signals. Point both at the same clean, absolute URL and the two systems stay in agreement.
Do I need og: tags if I already have Twitter cards?
Yes. It works in the other direction: X falls back to og: tags when twitter: tags are missing, but Facebook, LinkedIn, WhatsApp, Slack, and Discord all read og: tags and ignore the twitter: namespace. The og: set is the foundation, with twitter: tags as an optional override.