Make the draft fit
How to shorten a tweet without losing the point
Your draft is over 280 characters. Cutting the example or the caveat would make it fit, but it would also change what you're saying. Remove the setup before you remove the substance.
On this page
Keep the point before cutting the words
To shorten a tweet, identify the sentence you want someone to remember. Keep the detail that supports it and any condition that limits the claim. Then cut the introduction, repeated explanation, and unrelated second idea before replacing words with abbreviations.
A draft that fits but no longer says what you mean needs another edit. "One person couldn't find the button" cannot become "Nobody understands the interface" just because the second sentence is shorter.
X's posting guide describes ordinary posts of up to 280 characters and longer posts for eligible subscribers. This guide is for making one ordinary post fit. It does not assume that every account or publishing tool accepts a longer version.
Keep a copy of the full draft while you edit. You may want the detail later, even if it doesn't belong in this post. If the problem is finding the saved version, the Twitter drafts guide covers where to look.
Three shorter tweets, with the counts checked
These are fictional writing examples, not the founder's posts or customer results. Each pair uses plain ASCII text with no links or emoji, so the character counts include the spaces and punctuation as written.
1. Remove the account of how you arrived at the point
The useful change is where the research notes live. The opening delays it.
Before: 330 characters.
I've been spending a lot of time thinking about how to make my writing process less frustrating, and one change I made this week was to move my research notes beside the draft instead of keeping them in a separate document. I can now check the source without switching windows. I haven't measured whether it makes me write faster.
After: 145 characters.
I moved my research notes beside the draft so I can check sources without switching windows. I haven't measured whether it makes me write faster.
The edit keeps the change, its practical use, and the unmeasured outcome. It removes the preparation for saying them. There is no need to fill the remaining space: 280 is a limit for this format, not a target.
2. Name the reader once, then give the action
This draft gives photographers a small portfolio check. Its opening describes that audience at length before reaching the check.
Before: 346 characters.
If you are a photographer who is trying to put together a portfolio and you are having a hard time deciding which images should appear first, something you could try is asking one person what kind of work they think you want to be hired for after looking at the first three images. Their answer may show you a mismatch before you add more photos.
After: 183 characters.
Photographers: show someone the first three images in your portfolio. Ask what work they think you want to be hired for. Their answer may reveal a mismatch before you add more photos.
The reader, number of images, question, and possible use of the answer survive. "Improve your portfolio" would be shorter still, but it would discard the instruction that made the post worth reading.
3. Keep the limitation that prevents a false result
Here the writer observed one person during a call. There is no completed experiment or measured signup improvement.
Before: 352 characters.
Yesterday I watched one person try the new signup form during a call. They stopped when they reached the company-size field and asked why we needed that information. We haven't changed the form or tested a different version yet, so I don't know whether removing that field would increase completed signups. It's the next question I want to investigate.
After: 192 characters.
One person paused at the company-size field in our new signup form and asked why we needed it. We haven't tested removing it. Next I want to test whether removing it changes completed signups.
Removing "one person" or "haven't tested" would save space by changing the evidence. Keep those words. A punchier claim about a field killing conversions would require a result the writer doesn't have.
Cut in an order that preserves meaning
Read the whole draft before editing individual words. If it contains two independent points, choose which one this post should make. Save the other as a separate idea with enough context to stand alone; don't cut both explanations until neither makes sense.
Next, remove sentences that only announce the point or repeat it afterward. "I wanted to share a quick observation" can often disappear. "We haven't tested it" cannot disappear when it is the difference between an observation and a result.
Replace long phrasing when the replacement means the same thing. "At this point in time" can become "now." Keep a technical term when it names the actual problem, and don't substitute an abbreviation your intended reader may not know.
Read the shortened post without the original beside it. Check whether a stranger can tell what happened, what you suggest, or what remains unknown. If you are mostly cutting the first line, the Twitter hook guide explains how to bring the useful point forward without making the claim bigger.
Check the count that X actually uses
X uses a weighted count rather than treating every visible symbol alike. Its character-counting documentation describes these rules:
| Content in the post | How it counts |
|---|---|
| Ordinary Latin letters and common punctuation | Usually one character each |
| Emoji, including supported combined sequences | Two characters per emoji |
| Chinese, Japanese, and Korean characters | Two each |
| A valid URL detected in the text | 23 characters, regardless of its original length |
| Hashtags and manually typed mentions | Count as text, including the tag or handle |
A word processor's count may therefore differ from the count in X. Don't remove a useful emoji based only on how many underlying symbols your editor reports, or assume every language has room for 280 visible characters.
X's link-posting guidance explains its t.co handling. Replacing a recognized long URL with a shorter URL doesn't reduce the fixed 23-character allowance. Edit the surrounding sentence instead, and verify that the link still opens the intended page. Don't damage the destination to make the text box look shorter.
Use the free PilotMyX Twitter character counter and post preview to compare your drafts. The text preview and estimated weighted count update as you type, with the draft processed in your browser. It is an estimate, not a guarantee of how every emoji sequence or account-specific limit will behave. Check the final text in X before publishing.
Ask an agent for cuts, not a new story
If an AI keeps turning your draft into a different opinion, give it the facts and qualifications it must preserve. The guide to writing Twitter posts in your voice covers voice examples; the task here is narrower.
Shorten this original X/Twitter draft to fit an ordinary post.
Draft: [full text]
Point I want to keep: [one sentence]
Facts, numbers, attribution, and uncertainty that must stay: [list]
Link or mention that must stay unchanged: [exact text, or none]
Intended reader: [who should understand it]
Show one edited version and explain what you removed.
Preserve the meaning and my tone. Do not invent results, make a
claim more certain, or add a call to action I didn't request.
If it cannot fit without losing essential context, tell me which
idea needs a separate explanation instead of forcing the edit.
Do not save a draft, schedule, or publish anything.
Check the exact text rather than trusting a character count in chat. Compare the revision with the original, verify it in the counter, and read it aloud once. Stop cutting when the post fits and still says what you intended.
Use your own account