Every platform that shows text to people has to decide, somewhere in its design, how much of it to allow or display at once — and those decisions turn into the character limits that shape how social posts, text messages, and search results get written. Knowing the actual numbers, and why they exist, makes it much easier to write for a limit instead of discovering it the hard way when a post gets cut off.

Common character limits at a glance

  • X (Twitter) post: 280 characters
  • SMS text message: 160 characters per segment (longer messages are split and reassembled)
  • Google search result title: no strict character cap, but roughly 50–60 characters is the practical display width before truncation
  • Meta description: no strict cap either, but roughly 150–160 characters is the commonly used safe planning length
  • Instagram caption: 2,200 characters allowed, but only the first ~125 characters show before "more"
  • YouTube video title: 100 characters

Why SMS specifically works in 160-character segments

The 160-character SMS limit comes from an old technical standard (GSM-7 encoding) used to fit a text message into a single data packet on early mobile networks. A message longer than that gets automatically split into multiple linked segments behind the scenes and reassembled on the receiving phone, which is why a long text still arrives as one message even though it was technically sent as several — but each segment is billed and encoded separately, which is also why messages using certain emoji or non-Latin characters can hit a much lower per-segment limit (70 characters) under a different encoding.

How to write effectively within a limit

Front-load the most important information first, since a reader (or a platform's preview) may only show the opening portion before a cutoff. Cut filler words ruthlessly — "in order to" can almost always become "to," and qualifiers like "very" or "really" rarely add real meaning. It also helps to check whichever limit is actually enforced by the platform you're writing for, rather than assuming a number you remember from a different one — the specific limits above shift occasionally as platforms update their products.

The nuance behind Google's title and description limits

Google doesn't actually enforce a fixed character count for titles or meta descriptions — what it enforces is a pixel width, since the snippet is rendered visually in a search result. That's why two titles with the same character count can get truncated differently: a title full of wide letters like "W" and "M" takes up more pixel space than one full of narrow letters like "i" and "l," even at an identical character count. The commonly cited 155–160 character guideline for meta descriptions is a practical approximation of that pixel limit, not an exact rule, which is why it's worth previewing how a title or description actually renders rather than trusting the character count alone. The same pixel-width logic applies to page titles shown in search results, which is part of why two titles that look the same length in a text editor can display very differently once Google renders them.

Try the Text Tools yourself — free, instant, no sign-up.

Open the calculator

Frequently asked questions

Why is the SMS limit 160 characters specifically?

It comes from the GSM-7 text encoding standard used on early mobile networks, which was built to fit a message into a single data packet at that character count; longer messages are automatically split into linked segments and reassembled on arrival.

Does Google actually cut off meta descriptions at a fixed character count?

Not exactly — Google truncates based on pixel width in the rendered search result, not a strict character count, which is why the commonly cited 150–160 character guideline is an approximation rather than an exact technical limit.

Do emoji count differently toward character limits?

Often yes. Many platforms count certain emoji as two characters instead of one, and SMS messages containing emoji or certain non-Latin characters can switch to a lower-capacity encoding with a shorter per-segment limit, so a message with emoji can hit its limit sooner than the plain-text character count would suggest.