Google SERP Snippet Preview & Pixel Length Checker
See exactly how a title and meta description will look in Google results, with real pixel-width truncation warnings.
Preview
Pixel widths are estimated from typical Google rendering (desktop title ≈600px, description ≈920px; mobile title ≈380px, description ≈680px). Google doesn't publish exact figures and these can shift over time — treat this as a strong guide, not a guarantee.
How it works
- 1
Enter your title and description
Type or paste your title tag and meta description, or load them directly from a live URL.
- 2
Choose desktop or mobile
Switch between the two to check pixel width against each device's own truncation limits.
- 3
Watch the pixel meter
Each field shows a live pixel-width bar that turns amber near the limit and red once it's over.
- 4
Check the preview
The search result preview shows the title and description truncated exactly where Google is likely to cut them off.
- 5
Adjust until it fits
Trim or rewrite until the result banner confirms both fit without truncation on the device you're checking.
About the Google SERP Snippet Preview & Pixel Length Checker
Character counts are a rough guide at best, Google truncates titles and descriptions based on actual rendered pixel width, not a fixed number of letters, so a title full of narrow letters like "i" and "l" can fit fine at 65 characters while a title full of wide letters like "W" and "M" gets cut off at 50. This tool measures real pixel width the way a browser actually renders it, on both desktop and mobile, and shows exactly where Google is likely to add the cutoff ellipsis, live, as you type.
Why pixel width matters more than character count
A 60 character rule of thumb for titles gets repeated constantly, but it's an approximation of an approximation, Google renders titles and descriptions as actual text in a proportional font, where every character takes up a different amount of horizontal space, not a fixed-width font where every character counts the same. Two titles with the same character count can render at meaningfully different pixel widths depending on which letters they use, which is why a title that looks safely short by character count can still get truncated, and a longer one can render just fine. Measuring the actual rendered width, the way this tool does, is the only way to know for certain rather than guessing from a character limit that was never how Google actually decides.
Why desktop and mobile need separate checks
Google's mobile search results render in a narrower space with different font sizing than desktop, which means the pixel width available before truncation is genuinely different between the two, not just a smaller version of the same layout. A title carefully tuned to fit desktop results can still get cut off on mobile, where the majority of searches actually happen, so checking only one device gives an incomplete picture. This tool lets you switch between desktop and mobile limits directly, using separate thresholds for each rather than a single generic number applied to both.
Loading a real page instead of typing from scratch
Rather than retyping a title and description you've already written, entering a URL and clicking Load fetches that page directly and pulls its actual title tag and meta description into the tool, along with the domain and path used in the preview. This is meant for checking a page that's already live, or auditing an existing site's search snippets, since it saves the step of opening the page's source just to copy two lines of text out of it.
What this can't guarantee
Google has never published the exact pixel values it uses for truncation, and they've changed over time as the search results design has evolved, so the thresholds used here are well established industry estimates, not official figures pulled from Google itself. Loading a page also reads its raw HTML only, a title or description that gets inserted or changed by JavaScript after the page loads won't be picked up, since that would require actually rendering the page in a browser rather than just reading its source, which this tool doesn't do. For most sites, where title and description tags are part of the initial HTML, this isn't a practical limitation, but it's worth knowing about for a page that sets those tags dynamically.
Runs entirely in your browser
Pixel measurement happens locally using your browser's own text rendering, nothing you type is sent anywhere. Loading a page by URL does make a request through this site to fetch that page's content, but the title and description you end up editing stay entirely in your browser from that point on. Once your sitemap or robots rules are in good shape too, our XML Sitemap Generator and Robots.txt Tester are part of the same Technical SEO collection this tool belongs to.
Frequently asked questions
Why does this measure pixels instead of just counting characters?
Google renders titles and descriptions in a proportional font, where different letters take up different amounts of space, so pixel width reflects actual truncation far more accurately than a fixed character count ever can.
Are the pixel limits used here official Google numbers?
No, Google has never published exact figures, and they've shifted over time. The limits used are well established industry estimates, treated here as a strong guide rather than a guarantee.
Why are desktop and mobile checked separately?
Mobile search results render in a narrower space with different font sizing than desktop, so the pixel width available before truncation genuinely differs between the two, not just a scaled-down version of the same limit.
Does Load from URL work on any website?
It fetches a page's raw HTML and reads its title and meta description tags directly. It won't pick up a title or description that's inserted or changed by JavaScript after the page loads, since that would require rendering the page rather than just reading its source.
Why isn't there a JS rendering option like some other tools have?
That requires running a real headless browser to execute a page's JavaScript before reading its tags, which isn't something this tool does. For the large majority of sites, where title and description are part of the initial HTML, this isn't a practical limitation.
What does the colored bar under each field mean?
Green means comfortably within the pixel limit, amber means it's getting close, and red means it's over and will likely be truncated in Google's results.
Does the preview show the exact text Google will display?
It shows text truncated at the same pixel width estimates this tool checks against, including the cutoff ellipsis, so it reflects where truncation is likely to happen rather than just displaying the full text underneath a warning.
Is my title and description sent to a server?
No, pixel measurement happens locally in your browser. Loading a page by URL does fetch that page's content through this site, but everything you type or edit afterward stays in your browser.