Bulk generation

The dynamic APIis the maintenance-free default — wire a template once and every image matches the page's live title forever. Bulk generation is the fallback for sites that cannot call a live endpoint (a fully static export, for example) and for anyone who would rather own the image files directly.

Scan, edit, generate

From a template, open Bulk generate. Under From your site, paste a sitemap.xml URL or a list of page URLs (one per line), then click Scan pages. OGKit crawls each page on the server and pulls its real title and description. Titles prefer og:title, then fall back to twitter:title, the <title> tag, the first <h1>, and finally the URL's slug if a page has none of those. Descriptions prefer og:description, then fall back to twitter:description and the meta name="description" tag, left blank if a page has none of those.

Prefer not to crawl at all? Switch to From CSV and upload a file with title, subtitle, and site columns — OGKit reads the rows directly into the preview table without visiting any pages.

The scan (or CSV import) results land in an editable preview table — fix up any title or subtitle before committing. When it looks right, click Generate to render every row against your template and download a ZIP.

What is in the ZIP

• og-images/ — one PNG per page, named from its URL path (/blog/how-to-x becomes blog/how-to-x.png)
• manifest.csv — the URL ↔ file ↔ title mapping for every page
• README.md — a wiring <meta> template (use manifest.csvto look up each page's file), plus the staleness note below

Limits

Free plans can scan and generate up to 5 pages per run; Pro up to 50. Scanning a larger sitemap keeps the first pages up to that cap and flags the rest as truncated.