- Why the words load but the pictures don't
- Example: half the timeline shows broken images
- Step-by-step fixes, in the order to try them
- When it's a browser problem specifically
- When images, GIFs and videos all fail together
- When the problem is your website, not X
- Is X throttling your account's images?
- Data saver and upload quality settings
- Last resorts: log out, reinstall, check the firewall
- Frequently asked questions
Images don't load on X when your app or browser is holding a broken cached copy, your connection is too weak or filtered to finish the download, a browser extension is blocking the separate domain X loads pictures from, your app is out of date, or X itself is having a partial outage. Three quick tests tell you which: close and reopen the app, switch between wifi and mobile data, and open X in a private browser window.
Whichever of those three changes the result points to the cause, and you can usually narrow it down in under five minutes. Run them before you go hunting for outage reports: the fix usually sits on your side, and it's usually dull.
Why the words load but the pictures don't
The text of a post and the pictures in it arrive separately. The words come with the page, but each image is a second download from a separate image domain. X's own developer data dictionary shows it: profile pictures and banners sit at pbs.twimg.com addresses, not on x.com. That extra trip is where things break. A post can show its text perfectly and still give you a grey box or a broken-image icon if that second download is slow, blocked or served from a stale copy your browser cached earlier.
X doesn't publish an outage history for image delivery, so there's no figure to quote on how often the fault is theirs. That's exactly why the tests below check both ends: your device and network first, X second.
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 blocking twimg.com, the image domain X's developer docs show for profile pictures, which depends on the filter lists they run
- A partial outage or a limit on X's side, which you can't fix from your end
Example: half the timeline shows broken images
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.
When the picture is less clear-cut, match what you're seeing to this table:
| Images fail only... | What it points to | Fix to try |
|---|---|---|
| On one wifi network (office, cafe, hotel) | That network filters or throttles image traffic | Switch to mobile data; if images load, the network is the cause |
| In the app, but fine in a browser | App cache or an old app version | Clear the cache (steps below) and update the app |
| In one browser, but fine in a private window | An extension or that browser's cache | Turn extensions off one at a time, then clear cached images |
| For you, on every device and network, while others see them | Something tied to your account | Pause any automation for a day, log out and back in |
| For everyone at once | X's side | Wait; nothing on your device will fix it |
Three patterns the table doesn't cover:
- Images missing only from your own posts. Ask someone else to open the post, or check it on a second device. If they see the picture, the fault is your cache. If nobody does, the upload didn't finish: delete the post and share it again rather than waiting for it to appear.
- The main post loads but images in the replies don't. Replies load as you scroll, each picture a fresh download, so a connection that's just about coping fails here first. Refresh the thread on a stronger connection before changing any settings.
- Fine in the app, broken on the web (or the other way round). The one that works proves your account and X's servers are fine. Fix only the failing one: browser cache and extensions on the web, cache and update in the app. Logging out and back in on that one is worth a try last.
Step-by-step fixes, in the order to try them
- Refresh and retry. Close the tab or app completely and reopen it. That 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. The route depends on where you use X:
- Android app: open your phone's Settings, then Apps, then X, then Storage, and tap Clear cache. Every Android app has that same Storage screen, though the menu names shift a little between phone makers, and on some phones Apps is called Applications or App management. Leave Clear storage alone unless you're happy to log in again, because that wipes the app's data too.
- iPhone app: iOS has no cache button for individual apps. Apple's guide to iPhone storage gives the route instead: Settings, General, iPhone Storage, tap X, then Offload App. Apple says offloading frees the storage the app uses but keeps its documents and data, then download X again from the same screen or the App Store.
- Chrome on a computer: in Chrome's privacy settings, delete browsing data with only cached images and files ticked, and try the last 24 hours first before wiping everything.
- Safari on a Mac: Apple's Safari guide gives the route: Safari, Settings, Privacy, Manage Website Data. Search for x.com and then twimg.com, select each and click Remove. Apple warns this may sign you out of those sites.
- Switch networks. Toggle wifi off and use mobile data, or the reverse. Some office and cafe networks filter or throttle image traffic without telling you.
- Disable ad blockers and privacy extensions temporarily. Whether one blocks X's images depends on the filter lists it uses, so test rather than assume: pause the extension on x.com, reload, and if images come back, add x.com and twimg.com to its allow list rather than leaving the whole blocker off.
- Update the app. If the App Store or Google Play shows an update waiting for X, install it. Old versions keep bugs that have already been fixed for everyone else.
- 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 up to date.
If you want proof rather than guesswork, the browser will show you the failed request. Google's DevTools guide gives the steps: in Chrome press Control+Shift+J (Command+Option+J on a Mac), click the Network tab, type twimg in the filter box and reload the page. Failed requests usually show in red. If an image request fails while the same page loads fine in a private window with extensions switched off, an extension is the likeliest culprit. The Status column shows the response code, so rows that come back 200 while the picture still doesn't appear point at a cache or display problem, and rows that never finish point at the network.
When images, GIFs and videos all fail together
If images, GIFs, and videos are all failing on X at the same time, look at your network before anything else. That pattern usually points to a network-level block rather than a problem with any single piece of media, because all three come from related twimg.com addresses. The fixes overlap too, so if you've already worked through GIFs not playing on Twitter or videos refusing to load, the cache and network steps there apply here as well.
Videos that load and then keep pausing partway through are a bandwidth problem rather than a block, so the fix there is lower video quality or moving closer to your router, not the all-or-nothing checks above.
When the problem is your website, not X
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. The usual suspects are covered in common website glitches and how to fix them. Test the same embed on a different page or a fresh browser tab on your site to isolate it.
Is X throttling your account's images?
There's a theory that X quietly throttles images for accounts that post or follow very fast or run automation. X doesn't publish anything showing media is limited that way, so I wouldn't spend long on it. If you schedule posts through a third-party tool and every test above passes, pausing it for a day is a free check. If images come back during the pause, the tool is your suspect, not your phone, so check its upload settings before you switch it back on. No scheduling tool? Skip this one.
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.
Data saver and upload quality settings
The X app has a data saver option that loads lighter images on mobile data, and a separate choice for higher quality uploads. Both live in the app's settings, in the area that covers display and data. X's help articles on data usage and autoplay both return a 404 today, with no archived copy, and the wording shifts between app versions, so look for the setting by what it does rather than an exact menu path. If images fail only on mobile data, switch data saver off and test again. If your own uploads look soft, look for the upload quality option on the same screen.
While you're in settings, it's also a good moment for clearing your X viewing history.
Last resorts: log out, reinstall, check the firewall
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 networks do to save bandwidth. 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.
If several people post to one X account through scheduling or link-in-bio tools, check whether one of those tools is behind repeated image failures before blaming X, and compare options such as the best link in bio tools for Instagram and TikTok before you commit the whole team to one.
This guide is part of my Twitter (X) Help: 21 Guides to Features, Verification, Video Fixes and Tools.
I cover why Twitter says you're rate limited in a separate guide. If everything on X is broken rather than just images, start with my post on checking whether Twitter is down.
Frequently asked questions
Is X down or is it just me?
Test it in two minutes: load X on a different network (mobile data instead of wifi) and on a second device. If images work there, it's your device or network. If they fail everywhere and other users are reporting the same thing on outage-tracking sites, it's X, and waiting is the only fix.
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?
Partial outages that hit images, GIFs or video while text still loads do happen, but X doesn't publish an outage history, so nobody can tell you how often. If images fail for you on every device and network, check whether other people are reporting it before you change any settings.
Why do GIFs and videos load but images don't?
Because they're separate downloads from separate addresses, one can fail while the others work. That pattern points away from your connection as a whole and towards something specific to images: a cached broken copy, a filter rule in an extension, or a data saver setting. Clear cached images first, then test in a private window.
Run a business, a brand or a blog? I feature tools, products and expert guest posts for an audience of 15,000. See how it works