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

The PlayStation 5 has no button labeled make it faster. What it has instead is a maintenance chore buried three menus deep in a boot environment most owners meet exactly once — the day something breaks. Clearing the system software cache is that chore. It is not a performance mod, not a secret unlock, and emphatically not the thing a YouTube thumbnail with a red arrow and the word BOOST promises it is. It is Sony's version of turning it off and on again, with one extra step that actually does something.

This guide walks the entire operation end to end: what the cache is, why occasionally throwing it away helps, the exact twelve-step Safe Mode route as it exists on firmware 26.05-13.60.00 — the current stable build as of August 2026 — and, because a depressing fraction of the internet still gets this wrong, why the menu item you want is Option 6, not Option 5. We will also be honest about when clearing the cache is the wrong tool, which is more often than the tutorials admit. Budget ten minutes, find a USB-C data cable, and whatever you do, do not reach for Rest Mode.

What Clearing the Cache Actually Does (and Doesn't)

A cache is scratch space. Any operating system worth the name writes temporary files so it does not have to recompute the same thing twice: thumbnail art for your game tiles, staging data for store pages, shader and asset scratch, transient bits of interface state. On a console you use every day for a couple of years, that scratchpad accumulates, and some of it goes stale or subtly corrupt. When the OS trips over a bad entry you get the familiar symptoms — a home screen that hitches, a store page that spins forever, a game that hangs on its splash logo, a download frozen at 99%. Clearing the cache forces the console to bin the scratchpad and rebuild it from source. That is the entire mechanism. There is no magic in it, and there is no downside beyond a slightly slower next boot.

The system software cache, in plain terms

The word that matters is system. The action you are performing — Clear System Software Cache — targets the operating system's own temporary files, not your game data. It is distinct from a game's internal cache and completely separate from your save files. Clearing it deletes nothing you cannot regenerate: no saves, no installed games, no accounts, no trophies, no settings. Sony's own Safe Mode documentation describes the option as targeting temporary files without touching your personal data or default settings, and Engadget's how-to frames the whole thing as a troubleshooting step rather than a data wipe. Here is the exact split:

CLEARED by Clear System Software Cache:
  - OS thumbnail / image cache
  - UI and store staging data
  - transient system temp files
  - stale download / patch scratch data

KEPT (untouched):
  - installed games and apps
  - save data (local and cloud)
  - screenshots and video clips
  - accounts, trophies, friends
  - all Settings (network, video, audio, HDR)

What it will not fix

Set your expectations at floor level. Clearing the cache will not raise the frame rate of a game that was already running fine. It will not conjure CPU or GPU headroom — the silicon does not get faster because you deleted some thumbnails. It will not repair a failing SSD, a dying fan, thermal throttling, a marginal HDMI cable, or a game's own shipped bugs. Engadget is blunt on this point: cache clearing is a short-term remedy and does nothing about hardware degradation. If your PS5 is loud, hot, or crashing under sustained load, this is not your fix. The actual performance story of the machine lives in its hardware, not its scratch files — we went deep on exactly what the box can do in our PS5-versus-PS4 breakdown, and none of that ceiling moves because you cleared a cache.

Why Sony buried it in Safe Mode

Clearing the cache is a recovery action, not a daily setting, so it lives in the recovery environment alongside the other something-is-wrong tools. There is deliberately no path to it from the normal Settings interface. That is the same design logic that keeps the genuinely destructive options — Reset PS5, Reinstall System Software — behind the same boot sequence: Sony gates maintenance and nuke buttons behind an intentional, slightly awkward ritual so you cannot fat-finger your way to a wiped console from the couch. The awkwardness is the feature, not a bug in the interface.

It's Option 6, Not Option 5: The Menu Renumbering

Follow an older tutorial — or read TechRadar's guide, which refers to the fifth option down — and you will be told to select Option 5. On current firmware that instruction is wrong, and following it by rote lands you on Restore Default Settings, a different and considerably more annoying action. The correct entry today is Option 6. This is not pedantry; it is the single most common way people botch this procedure, and it is the reason we keep repeating the number until it sticks.

The current 8-item Safe Mode layout

On firmware 26.05-13.60.00, the Safe Mode menu has eight entries, in this order:

PS5 Safe Mode menu - firmware 26.05-13.60.00 (Aug 2026)

  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 want this
  7. Reset PS5
  8. Reset PS5 (Reinstall System Software)

  Option 6 opens two children:
     a) Clear System Software Cache   (light - the goal)
     b) Rebuild Database              (heavy)

