PS5 Clear Cache 2026: 12 Steps in Safe Mode, 2 Min

Somewhere in a support forum right now, a stranger is being told to open Settings > System > Storage > Temporary Files on their PS5 and clear the cache from there. That path does not exist. It has never existed. The person offering it is confusing the PlayStation 5 with an Android phone, a web browser, or a dream they once had, and the person receiving it is about to spend fifteen minutes scrolling through menus that will never contain the thing they were promised.

Here is the whole truth, stated once and plainly: the only way to clear the cache on a PlayStation 5 in 2026 is to boot into Safe Mode and select Option 6, “Clear Cache and Rebuild Database,” then choose the sub-option “Clear System Software Cache.” There is no toggle in the standard Settings interface. There is no app. There is no third-party tool, from Sony or anyone else. Sony did not bury it to be cruel. They buried it because the operation touches temporary system state and lives one menu away from the buttons that factory-reset your console, and they would rather you not stumble into it while hunting for the brightness slider.

This guide walks the full procedure in twelve numbered steps, explains what each step is actually for, and — more usefully than most write-ups — tells you when clearing the cache will fix your problem and when you are simply performing a ritual to feel productive. The whole thing takes about two minutes. It needs a USB-C cable and nothing else. It will not delete your games. Let's begin with why the button you are looking for is not where the internet keeps insisting it is.

Why There's No Clear Cache Button

The single most important fact about clearing the PS5 cache is a negative one: the feature you are picturing does not live in Settings. Not under System, not under Storage, not under Saved Data, not under Devices. Understanding why saves you from the dozen dead-end menu paths that circulate as folklore, so we start here rather than at the power button.

The Settings menu path that doesn't exist

The confusion has a paper trail. A 2024–2025 user report on JustAnswer confidently described a route through Settings > System > Storage > Temporary Files, and because it sounded plausible — every other device on Earth has something like it — it propagated. Sony never shipped that screen. Engadget's 2025 cache guide is blunt about it: you cannot reach Safe Mode from Settings at all, and Safe Mode is the only place the cache-clearing function exists. Here is a catalogue of the paths people swear by, every one of which is a mirage:

# Paths people SWEAR exist on PS5. None of them do:
Settings > System > Storage > Temporary Files          # no
Settings > Storage > Clear Cache                        # no
Settings > Devices > Blu-Ray > Clear Cache              # no (that's an Xbox-ism)
Settings > Saved Data and Game/App Settings > Cache     # no

# The ONE real path is not in Settings at all:
[Power OFF] -> [hold power to 2nd beep] -> Safe Mode -> Option 6

Note the third line especially. The “clear the Blu-Ray persistent storage” idea is imported wholesale from the Xbox Series X/S, where Settings > Devices & connections > Blu-ray > Persistent storage genuinely is a menu item. People who owned both consoles muscle-memory their way into looking for it on the PS5 and find nothing, because Sony architected the two boxes differently. If you came here from the green side of the aisle, our breakdown of why Sony and Microsoft diverged so hard last generation explains the philosophical split that still shapes both menus today.

What Sony actually means by “cache”

“Cache” on the PS5 is not one thing; it is a bucket of temporary state the operating system stages to avoid recomputing work. That includes UI and shader scratch data, download and install staging files, thumbnail and store-page caches, and assorted temp files that individual apps drop into system-managed space. None of it is your save game. None of it is your installed game. It is the OS equivalent of a scratchpad, and like any scratchpad it occasionally accumulates a scribble that confuses whatever reads it next — which is when you get the symptoms that send people looking for this button: menu lag, sluggish scrolling, apps that refuse to launch after a firmware update, random crashes, and store pages that load like it's 2011.

What clearing that scratchpad does not do is repair hardware. As Engadget notes, a cache clear is a short-term remedy; it will not resurrect a failing SSD, fix thermal throttling, or undo a degrading power supply. If your console is crashing because the internal drive is dying, you can clear the cache until the heat death of the universe and the crashes will return. Keep that boundary in mind — half the “it didn't work!” complaints are people applying a software fix to a hardware fault.

Why Safe Mode is the only door

