FAQ Open Graph Image Template
An FAQ card with a help center chip, question title, and answer preview.
An FAQ card with a help center chip, question title, and answer preview.
Search blocks by description or jump to a page.
Every Open Graph image template is included with Basic and Pro. Pick a plan to copy the code, install with the CLI, and download the raw SVG.
Already purchased? Log in
Use the FAQ template when you want every help center answer to carry a share card that reads like a search result. It leads with the question as the headline, then shows the opening line of the answer underneath, the two things a reader scans before deciding the page holds what they need.
This template is a metadata image route for the Next.js App Router. The file exports size, contentType, and alt values plus a default async function that returns an ImageResponse. When a page in the segment is shared, satori converts the JSX into an SVG document, the runtime rasterizes that SVG into a 1200 by 630 PNG, and Next.js serves the result and wires the og:image and twitter:image tags into the page head automatically. The answer preview sits behind a thin accent bar, so a longer reply still reads as one clean pull quote.
Install with the shadcn CLI using your Shadcn UI Blocks API key:
npx shadcn@latest add @shadcn-ui-blocks/og-image-faq-answer
The file lands at app/opengraph-image.tsx, which makes it the site wide share card. For a help center you will usually move it into the article segment instead, for example app/help/[slug]/opengraph-image.tsx. You can also copy the code from this page straight into your project.
The card renders text with Inter, read from assets/fonts at your project root with node:fs so the font files never ship to the browser. Download the latin woff files for weights 400, 500, 600, and 700 from Fontsource and save them as assets/fonts/inter-latin-400-normal.woff and so on.
The content object holds the brand row, the label chip, the question, the answer, an updated line, and the url. To generate a unique card per answer, accept params in the default export, look up the article the same way the page does, and feed its fields into the JSX. The question stays readable up to about two rendered lines; keep the answer preview under roughly 160 characters so it never crowds the footer.
satori supports a focused subset of CSS: flexbox layout only, flat colors, and an explicit display: flex on any element with multiple children. Keep those rules in mind if you rework the layout.