Twitter X not loading is usually one of four things, and reinstalling the app fixes almost none of them. The most common cause is a read limit. X caps how many posts an account can pull in a given window, and it caps signed-out browsing hardest of all, so when you hit the ceiling the timeline simply stops with no error message explaining why. The second cause is a setting on your own account quietly hiding media from you. The third is your browser or your app: an ad blocker, a privacy extension, a cached service worker that has gone stale, or a build that is months out of date. The fourth is the account itself, which may be brand new, restricted, or not the one you thought you were signed into. Before any of that, spend thirty seconds working out whether the problem is even yours.
Table of Contents
Find out first whether X is down for everybody
This takes half a minute and it saves you an hour of pointless fixing. Open X in a completely different context. A second device on mobile data works, so does a different browser, so does somebody else’s phone. If it fails in all of them, stop. Nothing on your device will help, and wiping your data at that moment only signs you out and makes the next hour considerably worse.
Outage trackers are a reasonable second opinion. Honestly, a search on any other platform for people complaining about the same thing in the same minute is faster than most status pages. What you are looking for is a spike inside the last hour rather than the general background hum of complaints, because there is always a background hum of complaints.
Read limits look exactly like a broken app
X limits how much any account can read in a period. Cross that limit and the app does not tell you so. You get an empty column, or a spinner that never resolves, or a timeline that refuses to load anything past a certain point, or posts that appear once and then nothing more. Every one of those looks like a fault, so almost everybody misdiagnoses it. They force quit, reinstall, clear everything, and arrive back at the identical wall.
Signed-out browsing gets the tightest cap by a wide margin. If you are reading X through a link somebody sent you, with no account, you will hit a wall after a modest amount of scrolling and it will look as though the site has died. Sign in and it works. That one test separates a read limit from everything else in this article, and it costs you nothing.
You were expecting me to say clear your cache, right? Hold on. Clearing site data in a browser signs you out, which drops you straight into the strictest read limit there is, and then the site really does stop working while you congratulate yourself for taking action. Do the signed-in check first. Clear things only once the limit is ruled out.
There is no way to force the counter to reset early. It refreshes on its own after a while. Put the phone down, go and do something else, come back later. Brand new accounts get a tighter allowance than established ones, which is why a fresh account can feel broken from its first hour of life.
When the text loads but the pictures and videos do not
This is a separate problem with a separate set of causes, and it gets lumped in with the timeline freezing constantly.
- Data saver. X has a data saving mode that drops image quality and stops video preloading. On a slow connection that shows up as pictures that never resolve past a grey box. It lives in the data usage section of settings.
- Autoplay. Video autoplay can be set to Wi-Fi only or switched off completely. On mobile data with Wi-Fi only selected, nothing plays until you tap it, which reads as broken video.
- Sensitive media settings. If your account is not set to display media that may contain sensitive content, posts get hidden or covered with very little explanation. An entire thread can look empty because of it. Check the privacy and safety settings, in the section covering the content you see.
- The media host itself. Text and media come from different places. Text arriving while images fail is a distinctive signature, and it usually means the media side is having a bad afternoon rather than anything on your device.
Worth knowing as well: image and video quality settings are separate from data saver on some builds, so switching data saver off does not always restore full quality by itself.
Your browser is probably serving you a stale copy
The web version of X installs a service worker, which is a small piece of code that caches the site so it loads fast. When one goes stale it will cheerfully serve you a broken half-loaded shell forever, and an ordinary refresh will not shift it, because avoiding the network is the entire purpose of the thing.
A hard reload is the first move. Hold shift while clicking reload, or use whichever keyboard shortcut your browser assigns to a cache-bypassing refresh. If that fails, try the site in a private window. Loading correctly in private while failing in your normal window points at the cache or an extension, and you have narrowed it to two suspects without deleting a thing.
Ad blockers and privacy extensions break X regularly. The site pulls a lot of scripts from a lot of subdomains, and blocker rule lists update constantly, so a filter that was harmless last week can take the timeline out this week. Disable them for the site rather than globally. On the app side, an out of date version is a genuine cause and not a support-desk brush-off, because X changes its interfaces often and old builds get left behind.
The account itself can be the problem
Several account-level situations produce a timeline that will not load, and none of them look like what they actually are.
- New accounts, and accounts that have never confirmed a phone number or email address, carry tighter limits on how much they can read and do. Everything feels sluggish and capped because it genuinely is.
- You may be signed into the wrong account. If you run more than one, the app remembers whichever you used last, and a limited secondary account shows you a stripped-back experience that you read as an outage.
- The account may be temporarily restricted after an automated flag. Restrictions usually surface as a banner, though not always, and not on every screen.
- You may be logged out in a browser you were certain you were logged into. Sessions expire quietly. The interface looks broadly similar until you go looking for your own profile.
Work through it in this order
- Check X on a second device or a different connection. If it is down everywhere, stop here and wait.
- If you are signed out, sign in. This alone resolves a large share of frozen timelines.
- Hard reload the page, or force close and reopen the app.
- Switch off ad blockers and extensions for the site, then reload.
- Check data saver, autoplay and sensitive media settings, if the problem is media rather than the whole timeline.
- Update the app. Confirm you are on the account you meant to be on.
- Leave it alone for an hour. If a read limit caused this, that is the only fix that exists.
- Clear site data or reinstall. Last, because it signs you out and costs you the most.
The part where you need to be careful
Whenever X breaks, a swarm of pages appears offering to fix it. Some want you to sign in through their page to restore your timeline. Others offer a tool that supposedly lifts read limits. Every single one of those is after your login, and handing it over is how an account gets taken and turned on the people who follow you.
X will never ask you to sign in anywhere except x.com or its official app. If a page wants your password in order to solve a loading problem, close the tab. If you have already typed your details into something like that, change your password immediately from the real site, then check your active sessions and connected apps and revoke anything you do not recognise.
One more. If you decide you are locked out and start a password reset while the platform is actually just down, you can strand yourself in a half-finished reset with no way back in and no support queue moving. Confirm the outage before you touch anything involving credentials. That advice is dull and it will save you a bad evening.
Where this leaves you
Most of the time you have broken nothing. You read too much, or a setting is hiding half the content from you, or a cached copy of the site is lying to your face. Reinstalling sits at the bottom of that list for a reason: it is the most disruptive thing available to you and it addresses the least likely cause. Try the boring checks first, in order, and keep your credentials to yourself while you do it.
