Framework guide

Dynamic Open Graph images for Remix

Use a layout route or a loader to pass `og:image` into a `<meta>` export or a SEO component for each document.

Every framework only needs a stable, absolute HTTPS og:image. OGKit gives you one URL, production templates, and query parameters for titles, images, logos, authors, products, events, jobs, and code snippets.

Server-rendered metadata is the SEO boundary

Open Graph images only help distribution when the final HTML response already contains the metadata. Most scrapers do not wait for client-side JavaScript, so React hydration, client routers, and analytics callbacks are too late. Build the OGKit URL in the server route, loader, layout, view helper, or static generation step that owns the document head.

Use one deterministic image URL per canonical page

The strongest pattern is one stable 1200x630 image URL for each canonical URL. Put the same image in Open Graph and Twitter/X metadata, keep the title aligned with the visible H1, and include page-specific context such as author, product name, release version, or docs section. That gives Slack, Discord, LinkedIn, iMessage, and browser-assisted LLM crawlers the same topic signal as the page body.

When to choose hosted templates over custom renderers

Custom Satori, Puppeteer, or screenshot routes make sense when you need arbitrary layout control. Hosted templates make more sense when the business need is repeatable: blog cards, launch pages, changelogs, docs pages, product pages, and comparison pages that should look consistent without a renderer living in every codebase.

Implementation pattern

Generate the OGKit URL before the crawler sees the HTML. That can happen during static generation, in a server route, or in the framework metadata layer. Start with the API reference, deep guides, test the URL in the Playground, then validate the deployed page with the preview debugging tools.

export const meta: MetaFunction = ({ data }) => {
  const image = new URL("https://www.webmorp.art/api/og/article");
  image.searchParams.set("key", process.env.OGKIT_KEY!);
  image.searchParams.set("title", data.post.title);
  image.searchParams.set("subtitle", data.post.summary);
  const url = image.toString();
  return [
    { property: "og:image", content: url },
    { name: "twitter:card", content: "summary_large_image" },
    { name: "twitter:image", content: url },
  ];
};

Deeper Remix notes

Loaders own the truth

Derive card fields from the same loader data you render on the page so Slack titles match the H1. If a nested route overrides meta, ensure parent layouts do not clobber og:image with a homepage default.

Edge vs Node

Remix can run on many adapters. OGKit does not need Edge ImageResponse — only a place to build a string URL. That keeps adapters interchangeable.

Worked steps

Read title/summary in the route loader.
Build OGKit URL in meta() with process.env.OGKIT_KEY.
Return og:image + twitter:image.
Rescrape after content edits (see caching guide).

Checklist

Build the image in loader/meta code from route data.
Share the same URL in Twitter metadata.
Avoid client-only metadata updates.
URL-encode dynamic titles from loaders.

Common pitfalls

Missing twitter:image
Leaking keys to browser code
Not URL-encoding dynamic route data
Using relative image URLs in nested routes

When a hosted OG API makes sense

A hosted Open Graph image API is useful when you need consistent cards across many pages but do not want to maintain a custom renderer in every app. It is especially useful for docs, changelogs, launch pages, public customer pages, and content collections where the title and summary change often. For HMAC signing and rescrape workflows, see signed URLs and caching & rescrape.

Frequently asked questions

How do I add dynamic Open Graph images to Remix?

Build an absolute OGKit image URL on the server or during static generation, then place it in og:image and twitter:image metadata for each important page.

Can I use OGKit with Remix without a custom image route?

Yes. OGKit returns a normal 1200x630 PNG URL from template and query parameters, so you do not need to maintain a Satori, Puppeteer, or screenshot pipeline.

Where should I keep the OGKit API key?

Keep the API key in server-side environment variables, framework runtime config, or build-time secrets. Do not bundle it into client-side JavaScript.

I changed the title but Slack still shows the old card — what now?

Rebuild/redeploy so HTML has the new OGKit query, confirm with curl, then rescrape Facebook/LinkedIn. Slack often needs a new image URL (updated fields or v=). See /guides/troubleshooting.