Google doesn't count characters — it measures pixels
The '60 character title, 160 character description' rule of thumb that gets repeated everywhere is an approximation of something more fundamental: Google renders search results in a proportional font, where every character occupies a different amount of horizontal space. A lowercase 'i' takes up a sliver of width; an uppercase 'W' takes up several times that. Two titles with the identical character count can truncate completely differently in the actual search results, because character count says nothing about how wide those specific characters render.
This is why this tool measures pixel width directly rather than just counting characters. Google caps titles at roughly 600 pixels on desktop and descriptions at roughly 960 pixels — anything beyond that gets cut with an ellipsis, regardless of how many characters it took to get there.
Pixel limits vs. the character-count rule of thumb
| Element | Pixel limit | Rough character equivalent | Why it's only rough |
|---|---|---|---|
| Title | ~600px | ~60 characters | Varies heavily with letter width mix |
| Description | ~960px | ~160 characters | Same issue, larger margin for error |
Using the SERP Preview
Type your page title, URL, and meta description into the form.
Watch the live pixel-width meters — green is good, amber is borderline, red means it's too long and will be truncated.
See how the snippet renders on both desktop and mobile layouts in real time.
Trim your copy until the meters stay green and the preview reads cleanly.
How the pixel-width estimate actually works
The tool estimates pixel width using an average of roughly 10 pixels per character, based on Arial's typical letter widths — a practical approximation, not a character-by-character rendering engine. It's a genuinely useful signal because it accounts for the fact that a title packed with narrow characters (i, l, t, f) fits more text into the same pixel budget than one packed with wide characters (W, M, O), which pure character counting completely misses.
Why Google sometimes ignores your title tag entirely
Even a title that fits comfortably within the pixel budget can still get overridden by Google, which will substitute its own generated title if yours is judged too long, stuffed with repeated keywords, or a poor match for what the page actually contains. This isn't a pixel-width problem, so no amount of trimming fixes it — the fix is writing a title that's genuinely descriptive of the page and reasonably concise (comfortably under 60 characters is a safe zone), rather than one optimized purely to hit a pixel target while ignoring what a search visitor and Google's relevance matching are looking for.
Desktop and mobile aren't the same preview
Checking both layouts matters because mobile search results have different width constraints and typically show a shorter effective preview than desktop, meaning a title or description that fits cleanly on desktop can still truncate earlier on mobile. Since a large share of search traffic happens on mobile devices, a snippet that only gets pixel-checked against the desktop layout risks shipping copy that's already cutting off for a majority of visitors — checking both is the only way to catch that gap before it goes live.
Common mistakes
Writing to the exact character-count rule of thumb (60/160) without checking pixel width, then being surprised when a wide-letter-heavy title truncates earlier than expected.
Trimming a title down to fit pixel width but losing what actually describes the page — a technically short, keyword-stuffed title is exactly the kind Google is more likely to override.
Only checking the desktop preview and assuming mobile will look the same — mobile's tighter width often truncates sooner.
Treating the pixel meter as an exact guarantee rather than an estimate — leave a small safety margin instead of writing right to the edge of green.
Real use cases
Rewriting a product page title that keeps getting cut off mid-word in actual Google results.
Checking a batch of blog post titles before publishing to catch pixel-width overflow before it ships.
Comparing how the same title and description render differently on desktop versus mobile before finalizing copy.
Diagnosing why a page's search snippet doesn't match the title tag in the page's HTML — checking length and keyword density against Google's override triggers.
Frequently asked questions
Q: How does Google truncate titles?
A: Google caps titles at roughly 600px on desktop, adding an ellipsis beyond that. This tool estimates pixel width at roughly 10px per character (Arial-based) and flags when you exceed 600px.
Q: What's the description limit?
A: Google shows about 960px of description, roughly 160 characters. Anything longer gets cut with an ellipsis — this tool flags at 960px and warns up to 1200px.
Q: Why does Google sometimes rewrite my title?
A: Google may override your title tag if it's too long, stuffed with keywords, or doesn't match the page's content. Keep titles descriptive, under 60 characters, and aligned with what users will actually see on the page.
Q: Are the pixel widths exact?
A: They're estimates based on average character widths. Actual rendering varies by browser, font, and character mix — wide letters like W versus narrow ones like i. Treat them as a guide, not a hard limit.
Q: Can I preview rich snippets?
A: This tool previews the standard organic result. For rich results like FAQ, product, or review snippets, you'll need structured data on your page — see the JSON-LD examples on each EasySEO tool page.
Q: If my title is well under the pixel limit, is that enough to guarantee Google won't rewrite it?
A: No — pixel width only controls truncation, not Google's separate decision to override a title entirely for relevance or quality reasons. A short, well-fitting title can still get replaced if it's vague, keyword-stuffed, or mismatched with the page content.
Preview your snippet now
Check your title and description with SERP Preview. Need to generate the underlying tags first? Try the Meta Tag Generator. Checking how a page looks when shared on social media instead? See Open Graph Preview, or manage crawler access with the Robots.txt Generator.
