Open Graph & meta tag generator
Fill in a page's title, description, URL and image and get the <meta> tags for its <head>, the equivalent Next.js metadata export, and a live preview of how the link renders on Google, X and Facebook or LinkedIn — with warnings for a title that will be cut, an image over http or a handle without its @. No account needed, nothing leaves your browser.
Page
Image
X card
Google result
Launch week: what shipped in Orbit 2.0
Orbit 2.0 ships shared cursors, a faster sync engine and an offline mode. Here is everything that changed, what it costs and how to upgrade.
X card

Facebook and LinkedIn card

Previews approximate each platform's layout and cut-off. The real cut is by pixel width and the layouts change without notice; each network's own debugger has the last word.
Nothing to fix
Lengths, URLs, image and handle all look right.
HTML meta tags
Paste into <head>.
<title>Launch week: what shipped in Orbit 2.0</title>
<meta name="description" content="Orbit 2.0 ships shared cursors, a faster sync engine and an offline mode. Here is everything that changed, what it costs and how to upgrade." />
<link rel="canonical" href="https://orbit.example.com/blog/launch-week" />
<meta property="og:type" content="article" />
<meta property="og:url" content="https://orbit.example.com/blog/launch-week" />
<meta property="og:title" content="Launch week: what shipped in Orbit 2.0" />
<meta property="og:description" content="Orbit 2.0 ships shared cursors, a faster sync engine and an offline mode. Here is everything that changed, what it costs and how to upgrade." />
<meta property="og:site_name" content="Orbit" />
<meta property="og:locale" content="en_US" />
<meta property="og:image" content="https://orbit.example.com/og/launch-week.png" />
<meta property="og:image:alt" content="The Orbit 2.0 logo over a dark blue gradient" />
<meta name="twitter:card" content="summary_large_image" />
<meta name="twitter:site" content="@orbitapp" />
<meta name="twitter:title" content="Launch week: what shipped in Orbit 2.0" />
<meta name="twitter:description" content="Orbit 2.0 ships shared cursors, a faster sync engine and an offline mode. Here is everything that changed, what it costs and how to upgrade." />
<meta name="twitter:image" content="https://orbit.example.com/og/launch-week.png" />
<meta name="twitter:image:alt" content="The Orbit 2.0 logo over a dark blue gradient" />
<!-- Generated with Nodlume — https://nodlume.dev/meta-tag-generator -->
Next.js metadata export
Paste into a page.tsx or layout.tsx in the App Router.
import type { Metadata } from "next"
export const metadata: Metadata = {
title: "Launch week: what shipped in Orbit 2.0",
description: "Orbit 2.0 ships shared cursors, a faster sync engine and an offline mode. Here is everything that changed, what it costs and how to upgrade.",
alternates: { canonical: "https://orbit.example.com/blog/launch-week" },
openGraph: {
type: "article",
url: "https://orbit.example.com/blog/launch-week",
title: "Launch week: what shipped in Orbit 2.0",
description: "Orbit 2.0 ships shared cursors, a faster sync engine and an offline mode. Here is everything that changed, what it costs and how to upgrade.",
siteName: "Orbit",
locale: "en_US",
images: [{ url: "https://orbit.example.com/og/launch-week.png", alt: "The Orbit 2.0 logo over a dark blue gradient" }],
},
twitter: {
card: "summary_large_image",
site: "@orbitapp",
title: "Launch week: what shipped in Orbit 2.0",
description: "Orbit 2.0 ships shared cursors, a faster sync engine and an offline mode. Here is everything that changed, what it costs and how to upgrade.",
images: [{ url: "https://orbit.example.com/og/launch-week.png", alt: "The Orbit 2.0 logo over a dark blue gradient" }],
},
}
// Generated with Nodlume — https://nodlume.dev/meta-tag-generator
Escaped, in order
Quotes, ampersands and angle brackets in a title become entities in the attribute, line breaks in a description collapse to one line, and the tags come out in the order the Open Graph and X docs list them — so the block is checkable top to bottom.
Previews, not promises
The Google result, the X card and the Facebook card are drawn to each platform's layout and character cut-off, which is where a long title or a missing picture shows up before anyone shares the link.
Two outputs, one source
The HTML fragment and the Next.js export const metadata are generated from the same fields, so a value is never set in one and forgotten in the other — and an empty field is left out of both rather than emitted blank.
How to generate Open Graph and meta tags
Three steps from a blank form to a head you can paste. The previews and both outputs rebuild on every keystroke.
Describe the page
Title under about 60 characters, description between 70 and 155, the page's absolute URL and, usually, the same address as the canonical. Pick website or article for og:type and set the site name and locale.
Add the image and the X card
An absolute https URL to a 1200 × 630 image with alt text. Choose summary_large_image unless the picture is a small logo, and add the site's @handle. Watch the three previews and the warnings list as you go.
Copy the output you need
The HTML block goes inside <head> on any site. The Next.js block is a typed metadata export for a page.tsx or layout.tsx in the App Router. Both carry a Nodlume credit comment on the last line that you can delete.
What the outputs contain
- HTML meta tags
- <title>, the description meta, <link rel=canonical>, the og:* block (type, url, title, description, site_name, locale, image, image:alt) and the twitter:* block (card, site, title, description, image, image:alt). Only tags with a value.
- Next.js metadata export
- import type { Metadata } from "next" and export const metadata: Metadata = { title, description, alternates.canonical, openGraph, twitter } with the same values, every string JSON-quoted.
Open Graph and meta tags, answered
- What is Open Graph?
- A set of <meta> tags, prefixed og:, that tell a link-unfurling app what a page is: og:title, og:description, og:image, og:url and og:type. Facebook introduced the protocol in 2010 and almost everything that renders a link card reads it now — LinkedIn, Slack, Discord, iMessage, WhatsApp, Teams — so one set of tags covers them all. Without them each app guesses from the page body, and the guess is usually a wrong picture and a truncated first paragraph.
- Which Open Graph tags are required?
- The protocol names four: og:title, og:type, og:image and og:url. In practice og:description is the fifth, because every card shows one, and og:site_name is cheap and useful. This tool emits only the tags you have filled in and never writes an empty one — an empty og:image is reported as a broken image, which is worse than letting the app fall back.
- What size should the og:image be?
- 1200 × 630 pixels — a 1.91:1 ratio — under about 5 MB, served over https from an absolute URL. That is the size Facebook, LinkedIn and X's summary_large_image card all crop to, so one image fits every card without a second asset. Keep the subject away from the edges: the summary card and some chat apps crop it square. Add og:image:alt for screen readers; the warnings list reminds you when it is missing.
- What is the difference between summary and summary_large_image?
- They are the two shapes an X card can take. summary shows a small square thumbnail beside the title and description; summary_large_image puts the picture on top, full width, and is what a link with a real image should use. Both are set with the twitter:card tag, and the X preview above switches between them as you change the field.
- Do I need both og: and twitter: tags?
- X reads og:title, og:description and og:image when the twitter: versions are absent, so the only tag it strictly needs is twitter:card, which has no og: equivalent. This generator emits both sets anyway: the twitter: tags cost nothing, keep the X card explicit when the og: ones change, and twitter:site attributes the card to your account. Everything else that unfurls links reads the og: set only.
- How does the Next.js metadata export relate to the tags?
- In the App Router you do not write <meta> tags by hand. A page or layout exports a metadata object — title, description, alternates.canonical, openGraph, twitter — and Next renders the <head> from it, deduplicating against parent layouts. The second output here is that object, typed as Metadata, with the same values as the HTML block: paste it into page.tsx or layout.tsx. Relative URLs in it resolve against metadataBase from the root layout; the generator writes absolute ones so it works without it.
- Does this tool send my data anywhere?
- No. The page runs entirely in your browser and stores nothing — reload and it starts from the sample page again. The image URL you type is shown in the previews as a plain <img> with no referrer sent to the image host; nothing is fetched or proxied by Nodlume. What you copy is yours.
Where the tags go next
One page's head is a start; a site has one per route. In the Nodlume workspace every page on the route tree you draw with the Structure Painter carries its own title and description, and the generated project emits the metadata for all of them at once. The Manifest V3 generator does the same job for a browser extension's manifest, and the Zod schema builder types the data behind the page.