# Character limits that actually matter in 2026

> The limits worth knowing: 60 characters for a title tag, 155 for a meta description, 280 for an X post, 160 per SMS segment. Google actually truncates titles at about 580 pixels rather than a character count, so a title full of wide capitals gets cut sooner than the count suggests.

Source: https://rankcert.com/blog/character-limits-guide
Published: 2026-09-02 · Updated: 2026-09-02

---


Most character limits are enforced silently. The form accepts your text, the platform truncates it, and you find out when you see it live.

## The limits worth memorising

| Where | Limit | Notes |
| --- | --- | --- |
| Title tag | ~60 chars | Actually a pixel limit, see below |
| Meta description | 155 chars | ~120 on mobile |
| X post | 280 chars | Links count as 23 regardless of length |
| SMS segment | 160 chars | 70 if any character is non-GSM |
| Instagram caption | 2,200 chars | Truncated at ~125 in feed |
| LinkedIn post | 3,000 chars | "See more" at ~210 |
| YouTube title | 100 chars | Truncated at ~70 in most surfaces |
| Open Graph title | ~88 chars | Platform-dependent |

Free tool: [Character Counter](https://rankcert.com/tools/character-counter) - Count characters with and without spaces in real time, plus words, sentences and paragraphs, against the limits for meta descriptions, X posts and bios.

## Google measures pixels, not characters

This is the one that surprises people. Google truncates the title in search results at roughly 580 pixels on desktop, not at a character count.

A title in narrow characters fits far more than 60. A title in capitals, or heavy with W and M, gets cut at 50. `WWWWWWWWWW` and `iiiiiiiiii` are both ten characters and one is four times wider.

Meta descriptions work the same way, truncating around 920 pixels desktop and 680 mobile.

The practical rule: aim for 60 characters, put the important words first, and check the rendered result rather than trusting the count. If the title is cut, nothing is lost provided the front half carries the meaning.

## Emoji are not one character

An emoji is one *grapheme* and usually several *code units*, and almost every web form counts code units.

- Simple emoji like ☕ - 1 unit
- Most emoji like 😀 - 2 units
- Skin tone modifiers - 4 units
- 👨‍👩‍👧‍👦 (family) - 11 units

So an X post with ten family emoji has burned 110 of its 280 characters. Any counter that reports what JavaScript's `.length` reports - including most form validators and this site's counter - is showing code units, which is what the platform will count too.

## SMS is stricter than it looks

A standard SMS holds 160 characters using the GSM 7-bit alphabet. Introduce one character outside that alphabet - a curly quote, an em dash, an emoji - and the whole message switches to UCS-2 and the limit drops to **70**.

This is why a 150-character message sometimes bills as three. The usual culprit is a smart quote pasted from a word processor. Strip typographic punctuation from anything going to SMS.

Messages over the limit are split into segments of 153 (or 67) characters, since each segment carries a header saying how to reassemble it.

## Word count is a different question

Character limits are hard constraints. Word count is not - there is no word limit on a blog post, and no ranking benefit to hitting a number.

The only useful benchmark is the pages already ranking for the query. If they all cover eight subtopics and you cover three, the gap is coverage, not length. Padding to reach a word target adds nothing and dilutes what is there.

## Practical habits

- Write the title and description to fit, do not trim afterwards. Trimming produces truncated sentences; writing to length produces complete ones.
- Front-load. Assume the last third of anything will be cut.
- Check the rendered result for anything user-facing - the [meta tags checker](/tools/meta-tags-checker) shows the actual title and description a crawler reads.
- Count before you paste, not after it fails, with the [character counter](/tools/character-counter).