Option 6, Clear Cache and Rebuild Database, opens a sub-menu with two children. The first, Clear System Software Cache, is the light action you almost always want. The second, Rebuild Database, is the heavy one. More on that distinction shortly, because confusing the two is the second most common mistake after the number itself.

Why old guides say 5

The number moved. Earlier PS5 Safe Mode layouts carried fewer entries and ordered them differently; the standalone cache-clear child is a relatively recent addition, having arrived alongside the 8TB-drive and Dolby Atmos era in late 2023. When Sony inserted Repair Console Storage into the list — it now sits at position 3 — and folded cache-clearing and database-rebuilding into the combined Option 6, every entry below the insertion point slid down a slot. Guides written against the older menu, and search results quoting 2022-vintage screenshots, still say 5. This is also why mainstream outlets openly disagree: some describe the fifth option down, others tell you to pick Clear Cache and Rebuild Database by name. The name has been stable across the renumbering; the ordinal has not.

Navigate by label, not by number

The lesson writes itself. Ignore the number. Read the words. On any firmware from late 2023 onward — which, given how relentlessly Sony nags you to update, is effectively all of them — you are looking for the text Clear Cache and Rebuild Database, and then, inside it, Clear System Software Cache. If a 2026 video swears it is Option 5 and another swears it is Option 6, they are both describing something real; they are just standing on different firmware. The label is your source of truth, and the label has not changed.

Prerequisites: Firmware, a Cable, and Ten Minutes

This is a short procedure with a short list of requirements, but two of them trip people up: knowing what firmware you are actually on, and understanding that your controller has to be physically tethered. Handle these before you power down and the rest is a two-minute menu walk. Rush them and you will spend twenty minutes convinced your console is frozen when it is simply waiting for a controller it cannot see.

Check your firmware version first

While the console is still on, go to Settings → System → System Software → Console Information. You are looking for the System Software Version string. As of this writing the current stable build is 26.05-13.60.00, shipped 23 July 2026 as the second of that month's two updates (the first, 26.04-13.42.00, landed around 1 July). Sony ships these roughly monthly under the boilerplate banner of improved system performance and stability.

Settings → System → System Software → Console Information

  System Software Version : 26.05-13.60.00

  26  = year (2026)
  05  = release number within the year (the 5th)
  13  = major build
  60  = minor build
  00  = patch

  This is NOT a PS4-style number.
  There is no PS5 Version 7.00 or Version 9.00.

One myth to kill on sight: the PS5 has never used a plain PS4-style version number. If a guide instructs you to be on Version 7.00 or Version 9.00 before clearing the cache, that guide is describing a PlayStation 4 wearing a PS5 costume. The PS5's scheme is year-based, and the cache procedure is identical regardless of which monthly patch you happen to be sitting on.

The hardware you actually need

A PS5 or PS5 Pro — the procedure is identical across the family, which is why 2025 and 2026 guides that mention the Pro use the exact same steps. A television or monitor. And, non-negotiably, a USB cable to wire the controller. The DualSense ships with a USB-A-to-USB-C lead; the controller end is USB-C. This matters because Bluetooth is switched off inside Safe Mode. Your pad will not pair wirelessly there no matter how many times you press the PS button in frustration. You must physically tether it, and — a trap we will return to — it has to be a data cable, not a charge-only one.

What you do not need

You do not need PlayStation Plus; the operation is free. You do not need an internet connection for the cache clear itself — you would only need one for the neighbouring Update System Software option. You do not need a factory reset, and any guide that treats clear cache and reset console as synonyms should be closed immediately. What you should do, purely on principle, is make sure your saves are backed up before you enter Safe Mode — not because clearing the cache touches them, but because you are about to be one careless D-pad press away from Reset PS5, which lives two rows below the option you want. Cloud saves need PS Plus; a USB save export does not.