Safe Mode is a separate, minimal boot environment. It loads before the full system software comes up, which is precisely why it can safely operate on files the running OS would otherwise have locked. You cannot clear a cache that the live operating system is actively holding open; the console has to be in a state where those files are quiescent. That is the entire engineering reason the function is gated behind a physical power-button sequence rather than a Settings toggle — Settings runs inside the very environment whose scratchpad you are trying to wipe. It is the same reason your PC's disk-check utilities schedule themselves for the next reboot instead of running live. Once you internalize that, the “why is this so annoying” feeling evaporates: it is not annoying, it is correct.

Prerequisites: Firmware, Cable, Time

You need remarkably little for this job, but the little you need is non-negotiable. Skipping the cable requirement in particular is the number-one reason people get stranded on the Safe Mode screen staring at an unresponsive controller. Here is the full checklist before you power anything down.

Firmware: 26.04-13.42.00 (or whatever shipped this month)

The current PS5 system software as of this writing is 26.04-13.42.00, released July 1, 2026 — a roughly 1 GB “we've improved system performance and stability” drop, which is Sony's standard phrasing for a security-and-bugfix patch it doesn't want to advertise, per PlayStation LifeStyle and Push Square. The version format is YY.0X-major.minor.patch, and Sony ships one of these nearly every month. The exact digits do not change the procedure. The Safe Mode layout has been stable for years, and the cache sub-option has lived under Option 6 since roughly late 2023. If a support script tells you the process depends on “System Software Version 7.00” or “Version 9.00,” close the tab — those are PlayStation 4 version numbers. The PS5 has never used them. Confirm what you're actually running here (this path, unlike the mythical ones, exists):

Settings > System > System Software > Console Information

  System Software Version   26.04-13.42.00
  Model                     CFI-7000 (Launch) / CFI-2000 (Slim) / CFI-7000B (Pro)

# The path ABOVE exists. This is where you verify firmware.
# It is NOT where you clear the cache. Nothing in Settings is.

Hardware: one USB-C cable, one power outlet

You need a data-capable USB cable with a USB-C end for the DualSense controller. This is the single detail everyone underestimates. Bluetooth is disabled in Safe Mode — the wireless stack simply isn't loaded — so a controller that pairs flawlessly during normal use is a dead brick on the Safe Mode screen until you wire it in. The cable that shipped in your PS5 box works. A random charge-only cable from a drawer may not, because charge-only cables omit the data lines and the console will see nothing on the USB bus. If your controller won't respond after connecting, suspect the cable before you suspect the console. You do not need a PlayStation Plus subscription, an internet connection, a USB storage drive, or any purchased tool. The operation is free and entirely local. This is a genuine contrast with the Xbox “unplug the console and wait two minutes” ritual, which relies on a full power cycle to drain volatile memory; the PS5 does something more surgical and never asks you to touch the wall socket.

Time, expectations, and a backup you probably don't need

Budget about two minutes for the cache clear itself, plus a minute or two of the console restarting automatically. If you accidentally (or deliberately) pick the other sub-option, Rebuild Database, budget anywhere from ten minutes to about an hour depending on how full your drive is — we'll cover that distinction next. Clearing the cache does not delete games, apps, saved data, or account information, a point Sony's support pages state directly and one that Epic Games leans on in its own troubleshooting docs. Still, if you are the belt-and-suspenders type, back up saves first: Settings > Saved Data and Game/App Settings > Cloud Storage (PS Plus) or copy them to an exFAT/FAT32 USB drive. You almost certainly won't need the backup for a cache clear. You will be glad you have it the day you fat-finger your way to Option 7. If you've been babying a 90 GB install — say, the one you're guarding for the November GTA VI launch — rest easy: the cache clear leaves it untouched.

Cache vs. Rebuild Database

Option 6 is labeled “Clear Cache and Rebuild Database,” and that single label hides two very different operations behind one door. Choosing the wrong one is harmless to your data but catastrophic to your afternoon, because one takes ninety seconds and the other can take an hour. Know the difference before you're standing in the menu.

Clear System Software Cache: the light touch

This is the one you almost always want. It purges the operating system's temporary files — the scratchpad described earlier — and nothing else. It touches no game data, rebuilds no index, and finishes in roughly one to two minutes. It is the correct tool for menu sluggishness, post-update weirdness, apps that hang on launch, store pages that won't render, and the general “my PS5 feels off since the last patch” complaint. Epic Games explicitly recommends exactly this sub-option to fix Rocket League “load failure” errors, and their step-by-step help article walks the same Safe Mode path we're about to detail. When a game developer's official fix is “clear the system cache,” this is the sub-option they mean.

