Skip to content
ToolsMinify logo
All articles

Twitter Cards vs Open Graph - When You Need Both

Compare Twitter Card types with Open Graph tags: summary vs summary_large_image, OG fallbacks on X, image sizes, and when both tag sets belong in your head. Build twitter:* tags privately in the browser.

Updated November 14, 20268 min read

Use Twitter Card Generator - Free

Open the live tool and apply what you learned in this guide.

Open Twitter Card Generator

Social previews look simple - a title, a description, and an image - but two tag families drive them. Open Graph (og:*) is the shared base Facebook, LinkedIn, Slack, and most chat apps read. Twitter Cards (twitter:*) give X explicit control over card type and handles. X can fall back to Open Graph when twitter:* is missing, but Facebook and LinkedIn ignore twitter:* entirely. This guide compares card types, fallbacks, image sizes, and when both sets belong in the head. Build the X markup with the free Twitter Card Generator; for the full og:* walkthrough see Open Graph Tags Complete Guide.

Quick answer

Ship Open Graph on every public URL you share. Add twitter:card (summary_large_image or summary) plus matching title, description, and image when you care about X. Prefer absolute https images - about 1200 x 628 for large cards, square for summary. twitter:* wins on X when both exist; og:* still wins everywhere else. The tool page owns transactional twitter card generator searches; this article covers when and why both tag sets matter.

What each protocol controls

Open Graph defines og:title, og:description, og:image, og:url, and og:type (plus extras like og:site_name). Those tags shape the card on Facebook, LinkedIn, Slack, Discord, and many messengers. Twitter Cards define twitter:card and optional twitter:title, twitter:description, twitter:image, twitter:site, and twitter:creator. They only matter on X. Search engines still use the HTML title and meta description for the SERP - neither OG nor Twitter Cards replace those.

  • Open Graph - shared social base for Facebook, LinkedIn, Slack, and similar apps
  • Twitter Cards - X-specific layout (summary vs summary_large_image) and @handles
  • HTML title + meta description - Google SERP, not the share card
  • Emit both OG and twitter:* when the same URL will be shared on X and elsewhere

Twitter Card types - summary vs summary_large_image

twitter:card tells X which layout to render. Two values cover almost every marketing and docs page.

  • summary_large_image - wide hero image above the title. Best for blog posts, launches, and product stories when you have a landscape asset.
  • summary - compact card with a small square thumbnail beside the text. Better for docs, support links, and shares that should stay small in the timeline.
  • Older player and app card types are niche; skip them unless you have a media or install flow that needs them.
  • Pick the type that matches your image crop - a square hero on a large-image card looks stretched or cropped poorly.

How X falls back to Open Graph

If twitter:title, twitter:description, or twitter:image is missing, X can fill gaps from og:title, og:description, and og:image. A bare Open Graph object often still produces a usable X preview. The reverse is not true: Facebook and LinkedIn do not read twitter:* as a substitute for og:*. Start with OG, then add twitter:card so you choose summary vs summary_large_image instead of hoping the fallback picks a layout you like.

  • Missing twitter:title - X may use og:title
  • Missing twitter:description - X may use og:description
  • Missing twitter:image - X may use og:image
  • Missing twitter:card - layout is less predictable; set it explicitly
  • Only twitter:* present - X may work; Facebook and LinkedIn will not

Image sizes that actually work

Both protocols want absolute https URLs. Relative paths fail because social crawlers are not browsing your site with a base URL. Size and crop differ slightly by card type.

  • Open Graph / LinkedIn landscape - 1200 x 630 (about 1.91:1) is the usual target
  • summary_large_image - about 1200 x 628 works well; stay landscape and keep the subject centered
  • summary - square thumbnail, at least 144 x 144, ideally larger (400 x 400 or more)
  • Host images publicly - robots.txt blocks and login walls hide assets from crawlers
  • Keep files reasonably small; stale caches often need a new URL after you replace pixels

Same pixels, two jobs

One 1200 x 630 asset can serve og:image and twitter:image for a large-image card. If you also offer a summary card elsewhere, prepare a square crop instead of forcing the landscape file into a small thumbnail.

When both tag sets are needed

You need Open Graph whenever the URL might be pasted into Facebook, LinkedIn, Slack, or similar apps. You need Twitter Cards when you want a deliberate X layout, brand @site, or creator attribution - or when your OG image crop is wrong for summary_large_image and you want a different twitter:image. Most public marketing and blog URLs should emit both. Internal docs shared only in Slack can live on OG alone. X-only experiments can start with twitter:*, but adding OG costs little and covers the rest of the web.

  • Always: og:title, og:type, og:image, og:url (plus description when you have it)
  • For X control: twitter:card plus matching title, description, and image
  • For brand on X: twitter:site (@handle); optional twitter:creator for authors
  • Keep values consistent across protocols unless you intentionally diverge for network tone

A practical head markup checklist

  • Put tags in the document head on the exact public URL people share
  • Use absolute https for og:url, og:image, and twitter:image
  • Escape quotes and ampersands inside content attributes
  • Set twitter:card to summary_large_image or summary before you ship
  • Rescrape after changes - Facebook, LinkedIn, and X all cache the first fetch
  • Generate privately in the browser when draft copy should not hit a server

Build Twitter Card tags locally

SERP articles explain the difference; they cannot safely hold unpublished titles and image URLs. Generate the twitter:* HTML in your browser, then pair it with OG from the Open Graph generator.

Frequently asked questions

Does X still read Open Graph tags?

Yes. X can fall back to og:title, og:description, and og:image when twitter:* fields are missing. Dedicated twitter:card tags still give you explicit layout control.

Can I use only Twitter Cards?

Only if the URL will never be shared outside X. Facebook, LinkedIn, and Slack ignore twitter:* and need Open Graph.

What is the best Twitter Card image size?

For summary_large_image use a landscape image around 1200 x 628. For summary use a square of at least 144 x 144 (larger is safer). Always use an absolute https URL.

Should twitter:title match og:title?

Usually yes. Matching values keep previews consistent. Diverge only when you intentionally want a shorter or network-specific headline on X.

Is my copy uploaded?

Not on ToolsMinify. The Twitter Card Generator and Open Graph Tag Generator run in the browser, so draft titles and image URLs stay on your device.

Generate Twitter Cards without uploading

Open the free Twitter Card Generator, pick summary or summary_large_image, fill title, description, image, and optional @handles, then copy the HTML into your page head.

Use Twitter Card Generator - Free

Open the live tool and apply what you learned in this guide.

Open Twitter Card Generator

Related articles