Meta Description Length Checker and Preview
Paste a meta description and this checker estimates its width in pixels, shows how much of it a desktop or a mobile snippet could hold, and draws a preview with an optional date in front. It also points out text that reads like a list of terms or runs in capitals. All of it happens in your browser, and every figure is an estimate.
Measured in this browser tab. Nothing is uploaded or saved.
Limits: Up to 8 KB of description text. Larger input is refused with a message. The date box has no cap of its own.
Results
- Characters
- -
- Estimated width, 14 px Arial
- - px
- Desktop estimate, 920 px budget
- -
- Mobile estimate, 680 px budget
- -
Snippet preview
An approximation drawn from the estimates above, not a copy of a real results page.
Your description appears here
Your description appears here
| Level | What the checker found |
|---|
How to use the Meta Description Length Checker and Preview
- Paste the text from the content attribute of your page's meta description tag.
- If your result might show a date, type it in the settings, for example Mar 4, 2026.
- Compare the estimated width with the desktop and mobile budgets and read where the preview stops.
- Move the most useful detail into the part both estimates keep, then check it again.
Worked example
A care guide for leather hiking boots, written as one full sentence of 160 characters and shown with a date in front. Press Load the example to measure it with the date listed below; these are the results the checker shows in Chrome with Arial installed.
Clean and waterproof leather hiking boots after a muddy trip with soap, a soft brush and wax, then dry them slowly away from heat so the leather does not crack.
- Date in front of the snippet
- Mar 4, 2026
- Characters
- 160
- Estimated width, 14 px Arial
- 995
- Desktop estimate, 920 px budget
- Cut after 129 of 160 characters
- Mobile estimate, 680 px budget
- Cut after 92 of 160 characters
How to read the results
- Characters
- What the description holds, counted the way it looks, once spaces and line breaks are reduced to single spaces. A flag or an emoji counts as one.
- Estimated width
- The description laid out on one line in Arial at 14 px, kerning off, to the nearest pixel. It does not include the date.
- Desktop and mobile estimates
- Either the room left over, or how many characters the snippet would keep out of the total. With a date set, the budget is first reduced by the date's own width.
- Snippet preview
- The description as each estimate would show it, with the date in front when you give one. The text wraps inside the frame; where it ends is set by the estimate, not by the frame.
- Checks
- Warnings mark text likely to be cut on both devices, a run of capitals or a list of terms. Notes cover softer points, such as the width a date uses or a description well under half the mobile budget.
How this tool works and its limitations
The checker draws nothing to measure: it asks the browser's canvas measureText method for the width of the text in Arial, or Helvetica, Liberation Sans or Arimo, which have the same letter widths, at 14 px with kerning off. Before trusting the numbers, it measures a reference pangram whose Arial width is known and shows a warning on this page if your browser is drawing with a different font. The preview uses the same font stack and kerning setting, so the text it shows was measured in the font it is shown in.
Google documents no font, size or width for snippets. The 14 px Arial assumption and the 920 px desktop and 680 px mobile budgets follow figures commonly used by SEO tool makers, and they are fixed here so results can be compared from one edit to the next. A date reduces both budgets by its measured width plus a short joiner. When the description is too wide, the preview keeps the longest start that fits with an ellipsis and then backs up to a whole word. Google's documentation cited above was read on 21 October 2026. These limits remain:
- The 920 px and 680 px budgets are this checker's reference figures. Google sets no length for a meta description and cuts snippets to fit the screen.
- A snippet is often written from the page text instead of your description, and it can change with each search, so the preview shows only the case where your description is used as it stands.
- Google's real snippets wrap over lines and may cut at a different word; this checker measures the description as one line against a total width.
- Widths come from the fonts installed on your computer. Without Arial or a font that has its widths, the page says so, and the estimates move by the share it states.
- Whether a date appears, and which date, is decided by Google; the date setting only shows what one would cost in width.
- The description box takes up to 8 KB of text and refuses more with a message; the date box sets no cap of its own.
Features
- Pixel width measured in Arial at 14 px, the size this checker assumes for snippet text.
- Desktop and mobile budgets side by side, with the room a date takes subtracted from both.
- A snippet preview cut at the last whole word that fits, ending in an ellipsis.
- Plain warnings for keyword lists, capitals and very short descriptions, with no score.
Google often writes the snippet itself
Google's page on snippets says they are primarily created from the page content itself, and that a meta description is used when it might give a more accurate description than the page text alone. The snippet can also change with the search, since Google picks text that fits the query. So a description is a strong suggestion rather than a setting. Writing one still pays, because it is the summary you control, and it is the text people see whenever Google does use it.
Where the width of a snippet goes
The same page says there is no limit on how long a meta description can be, but the snippet is truncated as needed to fit the device width. A byline date, when Google shows one, sits in front of the text and uses part of that width; Google estimates the date itself and does not guarantee to show it. In the worked example the date costs about 87 px, nearly a tenth of the desktop budget. You can also cap a snippet yourself: the robots meta tag rule max-snippet sets a maximum in characters, nosnippet removes it, and the data-nosnippet attribute keeps parts of a page out.
What makes a description worth showing
Google's advice is to write a unique, relevant summary for each page rather than one description shared across a site, and it notes that long strings of keywords give readers no clear idea of the page and are less likely to be shown. Specifics help: for a product, the facts a buyer compares; for an article, the author or the publication date. Large sites may generate descriptions from their data, as long as each one reads like a sentence written for a person. Put the detail that decides the click in the first line or so, where both estimates keep it.
Frequently asked questions
What is the ideal meta description length?
Google gives none. This checker compares the width with 920 px on desktop and 680 px on mobile at 14 px, which are reference figures for comparison. The 160 character example on this page measures about 995 px, so it is cut on both.
Why does Google ignore my meta description?
Google uses a meta description only when it judges it more accurate than text taken from the page, and the snippet can change with each search. A description that is missing, shared by many pages or made of keyword strings is less likely to be shown.
Does a date really take room from my description?
When a date appears it is part of the snippet line, so the description starts later and less of it fits. The checker measures the date and its joiner in the same font and subtracts that width from both budgets.
Can I limit or block the snippet Google shows?
Yes. A robots meta tag with max-snippet and a number caps the snippet at that many characters, nosnippet stops it, and data-nosnippet on an element keeps that part of the page out of snippets.
Does a better meta description improve rankings?
This checker makes no ranking claim. Google's snippet guidance is about describing a page well to the people searching, and the checker only helps you see how much of that description could appear.
Should every page have its own description?
Google says identical or similar descriptions on every page are not helpful. Give each page a description of its own; on a large catalog, building them from each item's data is fine when the result reads naturally.
Last updated .