OG Images Generator for Articles
An article without an Open Graph card unfurls as a bare link in feeds — invisible to algorithms and indistinguishable from spam to readers. Paste the article URL and get a per-post 1200×630 card that uses the real headline, byline and brand.

Why choose Oginify
Built for the way modern teams publish at scale — per-post, brand-aware, and wired into any CMS without a plugin.
Pulls the real headline
Oginify fetches the article's actual <h1> and byline from the live page. No copy-paste, no manual override, no editor having to remember to set an image before publishing. What's on the page is what's on the card.
Survives at 600×314
Mobile feeds downsample OG cards to half size. The article preset uses oversized display type with a short kicker so the headline still reads when the card is the size of a postage stamp in someone's thumb.
Per-post, not per-blog
One generic 'the blog' card across 200 posts looks like spam and tells readers nothing. Re-run Oginify per URL, or wire the API into your publish flow so every new post gets its own card automatically.
Validate before you ship
A card that breaks on LinkedIn is worse than no card at all. The built-in Open Graph validator confirms X, LinkedIn, Slack and iMessage render the article exactly the way you intend before the post goes live.
Refreshes on edits
Title changed after a copy-edit? Hero photo swapped? Re-run the URL and the card updates in seconds. No CMS migration, no manual upload, no waiting on a deploy.
Works with every CMS
Oginify reads the rendered HTML, so it works with WordPress, Ghost, Substack, Sanity, Contentful, Notion and hand-rolled blogs alike. If the page renders in a browser, Oginify can read it.
SaaS · stacklane.com
For articles on SaaS sites
Product blogs on B2B SaaS sites compete with every other launch post in the feed — a stale brand-only card gets scrolled past in half a second. Oginify pulls the real post title and surfaces it on the card in display type, with the product wordmark as a quiet signature so the post reads as news from a brand, not marketing fluff.

E-commerce · kestrel & co
For articles on e-commerce sites
Editorial content on DTC sites — brand stories, look-books, behind-the-scenes — exists to lift the brand, but a flat platform card cuts off exactly that lift. Oginify renders an editorial-flavored card with a generous photographic backdrop and a serif headline, so the story unfurls as a magazine piece, not a product blurb.

Content & media · the meridian
For articles on content & media sites
Newsletter issues and magazine features need to look like a publication, not an email blast — inbox subscribers see the card on every share, quote-tweet and forward. Oginify keeps the masthead typography intact, uses a tall serif for the headline and stamps an issue or date kicker so the card sits inside the publication's visual system.

Dev tool · forge.dev
For articles on dev-tool & open-source sites
Engineering posts get shared on Hacker News and dev Slacks where any whiff of marketing kills the click. Oginify renders a terminal-flavored card with monospace headline, a faint scan-line texture and an accent line pulled from the brand — the card reads as something an engineer wrote, not something a growth team scheduled.

The prompts behind these four cards
Each card above started as a one-paragraph prompt. Here are the four we used — paste them into Oginify with your own URL and you'll get the same direction in your brand.
SaaS blog · stacklane.com / changelog
Generate a 1200×630 Open Graph card for a stacklane.com changelog post. Dark near-black background, tiny "stacklane / changelog" mono label top-left. Big white sans-serif display headline left-aligned reading "Introducing scheduled deploys", with a smaller muted gray sub-line beneath: "Roll out new versions on a schedule, with one-click rollback." Right side: a quiet faded UI fragment of a deploy timeline with three pill-shaped commits. Premium B2B SaaS, generous negative space, no decoration.
Brand story · kestrel & co / journal
Generate a 1200×630 Open Graph card for a kestrel & co journal brand story. Warm cream background, small dark espresso "kestrel & co · journal" serif label top-left. Left side: large dark espresso serif headline reading "Where the linen comes from", with a smaller italic serif line beneath: "A week in the mills of northern Portugal." Right side: a soft-focus photographic backdrop of folded oatmeal linen on a wooden table with natural window light and a long soft shadow. Editorial DTC magazine aesthetic, generous margins, no UI.
Newsletter · the meridian / issue 47
Generate a 1200×630 Open Graph card for The Meridian newsletter, issue 47. Off-white paper background with faint texture. Classical serif masthead at top reading "The Meridian" with thin hairline rules above and below, and a small mono date stamp at the right edge of the lower rule reading "Issue 47 · May 2026". Centered below: a tall serif headline "On attention, after the feeds", and beneath it one italic serif line: "A short letter on putting the phone down for an hour." Black ink only, no other color, newspaper editorial typography.
Engineering · forge.dev / blog
Generate a 1200×630 Open Graph card for a forge.dev engineering blog post. Pure black background with a very faint horizontal scan-line texture. Small mono label top-left reading "forge.dev / blog". Big white monospace headline left-aligned reading "Why we rewrote the scheduler in Rust", with a smaller muted gray monospace sub-line beneath: "Cutting tail latency from 240ms to 12ms with a work-stealing queue." Below the headline, a single thin horizontal green accent rule. Hacker / open-source aesthetic, pixel-perfect type, no decoration.
Article Open Graph FAQ
How per-article cards work, how to wire them into a publish flow, and how to keep them readable across every channel.
Do I need a different card for every article?
Yes. A single generic 'blog' card across hundreds of posts is the digital equivalent of a stock photo in a press release — it tells readers nothing about the actual content. Per-article cards lift CTR on social shares meaningfully because the card is the headline, not a placeholder.
Can I generate cards automatically when a post publishes?
Yes. Wire the Oginify API into the webhook your CMS fires on publish — WordPress, Ghost, Sanity, Contentful and Notion all support outbound webhooks. The post URL goes in, the og:image URL comes back, your CMS stamps it into the meta tags.
What if my article doesn't have a hero image?
Most articles don't — and that's fine. The magazine and newspaper presets are typography-led: they make the headline the hero and use the brand palette as background. The terminal preset doesn't need a photo at all; the headline plus an accent rule is the whole composition.
Will Oginify pick the right style automatically?
Yes. Oginify reads the article and proposes one default direction plus three alternatives. For a news-flavored post you get newspaper-first; for a long essay you get magazine; for an engineering writeup you get terminal. You can lock the preset per blog if you want every post in the same visual system.
Does it work with Substack, Beehiiv and Ghost?
Yes. All three render Open Graph meta tags on their hosted posts, and all three let you override the og:image URL via the post settings. Generate the card with Oginify, paste the URL into the post's OG image field, the unfurl uses it everywhere.
Stop shipping articles without a card
Paste any article URL and get a per-post 1200×630 Open Graph card in seconds. No signup, no CMS plugin.