Message Splitter

The right number depends on the channel, and the safest approach is to check the limit rather than assume it. SMS is the strictest and the most surprising: 160 characters when the whole message uses the GSM-7 alphabet, but only 70 as soon as a single emoji, curly quote or accented letter forces it into Unicode.

Longer messages are usually delivered as several linked segments, each carrying a header, which drops the usable space to 153 characters per part in GSM-7 and 67 in Unicode. If you are billed per segment, splitting deliberately at 153 gives you control over the number of parts instead of leaving it to the carrier.

• 70 characters: a single SMS that contains any emoji or accented character.
• 153 characters: one part of a multi-part SMS written in the GSM-7 alphabet.
• 160 characters: a single plain-text SMS with no Unicode characters in it.
• 280 characters: a short public post on a microblogging platform.
• 1,000 to 2,000 characters: typical caps for chat and community platform messages.

Splitting strictly on a character count will cut through the middle of a word, which reads badly and occasionally changes the meaning. With word-safe splitting on, each chunk ends at the last space that fits, so parts come out slightly shorter than the limit but always readable. Turn it off only when exact chunk length matters more than legibility.

Numbering adds a marker such as (1/4) to every part. It is worth the characters it costs, because messages sent in sequence often arrive out of order, and a reader who can see there are four parts will wait for the rest. Remember that the marker itself is counted, so budget a handful of characters for it.

If the limit exists because the platform wants shorter posts, several chained messages can read as spam and may be rate-limited or hidden. A single link to a longer document is often better received. Some platforms also collapse rapid repeat messages from one account, so the later parts of a long chain may never be seen at all.

Splitting is at its best for technical limits rather than social ones: a form field with a hard maximum, a legacy system that truncates at 255 characters, an SMS gateway billed per segment, or a caption box that silently drops the overflow. In those cases the chunk boundary is a constraint, not a style choice.