The Procedure: 12 Steps to a Clean Cache

The whole thing is a menu walk. Only two moments carry any real risk of error — the shutdown, which must be a true power-off rather than Rest Mode, and the controller, which must be wired. Everything else is reading a list and pressing X. Here is the full sequence, with the reasoning for each step, because a step you understand is a step you will not skip.

1. Save and quit everything. You are about to cut power to the console. Anything unsaved in an open game dies with the session, so close out cleanly first rather than trusting an autosave you have not verified.
2. Fully shut the console down — do not use Rest Mode. Safe Mode can only be triggered from a genuine power-off state. SlashGear's guide hammers this specifically: turn the PS5 all the way off and do not leave it napping in Rest Mode. Press the power button and choose Turn Off PS5 from the power menu.
3. Wait for a complete power-down. The indicator light should go fully dark and the fan should fall silent. The second-beep timing in the next steps only behaves correctly from cold; if the light is still pulsing, you are in Rest Mode and the hold will do the wrong thing entirely.
4. Press and hold the physical power button. There is no Settings route into Safe Mode on any PlayStation — not on the PS4, not on the PS5. The physical button is the only door. Contrary to a common brief-writer's myth, this is not a PS5-versus-PS4 distinction; neither console has ever offered a menu-based Safe Mode.
5. Listen for two beeps and release after the second. The first beep fires the instant you press. Keep holding. The second beep sounds at roughly seven seconds and signals that Safe Mode is booting — release then. Asurion, Engadget, and SlashGear all describe the identical seven-second, second-beep release.
6. Wait for the Safe Mode screen. You will get a stark black screen with a plain list and a prompt to connect a controller. This is Safe Mode; it is meant to look austere, and its ugliness is not a fault.
7. Connect the DualSense with a USB cable. Because Bluetooth is disabled here, the pad cannot connect wirelessly. Engadget spells this out explicitly: connect the controller with a USB cable. Plug the USB-C end into the pad and the other end into the console's front port.
8. Press the PS button once. This registers the wired pad as controller one and unlocks navigation. Nothing on screen responds until you do this, which is the source of endless false frozen-console panics.
9. Select Option 6, Clear Cache and Rebuild Database. This opens the two-child sub-menu. Read the label to confirm — if the highlighted row says Restore Default Settings, you are on 5 and one row too high.
10. Choose Clear System Software Cache. This is the light, cache-only action and the entire reason you are here. Its sibling, Rebuild Database, is heavier, slower, and unnecessary for a simple cache clear.
11. Confirm with OK. A single confirmation. There is no lengthy warning wall because nothing you care about is being deleted.
12. Let it restart. The console runs the clear — anywhere from a few seconds to a minute or two — and reboots to the normal interface on its own. Do not intervene, and do not pull power because it looks slow.

For readers who think in timelines rather than prose, here is the same sequence as a timing map:

t = 0.0s   press and HOLD power button   → BEEP #1 (fires on press)
t ~ 7.0s   keep holding ............... → BEEP #2   ← RELEASE HERE
t ~ 7.5s   release the button
           → console boots to Safe Mode (black screen)
           → connect DualSense via USB-C data cable
           → press the PS button
           → 6  →  Clear System Software Cache  →  OK
           → 10 to 90 seconds, then automatic restart

One piece of practical timing advice: if you are clearing the cache because a large install is about to land — the Elden Ring content drop due 28 August being the obvious late-summer example — do the clear first, then start the download. A clean patch-scratch space is exactly the condition under which a big installer is least likely to wedge itself at 99%.

Expected Output: What a Normal Run Looks Like

A console is not a terminal. It does not stream a log to your television while it works, so let us be precise about what expected output means here: a brief progress indicator, an automatic reboot, and a home screen that looks momentarily undressed while its artwork re-caches. If you were watching a PC do this, the log would read something like the block below — treat it as a faithful representation of the stages, not as literal text the PS5 prints on screen.

