Fediverse Post Formatter

Free forever, no sign-up, no watermark

Format your posts for Fediverse platforms including Mastodon, Misskey, Pleroma, and other ActivityPub-compatible services.

Formatting Options

Your formatted text will appear here...

Tips for Fediverse Post Formatting

  • Character limits vary by Fediverse instance (typically 500).
  • Line breaks carry over to most ActivityPub platforms, though each app displays posts its own way.
  • Use hashtags for cross-instance discoverability.
  • Clean formatting works across Mastodon, Misskey, Pleroma, etc.
  • Content warnings are a Fediverse best practice for sensitive topics.

The fediverse post formatter prepares text that will travel across many different servers and apps. The fediverse is not one network: it is thousands of independently run servers, using different software, that exchange posts through a shared protocol called ActivityPub. A post you write on one server can be read on Mastodon, Misskey, Pleroma, Akkoma, Friendica, Pixelfed and more, each of which displays it in its own way. Clean, plain formatting is what survives that journey best.

Paste your draft and the formatter trims stray spaces from each line, collapses double spaces, reduces long gaps to a single blank line, and can move hashtag lines into one row at the end. The result is text that reads well no matter which software your readers use. This guide explains why plain formatting matters so much in a federated network, what the tool does, and how to write posts that look right everywhere.

Why the fediverse needs a different approach to formatting

On a single network, you can see exactly how your post will look because everyone uses the same app. In the fediverse, your post leaves your server and is shown by software you have never used. Some platforms support Markdown, some have their own markup, some allow rich text through HTML, and some show only plain text. Bold text written one way on your server may arrive elsewhere as literal asterisks, or be stripped entirely.

The safest common ground is plain text with real line breaks: short paragraphs separated by one blank line, links on their own line, mentions and hashtags written normally. Every fediverse platform understands that. The formatter is built to produce exactly this kind of portable text, rather than decoration that only works in one place.

What the fediverse post formatter does

The tool works in your browser and does not connect to any server.

It also does some cleanup you never have to switch on. Invisible characters such as zero-width spaces, word joiners and byte order marks are stripped, Windows line endings are turned into plain line breaks, and non-breaking spaces and similar odd spaces from word processors become regular spaces. Because old spacers are removed first, a post that was already formatted does not end up with two invisible characters after each line break. Five switches then let you choose the rest of the cleanup:

Trim Lines

Removes spaces at the start and end of each line. Some software collapses leading spaces and some keeps them, so removing them gives the same result everywhere.

Fix Double Spaces

Collapses repeated spaces to one, since different renderers treat runs of spaces differently.

Clean Extra Whitespace

Limits gaps to one blank line. Long runs of empty lines may be kept on one platform and squashed on another, so a single blank line is the predictable choice.

Preserve Line Breaks

Adds an invisible zero-width space after each line break. It can help if you paste into an app that drops empty lines, but most fediverse software keeps line breaks, and the invisible characters count toward length limits. It starts switched off here, so turn it on only if you see empty lines disappearing.

Separate Hashtags

Gathers every line made up only of hashtags into one row at the end of the post. A line that just begins with one, like #1 tip, stays in the body. Hashtags are how posts travel between servers, so keeping them tidy and together is useful.

How to use the fediverse post formatter

  1. Paste your post into the Your Text box.
  2. Watch the counter. It measures the formatted post the way Mastodon counts, with each link as 23 characters, and uses 500 characters, the default on standard Mastodon servers, as a conservative guide. Your own server may allow more.
  3. Remove any Markdown or platform-specific markup you are not sure every reader's app will understand.
  4. Leave Preserve Line Breaks off, as it starts, unless your posting app drops empty lines.
  5. Put hashtags on separate lines and switch on Separate Hashtags to collect them at the end.
  6. Copy the Formatted for Fediverse output into your server's composer, add a content warning and image descriptions where needed, and post.

Character limits differ from server to server

There is no single fediverse character limit. Each software project sets its own default, and each server admin can change it. Standard Mastodon uses 500 characters, while other platforms commonly allow much longer posts, and some are built around images or long-form articles instead of short notes.

