Meta Description Checker
Measure a meta description's real pixel width the way Google does, see the character count, and know before you publish whether it fits or gets cut in the results.
Your meta description
The meta description is the grey text under your title in Google, and it is your pitch for the click before anyone reaches the page. If it runs too long Google cuts it with an ellipsis, often mid-sentence, and the catch is that the cut happens on pixel width, not character count, so a description that looks fine by the numbers can still be trimmed. This free meta description checker measures the rendered width of your text in the exact font Google uses, shows it against the roughly 920-pixel desktop limit, and previews how the snippet will actually read. It is built for SEOs, content writers and site owners who want a description that lands in full and earns the click.
How to use it
Type or paste your description
Drop your meta description into the box. The pixel width, character count and verdict update instantly as you type, with nothing to submit.
Read the width against the limit
The bar and counter show your description's rendered width against Google's roughly 920-pixel desktop cut, and flag it as truncated, good length or too short at a glance.
Trim until the preview reads well
Watch the Google-style snippet: when the text runs over, it is cut with an ellipsis exactly where Google would cut it. Edit until the key sentence survives, then copy it out.
Why it's useful
Pixel-accurate, not a character count
Google truncates on rendered width, so a description heavy with wide letters is cut sooner than a longer one in narrow letters at the same character count. This tool measures the real width in the font Google uses, so the verdict matches what shows in the results rather than a rough character guess.
See the cut before it happens
The live preview renders your description inside a Google-style snippet and adds the ellipsis at the exact point the text would be trimmed, so you catch a cut description while you can still rewrite it instead of after it is published.
Nothing leaves your browser
The check runs entirely client-side. Your descriptions are never uploaded or stored, so you can safely test unpublished pages, drafts and client work without signing in.
Writing a meta description that earns the click
Why Google cuts descriptions on pixels, not characters
Google truncates the description on rendered width, not on how many characters it holds. A line full of wide letters takes more space than a narrow one of the same length, so a description that passes a character count can still be cut, and one that looks long can fit. That is why a character count alone misleads, and why this tool measures the actual pixel width of your text in the font Google uses, showing the character count beside it only for reference.
The practical ceiling is around 920 pixels on desktop, which lands near 150 to 160 characters for average text but shifts with the letters you use. Mobile and different result types cut at other points, and Google adjusts the display over time, so treat the number as a close approximation rather than a hard guarantee. Use it to catch anything clearly too long, then judge the wording on its own merits.
Make the first sentence carry the weight
Whatever is dropped is the end of the description, so the opening has to work on its own. Lead with what the page delivers and the reason to click, and keep the first sentence a complete thought, because that is the part a scanner reads and the part most likely to survive the cut. A description that still makes sense at half its length keeps earning clicks even when it is trimmed.
There is a floor as well as a ceiling. A description far under the limit leaves the snippet looking thin and wastes space you could use to sell the click, which is why the tool flags a very short description as well as an over-long one. Aim to use the space well without padding to reach the limit.
Write for the click, not the character limit
Filling every pixel is not the goal. A description that is clear, specific and answers the query will out-click a longer one padded to reach the limit. Use the ceiling as a line not to cross, stop when the pitch is made, and leave a little headroom so small variations in how Google renders the line do not cut your message short.
What the checker does not decide
Google frequently rewrites the description it shows, pulling a passage from the page when that matches the exact query better than your tag. That is normal and not a sign of a problem: a well-written meta description is still the version Google starts from and often keeps, especially for branded and navigational searches, so it remains worth getting right. After you check the width, publish the page, then watch how the real snippet renders and clicks in Search Console and refine the pages that are indexed but under-clicked. A description that lands in full and reads well is what gets found and gets clicked, across every language you publish in, which is where Otorank picks up: it writes, publishes and tracks content built to be found across 150+ languages once you move from checking one line to running the whole channel.
They use Otorank
Questions
What the checker measures, why pixels beat characters, and why Google sometimes shows a different description.
Google cuts the description around 920 pixels on desktop, roughly 150 to 160 characters for average text. Below about 70 characters it leaves space unused; past the limit the end is dropped.
Google truncates on rendered width, not sign count. A line full of wide letters is cut sooner than a narrow one at the same character count, so pixels predict the cut and characters only approximate it.
A description well under the limit leaves the snippet looking thin and wastes space you could use to earn the click. It is not an error, just a nudge that there is room to say more.
Google often rewrites the displayed description from the page content when a passage matches the query better. A careful meta description is still worth writing: it is the starting point Google keeps for branded and navigational searches.
No. Everything is measured in your browser; nothing is uploaded or stored, so you can check unpublished and confidential copy safely.