Mastodon Error 422 ‘Validation Failed’: Common Causes

When you see Mastodon Error 422 with the message “Validation Failed,” the server has rejected your request because the data you sent does not meet its rules. This error often appears when posting, following accounts, or uploading media. The problem usually stems from malformed API requests, expired session tokens, or content that violates instance-specific limits. This article explains the technical reasons behind Error 422 and provides clear steps to resolve each cause.

Why Mastodon Returns a 422 Validation Failed Error

Mastodon uses HTTP status code 422 to indicate that the server understands your request but cannot process it because the data is invalid. This is not a server outage or a network problem. The server specifically rejects the payload you sent.

The most common triggers include:

Invalid API Request Format

Third-party apps like Tusky, Fedilab, or web clients send requests with missing or incorrectly formatted fields. For example, a follow request might lack the required account_id parameter. The server validates every required field and returns 422 if any field is missing or has the wrong data type.

Expired or Corrupted Session Tokens

Every authenticated request includes a session token stored in your browser or app. If this token becomes stale, corrupted, or revoked, the server cannot verify your identity. It then rejects the action with a 422 error instead of the expected 401 Unauthorized.

Content That Violates Instance Rules

Each Mastodon instance sets its own limits on post length, media size, and file types. If you try to post text exceeding 500 characters on a standard instance, or upload a video larger than 40 MB, the server validation fails. The error message may not always specify the limit.

Steps to Resolve Each Cause of Error 422

1. Refresh the page or restart the app
   Temporary glitches in the web interface or mobile app can cause malformed requests. Close the browser tab or app completely, then reopen it. Try the same action again. If the error disappears, the cause was a one-time session hiccup.
2. Log out and log back into your account
   Go to Preferences > Account > Log out. After logging out, close the browser or app. Log back in with your credentials. This replaces the session token with a fresh one. Test the action that previously failed.
3. Check your post length and media attachments
   Count the characters in your post, including the content warning text and media descriptions. Standard Mastodon instances allow up to 500 characters. If you use a custom instance, check the instance rules page. Reduce the post length or split it into multiple posts. For media, verify that images are under 10 MB and videos under 40 MB. Use JPEG, PNG, GIF, or WebP for images and MP4 or WebM for video.
4. Revoke and reauthorize third-party apps
   If you use a third-party client like Tusky or Fedilab, go to Preferences > Account > Authorized apps. Find the app that triggered the error and click Revoke. Then log in again through that app. This ensures the app uses a valid API token with the correct permissions.
5. Clear browser cache and cookies
   In your browser settings, clear cached data and cookies for the Mastodon domain. On Chrome, go to Settings > Privacy and security > Clear browsing data. Select Cookies and other site data and Cached images and files. Click Clear data. Reload Mastodon and try again.
6. Try a different browser or device
   If the error persists on one browser, switch to a different one like Firefox, Edge, or Safari. If you use a mobile app, try the web interface instead. This helps isolate whether the problem is specific to your current client.

What to Do If Mastodon Error 422 Still Appears

Error 422 When Following a User

If you get a 422 error when trying to follow someone, the target account may have been suspended or deleted. Check the user’s profile page directly. If it shows a “This account has been suspended” message, you cannot follow them. If the account exists, try following from a different client or the web interface.

Error 422 When Posting With Hashtags

Some instances restrict the number of hashtags per post. If your post includes more than ten hashtags, reduce the count to five or fewer. Also ensure hashtags do not contain spaces or special characters other than underscores.

Error 422 When Uploading a Profile Picture

Profile pictures must be under 2 MB and in a supported format. Resize your image to 400×400 pixels or smaller using an image editor. Save as JPEG or PNG and try uploading again.

Mastodon Error 422 vs Other HTTP Errors

Item	Error 422 Validation Failed	Error 401 Unauthorized
Description	Request data is invalid or incomplete	Missing or invalid authentication credentials
Common cause	Post too long, missing fields, bad file format	Expired token, logged out, wrong password
Solution	Check input limits, refresh token, revoke apps	Log in again, reset password

Understanding the difference helps you apply the correct fix faster. A 422 error means the server saw your credentials but rejected the data. A 401 error means the server did not recognize your credentials at all.

Now you can identify the cause of Mastodon Error 422 and apply the right solution. Start by refreshing your session and checking post limits. If the error persists, revoke and reauthorize third-party apps. For advanced troubleshooting, inspect the browser developer console for specific validation messages under the Network tab.