This matters when your post is read elsewhere. A long post written on a server with a generous limit will still arrive on Mastodon servers, where it may be shown in full but collapsed behind a read more control, depending on the app. If you want a post to read comfortably everywhere, keeping it near 500 characters is a sensible habit, which is why the counter here uses that number. Treat it as a guide, not a rule: your composer shows your real limit.

Use cases across the fediverse

Posting from non-Mastodon software

If you post from Misskey, Akkoma, Friendica or similar software, many of your followers read you through Mastodon apps. Plain formatting means your post looks intended on their side too.

Accounts with followers on many platforms

Projects, publications and community accounts are often followed from many kinds of servers at once. One clean version of a post serves all of them.

Bridged and relayed posts

Some posts travel through relays or bridges that pass content between networks. Simple text with standard hashtags and links is the least likely to be mangled along the way.

Group and forum-style posts

Some fediverse software organizes posts into groups or threads like a forum. A clear first line and tidy paragraphs help a post work both as a timeline update and as a discussion starter.

Moving between servers

When you rewrite a pinned introduction or profile post after moving to a new server, run it through the formatter so it looks consistent with your new home.

Best practices for portable fediverse posts

Write in plain text first

Assume your reader sees no styling at all. If the post still reads well, any extra formatting a platform adds is a bonus, not a requirement.

Use content warnings consistently

Most fediverse software supports a content warning or summary field, though each shows it a little differently. Use one for sensitive topics and spoilers, especially when posting to communities that expect it.

Add descriptions to every image

Image descriptions travel with the media to other servers. They are widely expected across the fediverse and make your post usable for people with screen readers.

Write hashtags in CamelCase

Tags such as #OpenSource are easier for people and screen readers to read than lowercase run-together words, and they still match the same tag on every server.

Give links their own line

Some software shows a preview card for links and some does not. A link on its own line reads cleanly whether or not a card appears.

Mistakes that break across servers

Depending on platform-specific markup

Special markup for colors, animations or styled text may work beautifully on your own server and show up as raw code elsewhere. Keep it for posts meant mainly for your own community.

Unicode lookalike letters

Mathematical bold and italic characters look styled in most apps but are read letter by letter by screen readers and are not found by search. Avoid them for anything important.

Expecting hashtags to reach everyone

A hashtag search on a server shows posts that server knows about. Your post spreads further as people follow and boost it, so tags help discovery but do not guarantee reach across the whole network.

Leaving hidden characters in the text

Zero-width spaces from Preserve Line Breaks are invisible but still count as characters, and they are unnecessary on most fediverse software. Leave that switch off unless you need it.

Publishing to the fediverse on a schedule

If you post to a Mastodon account as part of a regular schedule, FoPost can publish to it alongside your other networks. Format the text once here, check it, and schedule it with everything else. For posts from other fediverse software, copy the formatted text into that server's composer.

Frequently asked questions

What is the fediverse?

The fediverse is a network of independently run servers, using different software, that share posts with each other through the ActivityPub protocol. Someone on a Mastodon server can follow and reply to someone on Misskey, Pleroma, Friendica or Pixelfed, and the reverse.

How is this different from the Mastodon post formatter?

The cleanup switches are the same, but the advice differs. The Mastodon page focuses on Mastodon's own rules, such as its link counting. This page is about writing posts that read well on any fediverse software, where limits, markup and display all vary.

What is the character limit on the fediverse?

There is no single limit. Each platform sets a default and each server can change it. Standard Mastodon uses 500 characters, and other software often allows more. The counter here uses 500 as a conservative guide.

Is formatting preserved across ActivityPub platforms?

Line breaks, links, mentions and hashtags are preserved almost everywhere. Bold, italic, Markdown and platform-specific markup are not reliable, since each app decides what to render. That is why plain text with clean spacing is the safest choice.

Do hashtags work across servers?

Yes. Hashtags are understood across fediverse software and help people find posts on topics they follow. A server's hashtag results show the posts it has received, so reach grows as your post is boosted and followed.

Should I use content warnings?

They are a widely shared fediverse practice for sensitive topics and spoilers. Most software supports them, though they look a little different in each app.

Does the tool post to my server?

No. It runs in your browser, connects to nothing, and does not save your text. You copy the result and publish it yourself.

The same tool for other networks