OG Images (Open Graph)

The preview image that decides whether someone clicks your link — or scrolls past it

← E-commerce & Internet Marketing knowledge base  ·  Tech knowledge base

What Is an OG Image?

When you paste a URL into X (Twitter), LinkedIn, Facebook, Slack, Discord, or iMessage, the platform fetches metadata from your page and renders a preview card — title, description, and a large thumbnail image. That thumbnail comes from the og:image Open Graph meta tag.

Same idea applies to Twitter Cards (twitter:image) and messaging apps that read Open Graph. One image, many surfaces.

If you don't set it, platforms either show a random image scraped from your page (often a logo, footer graphic, or nothing useful) or a blank gray box. Both kill click-through rate and make you look amateur.

Why It Matters for Marketing & Trust

Click Conversion

A strong OG image can 2–3× click-through on shared links. You're competing with every other post in the feed — the preview is your billboard.

Brand Recognition

Consistent colors, logo, and typography build instant recognition before anyone lands on your site. They know who they're clicking.

Trust Signal

Missing or broken OG images signal "someone didn't finish this site." A polished preview says professional, intentional, worth my time.

Content Marketing ROI

You already wrote the article, built the product page, or recorded the video. OG image is the packaging — without it, distribution underperforms.

This is why we're standardizing OG images across our properties. Too many of our sites still ship without a proper default — and every share is a missed conversion.

Dimensions & Technical Specs

Platform / Use Recommended Size Aspect Ratio Notes
Open Graph (universal) 1200 × 630 px 1.91:1 The safe default for Facebook, LinkedIn, Slack, most crawlers
X / Twitter (large image) 1200 × 675 px (or 1200 × 630) 16:9 or 1.91:1 summary_large_image card — 1200×630 works fine in practice
Minimum 600 × 315 px 1.91:1 Below this, previews may look blurry or get rejected
File size Under 5 MB (aim < 300 KB) JPG for photos, PNG for text-heavy graphics; compress aggressively
Safe zone Keep key text/logo inside center 80% Some platforms crop edges on mobile

Required Meta Tags

<!-- Open Graph -->
<meta property="og:title" content="Your Page Title" />
<meta property="og:description" content="One compelling sentence." />
<meta property="og:image" content="https://yoursite.com/og/your-page.jpg" />
<meta property="og:image:width" content="1200" />
<meta property="og:image:height" content="630" />
<meta property="og:url" content="https://yoursite.com/page/" />
<meta property="og:type" content="website" />

<!-- Twitter / X Card -->
<meta name="twitter:card" content="summary_large_image" />
<meta name="twitter:title" content="Your Page Title" />
<meta name="twitter:description" content="One compelling sentence." />
<meta name="twitter:image" content="https://yoursite.com/og/your-page.jpg" />

Critical: og:image must be an absolute URL (full https:// path). Relative paths break on most platforms.

Design Tactics That Convert

  • One clear headline — readable at thumbnail size. Max 6–8 words. No tiny body copy.
  • High contrast — dark text on light background or white text on bold color. Feeds compress images; subtle gradients disappear.
  • Brand anchor — logo or wordmark in a consistent corner. Same position on every OG image builds recognition.
  • Human face (when relevant) — eyes draw clicks for personal brands, podcasts, and thought leadership.
  • Product hero shot — for e-commerce and launches, show the product large and centered (like mockup-driven campaigns).
  • Category color coding — AI content = one palette, e-commerce = another. Scannable in a busy Slack channel.
  • No critical info at edges — platforms crop differently; keep logo and headline in the safe zone.
  • Template system — one Figma/Canva template with swappable headline, image, and accent color. Ship OG images in minutes, not hours.

What to Avoid

  • Tiny text that becomes illegible in the feed
  • Busy screenshots with no focal point
  • Defaulting to a generic profile photo for every page (we're guilty of this on MikesBlogDesign — one image for everything)
  • Stock photos with no connection to the content
  • Forgetting to update OG when you update the page title

Default vs. Per-Page OG Images

Strategy When to Use Trade-off
Site-wide default Every site should have at minimum one branded fallback Better than nothing; all pages look the same when shared
Per-page / per-article High-traffic pages, product launches, blog posts you promote Highest CTR; more design work unless templated
Auto-generated Astro/Next.js OG image routes, or tools like Bannerbear, Placid, Vercel OG Scales to hundreds of pages; needs setup once

Our stack on MikesBlogDesign uses /images/mb-og-opengraph.jpg as the site-wide default in BaseLayout.astro, with per-category and per-page overrides where it matters. Next step: custom OG images for every page we actively promote.

Implementation Checklist (Every Site)

  1. Create a 1200×630 branded default OG image — logo, site name, tagline
  2. Add og:image, og:title, og:description, og:url to your base layout
  3. Add twitter:card = summary_large_image and twitter:image
  4. Use absolute URLs for all image paths
  5. Allow per-page override via layout props (title, description, image)
  6. Test every important URL with:
  7. Re-scrape after deploy — platforms cache OG metadata aggressively
  8. Build a template so new pages get custom OG images without a design bottleneck

Astro Pattern (Per-Page Override)

Extend your layout props so any page can pass a custom OG image:

// BaseLayout.astro — add ogImage prop
export interface Props {
  title: string;
  description?: string;
  ogImage?: string;  // optional per-page override
}
const ogImage = ogImage || 'https://mikesblogdesign.com/images/mb-og-opengraph.jpg';

<meta property="og:image" content={ogImage} />
<meta name="twitter:image" content={ogImage} />

// Any page.astro
<BaseLayout
  title="My Article"
  description="Why OG images matter."
  ogImage="https://mikesblogdesign.com/og/my-article.jpg"
>

For scale, consider Astro's dynamic OG image generation or a build script that generates images from page titles.

Portfolio Audit: Sites That Need OG Defaults

Every property we share publicly should pass the "paste in Slack" test. Before promoting a link, check:

  • Does a preview image appear?
  • Is the title accurate (not duplicated site name twice)?
  • Does it look on-brand?
  • Would you click it?

This applies to ExcaliburBrothers.com, marketplace listings, new launches like EB Men's Care, and every blog article we post on X.

Key Takeaways

  • OG image = your link's packaging in every social feed and chat app
  • Standard size: 1200 × 630 px, under 300 KB, absolute HTTPS URL
  • Every site needs a default; high-value pages need custom images
  • Design for thumbnail size: big headline, high contrast, brand anchor, safe zones
  • Test with OG debuggers after every deploy — caches lie
  • Template + props pattern scales across a portfolio without a designer per page

Related Guides

Backlink Building Framework

OG images improve click-through when your links appear in outreach, guest posts, and resource pages.

Read the framework →

Marketing Trends 2025

Distribution and content systems — OG images are part of the packaging layer.

Read the playbook →

The Distribution Engineer

Treat share-preview assets as distribution infrastructure, not an afterthought.

Read the deep dive →

How to Make Good Content

Content quality gets wasted without packaging that earns the click.

Read the guide →

Case Studies

Case study pages shared on social need custom OG images with results headlines.

Read the guide →

Excalibur Brothers Men's Care

New product launches — lifestyle mockups are built to become OG/social creatives.

View brainstorm →

Browse more in E-commerce & Internet Marketing and Tech.