# How to Clear Twitter Cache > Step-by-step instructions to clear your Twitter app cache and browser cache to resolve performance issues. - Source: https://tweetsweep.com/blog/how-to-clear-twitter-cache - Published: 2025-01-20 - Updated: 2026-08-16 - Reading time: 5 min --- ## Stale cache symptoms Clear Media storage in the X app when images will not load, the Home timeline stays on posts you already saw, video stalls, or the app feels heavier than it did. X stores images, video, and page data locally so the second visit is faster. Over months that cache grows to a gigabyte or more. When a file in that store goes stale the app keeps serving it. You tap a photo and get a blank square. You pull to refresh and the same posts stay at the top. You start a video and it freezes at one second. The heavier feel is the app walking a large local index at launch. The timeline still lives on X's servers. The phone is showing a local copy that no longer matches. Clearing that copy forces a fresh download the next time you open a post or a profile. ## iPhone app path Open the X app on iPhone. Tap your profile picture in the upper left. Tap Settings and privacy. Tap Accessibility, display and languages. Tap Data usage. The Data usage screen holds two rows: Media storage and Web storage. Each row shows how much space that store is using. Media storage is almost always the larger number. That row is the images and video the app saved so it would not download them again. Web storage is smaller and holds cached pages and cookies from links you opened inside the app. Stay on Data usage. On iOS there is no useful system-level clear for this app that matches these two stores. The in-app path is the one that reaches Media storage and Web storage directly. ## Media storage and web storage Clear media storage first. It is the larger of the two and the safer one to clear. Tap Media storage and confirm. The app deletes the saved images and video and keeps you signed in. The next scroll will re-download those files, so the timeline can feel slower for a few minutes. That is expected. Web storage is the second row. It includes cached web pages and cookies. Clearing all of it may sign you out of pages you opened inside the app, such as a linked article. If you only have a display glitch, leave Web storage alone. If the in-app browser itself is broken, clear Web storage and be ready to log in again on those pages. You stay logged into X after either action. ## Android cache steps On Android the same in-app path exists. Open X, tap your profile picture, tap Settings and privacy, tap Accessibility, display and languages, tap Data usage, then clear Media storage first. Force-close X from the recents screen and open it again so it rebuilds the local index. Android also lets you clear from outside the app. Open the phone Settings app. Tap Apps, or Apps and notifications. Tap X. Tap Storage. Tap Clear cache. Wait until the cache size drops. Do not tap Clear storage. Do not tap Clear data. Those buttons reset the app entirely, wipe the login token, and sign you out. Clear cache is the only button on that screen that matches this job. After it finishes, open X and let the timeline reload. If you tapped Clear data by mistake you will see the login screen. Your posts are still on the servers. Only the local session is gone. ## Browser site data In a browser, clear cached images and files for x.com through history or site settings. In Chrome, click the icon beside the address bar while you are on x.com, then Site settings, then Delete data. That removes cookies, cached files, and stored data for that site only. Other sites stay untouched. After the delete, close the tab and open x.com again. You may need to log in. A full history wipe of the last hour also works but it hits every site you visited, which is more than this job needs. Use the per-site delete when you can. The goal is the local copy of x.com, not the rest of the browser. If you use another browser, open site settings or the stored data list, find x.com, and delete the cached images and files for that host only. ## Hard reload shortcut A hard reload often fixes a broken page without clearing anything. On Windows press Ctrl and Shift and R. On a Mac press Command and Shift and R. The browser skips its local copy of the page and fetches a new one from X. Use this when a single tweet page is blank, a settings screen will not save, or a media viewer is stuck on a spinner. It does not touch cookies, so you stay signed in. It does not free a gigabyte of space. It only refreshes the current document. If the hard reload works, stop there. If the same glitch returns on the next visit, delete site data. On a phone browser, close the tab and open x.com again after you have already cleared the app cache. ## Account data on the servers Cache clearing frees space and resolves display glitches. It does not delete anything from your account. Your posts, likes, and direct messages live on X's servers, and none of them are touched. The local store never held the canonical copy. It held a convenience copy so the app could paint the screen faster. After a clear, the app asks the servers again and rebuilds the store. Followers, lists, bookmarks, and notification history remain. If a post is missing after a clear, pull to refresh. If it is still missing, that post was already gone on the server. Clearing cache cannot hide a tweet and cannot bring one back. The only files that disappear are the ones that sat in Media storage and Web storage on that device. ## Posts you actually want gone If what you actually want is to remove the posts themselves, that is a different job. TweetSweep deletes them for real, by date range, and keeps a record of what it removed. Use cache clear when the problem is a blank image or a stuck timeline. Use TweetSweep when the problem is the tweets still sitting on your profile. Those two actions do not replace each other. Clearing cache will not take an old thread off your profile. Deleting through TweetSweep will not shrink the gigabyte of media sitting on the phone. Do the cache steps first if the app is misbehaving. Then, if the goal is a clean profile, run the delete by date. The record TweetSweep keeps is so you can see which posts left the account. The cache has no such record because the files it drops were never the posts.