AnyTool
Your files never leave your device. All processing happens locally in your browser.

How do I preview how my page title and meta description look in Google search — with pixel-accurate truncation — without uploading anything?

Open AnyTool’s Google SERP Preview, type your page title, meta description and URL (optionally a site name and a date), and it renders a live DESKTOP and MOBILE result card — favicon dot, site name + breadcrumb URL, blue title and the description — truncated with an ellipsis exactly where Google would cut it. Truncation is measured by PIXEL WIDTH, not character count: the engine uses the Canvas measureText() API in the same fonts Google renders the SERP in (~Arial 20px desktop / 16px mobile titles, ~14px descriptions), so wide letters (W, M) eat the budget faster than narrow ones (i, l). Per-field meters show characters and pixels against Google’s approximate limits — title ~600px desktop / ~545px mobile, description ~920px desktop / ~680px mobile — in green / amber / red with a truncation warning, and you can copy the <title> and <meta> tags. Everything runs in your browser, so nothing is uploaded. Honest caveat: this PREVIEWS your snippet, but Google frequently REWRITES titles (studies find 61%+, up to ~76% in early 2025 — often dropping the brand) and OFTEN auto-generates or rewrites the description per query, so what actually shows can differ — verify in Google Search Console.

  • Live desktop + mobile result card with pixel-accurate truncation (canvas measureText, Google’s fonts)
  • Per-field meters: characters AND pixels vs Google’s limits, green / amber / red, with truncation warnings
  • Modern layout: favicon dot, site name + breadcrumb URL above the title, optional date, light/dark SERP toggle
  • 100% client-side — your title, description and URL are never uploaded; works offline once cached
  • Honest: Google rewrites ~61%+ of titles and often rewrites descriptions; pixel limits are approximate — verify in Search Console

What is

SERP snippet (title + meta description preview)

A SERP snippet is the block Google shows for a page in search results: the site name and breadcrumb URL, the clickable blue title, and the descriptive text beneath it. Google truncates the title and description by PIXEL WIDTH (not character count) to fit the result — roughly 600px (≈50–60 chars) for the desktop title and ~920px desktop / ~680px mobile for the description — adding an ellipsis when text overflows. A SERP preview tool measures your title and meta description in the same fonts Google uses and renders how the snippet would look, so you can keep the important words visible. Crucially, Google treats your <title> and meta description as signals it can override: it rewrites a large share of titles (using your H1, anchor text or site name) and often auto-generates the description per query.

SEO & Web

Related terms

Title tagMeta descriptionPixel width truncationSERPmeasureTextClick-through rateSearch Console

Frequently Asked Questions

Often not. Google uses your title and description as strong signals but frequently rewrites them — studies find it changes 61%+ of titles (up to ~76% in early 2025) and often auto-generates the description per query.

Google treats your <title> and meta description as signals, not commands. For titles, large studies (Zyppy, Portent and others) found Google rewrites roughly 61% of title tags, with one 2025 analysis reporting ~76% changed in Q1 2025; the most common change is removing the brand name, and Google may substitute your H1, the anchor text people link to your page with, or your site name. Meta descriptions are rewritten or auto-generated even more often — Google pulls the sentence from your page that best matches the searcher’s query, so the same page can show different descriptions for different searches. That is why this tool is explicit that it PREVIEWS and MEASURES your snippet; it does not promise Google will display it verbatim. Write a clear, accurate title and description for users, front-load the key words, and check what actually appears in Google Search Console.

Because Google truncates by pixel width, not characters. A title of wide letters (W, M) is cut sooner than one of narrow letters (i, l) at the same character count — so pixels are accurate and character counts are only a rough proxy.

Google decides where to cut a title or description by how many PIXELS it occupies in the result, not how many characters it has. Uppercase and wide glyphs like W and M take far more space than narrow ones like i, l and t, so “WWWWWWWW” and “iiiiiiii” have the same character count but very different widths. This tool therefore measures each field with the Canvas measureText() API using the same fonts Google renders the SERP in (~Arial 20px desktop / 16px mobile for titles, ~14px for descriptions) and truncates with an ellipsis exactly where the pixel budget runs out — title ~600px desktop / ~545px mobile, description ~920px desktop / ~680px mobile. The meters still show a character count for familiarity, but the pixel reading and the on-card truncation are what match real Google behaviour. The limits are approximations because fonts, devices, zoom and SERP features all shift the exact cut-off.