[Safe Mode] Clear System Software Cache ... running
[Safe Mode] Done.
[Safe Mode] Restarting PS5 ...
[Boot]      longer-than-usual splash  (this is normal)
[Home]      UI returns; thumbnails and store art
            re-render over the next few minutes

The timings you should see

Clear System Software Cache is fast: seconds on a tidy console, up to a minute or two at the outside. That is the whole point of choosing it over its sibling. Rebuild Database, by contrast, has to scan and re-index everything on the drive and can run from several minutes to the better part of an hour on a full 8TB SSD. If you selected the cache option and the operation is still grinding twenty minutes later, you did not select the cache option — you are rebuilding the database. Let it finish anyway; interrupting a rebuild is a reliable way to manufacture the exact corruption you were trying to fix.

The deliberately slow first boot

The reboot after a cache clear is slower than a normal start-up, and this alarms people who assume they have bricked something. They have not. The console is regenerating the temp files it just discarded — repopulating thumbnails, store art, recently-played tiles — and that work happens during and just after the first boot. Expect the home screen to appear with missing box art that fills in over the following few minutes of use. This is expected behaviour, not a hang. Do not yank the power cord to fix it; pulling power mid-rebuild is how a harmless slow boot becomes a genuine problem worth writing a support ticket about.

How to confirm it actually worked

There is no triumphant success dialog beyond the restart itself, which frustrates people who want a green checkmark. You confirm the fix by symptom, not by message. The store page that would not load now loads. The download stuck at 99% resumes. The hitchy carousel scrolls smoothly. The game that hung on its splash boots. If the symptom persists, the cache was not the cause — which is itself useful information, because clearing the cache is also the cheapest way to rule the cache out before you escalate to heavier tools or start suspecting the hardware.

Clear Cache vs Rebuild Database vs Repair Storage

Three adjacent Safe Mode tools get confused constantly, partly because two of them share Option 6 and partly because brief-writers routinely swap their menu positions. Here is the clean mental model: cache-clear is a dusting, database-rebuild is a re-cataloguing, and storage-repair is a structural inspection. You escalate through them in that order, and you do not skip straight to the heavy one because a tutorial told you to.

The light option: Clear System Software Cache

The first child of Option 6. It deletes the operating system's temporary files and nothing else, runs in seconds, and is entirely non-destructive. This is your first resort for interface hitching, store pages that will not load, downloads that stall, and the class of game-launch failures that come from a poisoned cache. Epic Games, notably, officially recommends exactly this step to fix Rocket League Load Failure errors — a rare case of a developer pointing users straight at a Safe Mode maintenance action rather than pretending it does not exist.

The heavy option: Rebuild Database

The second child of Option 6. Instead of temp files, it scans everything on your storage and rebuilds the content database — the index that tracks where each game and media file lives and how your library is sorted. It does not delete your data, but it re-catalogues all of it, which is why it can take from minutes to roughly an hour on a full drive. Reach for it when your library shows phantom or missing titles, when the sort order has gone haywire, when you see duplicate tiles, or when a game throws a corrupted-data warning. A word on a persistent myth: the claim that clearing the cache resets your home-screen layout is a garbled description of a Rebuild Database side effect — a re-sort that some users noticed after certain large installs — reported anecdotally and never documented by Sony as a consequence of the cache clear. The light option does not rearrange your home screen.

The structural option: Repair Console Storage

This one is not under Option 6 at all — it is Option 3, a separate top-level entry, which is precisely the fact that trips up guides claiming Rebuild Database is Option 2. For the record: Option 2 is Change Video Output; Rebuild Database is a child of 6; and Repair Console Storage is 3. Repair Console Storage checks the file system itself for errors and is a step beyond a rebuild — use it only when storage is actually throwing read or write errors. Above it in severity sit the genuinely destructive options, Reset PS5 and Reinstall System Software, which wipe data and are last resorts. The full hierarchy:

Common Pitfalls and Fixes

Every failure mode in this procedure comes from one of three places: the console's power state, the controller connection, or the menu navigation. Here are the six that account for nearly every failed attempt — yes, six, because a list titled five that quietly runs long is very much in the spirit of this menu's numbering.