Rebuild Database: the up-to-an-hour reindex

Rebuild Database is a heavier animal. It scans the entire internal SSD and constructs a fresh content database — the index that tells the console what games, apps, saves, and media you have and where they live. It does not delete anything, but it reads every corner of the drive, so its runtime scales with how full that drive is. On a nearly empty console it might take ten minutes; on a stuffed 8 TB M.2 expansion it can run close to an hour. You reach for Rebuild only when the library itself is misbehaving: game icons that vanished or duplicated, a corrupt-looking content list, install entries that won't launch or delete, or a “Recently Played” row that's gone haywire. It is overkill for simple lag. If you've heard that clearing the cache “scrambles your home screen layout” — that's a real phenomenon, but it's a side effect of a Rebuild reshuffling the database, not of the lightweight cache clear. Blame the reindex, not the scratchpad wipe.

Which one you actually need

The decision tree is short. Symptoms about speed and stability point to Clear System Software Cache. Symptoms about the library and its contents point to Rebuild Database. When genuinely unsure, run the cache clear first — it's faster and less disruptive — and escalate to Rebuild only if the problem survives. The table below is the whole comparison at a glance.

The 12-Step Safe Mode Walkthrough

Here is the full procedure. Twelve steps, each with the reason it exists so you're not blindly following instructions. Read step 6 twice before you start — the beep timing is where most people go wrong, and getting it wrong just boots the console normally and wastes the run.

1. Close your games and apps. Quit anything running from the home screen (highlight the tile, press Options, Close Game). Rationale: you're about to fully shut down, and closing cleanly avoids an app writing to state mid-shutdown, which is exactly the kind of half-finished write that corrupts a cache in the first place.
2. Power the console fully OFF — not Rest Mode. Press the PS button, open the control center, choose Power > Turn Off PS5. Rationale: Rest Mode keeps the system partially alive and will not let you enter Safe Mode. This is the second-most-common failure after the beep timing. It must be a full shutdown.
3. Wait for the status light to stop blinking and go completely dark. The indicator pulses amber as it shuts down, then extinguishes. Rationale: holding the power button while the console is still mid-shutdown produces unpredictable behavior. Let it reach a true off state — give it a good ten seconds after the light dies.
4. Grab your controller and a data USB-C cable; don't plug in yet. Have them in hand. Rationale: Bluetooth is off in Safe Mode, so you'll need the wire in a moment. Staging it now means you're not fumbling in a drawer while the Safe Mode screen waits.
5. Press and hold the physical power button on the console. Not the controller's PS button — the actual button on the chassis. Rationale: this is the only supported entry to Safe Mode. There is no software path, from Settings or anywhere else. Keep holding; don't tap.
6. Release only after the SECOND beep (~7 seconds). You'll hear one beep the instant you press (that's a normal power-on), then a second beep about seven seconds later. Let go on the second. Rationale: releasing on the first beep boots the console normally and you'll have to start over. The two-tone gap is the entire signal.

   [press & hold the power button]
     t = 0.0s   *BEEP*      <- console powers ON. DO NOT release here.
     t = 7.0s   *BEEP*      <- Safe Mode armed. RELEASE NOW.
     t > 7s     (silence)   <- held too long; it still boots into Safe Mode
   
   Mnemonic: one-Mississippi ... seven-Mississippi, let go on the 2nd tone.

7. Connect the controller with the USB cable and press the PS button. USB-C into the DualSense, other end into a front USB port on the console, then press PS. Rationale: Safe Mode's on-screen prompt literally says to connect a controller with a USB cable and press the PS button — because wireless isn't available here. Nothing on screen will respond until you do this.
8. Read the menu and locate Option 6. You'll see a numbered list of eight items. Rationale: the ordering is fixed in current firmware, and it's worth a two-second read so you don't confuse Option 6 with the far more dangerous Options 7 and 8 sitting right below it.

   -- PS5 SAFE MODE --------------------------------------------
    1  Restart PS5
    2  Change Video Output
    3  Repair Console Storage
    4  Update System Software
    5  Restore Default Settings
    6  Clear Cache and Rebuild Database   <-- YOU ARE HERE
    7  Reset PS5
    8  Reset PS5 (Reinstall System Software)
   -------------------------------------------------------------