Aim for a title around 50–60 characters / under ~600px desktop (~545px mobile), and a description around 150 characters / under ~920px desktop, ~680px on mobile. Front-load the important words.

As a starting point, keep your title to roughly 50–60 characters so it stays under ~600px on desktop and ~545px on mobile, and your meta description to roughly 150 characters to fit ~920px on desktop and the tighter ~680px (~120 characters) on mobile — mobile is the binding constraint, so put the key message in the first ~105–120 characters. But treat these as pixel budgets, not hard character caps: this tool measures the actual width of your exact text and tells you whether it fits or will be cut, so you can use longer text made of narrow letters or trim text full of wide ones. Most importantly, do not pad to the limit for its own sake — a clear, compelling snippet that earns the click beats one that merely fills the bar, and Google may rewrite it anyway.

No. Your title, description and URL are measured and previewed entirely in your browser with plain JavaScript and the Canvas API — nothing is uploaded, logged or stored, and no page is crawled.

The Google SERP Preview is 100% client-side. The text you type is measured with the Canvas measureText() API and rendered into the preview card locally; nothing is fetched, uploaded, logged or stored on a server, and no URL is ever crawled. That makes it safe for unpublished pages, staging titles and draft descriptions you do not want to expose to a third-party tool. It works offline once cached as a PWA, supports dark mode and mobile with a sticky copy bar, and closing the tab discards everything you entered.

Detailed Explanation

How It Works

What the Google SERP Preview Shows and Measures

The Google SERP Preview answers a single practical question: how will this page’s title and meta description LOOK in Google search, and will either be cut off? The user types a page title, a meta description and a URL (with an optional site name and a date toggle), and the tool renders a live result card in the modern Google layout — a favicon dot, the site name and a breadcrumb URL above the clickable blue title, then the description beneath — for both DESKTOP and MOBILE, with a light/dark SERP theme toggle. The decisive feature is that truncation is PIXEL-ACCURATE: Google cuts titles and descriptions by pixel width, not character count, so the shared engine serpEngine.ts measures each field with the Canvas measureText() API in the same fonts Google renders the SERP in (~Arial 20px desktop / 16px mobile for titles, ~14px for descriptions) and trims with an ellipsis exactly where the pixel budget runs out. Per-field meters then report both characters AND pixels against Google’s approximate limits in green / amber / red with a truncation warning, and the user can copy the <title> and <meta name="description"> tags.

  • Live desktop + mobile result card in Google’s modern layout (favicon, site name, breadcrumb URL, title, description)
  • Truncation is pixel-accurate via Canvas measureText() in Google’s fonts — not a character cap
  • Approximate limits: title ~600px desktop / ~545px mobile; description ~920px desktop / ~680px mobile
  • Per-field meters show characters AND pixels with green / amber / red status and truncation warnings
  • All measurement and rendering is pure client-side JavaScript — no server call, no CDN, no upload, no crawl
Methodology

How Pixel-Width Truncation Is Computed

The reusable engine serpEngine.ts holds the verified limits per device and field and the CSS font shorthands Google renders the SERP in. measurePx(text, font) lazily creates a single offscreen <canvas> 2D context (cached, and created only on first call so importing the module touches no DOM), sets ctx.font and returns the rounded ctx.measureText(text).width; in a non-browser environment it falls back to a deterministic average-glyph estimate so it never throws. truncateToPx(text, font, maxPx) returns the full text unchanged when it fits, otherwise binary-searches for the longest character prefix whose width plus an ellipsis fits the budget, trims a trailing space or punctuation fragment, and appends “…”, mirroring how Google cuts mid-text. analyzeSerp({title, description}, device) runs both fields for the chosen device and returns, per field, the character count, the pixel width of the full text, the pixel limit, whether it will truncate, the exact text that would show, a percentage of the budget for the meter bar, and a traffic-light status (empty / short / good / warn / over). Because the measurement is by real glyph width, a title of wide letters (W, M, uppercase) is flagged as truncating at a lower character count than one of narrow letters (i, l, t) — which a character counter cannot do. The page renders the card from analyzeSerp’s shownText and drives the meters from the same analysis.

  • serpEngine.ts exports LIMITS, RECOMMENDED, SERP_FONTS, measurePx, truncateToPx, analyzeSerp and toDisplayUrl
  • measurePx lazily creates and caches one offscreen canvas context — no DOM work at import time
  • truncateToPx binary-searches the longest prefix that fits maxPx minus the ellipsis width, then appends “…”
  • analyzeSerp returns per field: chars, px, limitPx, willTruncate, shownText, pctOfLimit and a status
  • Wide vs narrow glyphs are measured by real width, so truncation matches Google better than a character cap
