PS5 Cache Clear 2026: Option 6 in 12 Steps, 10 Min

There is a genre of console advice that survives entirely on faith. Blow on the cartridge. Leave it unplugged overnight. Delete a save and it will run smoother. Most of it is superstition wearing a lab coat, folk medicine handed down from the Nintendo 64 era, and most of it does nothing but make you feel like you participated in the fix. Clearing the PS5 cache is the rare exception. It is a real, Sony-sanctioned maintenance routine, buried in a menu the console does not advertise on the box, and it fixes a specific, common, and genuinely annoying class of problems: menu stutter, apps that refuse to launch, black screens on boot, downloads that stall at ninety-nine percent, controllers that lag in the interface. It costs exactly nothing.

The catch is that half the internet cannot count. You will read, on otherwise reputable sites, that the cache option is the fifth entry in Safe Mode. It is not. On current firmware it is the sixth, and the difference is not pedantry — it is consequences. The fifth entry restores your default settings. The seventh wipes your console to the bare metal. A miscount in a black-screen menu, with a USB cable in your hand and mild panic in your chest, is how people accidentally factory-reset a machine they only wanted to dust. So we are going to give you the correct number, the correct timing on the power button, the one cable everyone forgets, and the twelve steps in the correct order. We are also going to tell you the part nobody writes down: what the cache actually is, and why deleting it works.

Ten minutes. No PlayStation Plus. No PC. No fee. Let us dust the machine.

What the PS5 Cache Actually Is

Before you hold down any buttons, it helps to know what you are about to delete, because "cache" on a PlayStation is a word doing at least three different jobs, and people routinely clear the wrong thing and then wonder why their problem persists. The PS5 is a computer with a fast custom SSD and an operating system that writes an enormous amount of temporary data in the background. Some of that data goes stale. Clearing it is the reset. But you have to know which pile of data you are torching.

Three Different Things Wearing the Same Name

When people say "clear the cache," they could mean any of three separate things. First, the system software cache: temporary files the OS generates constantly — decompressed UI textures, store carousel assets, shader pipelines, thumbnail art, network handshake data. This is the true "cache," and it is what you clear in Safe Mode. Second, the content database: an index of everything installed on the console — games, apps, saves, trophies, sort order — which the system rebuilds by rescanning the drive. That is the "rebuild," a heavier operation that lives under the same menu entry. Third, game-specific data: an individual title's saved files or downloaded assets, deleted from an entirely different menu (Settings, then Storage). PSX Extreme's guide makes exactly this distinction its whole reason for existing, separating console-storage save-data deletion from system cache clearing, and it is the distinction most casual guides blur into mush.

Why the Cache Rots in the First Place

The cache is not malicious. It exists to make the console faster — decompress a texture once, keep it around, do not decompress it again. The trouble starts when a write gets interrupted. A game updates in Rest Mode and the download is cut off mid-flush. The power blips. An install crashes. Now you have a half-written or orphaned temporary file that the system still trusts, and that stale entry produces exactly the symptoms people describe on forums: the interface stutters when you scroll, a game throws "cannot start the application," the store shows blank tiles, a download refuses to finish, the console hangs on a black screen after wake. It is the console-era equivalent of a browser cache that has gone sour — the fix is the same, delete it and let the system regenerate clean copies. A Reddit thread from late 2025 has a Starfield player reporting that clearing the system cache stopped their crashes "all day", which is exactly the class of intermittent, write-corruption bug this operation is built to clear.

What Clearing Touches, and What It Leaves Alone

This is the single most important paragraph in the article, so read it twice. Clearing the system software cache deletes temporary files only. It does not delete your games. It does not delete your saves. It does not touch screenshots, trophies, accounts, or settings. Nothing you care about is inside the cache. The rebuild-database operation is also non-destructive to your data — it re-reads your library, it does not erase it. The only Safe Mode entries that destroy data are option 7 (Reset PS5) and option 8 (Reset PS5 and Reinstall System Software), and both announce themselves in unambiguous language before they proceed. If a guide tells you clearing the cache might cost you a save file, close the guide. It is wrong, and it does not understand the machine.

Prerequisites: Firmware, Cable, 10 Minutes

