Mastodon posts, called toots, have a character limit that varies by instance. Unlike Twitter’s fixed 280 characters, Mastodon allows each server administrator to set their own maximum. This flexibility means a toot on one instance might be cut off or rejected on another. The default limit is 500 characters, but some instances allow 1000 or more. This article explains how the character limit works, how administrators configure it, and what users need to know when posting across instances.
Key Takeaways: Mastodon Character Limit Configuration
- Admin > Server Settings > Content Retention: Where instance administrators set the maximum toot character count.
- 500-character default: The standard limit on most Mastodon instances, configurable from 0 to 100000.
- Instance federation: A toot exceeding the local limit will be truncated when displayed on instances with smaller limits.
How the Mastodon Character Limit Works
Each Mastodon instance runs its own server software. The character limit is a server-side setting stored in the database. When a user submits a toot, the server checks its length against the instance’s configured maximum. If the toot exceeds the limit, the server rejects it with an error message. The user must shorten the post before it can be published.
The character limit applies to the visible text of the toot. It does not include media attachments, custom emoji, or links shortened by the server. However, content warnings and their text are included in the character count. The limit counts all Unicode characters, including spaces and punctuation.
Default Limit and Range
The default character limit in Mastodon is 500 characters. This value was chosen as a balance between Twitter’s 140-character limit and the need for longer-form discussion. Administrators can set the limit anywhere from 0 to 100000 characters. A limit of 0 effectively disables posting, while 100000 allows very long posts. Most instances set the limit between 500 and 1000 characters.
How the Limit Affects Federation
When a toot from another instance arrives, the receiving server stores it as-is. If the toot exceeds the receiving instance’s character limit, the server truncates the displayed text. The full toot remains available in the original instance’s API responses. Users on the receiving instance see a truncated version with a link to view the full post on the original instance.
Steps to Configure the Character Limit on Your Instance
Only instance administrators can change the character limit. The setting is in the administration panel under Server Settings. Follow these steps to modify the maximum toot length.
- Log in as an administrator
Use the Mastodon web interface with an account that has admin privileges. Navigate to the admin panel by clicking the hamburger menu and selecting Administration. - Open Server Settings
In the admin panel, click Server Settings in the left sidebar. This section contains all instance-wide configuration options. - Go to Content Retention
Scroll down to the Content Retention section. This area controls how posts are stored and displayed. The character limit setting is located here. - Set the maximum toot length
Find the field labeled Maximum toot length. Enter the desired character count as an integer. The value must be between 0 and 100000. Click Save Changes at the bottom of the page. - Test the new limit
Log out of the admin panel and create a new toot as a regular user. Compose a post near the new limit to verify the server accepts it. Check that the character counter shows the correct remaining count.
Common Issues and Limitations
Toot Exceeds the Instance Limit
If a user tries to post a toot longer than the instance’s maximum, the server shows a red error banner. The user must delete characters until the count falls below the limit. The character counter in the compose box turns red when the limit is exceeded.
Toot Truncated on Other Instances
A toot that fits on one instance may be too long for another instance’s display. The receiving instance truncates the text at its own limit and appends a link to view the full post. This does not affect the original post on its home instance. Users can still see the full content by clicking the link.
Character Count Discrepancies
Different instances may count characters slightly differently. Some instances count URLs as a fixed number of characters, while others count the actual URL length. This can cause a toot to be accepted on one instance but rejected on another. The safest approach is to keep toots under 500 characters for maximum compatibility.
Mastodon Character Limit vs Twitter Character Limit
| Item | Mastodon | |
|---|---|---|
| Default limit | 500 characters | 280 characters |
| Configurable range | 0 to 100000 | Fixed at 280 |
| Media counted | No | No |
| URL shortening | No | Yes, t.co links |
| Federation truncation | Yes, per-instance | Not applicable |
Mastodon offers significantly more flexibility than Twitter. Administrators can tailor the limit to their community’s needs. Users benefit from longer posts without the artificial constraints of a centralized platform.
Now you understand how the Mastodon character limit works and how to configure it on your instance. If you are an administrator, consider setting a limit that balances readability with server storage. For users, keeping toots under 500 characters ensures they display correctly across all instances. A practical tip is to use content warnings for toots that exceed 1000 characters to avoid overwhelming followers’ timelines.