Limitations

A Preview, Not a Promise: Google Rewrites Titles and Descriptions

The tool is explicit that it PREVIEWS and MEASURES a snippet rather than predicting exactly what Google will display, for three honest reasons. First, GOOGLE OFTEN REWRITES THE TITLE: it uses your <title> as a strong signal but frequently replaces it with your H1, the anchor text people link to your page with, or your site name — large studies (Zyppy, Portent and others) found Google changes roughly 61% of title tags, with one 2025 analysis reporting ~76% changed in Q1 2025, and the single most common change is removing the brand name. Second, GOOGLE OFTEN REWRITES OR AUTO-GENERATES THE META DESCRIPTION per query, pulling the sentence from your page that best matches the searcher’s intent, so the same page can show different descriptions for different searches and may ignore yours entirely. Third, THE PIXEL LIMITS ARE APPROXIMATIONS: the exact cut-off shifts with fonts, devices, browser zoom and SERP features, and rich elements (sitelinks, ratings, dates, FAQs, images) are added at Google’s discretion. The guidance is therefore to write a clear, accurate title and description for users, keep the key words near the front, treat the limits as budgets rather than targets, and verify what actually appears in Google Search Console rather than assuming the preview is what searchers see.

  • Google rewrites ~61% of title tags (up to ~76% in early 2025) — most often by removing the brand name
  • Google frequently auto-generates or rewrites the meta description per query, so it can differ by search
  • Pixel limits are approximate — fonts, devices, zoom and SERP features shift the exact truncation point
  • Rich elements (sitelinks, ratings, dates, FAQs) are added at Google’s discretion, not by this tool
  • Write for users, front-load key words, and verify the live snippet in Google Search Console
Privacy & Security

Why Previewing Your Snippet In-Browser Is a Privacy Win

Many online SERP preview tools send your title, description and URL — or crawl your URL — server-side. The Google SERP Preview instead runs entirely on the user’s device: the text is measured with the Canvas measureText() API and the result card is rendered locally; nothing is fetched, uploaded, logged or stored, and no page is ever crawled. That makes it safe to draft titles and descriptions for UNPUBLISHED or STAGING pages you do not want to expose to a third-party tool before launch. It works offline once cached as a PWA, supports dark mode and mobile with a sticky copy bar for the title and description, has exactly three ad slots, and adds NO new dependency — the measurement and truncation logic live in the small, reusable engine serpEngine.ts, which the sibling Google Snippet Preview imports so both tools share one well-typed source of pixel limits and truncation behaviour.

  • Title, description and URL are measured and previewed locally and never uploaded — no server, no CDN, no crawl
  • Safe for unpublished / staging titles and descriptions, unlike online previewers that crawl your URL
  • Works offline once cached; closing the tab discards your data
  • No new dependency — measurement and truncation live in the reusable serpEngine.ts, shared with the sibling
  • Dark mode and mobile support with a sticky copy bar; exactly three ad slots
SERP preview: in-browser (AnyTool) vs typical online previewers
CapabilityAnyToolTypical online tools
ProcessingRuns entirely in your browserSends your text / crawls your URL server-side
Your snippetNever uploaded, works offlineSent to or crawled by a server
TruncationPixel-accurate via canvas measureText() in Google’s fontsOften a character-count approximation
Desktop + mobileBoth, with light / dark SERP themesSometimes desktop only
MetersCharacters AND pixels, green / amber / redUsually characters only
HonestyStates Google rewrites titles/descriptions; limits approximateOften implies Google shows it verbatim
Cost / signupFree, no signupOften gated or ad-heavy

AnyTool measures and previews your title and meta description locally with the Canvas measureText() API in Google’s SERP fonts and uploads nothing, so it is safe for unpublished pages. Truncation is by pixel width (title ~600px desktop / ~545px mobile; description ~920px desktop / ~680px mobile) — approximations that shift with fonts, devices and SERP features. Google uses your title and description as signals but frequently rewrites titles (studies find ~61%, up to ~76% in early 2025, most often dropping the brand) and often auto-generates the description per query, so confirm the live snippet in Google Search Console. Comparison as of June 2026.