When scrolling through your Mastodon timeline, you might see the message Could not load more posts. This error stops you from viewing older toots and can interrupt your browsing. The problem often comes from a temporary network issue, a server-side rate limit, or a corrupted local cache. This article explains the root causes and provides clear steps to restore your timeline loading.
Key Takeaways: Fixing the Mastodon Timeline Loading Error
- Clear browser cache and cookies: Removes corrupted site data that blocks timeline requests.
- Disable browser extensions: Stops ad blockers or privacy tools from interfering with Mastodon API calls.
- Switch to a different network: Verifies whether your current internet connection is rate-limited or unstable.
Why Mastodon Shows Could Not Load More Posts
Mastodon loads posts in batches using a technique called pagination. When you reach the bottom of your timeline, the web app sends an API request to the server asking for the next batch. If that request fails, the error appears. The failure can happen for three main reasons.
First, the Mastodon server you are connected to may have rate limits. To prevent overload, administrators set a maximum number of API requests per minute per IP address. If you scroll very fast or refresh many times, you may exceed that limit temporarily. The server then refuses new requests for a short period, and the timeline stops loading.
Second, your browser or device may hold a corrupted cache. Mastodon stores timeline data locally to speed up loading. Over time, this cache can become outdated or damaged. When the app tries to merge cached data with a fresh API response, it may fail and show the error.
Third, browser extensions that block scripts or modify headers can break Mastodon API calls. Extensions like ad blockers, privacy filters, or VPN add-ons often interfere with the JSON data that Mastodon sends and receives. When the API response is blocked or altered, the timeline cannot load more posts.
Steps to Restore Timeline Loading
Follow these steps in order. Test the timeline after each step to see if the error is resolved.
Step 1: Refresh the Page and Wait
- Press F5 or Ctrl+R
This reloads the Mastodon web app and resets any temporary state. If the error was caused by a one-time network glitch, the timeline should load normally after refresh. - Wait 60 seconds before scrolling again
If you hit a rate limit, the server needs time to reset your request count. After one minute, scroll down slowly. Do not spam the scroll wheel or press the End key repeatedly.
Step 2: Clear Browser Cache and Cookies for Mastodon
- Open browser settings
In Chrome, click the three-dot menu > Settings > Privacy and security > Clear browsing data. In Firefox, click the hamburger menu > Settings > Privacy & Security > Cookies and Site Data > Clear Data. - Select Cached images and files and Cookies
Set the time range to All time. Make sure only these two options are checked. Click Clear data. This removes all stored Mastodon data without affecting your login session on other sites. - Reload Mastodon and sign in again
After clearing, the site may ask you to log in again. Enter your credentials and check the timeline. Scroll down to see if older posts load.
Step 3: Disable Browser Extensions Temporarily
- Open extension manager
In Chrome, type chrome://extensions in the address bar. In Firefox, type about:addons. In Edge, type edge://extensions. - Turn off all extensions
Use the toggle switch next to each extension to disable it. Do not uninstall anything. Reload Mastodon and test the timeline. - Re-enable extensions one by one
If the timeline works with all extensions off, turn them back on one at a time. After each enable, reload Mastodon and scroll. When the error returns, you have found the conflicting extension. Keep that extension disabled while using Mastodon or check its settings for a whitelist option.
Step 4: Switch to a Different Network
- Disconnect from your current Wi-Fi
Use your mobile phone as a hotspot, or connect to a different Wi-Fi network. If you are on a corporate or school network, it may have a firewall that blocks Mastodon API endpoints. - Test Mastodon on the new network
Open the same Mastodon instance and scroll down. If the error disappears, your original network is rate-limiting or blocking Mastodon. Contact your network administrator or use a VPN service.
Step 5: Use the Mastodon Mobile App or a Different Browser
- Install the official Mastodon app
Available for iOS and Android. Sign in to your instance and scroll the timeline. The app uses a different network stack and cache system, which often bypasses browser-specific issues. - Try a different desktop browser
If you use Chrome, switch to Firefox or Edge. Open Mastodon and test the timeline. If the error does not appear, your original browser may have a persistent cache or extension problem that clearing did not fix.
If Mastodon Still Shows the Error After These Fixes
Error appears only on one Mastodon instance
Try accessing a different Mastodon instance. If the timeline loads fine on another instance, the problem is on your home server. The server administrator may have set very low rate limits or the server may be under heavy load. Contact the admin through the instance contact page or use the Report feature to describe the error.
Error appears on all instances and all browsers
Your internet service provider or country-level firewall may be blocking Mastodon API traffic. Try using a VPN service that routes your connection through a different region. If the timeline loads with the VPN active, you need to keep the VPN enabled while using Mastodon.
Timeline loads but shows duplicate or missing posts
This is a different symptom from the loading error. It usually means your browser cache is corrupted. Clear cache and cookies again, then restart your browser completely before opening Mastodon.
| Item | Clearing Cache | Disabling Extensions |
|---|---|---|
| Time required | 2 minutes | 5 minutes |
| Affects login session | Yes, you must sign in again | No |
| Permanent change | No | No, extensions can be re-enabled |
| Best for | Corrupted local data | Extension interference |
Now you can resolve the Could not load more posts error on Mastodon by clearing cache, disabling extensions, or switching networks. Start with the quickest fix: refresh the page and wait one minute. If the error persists, move to clearing browser data. For persistent cases, use the Mastodon mobile app or a VPN. As an advanced tip, you can inspect the browser developer console (F12) under the Network tab to see the exact HTTP status code of the failed API request, which helps identify whether the issue is a rate limit (429) or a server error (500).