A Mastodon line breaker helps your posts keep the structure you gave them as they travel across the Fediverse. Mastodon is not one app but a network of independent servers, and your post is shown by many different web and mobile clients. Most respect line breaks, but text written elsewhere and pasted in can lose its empty lines, and a carefully spaced post can arrive as one dense paragraph.
This free tool takes your text, places an invisible character after every line break, and gives you a version that keeps its blank lines when pasted into Mastodon. It shows a live character and line count against the 500 character limit that default Mastodon servers use, runs entirely in your browser, and needs no account.
Why spacing matters on Mastodon
Mastodon timelines are chronological and full of text. With no algorithm deciding what gets attention, readers scroll and choose what to stop on, and a post that is easy to read at a glance has an advantage. Short paragraphs separated by blank lines are the simplest way to get there within a 500 character budget.
Because posts are federated, they are displayed by whichever client each reader uses. Some servers and clients normalize whitespace differently, and text pasted from a document or another network can bring its own quirks. Keeping your spacing explicit means less depends on the path your post takes.
How the Mastodon line breaker works
The tool makes a single change: after every line break it adds a zero-width space, a Unicode character that has no width and is not displayed. An empty line now contains that character, so it is less likely to be treated as removable whitespace on the way to your followers.
The left box is where you write. It counts characters and lines as you type, measuring the formatted version the way Mastodon does, and shows the 500 character limit, turning red when you pass it. The right box shows the formatted version for Mastodon. Copy to Clipboard copies it, and Clear empties both boxes. No text leaves your browser.
How to use the Mastodon line breaker
- Type or paste your post into the left box. Leave a blank line between ideas, and put each list item on its own line.
- Check the counter against 500 characters. If your server allows longer posts, you can go past it; the red number is a guide, not a block.
- Look at the formatted version on the right.
- Click Copy to Clipboard.
- Paste into the compose box of your Mastodon client, add a content warning or alt text if the post needs them, then publish.
Good uses on the Fediverse
Structured short posts
A question, a gap, then two or three options on separate lines reads far better than the same text run together.
Threads of related posts
When a topic needs more than one post, consistent spacing in each one makes the thread feel like a single piece of writing.
Announcements from projects and communities
Open source projects, events and groups often post release notes or schedules. One item per line keeps them clear.
Posts cross-written from other networks
If you draft for several networks at once, pasting into Mastodon is where spacing tends to break. Running the text through the tool first keeps it intact.
Poetry and short fiction
Line breaks are part of the meaning in verse. The tool keeps stanza gaps where you put them.
Mastodon’s character limit and how it counts
Default Mastodon servers allow 500 characters per post, and individual servers can raise that limit, so your own server may allow more. Mastodon counts in its own way: any link counts as 23 characters however long it really is, and a mention counts only the username, not the server part after the second @.
The counter on this page applies the same rules. It counts each link as 23 characters and each mention by its username only, and it measures the formatted version, so the invisible character added after each line break is already in the number. If you are right at the edge, your Mastodon client has the final word, since your server may set its own limit.
Best practices for Mastodon posts
Write hashtags in CamelCase
Capitalising each word, as in #OpenSource, makes tags easier to read and lets screen readers pronounce them as words.
Use content warnings thoughtfully
Mastodon culture uses content warnings for spoilers, heavy topics and long posts. Put a short, clear summary in the warning so people can decide whether to expand it.
Add alt text to images
Many people on Mastodon rely on image descriptions, and many skip boosting images without them. Write alt text for every image you attach.
Keep hashtags at the end
Mastodon search relies on hashtags, so they matter. Grouping them on a final line, after a gap, keeps the body easy to read.
One blank line is enough
A single empty line separates ideas. Several in a row waste vertical space in a timeline that people scroll quickly.
Mistakes to avoid
Do not let the invisible character sit directly in front of a hashtag or a mention at the start of a line if your client fails to link it. Mastodon detects hashtags and mentions by the characters around them, and an unusual character can occasionally get in the way. If a tag does not link in the preview, delete and retype its first character in the compose box.
Avoid pasting formatted text into fields that need exact values, such as your display name, profile metadata or a search box. And do not use spacing to pad a post: if your post only fits by squeezing out empty lines, it may be better as two posts in a thread.
Accessibility on Mastodon
Accessibility is a strong norm on the Fediverse, and spacing is part of it. Short lines and clear paragraphs help readers with low vision, dyslexia or a screen magnifier. Zero-width spaces are generally ignored by screen readers, so your post is read aloud as written.
The tool does not add alt text, content warnings or CamelCase hashtags for you. Those are written by hand in your Mastodon client, and they matter more to many readers than any formatting choice.
Where it fits in your workflow
For an occasional post, this page is all you need. If you publish to Mastodon alongside other networks, FoPost lets you keep a Mastodon version of each post, check it against the limit, and schedule it with the rest, so the Fediverse gets a post written for it instead of a copy cut down from somewhere else.