9. Select Option 6, “Clear Cache and Rebuild Database.” Navigate with the D-pad and press X. Rationale: this opens the two-choice sub-menu; selecting it does not run anything yet, so there's no risk in opening it to look.
10. Choose “Clear System Software Cache” — not Rebuild Database. It's the first of the two sub-options. Rationale: this is the ~2-minute cache purge you came for. Rebuild Database is the up-to-an-hour reindex you only want if your library is broken. Pick deliberately.

    -- 6. Clear Cache and Rebuild Database ----------------------
     > Clear System Software Cache     ~1-2 min    removes OS temp files
       Rebuild Database                up to ~1hr  re-indexes the whole SSD
    -------------------------------------------------------------
    Pick the FIRST one for a cache clear. The second is a different job.

11. Confirm with OK and let it run — do not cut the power. The console clears the cache and will restart automatically, possibly more than once. Rationale: interrupting power mid-operation is the one way to actually damage something here, potentially corrupting the database and forcing a full Rebuild or worse. Walk away for two minutes. Leave it alone.
12. Let it boot to the sign-in screen and verify. Sign in, open the app or menu that was misbehaving, and check whether the symptom is gone. Rationale: the first boot after a clear is slightly slower while shader and UI caches rewarm; that's expected and passes in under a minute. If the problem persists past a normal boot, escalate to Rebuild Database or firmware update rather than clearing the cache again — a second identical clear won't do anything the first didn't.

What You Should See On-Screen

Because the PS5 gives you almost no verbose feedback, it helps to know what “working correctly” looks like — otherwise a black screen and a fan spin-up reads as a crash when it's actually the normal restart. Here's the play-by-play.

The Safe Mode screen, described

Safe Mode is spartan: a plain background, a small numbered list of eight options, and a prompt at the bottom instructing you to connect a controller via USB and press the PS button. There is no animation, no PlayStation home-screen chrome, and deliberately no music. If you see the full, colorful home screen with your avatar and game tiles, you are not in Safe Mode — you released the power button on the first beep and booted normally. Power down and try step 6 again.

During the clear: restarts are normal

After you confirm the cache clear, expect the following sequence. The screen may go black, the fans may audibly spin, and the console may reboot once or twice on its own. This is normal and documented; do not interpret it as a hang and do not pull the power.

Clearing the system software cache...
[||||||||||||||||||||||||||||] 100%

Restarting...
(screen goes black; fans spin up; the console may reboot 1-2x)

PS5 boots to the sign-in screen.
First menu scroll may stutter ~20-30s while UI/shader caches rewarm,
then returns to full speed.

After: the first boot is slower, then faster

The single most misread part of this process is the first boot afterward. Because you just wiped the OS scratchpad, the console has to rebuild parts of it on the fly — the first time you open the store or scroll the game library, it may stutter for twenty to thirty seconds as those caches repopulate. This is not a failed clear; it is the evidence of a successful one. Give it one full session of normal use and the console should feel at least as snappy as before, and noticeably snappier if cache cruft was the original problem. If instead the console feels identical to before you started, the cache was never your bottleneck — head to the troubleshooting table.

6 Common Pitfalls and Their Fixes

Nearly every failed cache clear traces back to one of six mistakes, and all six are avoidable once named. Here they are in rough order of how often they trip people up.

The three that strand you before you even start

Pitfall 1 — Releasing on the first beep. You hold the power button, hear a beep, and let go — and the console boots normally. Fix: there are two beeps about seven seconds apart. The first is a standard power-on; you want the second. Count “one-Mississippi” up to seven and release on the second tone. Holding slightly too long is harmless; it still enters Safe Mode.

Pitfall 2 — A dead controller in Safe Mode. The controller pairs fine in daily use but does nothing on the Safe Mode screen. Fix: Bluetooth is disabled in Safe Mode by design. You must connect the DualSense with a data-capable USB-C cable and press the PS button. If a wired controller still won't respond, your cable is charge-only — swap it for the one that came with the console.