This is a low-barrier procedure — that is part of why it is worth knowing. You do not need special software, a subscription, or a spare console. You do need three things, and one of them is the thing everyone forgets, which is why they end up staring at a menu they cannot navigate.

Firmware and Hardware

Any PS5 works: the original disc console, the Digital Edition, the Slim, or the PS5 Pro. The Safe Mode path is identical across the entire line — a 2025 walkthrough explicitly covered the process for PS5 or PS5 Pro with the same steps, because Sony did not fork the recovery menu for the premium hardware. As a reference point, this guide was written against the July 2026 stability build; Sony ships firmware on a roughly monthly cadence, so by the time you read this you may be a point release ahead. The menu layout has been stable regardless. You can confirm your build in the interface before you start:

Settings > System > Console Information
-------------------------------------------------
Model:            CFI-xxxx  (PS5 / Digital / Slim / Pro)
System Software:  26.04-13.42.00     # reference: July 2026 build
Cadence:          monthly stability patches
Safe Mode:        8 options (layout unchanged since Sony
                  inserted "Repair Console Storage" at slot 3)

The One Cable Everyone Forgets

Here is where people fail. In Safe Mode, Bluetooth is off. Your DualSense will not pair wirelessly. It will sit there, dark and useless, while you mash the PS button at a menu that cannot hear it. You need a USB-C cable to physically connect the controller so it can register button presses. Asurion's tech tip spells this out as a required step — connect the controller by USB cable before you try to select anything — and Engadget's written guide gives the same instruction. Use the same cable you charge the controller with. If you own only the wireless charging dock and no data cable, this is the moment you discover that, so check now, not at step eight in the dark.

What You Do Not Need

You do not need PlayStation Plus. You do not need money. No credible 2025 or 2026 source attaches a dollar figure to this process, for the simple reason that it is a built-in system maintenance function, not a paid service — if someone is charging you to "clear your PS5 cache," they are charging you to hold a button. You do not need a PC, a second console, or a USB flash drive; the USB stick some guides mention is for the Update System Software path, not the cache clear. Budget ten minutes for the cache clear itself. Budget more — potentially up to an hour on a large, full drive — only if you also decide to rebuild the database, which is a separate button we will get to. Here is the whole pre-flight in one block:

PRE-FLIGHT  (cache clear)
[ ] All games and apps closed
[ ] USB-C cable in hand   (controller will NOT pair over Bluetooth)
[ ] Console fully OFF      (light dark, not pulsing orange Rest Mode)
[ ] You know the number:  option 6, by LABEL not by count
[ ] ~10 minutes           (add up to ~1 hour if you also Rebuild)

NOT required: PS Plus . a PC . a USB stick . a single cent

Option 6, Not 5: The Menu Fight

Now the part that trips up even the guides you would expect to be careful. The number of the cache-clear entry is genuinely contested across the internet, and if you go in trusting the wrong source you can select the wrong thing. So let us settle it with the primary document.

The Full Safe Mode Menu

Per PlayStation's own official Safe Mode support page, the current PS5 recovery menu has eight entries, in this exact order, and "Clear Cache and Rebuild Database" is the sixth:

PS5 Safe Mode   (source: playstation.com — 8 options)
1. Restart PS5
2. Change Video Output
3. Repair Console Storage              # does NOT erase data
4. Update System Software
5. Restore Default Settings            # keeps games/saves, resets settings
6. Clear Cache and Rebuild Database    [ THIS ONE ]
     - Clear System Software Cache     (light, seconds)
     - Rebuild Database                (heavy, minutes to ~1 hour)
7. Reset PS5                           # DELETES ALL USER DATA
8. Reset PS5 (Reinstall System Software)   # wipes data + firmware

Why Half the Guides Say Five

TechRadar's explainer calls the cache option the "fifth" entry in Safe Mode, describing the whole thing as a kind of "data dusting." A 2026 YouTube walkthrough titled "How to Clear Cache On PS5 & Increase Performance 2026" tells viewers to select "option five". Other 2026 videos, and the Reddit users actually doing it, say option six. Both camps are describing the same button; they are counting against different firmware. This is not just sloppiness — Sony has quietly reordered Safe Mode across system-software revisions, and the current menu inserts "Repair Console Storage" at slot 3. That single insertion shoves every option below it down by one, which is precisely how a guide that was correct at "five" became wrong without changing a word. The lesson is durable: do not count, read. The ordinal drifts between builds; the label "Clear Cache and Rebuild Database" does not.

