- Why images disappear on X in the first place
- Worked example: the half-loaded timeline
- Step-by-step fixes, in the order to try them
- When it's a browser problem specifically
- The connection between image, GIF, and video failures
- When the problem is your website, not X
- The uncomfortable bit nobody says out loud
- A quick word on mobile data and image quality
- If none of this works
- Frequently asked questions
The short version: images not loading on X is almost always caused by a dodgy cache, a slow or blocking connection, an outdated app, or X's own image servers having a bad day, and you can usually narrow it down in under five minutes. Start with the simple stuff (refresh, restart, check another site) before you assume it's broken on X's end. Nine times out of ten the fix is boring, not clever.
Why images disappear on X in the first place
X compresses and reprocesses nearly every image you upload, resizing it, stripping some metadata, and serving it from a content delivery network rather than from the original file. That extra step is exactly where things break. A photo that looks fine on your phone can fail to render once it has been through that pipeline, especially if your connection drops mid-load or your browser has cached an older, broken version of the same tweet.
It is also worth saying plainly: X's infrastructure has had more hiccups since 2023 than it did before, and nobody at the company is going to tell you that in a support article. If images on X feel flakier than they used to, you are not imagining it. That does not mean every broken image is X's fault, but it does mean you should not assume the problem is always your phone or your wifi.
The five most common causes
- A corrupted or stale browser/app cache holding onto a broken version of the page
- Weak, throttled, or public wifi that times out before the image finishes downloading
- An outdated X app or browser that no longer plays nicely with X's current image delivery system
- Ad blockers or privacy extensions mistaking X's image CDN (pbs.twimg.com) for tracking content and quietly blocking it
- A genuine outage or rate limit on X's side, which happens more than people admit
Worked example: the half-loaded timeline
Say you run a small events business and you are scrolling X on your phone at lunchtime to check replies to a promo you posted that morning. Half the images in your timeline show the little broken-image icon, but tapping directly into your own tweet shows the photo fine. That mismatch is a strong clue: it is not your account, it is not the specific image, it is almost certainly your connection or your app's cache choking on the volume of images loading at once on a weak signal.
The fix in that exact scenario is usually this: close the X app fully (not just minimise it), switch from wifi to mobile data or vice versa, reopen the app, and pull down to refresh the timeline. If that works, you have confirmed it was a connection or cache issue, not a broken image file. If it still fails after switching networks, move on to checking whether X itself is having problems, because at that point the issue is out of your hands.
Step-by-step fixes, in the order to try them
- Refresh and retry. Close the tab or app completely and reopen it. This alone fixes a surprising number of cases because it forces a fresh request instead of reusing a stuck one.
- Check if it's just you. Open X on a different device, or ask someone nearby to check. If images load fine for them, the problem is local to your device or network.
- Clear the app or browser cache. On the X app: Settings and privacy, then General, then Media (or clear app storage/cache via your phone's settings). On Chrome: Settings, Privacy and security, Clear browsing data, tick Cached images and files only, and clear just the last 24 hours first before wiping everything.
- Switch networks. Toggle wifi off and use mobile data, or the reverse. Many corporate and cafe wifi networks block or throttle image CDNs without telling you.
- Disable ad blockers and privacy extensions temporarily. Ublock Origin, Privacy Badger, and some VPN browser extensions have all been known to block pbs.twimg.com specifically because it looks like a tracking domain. Whitelist twimg.com and twitter.com if you use any of these.
- Update the app. If you are more than two versions behind on the X app, update it. X changes its image delivery endpoints more often than most apps, and an old client simply cannot keep up.
- Check X's status. If none of the above works and images are failing for lots of people at once, it is an outage, not your device. You will usually see other users complaining within minutes on sites that track service status.
When it's a browser problem specifically
If you only see broken images on desktop and the app works fine on mobile, the browser is almost certainly the culprit. Try these in order: disable browser extensions one by one rather than all at once (so you find the one causing it), try an incognito or private window (which runs without most extensions and without your existing cache), and if it works there, you know it is an extension or cache issue rather than anything wrong with X or your connection. Also check that your browser is updated; Safari and Firefox in particular have occasionally mishandled X's lazy-loading image scripts in older versions.
The connection between image, GIF, and video failures
If images, GIFs, and videos are all failing on X at the same time, that is a bigger clue than most people realise. It usually points to a network-level block rather than a problem with any single piece of media, because all three are served from related CDN infrastructure. The troubleshooting steps overlap a lot too. If you have already fought with GIFs not playing on Twitter or videos refusing to load, you have probably already fixed half of what causes broken images too, since the cache-clearing and network-switching steps are nearly identical.
Worth noting too: if your videos load but then keep pausing partway through, that is usually a bandwidth issue rather than a blocking issue, which is a slightly different fix (lower video quality settings, closer proximity to your router) than the all-or-nothing failure you get with broken images.
When the problem is your website, not X
One thing that trips people up: if you are embedding X posts on your own website and the images inside those embeds are not loading, the fault often sits with your site, not with X. Slow server response times, a plugin conflict, or an outdated embed script can all stop an otherwise working X post from rendering its image on your page. This is the same family of issue covered in common website glitches and how to fix them, and it is worth ruling out before you blame X at all. Test the same embed on a different page or a fresh browser tab on your site to isolate it.
The uncomfortable bit nobody says out loud
Here is the part most troubleshooting guides skip: sometimes images on X do not load because X has rate-limited your account or your IP address, either for posting too fast, following too aggressively, or triggering an automated spam flag, even if you have done nothing wrong by your own standards. Media loading is one of the first things that gets throttled quietly, before you get any formal notice or warning. If you have been posting a lot, running automation, or scheduling content through a third-party tool, and images specifically (not text, not replies) stop loading for your account while working fine for others, that is worth considering. There is no settings page that tells you this is happening. You just notice the pattern.
Want AI doing the heavy lifting in your marketing?
I build the systems that handle the boring 80 percent, so you get your week back. Done properly, with the human kept in.
If you suspect this, the only real test is time: stop any automated activity for a day and see if normal image loading returns. If it does, you have your answer, and no amount of clearing cache was ever going to fix it.
A quick word on mobile data and image quality
X automatically serves lower-resolution images when it detects a slow connection, which is sensible but occasionally overcorrects and serves a broken placeholder instead of a compressed version. You can force higher quality uploads and reduce this risk in Settings and privacy, then Accessibility, display and languages, then Data usage, where you can switch "High quality image uploads" on. This does not fix a loading failure that has already happened, but it reduces how often the compression step itself causes the glitch in the first place.
If none of this works
If you have worked through every step above, confirmed it is not an outage, and images still refuse to load on one specific account or device, the remaining options are: log out and back in completely (not just refresh), uninstall and reinstall the app rather than just updating it, and check whether your mobile carrier or workplace firewall blocks twimg.com entirely, which some do for bandwidth reasons. At that point you have exhausted the consumer-level fixes and the issue sits with either your network administrator or X's support team directly.
For business accounts managing this across a team, inconsistent media loading is also a good prompt to review your wider content workflow. If you are juggling link-in-bio tools, scheduling platforms, and multiple team members posting to the same X account, it is worth checking whether one of those tools is the actual source of repeated image failures rather than X itself, the same way it is worth comparing the best link in bio tools for Instagram and TikTok before committing to one for your whole team.
Frequently asked questions
Why do images on X only fail to load for some people and not others?
Because X's image delivery goes through a CDN that serves content based on your device, cache, network, and sometimes your geographic region, so a failure on one connection often does not affect someone on a different network or device even when viewing the exact same tweet.
Does clearing my cache delete my saved tweets or bookmarks on X?
No, clearing your browser or app cache only removes temporarily stored files like images and page data, not your account data, bookmarks, or saved tweets, which are stored on X's servers rather than your device.
Is it normal for X to have image loading outages?
Yes, partial outages affecting images, GIFs, or video specifically (rather than the whole platform) have become more frequent on X since 2023, and they usually resolve within a few hours without any announcement from X itself.
Can an ad blocker really stop images loading on X?
Yes, several popular ad blockers and privacy extensions block the domain pbs.twimg.com by default because it resembles a tracking subdomain, so whitelisting twimg.com is one of the quickest fixes to try if other steps have not worked.
