See your Google snippet, social cards & pixel widths live — then copy ready-to-paste <head> tags. Built in your browser.
The clickable blue headline. Google truncates by pixel width (~580–600px desktop), not characters.
Truncates near 920px desktop / 680px mobile and snaps to the nearest whole word.
Shown as the SERP breadcrumb path and used for og:url / canonical. Use an absolute https:// URL.
Recommended 1200×630px (1.91:1), under ~1MB. Must be absolute https — relative URLs silently fail.
Without an explicit card type X may default to a tiny summary card even when a large image exists.
Google snippet preview — Desktop
This free tool builds your title tag, meta description, Open Graph, and X (Twitter) card tags
and shows you exactly how they'll look — a live Google snippet, a Facebook/LinkedIn share card,
and an X card — before you ship them. Crucially, it measures your title and description by rendered
pixel width (the way Google actually truncates), not just character count, using an HTML canvas. When
you're happy, copy a ready-to-paste <head> block. Everything runs in your browser —
nothing you type is sent anywhere.
<head>.Say your title is Best Running Shoes for Flat Feet (2026 Guide) | Acme — that's 52 characters.
By character count it looks safe. But the canvas measures it at roughly 465px at the 20px
Arial size Google uses, comfortably under the ~580–600px desktop cap, so it shows Good. Now
imagine a brand suffix made of wide capitals — … | WORLDWIDE MEGAMART OUTLET — that can push the
same line past 600px even though it's only a few more characters. The tool flags it, and the SERP preview shows
the … exactly where Google would cut, snapping to the last whole word. That's the whole point:
pixels override characters when they disagree.
Google lays out the snippet in a fixed-width container and truncates the rendered text. A W or
M is roughly 14px wide while an i or l is about 4px — a 3× difference.
So two 60-character titles can render at very different widths. This tool uses
canvas.measureText() (gated behind document.fonts.ready) for the authoritative number,
and falls back to a character × average-width estimate only if the canvas isn't available. Character counts are
shown as a secondary guide and use code points ([...title].length) so emoji aren't miscounted.
og:title, og:type, og:url, og:image. og:description is recommended but optional.http:// URLs are the #1 reason share images don't appear.summary_large_image for the big banner — otherwise X may fall back to a small card even when a large image exists. X inherits OG tags when twitter:* are absent.og:image:alt / twitter:image:alt) — an accessibility and quality win the checklist flags.http:// og:image / twitter:image URLs (they silently fail).twitter:card="summary_large_image" and assuming the big banner shows.og:image:alt / twitter:image:alt.< > & ") in the markup — this tool escapes them for you.By pixel width. A 60-character title of wide letters can truncate while a 65-character narrow title fits. This tool measures real pixels via canvas and treats that as authoritative.
Title under ~580–600px (about 50–60 chars); description under ~920px desktop / ~680px mobile (~120–158 chars, first ~120 load-bearing for mobile). These are approximate container limits, not hard cutoffs.
Usually a relative or http:// URL. Crawlers need an absolute https:// image (1200×630, under ~1MB). Re-scrape with the Facebook Sharing Debugger and X Card Validator after changes — platforms cache.
Not always — Google rewrites titles and generates snippets from page content a large share of the time. The preview is a strong starting point, not a promise.
No. Google has ignored it for over a decade, so this tool doesn't generate one.
Built locally in your browser. Nothing you type — titles, descriptions, URLs — is ever sent, logged, or stored.