Verify It on Your Own Console

You can confirm which layout you are on in about two seconds without touching anything dangerous. If your Safe Mode menu shows "Repair Console Storage" as item 3, you are on the current firmware and the cache option is item 6. If it does not, you are on an older build and it may be item 5 — but in either case, the words on screen are identical, so aim for the string, not the number. And if you find yourself hovering over an entry that says "Reset PS5," you have overshot; back off. That is option 7, it is the one that deletes everything, and no amount of cache trouble is worth hitting it by accident.

Clear the Cache in 12 Steps

Here is the whole procedure, start to finish, with the reasoning attached to each step so you understand why it exists and do not skip the one that saves you. The actual cache clear takes seconds; the twelve steps below are almost entirely about getting the console into Safe Mode cleanly and connecting a controller that can navigate it.

The Two-Beep Timeline

The entire entry sequence hinges on a single skill: holding the power button through the first beep and releasing on the second. Get the timing wrong and you simply boot the console normally and start over. Here is the timeline to internalize before you begin:

t = 0.0s    press and HOLD the physical power button
t ~ 1.0s    BEEP #1   -> this is a NORMAL boot signal. DO NOT RELEASE.
t ~ 1-7s    keep holding. the screen stays black. keep holding.
t ~ 7.0s    BEEP #2   -> Safe Mode is armed. RELEASE NOW.
after       screen: "Connect the controller using the USB cable
            and press the PS button."

The Twelve Steps

1. Save and quit everything. Close every running game and app from the home screen. Rationale: the cache clear cannot help a file that is still open and being written, and you want the system in a clean, idle state before it powers down.
2. Open the Control Center with the PS button. From the home screen, press the PS button on the controller to bring up the Control Center bar. Rationale: this is the only reliable route to a genuine full shutdown; the physical button on the console can drift into Rest Mode instead, which is not what Safe Mode needs.
3. Choose Power, then "Turn Off PS5." Not "Enter Rest Mode." Fully off. Rationale: Engadget's guide has you take exactly this path — hold PS, choose Power, then Turn Off PS5 — because Rest Mode keeps the machine partially alive and Safe Mode requires a cold start.
4. Wait for the indicator light to go fully dark. Watch the light stop blinking and extinguish completely before you touch anything. Rationale: pulling the trigger while the console is still shutting down interrupts the write cycle and can create the very corruption you are trying to clear.
5. Press and hold the physical power button on the console. Use the button on the unit itself, not the controller. Rationale: Safe Mode is entered from the hardware, and it is a sustained hold, not a tap.
6. Hold through the first beep and release only after the second. First beep at about one second is normal boot; keep holding roughly seven seconds until the second beep, then let go. Rationale: multiple 2026 walkthroughs and the PSX Extreme guide all converge on the same detail — hold until the second beep after about seven seconds, then release to enter Safe Mode. Release between beeps and you boot normally.
7. Connect the DualSense with a USB-C cable and press PS. Plug the controller into the console and press the PS button to register it. Rationale: Bluetooth is disabled in Safe Mode, so a wireless controller does nothing; the cable is mandatory, per Asurion and Engadget both.
8. Select option 6, "Clear Cache and Rebuild Database," by its label. Read the words, do not count blindly. Rationale: it is item 6 on current firmware, but reading the label protects you if your build differs and, more importantly, keeps you far away from option 7.
9. Choose "Clear System Software Cache." The submenu offers two things; pick the cache one, not Rebuild Database. Rationale: this is the light, near-instant, cache-only operation — the fast fix. Rebuild is the heavier tool for a different problem.
10. Confirm with OK. There is no terrifying warning to fear here. Rationale: the operation is non-destructive to your games and saves, so the confirmation is a formality, not a point of no return.
11. Let it finish and let the console restart. The progress bar clears in seconds and the system reboots itself. Rationale: the cache clear is genuinely fast; if it appears to hang for minutes, that is a symptom in its own right — see the troubleshooting table.
12. Boot normally and launch your problem app first. Open whatever was misbehaving before you touched anything else. Rationale: the first launch will be slightly slower while the shader and UI caches repopulate from scratch. That slowness is expected and temporary, not a sign the fix failed.