Pitfall 3 — Rest Mode instead of a full shutdown. You “turned it off,” hold the power button, and it just wakes up normally. Fix: Rest Mode is not off. Use Power > Turn Off PS5 from the control center, wait for the status light to go fully dark, then hold the power button. Safe Mode requires a true cold state.

The three that waste your time or scare you

Pitfall 4 — Picking Rebuild Database by accident. You select Option 6 and, on autopilot, choose the wrong sub-option — now you're staring at a progress bar that says forty-five minutes remaining. Fix: the lightweight cache clear is the first sub-option, “Clear System Software Cache.” Rebuild is the second. If you've already started a Rebuild, though, don't panic and don't cut power — let it finish. It won't delete anything; it's just slow.

Pitfall 5 — Cutting the power mid-process. The console restarts on its own, you assume it froze, and you yank the plug. Fix: never interrupt the power during a clear or rebuild. Automatic restarts are part of the operation. Pulling power mid-write is the one action here that can genuinely corrupt the system database and force a lengthy repair. Patience is the fix.

Pitfall 6 — Expecting a cache clear to fix a hardware problem. You clear the cache to solve crashes, freezes, or storage errors, and they come right back. Fix: recognize the boundary. Cache clearing addresses software state. Failing storage, thermal throttling, a dying PSU, or a drive that's 100% full are different failures with different remedies — repair storage (Option 3), delete games to free space, or, if it's physical, service the console. Engadget is explicit that a cache clear does not repair hardware degradation.

Troubleshooting: 12 Failure Modes

When the procedure misbehaves, the fix is almost always mechanical and specific. Match your symptom to the row below. Note that several “the cache clear didn't help” entries resolve to a different tool entirely — the point of the cache clear is narrow, and half of troubleshooting is admitting you need Option 3, Option 4, or a fuller diagnosis instead.

PS5 Pro, Slim, and Digital

People ask whether the fancier or slimmer models change the procedure. They do not — but the button locations and the runtimes vary just enough to be worth thirty seconds of your attention.

PS5 Pro: identical procedure, bigger drive

The PS5 Pro, released November 2024, uses the identical Safe Mode cache-clearing procedure as the standard console. There is no Pro-specific firmware branch and no different menu; Option 6, both sub-options, the beep timing, the USB-controller requirement — all the same. The only practical difference is that the Pro ships with a larger internal SSD (2 TB), so if you run Rebuild Database on a heavily loaded Pro it will take longer than on a base console, simply because there's more drive to index. The lightweight cache clear is still a ~2-minute job regardless of model. If you're weighing whether the Pro's extra horsepower is worth it in the first place, our PS5 Pro vs. PS5 breakdown covers the $300 premium and the 45% rasterization gap in detail; maintenance behavior, at least, is a wash between them.

Slim and Digital: the button is in a different spot

The physical power button moved between hardware revisions, which matters because step 6 depends on finding it. On the launch model (CFI-1000/CFI-7000), the power button is the lower of the two buttons on the front. On the Slim (CFI-2000), the layout and disc-drive attachment differ, so orient yourself before you commit to a seven-second hold. On the all-digital variants there's no disc drive to use as a landmark, but the power button is still on the console body, not the controller. Whichever box you own, the rule is unchanged: physical button, hold to the second beep. There is no version of the PS5 — Standard, Slim, Digital, or Pro — that lets you clear the cache from Settings.

What about the original launch model?

The launch-day PS5 from November 2020 runs the same current firmware and the same eight-option Safe Mode as everything else; Sony has kept the maintenance surface consistent across the whole family. The only thing that meaningfully ages is the internal SSD's free space and the thermal paste, neither of which a cache clear addresses. If your day-one console is throwing crashes that a cache clear and a Rebuild both fail to fix, you're looking at a hardware-service conversation, not a software one.

Advanced Tips and the CMOS Myth

Once you understand that “clear the cache” is one narrow tool in a small toolbox, the advanced move is knowing which other Safe Mode option to reach for and which internet remedies to ignore entirely.

When to rebuild instead of clear

Run Rebuild Database, not a cache clear, after you've mass-deleted a batch of games, after a storage expansion or migration, or whenever the library UI shows ghosts — icons for games you removed, duplicates, or installs that won't launch. The rebuild reconciles the on-screen list with what's physically on the drive. It's slow but non-destructive, and it's the correct fix for exactly the class of problems a cache clear can't touch. A good habit: cache clear for behavior, rebuild for inventory.

