Skip to content
Aback Launch
Guides9 min read

Open Graph Tags: the OG Tags, Image Size and Twitter Card Setup That Make Links Look Good

The open graph tags every page needs, the right og image size (1200 x 630), how LinkedIn, X, Slack, Discord and iMessage build a link preview, and how to refresh a stale card after you fix it.

Devvrat Hans

Founder

November 19, 2026
Open Graph Tags: the OG Tags, Image Size and Twitter Card Setup That Make Links Look Good

Open Graph tags are meta tags in your page's <head> that tell social networks and chat apps what to show when someone shares your link: og:title, og:description, og:image, og:url and og:type, plus twitter:card for X. Get them right and every share becomes a large card with your image and headline; get them wrong and you get a bare URL that few people click. Paste any page into the free Open Graph checker to see the card it will show on X, LinkedIn, Slack and Facebook, and which tags to fix.

Founders usually discover their OG tags on launch day, when the Product Hunt link, the LinkedIn post and the team Slack all show a gray box or last month's tagline. This guide covers the tags that matter, the right og image size, how each major platform reads them, and how to force a refresh when a platform keeps showing an old card.

What Open Graph tags are

The Open Graph protocol was introduced by Facebook in 2010 so any web page could describe itself as a rich object when shared. It caught on far beyond Facebook: LinkedIn, Slack, Discord, WhatsApp, Telegram, iMessage and most link preview systems read the same tags today. Our Open Graph glossary entry has the one paragraph version.

The tags are plain meta elements with a property attribute. They do not change how your page looks in a browser, and they are not a Google ranking factor. Their job is the click through rate of every shared link, which on launch day is most of your traffic.

The OG tags that matter

Here is a complete, minimal set for a product home page:

<meta property="og:title" content="Acme: invoices that chase themselves" />
<meta property="og:description" content="Send an invoice once. Acme follows up until it is paid." />
<meta property="og:image" content="https://acme.com/og/home.png" />
<meta property="og:image:width" content="1200" />
<meta property="og:image:height" content="630" />
<meta property="og:image:alt" content="Acme dashboard showing three paid invoices" />
<meta property="og:url" content="https://acme.com/" />
<meta property="og:type" content="website" />
<meta property="og:site_name" content="Acme" />
<meta name="twitter:card" content="summary_large_image" />
TagWhat it doesTips
og:titleThe headline of the cardCan differ from your title tag. Write it for a feed, not for Google. Under about 70 characters
og:descriptionOne or two lines under the titleSome apps show it, some hide it. State the benefit, not the feature list
og:imageThe picture, and the biggest part of the cardFull https:// URL, 1200 x 630 pixels, PNG or JPEG
og:urlThe canonical address of the pageMatch your canonical URL so likes and shares collect on one address
og:typeThe kind of objectwebsite for most pages, article for blog posts
og:site_nameYour brand nameShown above or below the title on several platforms
twitter:cardThe card layout on Xsummary_large_image for the big image; summary gives a small square thumbnail

The Open Graph spec lists four tags as required for every page: og:title, og:type, og:image and og:url. In practice, og:image is the one that decides whether the card looks like a card at all.

Do you need twitter: tags as well?

Mostly no. X falls back to og:title, og:description and og:image when the matching twitter: tags are missing. The one tag you really need is twitter:card, because without it X may choose the small summary layout. Add twitter:image only if you want a different picture on X, for example one cropped to its 2:1 ratio.

Writing the title and description

Your og:title does not have to repeat your SEO title. A search title is written to match a query; a social title is written to stop a scroll. "Acme: invoices that chase themselves" beats "Invoice Automation Software for Freelancers | Acme" in a LinkedIn feed. If you want the search side too, the title tag guide covers how to write that one.

The right og image size

Use 1200 x 630 pixels, an aspect ratio of 1.91:1. It is the size Facebook and LinkedIn use for large link previews and it displays well almost everywhere else. Check any image against it with the free OG image size checker, which tests the dimensions, the ratio, the file type and the file size.

PlatformLayoutWhat happens to a 1200 x 630 image
Facebook1.91:1 large previewShown in full
LinkedIn1.91:1 large previewShown in full
X (summary_large_image)2:1A thin strip trimmed from the top and bottom
Slack and DiscordImage inside an embedShown scaled down, often quite small
iMessage and WhatsAppImage above the titleShown, sometimes cropped toward a squarer shape

Because each app crops a little differently, design for the middle:

  • Keep text and logos inside a safe area about 60 pixels in from every edge.
  • Use large type. The card is often shown at a third of its real size, especially on phones.
  • Prefer high contrast over subtle gradients, which turn to mush after compression.
  • Keep the file small. PNG or JPEG under 5 MB is accepted by every major network, and a few hundred kilobytes loads faster in chat apps.
  • Set og:image:width and og:image:height. Facebook can then render the image on the very first share instead of waiting to download it.

If you do not have a designer, the free OG image generator draws a 1200 x 630 image from templates (gradient, minimal, split or launch announcement) with your title, subtitle, colors and optional logo, and lets you download it as PNG. The image is drawn in your browser, so your logo is not uploaded anywhere. For X specifically, the X card image size checker tests the 2:1 layout.

