By Vibe Apps Pro Team · Published: 2026-07-26
Meta Description Length: Exact Character Limits in 2026
Google truncates meta descriptions by pixel width, not character count. See the real desktop, mobile, and social limits for 2026 — check yours free.
Google's practical cutoff for a meta description is 150–155 characters on desktop and around 120 on mobile — but neither number is a hard rule Google publishes. Both are estimates of a pixel-width limit, and Google can ignore your tag entirely and write its own snippet if it thinks your page text is more relevant. That gap between "character count" and "what actually gets displayed" is where most meta-description advice goes wrong.
Here's the real mechanism, the current 2026 limits by device and platform, and how to check a draft before it ships.
Why Google Doesn't Actually Use a Character Limit
Google's search results snippet is capped by pixel width, not character count — roughly 920px on desktop, rendered in a proportional font. A proportional font doesn't give every letter equal space: a capital "W" or "M" eats close to three times the pixel width of a lowercase "i" or "l".
Here's the same 100-character length rendering to two very different widths, purely from letter shape:
| Example (both exactly 100 characters) | Approx. Rendered Width | Room Before the ~920px Cutoff |
|---|---|---|
| "Compare word, character, and line counts instantly — no signup, no upload, 100% private." | ~640px | Wide margin left |
| "WWW MMM 1000 ALL CAPS WORDS WITH WIDE CAPITAL LETTERS AND NUMBERS EVERYWHERE TODAY NOW" | ~910px | Right at the edge |
Same character count, nearly 300px apart. In practice, a caps-and-numbers-heavy draft can clip as early as 140 characters, while a lowercase-heavy one can run past 165 before Google cuts it. Character-count advice — including the numbers in this article — is a working estimate of that pixel boundary, not a spec.
155 characters is the safe target because it leaves margin on both sides of that estimate. Write to it, don't optimize to the character.
2026 Character Limits by Context
Google's SERP isn't the only place a description gets truncated. Here's the full picture, since social previews use entirely separate tags with their own limits:
| Context | Practical Limit | What Happens Past It |
|---|---|---|
| Google Desktop SERP | ~155–160 characters (≈920px) | Truncated with an ellipsis, mid-word if needed |
| Google Mobile SERP | ~120 characters (≈680px) | Truncated earlier — narrower viewport, same font logic |
| Google (any device) | N/A — relevance-based | Google may discard your tag and auto-generate a snippet from page content |
| Facebook / Open Graph preview | ~300 characters shown, feed can cut earlier on mobile | Truncated with an ellipsis, no rewrite |
| LinkedIn link preview | ~200 characters, less on the mobile app | Truncated with an ellipsis |
The desktop-versus-mobile split matters more than most checklists suggest. If you write to the desktop limit alone, you're gambling that the sentence you're most proud of — the second half — never gets seen by the majority of your traffic, which is mobile.
Meta Description vs. Open Graph Description — Don't Reuse the Same String
These are two different tags read by two different systems, and copy-pasting one into the other wastes character budget written for the wrong context:
<meta name="description">— read by Google (and Bing) for the SERP snippet. Optimized for a searcher scanning results, deciding which blue link answers their query.<meta property="og:description">— read by Facebook, LinkedIn, Slack, and other link-unfurling platforms. Optimized for someone who already clicked "share" and is skimming a feed, not searching.
A search snippet needs to answer "does this page match what I typed?" A social preview needs to earn a click from someone scrolling past it with zero search intent. Writing both tags separately, each to its own limit in the table above, consistently outperforms one shared string trimmed to fit both.
Common Mistakes That Waste the Character Budget
Keyword stuffing the description. Repeating your target phrase two or three times doesn't influence rankings — the meta description isn't a ranking factor, only a click-through lever. It does make the snippet read as spam to a human. If you're not sure whether a draft has drifted into stuffing territory, our keyword density explainer covers why "ideal density" stopped being a real target back in 2011.
Writing a summary instead of a pitch. A meta description that restates the H1 in different words wastes the click-through opportunity. The strongest ones answer "why should I click this result instead of the nine others on the page" — a number, a promise, or a specific outcome, not a paraphrase.
Letting a CMS auto-generate it from body text. Most CMS platforms fall back to the first 155 characters of your article when no description is set. That's rarely the sentence you'd choose deliberately, and it's exactly the kind of low-effort snippet Google is most likely to override with its own auto-generated one anyway.
Ending mid-thought at the estimated cutoff. Since 155 characters is an estimate, not a guarantee, don't put your call-to-action or the most important clause right at the boundary — put it earlier, and treat anything after character 120 as a bonus for the readers who see the full desktop version.
Check Your Draft Before It Ships
Rather than counting by hand or guessing at the pixel math, paste your draft into our Character Limit Checker — runs 100% in your browser, zero data sent to any server — and switch to the built-in meta description preset for a live, color-coded gauge against the 160-character estimate. It gives you an instant green-or-red visual read before you commit the tag to your CMS, no mental pixel math required.
The tool counts at grapheme-cluster granularity via Intl.Segmenter, so an em dash, an accented character, or an emoji in your description counts as the one visible character it actually is — not the raw UTF-16 length JavaScript's .length property would report. That distinction matters if your brand name has an accent or your description ends on a checkmark or arrow.
If you're maintaining meta descriptions across dozens of template pages — an e-commerce category structure, a docs site — and need to batch-fix a boilerplate pattern that's run too long everywhere, Find & Replace with regex handles the bulk edit faster than opening each page individually. And once a rewritten batch is done, the Word Counter gives you a second, whole-page gut check if you want raw word and character counts side by side without switching tools.
When a description is simply too long and you want a hard cut rather than a rewrite, the Text Truncator trims to an exact character count on a word boundary, so you never ship a description that ends mid-word. It has a "preserve HTML tags" mode too, which matters if your CMS stores descriptions as rich-text fragments — truncating those with a plain substring() leaves an unclosed tag that can break the rendered page, not just the snippet.
The Platform-Limits Pattern Repeats Everywhere
Meta descriptions aren't the only place a "simple" character limit turns out to be a rendering approximation rather than a hard rule. Social platforms have the same problem across bios, captions, and post bodies — our social media character limits guide breaks down the current 2026 numbers for Twitter/X, Instagram, LinkedIn, and the rest, including where each platform's own "fold" cuts a caption before a reader ever taps "see more."
The pattern to remember: whenever a limit is described in characters but enforced by rendering, build in margin. 155 isn't a wall — it's where the estimate stops being reliable.