Why Character Count Matters More Than You Think
Master the art of writing within limits. From social media to resumes, learn why every character counts and how to make your words work harder.
A friend once spent two hours writing a Google Ads headline, sent it to me for feedback, and I had to tell her it was 47 characters over the limit. The headline was genuinely good — punchy, specific, with a real hook. But Google Ads headlines cap out at 30 characters, and there's no negotiating with an algorithm. She had to cut it down to something that felt like a pale shadow of the original. The lesson I took from watching her frustration: write to the constraint from the start, not after.
Character limits aren't arbitrary. Each platform set its limit based on something real — screen size, SMS packet structure, cognitive load research, search result rendering. Understanding why the limits exist makes it easier to write within them well, rather than just frantically deleting words until the count turns green.
The Limits That Actually Matter
Different platforms have different constraints, and getting them confused is a consistent source of wasted work. Here are the ones worth memorizing:
- Twitter/X: 280 characters per tweet. URLs always count as 23 characters regardless of actual length (Twitter wraps them). Images attached to a tweet don't consume characters.
- SMS: 160 characters in the GSM-7 character set. If you include a single character outside that set (like a curly apostrophe, an em-dash, or any emoji), the entire message switches to UCS-2 encoding and the limit drops to 70 characters per segment.
- Meta descriptions: Google typically displays 155–160 characters in search results before truncating with an ellipsis. Write past that and your carefully crafted ending gets cut.
- Google Ads headlines: 30 characters. Descriptions: 90 characters. These are hard stops — the platform won't let you save over the limit.
- LinkedIn posts: 3,000 characters before the "see more" truncation kicks in for the feed preview. The first 210 characters are what most people actually read.
- Email subject lines: Most email clients display roughly 60 characters on desktop, 30–40 on mobile. No enforced limit, but anything past 60 is statistically invisible to mobile users.
The SMS case is the one that catches people off guard most often. You can check your character count with the Text Counter tool, but a basic counter won't tell you whether you've accidentally switched encoding. If you're doing SMS campaigns, test with the actual sending platform before going live.
Bytes vs. Characters: Why They're Not the Same
This distinction matters far more than most people realize. When a developer says "string length," they often mean the number of UTF-16 code units in memory, not the number of visible characters a human would count. For plain ASCII text, these are identical. For anything else, they diverge.
Emoji are the most common example. The thumbs-up emoji 👍 is a single visible character, but it's encoded as two UTF-16 code units (a "surrogate pair"). JavaScript's string.length property returns 2, not 1. If a platform uses JavaScript's native string length to enforce its limit, a 280-character tweet containing 10 emoji might actually be calculated as 290 by the underlying code. MDN documents this behavior explicitly.
Chinese, Japanese, and Korean characters (CJK) present a different problem. A single CJK character is one character and one code unit in JavaScript, but it's 3 bytes in UTF-8 encoding. Platforms that measure limits in bytes rather than characters (some database fields, some legacy APIs) will cut off your text much sooner than you'd expect. A 255-byte VARCHAR field holds 255 ASCII characters but only 85 Chinese characters.
The practical implication: if you're writing content that includes emoji or non-Latin scripts and the platform matters to you, test actual submission rather than trusting a generic character counter. The Unicode Text Segmentation specification (UAX #29) defines what should count as a single user-perceived character, but not every platform follows it consistently.
How to Write Shorter Without Losing Meaning
The most effective technique I've found is to write the thesis sentence first, then build around it. When you start writing and meander toward your point, you end up with a lot of setup that doesn't survive cutting. When you start with the point and add supporting detail, every word has a job and you can see clearly which ones are carrying weight.
Active voice is the other big lever. "The report was submitted by the team on Friday" is 49 characters. "The team submitted the report Friday" is 36. Same information, 13 characters saved, and the sentence is cleaner. Passive voice constructions almost always cost you characters without adding precision.
Some specific patterns to cut when you're over the limit:
- "In order to" → "to" (saves 9 characters every time)
- "Due to the fact that" → "because" (saves 13 characters)
- "At this point in time" → "now" or "currently"
- "A large number of" → "many"
- "Has the ability to" → "can"
- Filler adjectives: "very," "really," "quite," "rather" — these almost never add meaning
For headlines specifically, concrete nouns and strong verbs outperform adjective-heavy phrasing almost every time. "Cut your tax bill by 30%" outperforms "Discover amazing strategies for significantly reducing your annual tax obligations" — and it's 96 characters shorter.
Meta Descriptions Deserve More Attention Than They Get
Google doesn't use meta descriptions as a ranking signal, which leads a lot of people to treat them as an afterthought. That's a mistake. The meta description is your ad copy in search results. It directly influences whether someone clicks your result or the one above or below it.
The 155–160 character window is tight but workable. A useful structure: one sentence stating what the page covers, one sentence with a specific benefit or differentiator, and a soft call to action if you have room. The most common failure mode is writing a description that accurately describes the page but gives the reader no reason to click. "This article covers unit conversion methods" is accurate and useless. "Learn why a $327 million Mars probe failed because of a unit conversion error — and how to avoid similar mistakes in everyday work" is accurate and interesting.
Worth knowing: Google rewrites meta descriptions fairly often — studies have found rewrites happen more than 60% of the time. Google tends to rewrite when it thinks your description doesn't match the page content, or when a different excerpt would better match the search query. Writing a genuinely accurate, useful description reduces how often this happens.
Tools and Workflows for Counting Consistently
The simplest workflow is to keep a character counter open while writing rather than checking at the end. Writing knowing the limit is in place changes how you phrase things from the first sentence. It's the same reason writing on index cards forces cleaner thinking than writing on a blank document — the constraint is visible the whole time.
For teams that write a lot of platform-specific copy, a shared template with the character limits labeled for each field saves more time than you'd think. A Google Ads template where each field shows "30 max" or "90 max" means writers don't have to remember the limits and reviewers can spot overruns at a glance.
The Text Counter tool gives you live character, word, and sentence counts as you type. For quick checks — paste your meta description, confirm it's under 160, move on — it's faster than switching to a specialized platform. If you're doing anything where byte count matters rather than character count, you'll want a tool that explicitly reports bytes, which most generic counters don't.
The broader skill here is treating character limits not as obstacles but as editing prompts. Every time a platform forces you to cut, it's asking: what's the most essential version of this? The answer is usually better than what you started with.