Where This Fits in a Bigger Toolkit

Clearing the cache is the console-maintenance equivalent of restarting a router: cheap, fast, and correct more often than it has any right to be. It sits alongside the other small rituals that keep a PlayStation healthy — the same way learning how to set up PS Remote Play in twelve steps is worth ten minutes once so you never fight it again. Know the procedure, run it when the symptoms appear, and move on with your day.

Clear Cache vs Rebuild Database

Both buttons live under option 6, both are non-destructive, and people constantly reach for the wrong one — usually the heavy one, out of a vague forum instinct that "more thorough" equals "better." It does not. They solve different problems and they cost wildly different amounts of your time.

Two Buttons, Two Jobs

"Clear System Software Cache" deletes the temporary junk — shaders, thumbnails, store assets, network scraps — and finishes in seconds. "Rebuild Database" is a different animal: it scans the entire drive and reconstructs the index of every piece of content on the system. On a small or mostly empty drive that takes a few minutes. On a large, stuffed drive — think a fully loaded 8TB M.2 — it can grind for close to an hour. The manbolo and easytechguides rebuild write-ups both frame it as the slow, deliberate option, and they are right to. Reaching for rebuild when you needed a cache clear is like power-washing a smudge off a window.

Time Cost and When It Matters

The Order of Operations

Try the cache clear first, always, because it is cheap and it is the correct fix for the most common complaints. Escalate to Rebuild Database only when the symptom is clearly about the library rather than performance: games missing from the home row, a sort order that has gone insane, a "corrupted data" prompt on a title you know is fine. Rebuilding reflexively for a shader stutter is the modern echo of the PS3-era ritual where every forum thread ended in "have you rebuilt your database?" — a superstition that occasionally worked and therefore never died. Match the tool to the failure. And whatever you do, do not confuse either of these with the nuclear options below them on the list.

What Success Looks Like

Guides love to end at "select OK" and leave you wondering whether anything happened. Here is what a successful clear actually looks like on screen and afterward, so you can tell the difference between "it worked" and "it hung."

The Screens, In Order

Once you select the cache clear, you should see a short, unremarkable sequence — a confirmation, a progress bar that barely registers, a completion message, an automatic restart:

[Safe Mode] > 6. Clear Cache and Rebuild Database
  > Clear System Software Cache
      "This clears the system software cache."
      [ OK ]   [ Cancel ]
  > OK
      ...clearing...              (progress bar, a few seconds)
      "Completed."
  > console restarts automatically

If you had instead chosen Rebuild Database, the output crawls rather than blinks, and the percentage is the thing to watch:

[Safe Mode] > 6 > Rebuild Database
  Scanning storage...            0%
  Reindexing content...         37%
  ...                           82%
  Building database...         100%
  Restarting.                        # total: minutes to ~1 hour on a full drive

Timing You Should Expect

The cache clear is over almost before you have refocused your eyes. If it takes more than a minute or two, that is not normal — it points at a deeper problem, usually a failing drive or a boot the console cannot complete, and you should move to the troubleshooting table rather than sitting there hoping. The rebuild, by contrast, is supposed to be slow; a percentage bar creeping upward for half an hour on a packed drive is the machine doing exactly what you asked.

The First Boot After

When the console comes back up, two things will look slightly off, and both are normal. First, your problem app may launch a touch slower than usual the first time, because its shader cache was among the temporary files you just deleted and the system is regenerating it. Second, the home screen may appear momentarily bare while thumbnail art reloads. This is not the cache clear "resetting your home screen" — that claim circulates on Reddit, and it is a misattribution. The real culprit behind an actually rearranged home screen is a full database rebuild, not a cache clear; the layout is intact, the art is simply repopulating. Give it one reboot and it settles. If your goal was smoother performance on a specific game, this is also the moment to check whether the fix took — and if you are the sort of person who cares about frame pacing enough to be clearing caches over it, you will appreciate our breakdown of running PS Remote Play at 1080p high quality for the same obsessive reasons.