Corrupt storage and the “Repair Console Storage” option

If you're seeing storage errors on boot — the CE-108255-1 family and its relatives — the tool is Safe Mode Option 3, Repair Console Storage, which scans and repairs the internal drive's file system rather than merely reindexing it. This sits a notch above Rebuild in severity and is the right escalation when the database won't even build cleanly. Don't jump to a factory reset (Options 7/8) until you've tried Repair and a firmware reinstall via Option 4; the nuclear options erase everything, and there's rarely a reason to reach them for a storage hiccup.

The CMOS-battery myth (and why it isn't cache)

A persistent piece of forum lore holds that you should replace the PS5's internal CMOS battery to “clear the cache” or fix game-launch issues. Do not conflate these. The CMOS battery keeps the real-time clock alive; it has nothing to do with the software cache you're clearing in Safe Mode, and swapping it on a modern PS5 can introduce time-sync problems rather than solve them. If someone tells you a coin-cell replacement is part of routine cache maintenance, they've crossed two unrelated wires. Cache is temporary software state, wiped in Safe Mode in two minutes; the CMOS cell is hardware timekeeping. The same category confusion produces the Xbox-style “unplug and drain the capacitors” advice, which also does nothing useful on a PS5. If you find yourself troubleshooting connected-play features rather than local performance, note that a cache clear won't help there either — that's a job for our PS5 Remote Play walkthrough, since streaming problems live in the network stack, not the local scratchpad. And if all of this maintenance has you wondering whether the box is nearing the end of its life, the honest answer on timelines lives in our PS6 release-window analysis — but a healthy PS5 with a clean cache has years left in it regardless.

The Complete Safe Mode Reference

Everything above, condensed into one reference you can screenshot. Keep it handy: the entry sequence never changes, and knowing what each of the eight Safe Mode options does — especially which two erase your data — turns a nerve-wracking menu into a routine one.

The full option map

This is the complete, working reference for the current firmware. The entry sequence, the menu map, the boundary of what a cache clear can and can't fix, and the two-minute optional backup are all here in one block.

############################################################
# PS5 CACHE / MAINTENANCE REFERENCE  (firmware 26.04-13.42.00)
############################################################

ENTRY  (the only method that exists):
  1. Controller: Power > Turn Off PS5     (NOT Rest Mode)
  2. Wait until the status light is fully dark
  3. Hold the physical power button -> release on the 2ND beep (~7s)
  4. Wire the controller (USB-C at the DualSense) -> press PS button

MENU MAP:
  Option 6  Clear Cache and Rebuild Database
     |__ Clear System Software Cache   light  ~1-2 min    SAFE   <- the cache clear
     |__ Rebuild Database              heavy  up to ~1hr  SAFE (long)

  Option 3  Repair Console Storage     for CE-108255-1 / corrupt file system
  Option 5  Restore Default Settings   keeps games+saves, resets preferences
  Option 7  Reset PS5                  WIPES EVERYTHING (nuclear)

WHAT A CACHE CLEAR DOES *NOT* FIX:
  - failing SSD / thermals / PSU        -> hardware service
  - storage 100% full                   -> delete games, not cache
  - account / PSN network outages        -> not local state
  - CMOS/clock issues                    -> unrelated to cache

OPTIONAL BACKUP FIRST (~2 min):
  Settings > Saved Data and Game/App Settings > Cloud Storage (PS+)
  or copy saves to a USB drive formatted exFAT / FAT32
############################################################

All eight options, ranked by danger

Read this once and you'll never fear the Safe Mode menu again. The only two rows that destroy data are 7 and 8 — everything above them is recoverable or purely cosmetic.

The one-line takeaway

There is no Clear Cache button in PS5 Settings, there never was, and anyone who tells you otherwise is describing a different console. The real procedure is Safe Mode, Option 6, “Clear System Software Cache” — reached by a physical power-button hold to the second beep and a wired controller. It takes two minutes, deletes nothing you care about, and fixes exactly the software gremlins it's meant to fix and none of the hardware ones it isn't. For the authoritative version of every step, Sony's own Safe Mode support page is the source of record. Bookmark it, bookmark this, and stop scrolling through Settings looking for a button that was never built.