2026-07-21
Character limits are the real design brief
Cross-posting falls apart when every network is treated like the same text box. The limits are the product.
When people talk about cross-posting they usually mean the same string in every box. That works until it does not. X cuts you off at 280 unless you pay them. Bluesky is in the same neighborhood, around 300. Threads gives you a bit more room. Mastodon depends on the instance, often 500. LinkedIn will let you write an essay. Telegram will let you write a short chapter. Instagram wants a caption under a photo, not a blog post with a thumbnail.
Those numbers are not trivia you put in a help article. They are the design brief. If your tool pretends every network is a Facebook caption, you will either truncate badly or you will train yourself to write the timid middle length that is slightly too long for X and slightly too thin for LinkedIn.
Default short, override long
I wanted the default to be the short version, because most of my posts start that way, and then a place to write the longer one without leaving the same post. The override is not a power feature I added so the pricing page would have a bullet. It is how I actually write.
A typical post for me looks like this. The default is two or three sentences that would survive on Bluesky. The LinkedIn override adds the setup: why this matters, who it is for, what I tried first. The Mastodon override might keep the short take and swap the link for a plain URL. Instagram, if it is in the set at all, gets the photo and a caption that does not assume you read the LinkedIn version.
None of that requires an AI rewriter. It requires seeing the destination while you edit. A character counter that knows where the text is going is more useful than a generic note that you have typed 412 characters. I even shipped a free counter on the site for that reason. You do not have to be a customer to use it.
What I look at when I try someone else's scheduler
If you are choosing a scheduler, ignore the screenshots of dashboards for a minute and ask a narrower question. When the limits disagree, does the product make that disagreement visible, or does it hide it until publish fails?
A lot of tools hide it. They show one box, a row of colorful icons, and a sense of progress. Then X rejects the post, or Mastodon eats the last paragraph, or LinkedIn goes out with a truncated joke because the author wrote for the shortest network and padded nothing. The failure is not mysterious. The UI never admitted the networks were different.
I would rather a composer that feels slightly stricter and tells the truth. The limits are not a nuisance on top of the product. For a cross-poster, they are the product.
Try the composer
Sign in with Google, connect the accounts you actually use, and publish or schedule.
Get started