Five Pitfalls to Avoid

Nearly every failed cache-clear attempt comes down to one of a handful of mistakes, and all of them are avoidable once named. Here are the ones that actually waste people's afternoons, grouped by where in the process they bite.

Timing and Power Mistakes

• Releasing the power button on the first beep. This is the most common failure by a mile. The first beep at about one second is a normal boot signal; if you let go there, the console boots to the home screen and you have to start over. Fix: keep holding for the full seven seconds and release only after the second beep.
• Using Rest Mode instead of a full shutdown. If you send the console to Rest Mode and then try to hold the power button, the entry can misfire or, worse, you re-trigger the exact interrupted-write corruption you are trying to clear. Fix: PS button, Power, Turn Off PS5, and wait for the light to go completely dark before you touch the power button.

Controller and Menu Mistakes

• Trying to use the controller over Bluetooth. Safe Mode disables wireless. A DualSense that is not physically plugged in will register nothing, and you will be stuck at a menu you cannot move through, convinced the console is frozen. Fix: connect the controller with a USB-C data cable and press the PS button.
• Counting instead of reading, and landing on the wrong option. If you count "five" from a stale guide, you may hit Restore Default Settings (option 5), which needlessly resets your settings. Worse, a slip toward option 7 is Reset PS5, which deletes everything you own. Fix: ignore the number, read the label "Clear Cache and Rebuild Database," and confirm it is the one before you commit.

Expectation Mistakes

• Expecting the cache clear to delete a broken game or save. It will not, because that data lives in a different menu entirely. People clear the cache to fix a corrupt save, see the save is still there, and conclude the process failed — when in fact it did precisely what it is supposed to. Fix: to remove game data, go to Settings, then Storage; the cache clear deliberately leaves your saves and games untouched, exactly as PSX Extreme explains.
• Panicking at the slower first boot or the bare home screen. The temporary slowness and reloading thumbnails are the cache repopulating, not data loss. Fix: wait, reboot once if needed, and launch your problem app to rebuild its shader cache — the machine catches up within minutes.

Troubleshooting Table

When the procedure does not go cleanly, the failure almost always maps to a known cause. Read this table symptom-first, apply the fix, and escalate only when the cheap fix genuinely does not move the needle.

How to Read This Table

Work top to bottom in order of likelihood. Most entries here are procedural — a mistimed button, a wireless controller, a Rest Mode that never fully powered down. A handful point at genuine trouble (a failing drive, a boot the console cannot complete), and those are flagged so you know when to stop clearing caches and start suspecting hardware.

Symptoms, Causes, and Fixes

When It's Not the Cache

Note the last row and take it seriously: the single most damaging "troubleshooting" outcome is not a stubborn bug, it is a person who counted wrong in a black-screen menu and hit a reset. That is not the cache's fault and no cache clear will undo it. On the flip side, the Rocket League row is the cleanest example of this fix's legitimacy — when a specific game's engine cache corrupts, Epic Games' own support documentation tells PS5 players to clear the PS5 cache to resolve Load Failure errors. When a first-party developer routes you to Safe Mode option 6 by name, you can stop wondering whether this is folklore. It is documented procedure.

Advanced Tips the Guides Skip

The step-by-step is the easy part. The judgment — when to run it, how often, and when to stop — is where most guides go quiet, because "do it whenever, it's a performance boost" gets more clicks than the honest answer.

How Often Is Actually Worth It

Clearing the cache is troubleshooting, not routine hygiene. You do not need to do it monthly, and you definitely do not need to do it "for performance" on a console that is behaving. The 2026 creator ecosystem frames this as a blanket speed-up — titles promising to "increase performance" or "fix lag" — and that framing oversells a narrow tool. Clearing an already-clean cache changes nothing except forcing a slow repopulation on your next boot; you have made the console momentarily slower in the name of speed. Run it when symptoms appear. Otherwise leave it alone. It is a fix, not a tune-up, and treating it as preventive maintenance is cargo-culting.