State errors: Rest Mode and the half-hold

Pitfall 1 — Rest Mode instead of a full shutdown. If the console was only resting, the power-button hold does not walk the beep sequence you expect; you end up waking the console or re-entering the OS. The fix is in step 2: choose Turn Off PS5 and wait for the light to go fully dark before you begin. Pitfall 2 — releasing on the first beep. The first beep fires immediately on press, and an itchy trigger finger reads it as the signal to let go. Releasing there just restarts the console normally, dropping you back at the login screen wondering what happened. Hold through to the second beep at around seven seconds.

Controller errors: wireless and the wrong cable

Pitfall 3 — expecting a wireless controller to work. Bluetooth is off in Safe Mode by design, so a wireless pad is inert there. Wire it. Pitfall 4 — using a charge-only cable. This is the sneaky one. Plenty of USB-C cables carry power but not data; plug one of those in and the DualSense will happily charge while never enumerating as a controller, leaving you convinced the console is frozen. Use the cable that came with the DualSense, or a known data cable, and confirm the pad responds after you press the PS button.

Navigation errors: wrong number, wrong child

Pitfall 5 — picking Option 5 from muscle memory. Old-guide reflex lands you on Restore Default Settings, which resets your system settings — network, video, audio, HDR — without touching your games. Not catastrophic, but a pointless detour and an evening of re-entering preferences you had dialled in months ago. Read the label; the cache lives at 6. Pitfall 6 — choosing Rebuild Database when you wanted the cache. Both live under Option 6, and it is easy to select the wrong child. It will not harm anything, but you have just signed up for a re-index that can run an hour on a full drive when you wanted a ten-second dusting. Pick the first child, Clear System Software Cache.

Troubleshooting Table: 11 Symptoms and Fixes

Cache-clearing is a precision instrument aimed at a narrow band of problems. The table below maps common PS5 symptoms to their likely cause, the correct first move, and where to escalate if the first move fails. Read it as a triage sheet: match the symptom, apply the first move, and only climb to the escalation column if the symptom survives.

When cache-clearing is the right tool

The top rows — interface stutter, store failures, stalled downloads, poisoned-cache launch failures — are the sweet spot. These are OS-scratch problems, and the light cache clear resolves them cleanly the majority of the time. If you are in this band, you are ten minutes from a fix and you do not need any of the heavier tools.

When it is emphatically not the right tool

The bottom rows are the trap. Persistent crashes under load, a fan that sounds like a hairdryer, thermal warnings — none of these are cache problems, and clearing the cache will burn your ten minutes and change nothing. Those are hardware and thermal issues that want dust removal, a repaste, or service. Diagnosing the wrong layer is how people end up clearing the cache five times in a week and concluding the console is haunted, when it is simply choked with dust.

Advanced: Version Strings, the August Beta, and Cadence

Once you have done this a couple of times, the procedure is muscle memory. The genuinely useful advanced knowledge is contextual: reading the firmware string correctly, understanding what Sony is about to change, and — most important — knowing how rarely you should actually be doing this.

Decoding the firmware version string

The PS5's version format is year-based, which is why it looks nothing like the PS4's. Take 26.05-13.60.00: the 26 is the year, 2026; the 05 is the release sequence within that year, i.e. the fifth; and 13.60.00 is the major, minor, and patch of the build. July 2026 alone carried two of these — 26.04-13.42.00 near the start of the month and 26.05-13.60.00 on the 23rd — which is a normal cadence for Sony's monthly performance-and-stability patches. Understanding this decode is the fastest way to spot a fraudulent guide: any tutorial referencing a bare Version 9.00 is quoting the PS4 scheme and has not been near a real PS5 menu.

The August 2026 beta and the Bluetooth twist

As of early August 2026, Sony is rolling out the next system-software update to beta testers, and two details are worth flagging. First, it turns the Enhance PSSR Image Quality setting on by default for PS5 Pro owners, extending the upgraded upscaler to any game that supported the original — the continuation of the story we covered in our PS5 Pro PSSR update piece. Second, and more relevant here, it adds a Bluetooth toggle: switch Bluetooth off and the console can no longer enter Rest Mode, and the HDMI link becomes unavailable. That is a useful mental bridge to Safe Mode, where Bluetooth is already off — which is the entire reason you wire the controller. If you are on the beta, none of this changes the cache procedure; just do not be startled by the new Bluetooth behaviour. The stable baseline this article is written against remains 26.05-13.60.00.