Every platform sends its own crawler to fetch your page when a link is first shared, reads the tags, and stores the result. The details differ.

LinkedIn

LinkedIn reads og:title, og:image and og:description and shows a large 1.91:1 image with the title under it. It caches the preview, so a change you make after the first share does not appear until LinkedIn refetches. Its free Post Inspector tool shows what LinkedIn sees and refetches the page when you inspect it.

X (Twitter)

X reads twitter:card to pick the layout and falls back to Open Graph for the rest. Link cards on X now carry very little text, so the image has to do the selling: put your headline in the picture. X's developer documentation says it recrawls card tags roughly every seven days, and the old Card Validator no longer shows previews or refreshes the cache.

Slack

Slack "unfurls" links by fetching the page and reading Open Graph and twitter: tags, then shows the site name, title, description and a scaled image. It caches unfurls, and there is no public button to refresh them.

Discord

Discord builds an embed from the same tags. It also reads the theme-color meta tag for the colored bar on the side of the embed, a cheap way to make your links look branded in community servers.

iMessage

Apple's Messages builds the preview on the sender's device, not on a server, and sends it along with the message. It reads og:title and og:image and falls back to the page title and icon. Because the sender's phone does the work, a slow or heavy page can produce a plain link, so keep your image light.

You fixed the tags, but the card still shows the old image. That is caching, and each platform clears it differently:

  1. Confirm the live page is right. Run it through the Open Graph checker. If the checker shows the old tags, your CDN or framework is serving a cached page, and no platform tool will help until you purge it.
  2. Facebook: paste the URL into the Sharing Debugger and press "Scrape Again".
  3. LinkedIn: inspect the URL in Post Inspector, which fetches it fresh.
  4. X, Slack, Discord: there is no reliable public refresh. Share a slightly different URL, such as adding ?v=2 to the end, which the platform treats as a new page.
  5. Change the image file name when you change the image. og-home-v2.png avoids every image cache along the way, including your own CDN's.

The cleanest fix is prevention: check the card before the first share, especially before a launch post goes out. The Product Hunt launch checklist includes that step for a reason.

Common Open Graph mistakes

  • Relative image URLs. /og.png works in a browser but many crawlers ignore it. Use the full https:// address.
  • Tags added by JavaScript. Most social crawlers do not run scripts. If a single page app injects the tags after load, the crawler sees nothing. Render them on the server or at build time.
  • The image is blocked or behind a login. If robots.txt disallows your image folder, or the image needs a cookie, crawlers cannot fetch it. The robots.txt guide explains how to check.
  • One image for every page. A site wide default is fine for the home page, but a blog post or launch page shared with the home page image wastes the card. Give important pages their own image.
  • og:url pointing somewhere else. A template that sets og:url to the home page on every page makes some platforms show the home page card for every link.
  • Duplicate tags. A plugin and your theme both writing og:image leaves the platform to pick one, often the wrong one.

Generate and check your tags

The fastest path from nothing to a good card:

  1. Design the image at 1200 x 630 with the OG image generator and upload it to your site.
  2. Fill in your title, description, image and URL in the Open Graph generator. It writes the og: and twitter: tags and shows a live preview of the card as you type.
  3. Paste the tags into your page's head and deploy.
  4. Check the live page with the free Open Graph checker, fix anything it flags, and only then share the link.

FAQ

What is the best og image size?

1200 x 630 pixels, a 1.91:1 ratio, as a PNG or JPEG under 5 MB. It shows in full on Facebook and LinkedIn and is only lightly cropped on X, Slack, Discord and iMessage.

What are the required Open Graph tags?

The Open Graph spec requires og:title, og:type, og:image and og:url. Add og:description and og:site_name for a complete card, and twitter:card set to summary_large_image so X shows the large image.

The usual causes are a relative og:image URL, an image the crawler cannot reach (blocked, behind a login or very slow), tags injected by JavaScript, or an old cached card. Check the live page with an Open Graph checker first, then refresh the platform's cache.

Do Open Graph tags help SEO?

Not directly. Google does not use them to rank pages. They matter for the clicks you get from social and chat shares, and those visits, links and mentions are what help over time.

On LinkedIn, inspect the URL in Post Inspector. On Facebook, use the Sharing Debugger and press "Scrape Again". Both refetch the page and update the card for new shares.

What is a twitter card?

A twitter card is the preview X shows for a link. The twitter:card tag picks the layout: summary for a small square thumbnail, summary_large_image for a wide image. X reads the rest from your Open Graph tags if no twitter: versions exist.

Written by

Devvrat Hans

Founder

Share
Newsletter
Get the Monday launch email
The week's new launches and winners, in one short email.

By subscribing, you agree to get our newsletter by email. Unsubscribe any time in one click. See our Privacy policy and Terms.

Launch your startup on Aback Launch

Get a launch page that search engines and AI assistants can read, a place in the weekly launch list, and a review by a real person. Free to join.