The External SSD and M.2 Angle

If you run games off an internal M.2 SSD or USB extended storage, a corrupt database can orphan those entries — games installed on a drive the index no longer trusts, showing as missing or refusing to launch. Rebuild Database rescans all attached drives and re-associates that content, which is exactly why it is the right tool for a missing-library problem and the cache clear is not. Keep every drive you care about connected when you rebuild; if a drive is unplugged during the scan, the new index simply will not include it, and you will have made the problem look worse.

The Rest Mode Trade-Off Nobody Mentions

Here is the upstream truth: a large share of these cache problems are born in Rest Mode. A game downloads an update overnight, the write is interrupted, and you wake up to corruption. If you find yourself clearing the cache every week, the cache is the symptom and Rest Mode plus automatic updates is the disease. Consider disabling "Keep Application Suspended," or simply powering the console fully down instead of resting it when a big patch is queued. Fixing the write-interruption source beats clearing the cache the tenth time. And if you are patching something enormous — the kind of hundred-gigabyte install that a next-gen release ships with, or the day-one download for a title like the one we covered in our GTA 6 pricing breakdown — a full power-down during the download is cheap insurance against exactly the corruption this whole article exists to clean up.

What Clearing Cache Will Not Fix

Be honest with yourself about the ceiling. Clearing the cache and rebuilding the database will not fix hardware faults, thermal shutdowns, a dying SSD, a failing disc drive, or anything server-side — a login outage, a store error, a game's own backend being down. If a cache clear followed by a rebuild does not move the needle, stop clearing. Repeating a null fix is the console-era descendant of blowing on the cartridge: it feels like action, it changes nothing, and it delays the real diagnosis. At that point you are looking at a hardware or account problem, and the smart money is on reading the failure, not re-running the ritual. Consoles are long-lived machines — people are still nursing launch PS5s while arguing about whether a PS6 even has a release date — and part of that longevity is knowing which problems software can fix and which it cannot.

The Complete Reference Card

Everything above, compressed into three blocks you can screenshot and keep. Print it, bookmark it, tape it to the console — whatever gets you through the black-screen menu without counting wrong.

The Menu, Memorized

PS5 SAFE MODE  (8 options — cache is #6, by LABEL not count)
1  Restart PS5
2  Change Video Output
3  Repair Console Storage                 non-destructive
4  Update System Software
5  Restore Default Settings               keeps games/saves
6  Clear Cache and Rebuild Database   <=  THE ONE YOU WANT
     a) Clear System Software Cache       seconds, non-destructive
     b) Rebuild Database                  minutes to ~1 hour
7  Reset PS5                              DELETES EVERYTHING
8  Reset PS5 (Reinstall System Software)  DELETES EVERYTHING

The Command Sequence

# PS5 cache clear — full sequence, ~10 minutes
PS button           ->  Control Center
Power               ->  Turn Off PS5           # NOT Rest Mode
wait                ->  indicator light fully dark
HOLD power button   ->  release AFTER beep #2 (~7 seconds)
connect DualSense   ->  USB-C cable, press PS   # Bluetooth is off
select              ->  6) Clear Cache and Rebuild Database
select              ->  Clear System Software Cache
confirm             ->  OK
result              ->  clears in seconds, auto-restart
first boot          ->  slightly slower launch = cache repopulating (normal)

The Decision Tree

symptom                                          ->  action
menu stutter / app won't launch / store glitch   ->  Clear System Software Cache (opt 6a)
missing game tiles / bad sort / "corrupt data"   ->  Rebuild Database (opt 6b)
black screen / no video signal                   ->  Change Video Output first (opt 2)
storage errors, want NO data loss                ->  Repair Console Storage (opt 3)
nothing helps after clear + rebuild              ->  STOP. suspect hardware or server-side
selling the console                              ->  Reset PS5 (opt 7) — and only then

That is the whole discipline. The cache clear is real, it is free, it is fast, and it fixes more than it has any right to — provided you power down fully, hold to the second beep, bring a cable, and read option 6 instead of counting to it. Everything else is superstition. Dust the machine when it needs dusting, and leave it alone when it does not.