How often you should actually do this

Almost never on a schedule. The advice to clear your cache after every major update is cargo-cult maintenance; Sony's real cadence is the far less exciting do it when you have a problem. Clearing the cache on a healthy console accomplishes nothing except costing you a slow first boot. A defensible rule of thumb: clear reactively when a symptom from the troubleshooting table appears, and — if you are constitutionally incapable of leaving well enough alone — permit yourself one light clear a quarter. Do not rebuild the database monthly for sport. You will be living with this console for years yet, given there is no PS6 arriving on the timeline the rumour mill keeps promising, so learn the routine once and stop poking a working machine.

The Complete Maintenance Routine (Copy-Paste Checklist)

Everything above, distilled into a single reproducible routine you can keep next to the console. It is verified against the current stable firmware and written to be followed top to bottom without decisions — the decision-making is factored out into the escalation tree at the end.

The full Safe Mode sequence, start to finish

# PS5 SYSTEM SOFTWARE CACHE CLEAR - full routine
# Verified against firmware 26.05-13.60.00 (stable, Aug 2026)

PRE
  1. Quit all games and apps; confirm saves are synced.
  2. Power → Turn Off PS5. Wait for the light OFF and fan silent.
     (Do NOT use Rest Mode.)

ENTER SAFE MODE
  3. Press and HOLD the power button.
  4. BEEP #1 fires on press; keep holding.
  5. BEEP #2 at about 7 seconds → RELEASE.
  6. Wait for the Safe Mode screen.
  7. Connect the DualSense with a USB-C DATA cable.
  8. Press the PS button.

CLEAR CACHE
  9.  Select 6) Clear Cache and Rebuild Database.
  10. Select Clear System Software Cache.
  11. Confirm: OK.
  12. Wait 10 to 90 seconds; the console auto-restarts.

POST
  - First boot is slow (temp files rebuilding) - this is normal.
  - Thumbnails and store art repopulate over a few minutes.
  - Verify the original symptom is gone.
  - If not: re-enter Safe Mode → Rebuild Database (6, child b).
  - Still broken → Repair Console Storage (3), then hardware.

A quarterly self-check (optional)

If you like your maintenance scheduled rather than reactive, this is the entire justified list — anything more is fussing:

• Confirm you are on current firmware (Settings → System → System Software → Console Information).
• Clear the system software cache only if a real symptom is present — not on principle.
• Export save data to USB, or confirm cloud sync if you have PlayStation Plus.
• Blow the dust out of the intake vents; heat is a real performance enemy in a way that cache never is.
• Check free storage; a drive kept near full is more prone to the database drift that a rebuild fixes.

When to escalate past the cache

The single most valuable thing in this entire guide is knowing which tool matches which symptom, so you stop reaching for the cache clear as a universal remedy. This tree is that knowledge on one screen:

symptom?
  UI hitch / store fail / stuck download / load-failure
     → Clear System Software Cache      (6 → child a)
  missing games / wrong sort / corrupt-data warning
     → Rebuild Database                 (6 → child b)
  storage read/write errors
     → Repair Console Storage           (3)
  settings-only gremlins (keeps games)
     → Restore Default Settings         (5)
  crashes under load / thermal / fan noise
     → NOT a cache problem - service / hardware

That is the whole discipline. The cache clear is a ten-minute chore that resolves a specific, narrow class of software problems and precisely nothing else. Do it when the symptom fits, ignore the thumbnail farmers promising frame rates from a menu that cannot deliver them, navigate by label rather than by ordinal — it is Option 6 — and keep a data cable in the drawer for the day the wireless pad refuses to talk. For anything the cache cannot touch, the corroborating write-ups from Engadget and TechRadar, plus Sony's own Safe Mode reference, agree with every step above — the rare occasion the internet reaches consensus.