PS5 Cache 2026: 12 Steps, 15 Min, No Data Loss

There is a particular flavor of console folklore that treats 'clearing the cache' as a magic incantation — mutter it over a stuttering PS5 and the frame drops vanish, the downloads double, the ghost icons dissolve. Most of it is nonsense. Some of it is real. This guide is about telling the two apart, and then doing the real part correctly, on the firmware you are actually running in 2026.

Here is the short version, so you do not have to scroll: on a PlayStation 5, clearing the system cache is a Safe Mode operation. You boot into Safe Mode with a physical power-button ritual, you select the sixth option — 'Clear Cache and Rebuild Database' — and you choose the sub-option called 'Clear System Software Cache.' It does not delete your games, your saves, or your screenshots. It takes a couple of minutes. It is free, it ignores your PlayStation Plus status entirely, and Sony documents the whole thing on its own support site. That is the truth. Everything else in this article is the reason the short version keeps going wrong for people.

And it goes wrong for predictable reasons. A brief that landed on my desk this week confidently described the procedure as living in 'System Software Version 7.00,' upgraded to 'Version 9.00 firmware (2025).' Both numbers are fiction. The PS5 has never used that versioning scheme — those are PS4 numbers, lifted and pasted onto the wrong console. The machine in front of you is running something that looks like 26.04-13.42.00. We will get to why that matters. First, the part everyone skips: what a 'cache' even is on this box.

Related: PS4 vs Xbox One

What 'Cache' Actually Means on a PS5

Before you hold down any buttons, understand that the PS5 does not have a single, tidy thing called 'the cache' that you empty like a wastebasket. It has several kinds of temporary data, living in different places, cleared by different actions. Lumping them together is how people end up performing the wrong ritual and then declaring the whole exercise useless.

The three different things people call 'the cache'

First, there is the system software cache: temporary files the operating system writes while it runs — interface elements, thumbnails, transient state for suspended apps. This is the one the Safe Mode option targets, and the one this guide is mostly about. Second, there is the shader cache and per-game data: pre-compiled GPU shaders and app-specific scratch files that individual games generate to avoid recomputing work every launch. The PS5 manages most of this transparently; you do not get a per-game 'clear cache' button the way you do on a phone. Third, there is volatile memory — the contents of RAM and the residual state held while the console sits in Rest Mode. That one you clear simply by powering the machine all the way down, which is why the humble full restart fixes more problems than people expect.

Notice what is not on that list: there is no general-purpose web-browser cache to clear, because the PS5 has no full web browser the way the PS4 shipped one. If a guide tells you to dump your PS5 browser history to speed up games, close the tab. It is describing a different console.

Why Sony buried it in Safe Mode

On a phone or a PC you clear caches from a settings menu while the system runs. Sony chose not to expose the system cache that way. The reason is boring and correct: the files in question are in active use while the OS is booted, and deleting them from underneath a running system is how you corrupt state. So the option lives in Safe Mode — a stripped-down boot environment where the main operating system is not loaded, the caches are not pinned, and the console can safely rewrite them. That design choice is the single biggest source of confusion in this whole topic, because it means there is no button for this in the normal interface. People search Settings for twenty minutes, find nothing, and conclude the feature does not exist. It exists. It is just behind a door that only opens with the power button.

What clearing it fixes — and what it cannot touch

A system cache clear is genuinely useful for a specific class of problems: sluggish or unresponsive UI, apps that hang on launch, storefront pages that will not load, downloads that stall, and games that throw load-failure errors after a botched update. Epic Games lists exactly this procedure as the official first step for Rocket League 'load failure' errors, which tells you the category of bug it addresses: corrupted or stale temporary data that survives a normal reboot.

What it will not do is repair hardware. As Engadget put it plainly in its 2025 cache guide, clearing the cache is a short-term remedy for performance issues; it does nothing for hardware degradation. If your PS5 is thermal-throttling because the internal fan is choked with dust, or the disc drive is failing, or the SSD is dying, no amount of cache-clearing will save you. Keep that boundary in mind, because it is the difference between a two-minute fix and a week of chasing a symptom that was never software. If you are weighing whether the whole console is simply past its prime, our breakdown of the PS5 Pro versus the base PS5 in 2026 lays out what an actual hardware upgrade buys you.

Prerequisites and a Firmware Reality Check

This is a low-stakes procedure — nothing here voids a warranty or risks a brick if you follow the steps — but it has hard prerequisites that trip people up. You need the right firmware understanding, the right cable, and a backup you will probably never use. Skip the reality check and you will spend your afternoon hunting for a menu named nothing like what your source promised.

The firmware you are actually running

Check it yourself before you believe anyone, including me: Settings > System > System Software > Console Information. As of the July 1, 2026 update, a current PS5 reports its system software as 26.04-13.42.00 (the June build was 26.04-13.40.00; these are the routine 'improved system performance and stability' updates Sony ships almost monthly). That string is not decoration — it is how you sanity-check every other claim in a tutorial.

26.04-13.42.00
26  -> year branch (26 = 2026)
04  -> SDK/branch month (April line)
13  -> major build
42  -> minor build
00  -> patch / hotfix

There is NO 'Version 7.00' and NO 'Version 9.00' on PS5.
Those are PS4 firmware numbers. If a guide cites them,
it was written for the wrong console (or by a bot).

Why hammer this? Because the brief for this very article insisted the cache option was 'introduced in System Software Version 7.00' and lives in 'Version 9.00 firmware.' The 'Clear Cache and Rebuild Database' option in fact arrived in a late-2023 system software update — the same window Sony added 8TB M.2 SSD support and Dolby Atmos — not in any 7.00 release, because no such PS5 release exists. You can cross-check any build against Sony's published system-software notes. If your console predates that update, the sub-option simply will not be there, and the fix is to update first, not to keep scrolling.

Hardware: one cable, and the port situation

You need exactly one piece of hardware you might not have to hand: a USB data cable. In Safe Mode the PS5 disables Bluetooth, so a wireless DualSense is a paperweight until you wire it in. The controller end is USB-C; the console end plugs into any of the PS5's USB ports (the original model gives you a USB-A and a USB-C on the front plus two USB-A on the back; the Slim and Pro moved to two USB-C on the front). Any cable that carries data — not a charge-only cable — will work. This is the single most common failure point in the entire process, and it has nothing to do with the cache: people reach Safe Mode, mash a dead wireless controller, and assume the console has frozen.

Related: ROG Ally X vs

If you are the sort of person who keeps the PS5 wired into a capture rig, you already own three cables that will do. If not, our PS5 capture-card walkthrough covers the same USB-C reality from the streaming side.

Back up first — the belt-and-suspenders step

Clearing the system cache does not delete saves. Sony says so, Engadget says so, and it is true. But you are one menu away from options that do wipe things, and a database rebuild does touch the content index, so the professional move is a backup you will almost certainly never restore from. Sync saves to the cloud (Settings > Saved Data and Game/App Settings) if you have PlayStation Plus, or copy them to a USB drive formatted as FAT32 or exFAT — the two filesystems the PS5 will read. Here is how to format that drive properly on each desktop OS:

# Windows (diskpart) - exFAT. Replace X with YOUR disk number.
diskpart
  list disk
  select disk X
  clean
  create partition primary
  format fs=exfat quick label=PS5BACKUP
  assign
  exit

# macOS (Terminal) - exFAT. Replace diskN with your device.
diskutil eraseDisk ExFAT PS5BACKUP MBRFormat /dev/diskN

# Linux - FAT32 for drives up to 32GB, exFAT for larger.
sudo mkfs.vfat -F 32 -n PS5BACKUP /dev/sdX1   # FAT32
sudo mkfs.exfat        -n PS5BACKUP /dev/sdX1   # exFAT

Double-check the disk number before you run any of these — clean and eraseDisk and mkfs do exactly what they say to whatever device you point them at, and pointing them at the wrong one is the actual dangerous move in this entire article. The cache clear is safe. The formatting command is where you can hurt yourself.

Two Methods: The Soft Flush vs. The Safe Mode Ritual

There are two tiers to this, and most people jump straight to the dramatic one when the boring one would have done the job. Try them in order. The first costs you sixty seconds; the second costs you a trip into Safe Mode.

Method A: the soft flush (power-down and unplug)

The lightest possible cache clear is a genuine, complete shutdown — not Rest Mode, which is the trap. Rest Mode keeps the RAM powered, the suspended game resident, and the volatile state warm; it is a nap, not a reboot. A real power-off drains that memory. Hold the power button, choose Turn Off PS5, wait for the indicator light to go fully dark, then — for good measure — pull the power cable from the wall for thirty to sixty seconds. That last step lets residual charge bleed out of the capacitors and guarantees the volatile memory is truly gone.

SOFT FLUSH (clears volatile memory only, ~60 seconds)
  1. Power button -> Turn Off PS5      (NOT Rest Mode)
  2. Wait for the light to stop pulsing and go black
  3. Unplug the AC cable from the wall
  4. Wait 30-60 seconds
  5. Replug, boot normally, re-test the symptom

If the stutter / hang / slow UI is gone -> STOP. You are done.

An astonishing share of 'my PS5 is slow' complaints evaporate right here, because the actual problem was a memory-resident glitch that a full power cycle clears. If it comes back in five minutes, escalate. If it does not, you just saved yourself the Safe Mode dance.

Method B: the Safe Mode ritual (system software cache)

When the soft flush does not hold — the UI is still sludge, an app still hangs, a store page still refuses to render — you go into Safe Mode and clear the system software cache directly. This is the procedure the rest of this guide details step by step. It reaches temporary files the soft flush never touches, because those files live on the SSD, not in RAM, and they persist across a normal reboot. This is the 'real' cache clear people mean when they say 'clear the PS5 cache.'

Which one you actually need

Rule of thumb: transient weirdness after a long uptime or a Rest Mode marathon points to the soft flush. Persistent misbehavior that survives reboots, especially right after a big game patch, points to the Safe Mode cache clear. Ghost icons, corrupted downloads, and a content library that shows the wrong thing point to the heavier 'Rebuild Database' sub-option, covered later. Matching the method to the symptom is the whole game; doing a database rebuild for a problem a sixty-second unplug would have fixed is how people convince themselves this stuff is voodoo.

Entering Safe Mode: The Two-Beep Ritual

Safe Mode has a reputation for being finicky, and it is, but only because the entry method is a timing exercise with no on-screen feedback until you get it right. There is no menu path. As of 2026 there is still no toggle in Settings that boots you into Safe Mode — not on PS5, and contrary to a persistent myth, not on the PS4 either. Both consoles require the physical button. Anyone who tells you the PS5 lost a Settings-based Safe Mode that the PS4 had is misremembering; neither had one.

Powering down completely (not Rest Mode)

Start from a true power-off. If the console is in Rest Mode, wake it, then hold the power button and select Turn Off PS5, and wait until the light stops pulsing and the box is fully dark. Safe Mode will not engage cleanly from Rest Mode, and starting from a warm state is how people get the timing wrong on the beeps. Cold, dark, silent — then begin.

Related: Switch OLED vs Switch

The beep timing that everyone fumbles

Here is the ritual, to the second. You press and hold the power button. You hear one beep the instant you press — that is just the console powering on. You keep holding. Roughly seven seconds later you hear a second beep. That second beep is your cue to release. Let go on the first beep and you have simply turned the console on normally; you will boot to the home screen wondering what went wrong. The gap between the two beeps is the entire trick.

THE TWO-BEEP HOLD
  t = 0.0s   press and HOLD the power button
             *BEEP*        (console is powering on - ignore this one)
  t ~ 1-6s   keep holding, do not release
  t ~ 7.0s   *BEEP*        (SECOND beep: RELEASE NOW)
             screen shows:
             'Connect the controller using a USB cable
              and then press the PS button.'

If you released too early, no harm done — the console just boots normally. Power it off and try again. There is no penalty for a botched attempt except the ten seconds it takes to retry.

Connecting the controller (Bluetooth is dead in here)

Once that prompt appears, wireless is off. Plug the DualSense into the console with your USB data cable and press the PS button once to register it. Now — and only now — the Safe Mode menu responds to input. This is the exact spot where half of all 'it froze' reports happen: the screen is waiting for a wired controller, and the user is jabbing a disconnected one. Wire it, press PS, and the eight-option menu comes alive:

PS5 SAFE MODE   (firmware 26.04-13.42.00, 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    (THIS ONE)
  7. Reset PS5
  8. Reset PS5 (Reinstall System Software)
------------------------------------------------
Options 7 and 8 WIPE the console. Do not fat-finger them.

Eight options, exactly as the official PlayStation support site lists them in 2026. The cache lives at number six. Numbers seven and eight are the nuclear options — factory reset and a full OS reinstall — and they sit one and two rows below the thing you actually want, which is a menu-design decision I have opinions about but no power over. Move deliberately.

Clearing the Cache in 12 Steps

This is the full procedure, start to finish, with the rationale for every step — because a step you understand is a step you will not skip. It assumes you have read the prerequisites: current firmware, a USB data cable, saves backed up. Budget about fifteen minutes end to end for a plain cache clear; a full database rebuild can run far longer, which we will get to.

The 12 steps, with the reason for each

1. Save and fully quit every game. Rationale: the system cache includes state for suspended apps; closing them first means you are not clearing data mid-write, which is the only way this otherwise-safe operation can lose you progress.
2. Power the PS5 all the way off — not Rest Mode. Rationale: Safe Mode will not engage cleanly from a suspended state, and a true shutdown also clears volatile memory, so you get the soft flush for free.
3. Optional: unplug the AC cable for 30-60 seconds. Rationale: drains residual charge and guarantees RAM is empty. If the symptom disappears when you reboot, you never needed Safe Mode at all — stop here.
4. Locate a USB data cable. Rationale: Bluetooth is disabled in Safe Mode; without a wired controller you cannot select a single menu item. The DualSense end is USB-C.
5. Confirm saves are backed up (cloud or exFAT/FAT32 USB). Rationale: the cache clear will not touch saves, but you are about to be one row away from the reset options, and a rebuild reindexes your library. Belt and suspenders.
6. Press and hold the power button until the second beep (about 7 seconds), then release. Rationale: the first beep is power-on; the second is the Safe Mode cue. Releasing early just boots you normally.
7. Plug the controller in and press the PS button. Rationale: this registers the wired pad. The menu ignores input until you do this — the number-one cause of false 'it froze' reports.
8. Select option 6, 'Clear Cache and Rebuild Database.' Rationale: it is the sixth of eight items. Do not confuse it with options 7 and 8, which wipe the console.
9. Choose the sub-option 'Clear System Software Cache.' Rationale: this is the light-touch action — it deletes system temporary files without re-indexing the entire drive, so it finishes in a minute or two.
10. Confirm, and do not interrupt the process. Rationale: the console may restart on its own during the operation. That is designed behavior; pulling the plug mid-clear is how you corrupt the very database you are trying to clean.
11. Let the console reboot to the home screen. Rationale: a normal boot confirms the operation completed. If a rebuild reshuffled your home-screen tiles, that is cosmetic — reorder them at your leisure.
12. Re-test the symptom; if it persists, run the heavier 'Rebuild Database' sub-option. Rationale: escalation. Rebuild Database scans the whole drive and reconstructs the content index, which is what actually kills ghost icons and library corruption.

What you should see on screen

When you pick the sub-option, the console throws up a progress indicator and an explicit warning not to power off. Expect something along these lines — a percentage counter that may pause at certain values before jumping ahead, which is normal and not a hang:

> Clear Cache and Rebuild Database
  > Clear System Software Cache

  Clearing the system software cache.
  Do not turn off the PS5.

  [##########..........]  51%

  The PS5 will restart automatically when finished.

The sub-menu you are choosing from looks like this — two options, escalating in weight and time cost:

6. Clear Cache and Rebuild Database
   |
   +-- Clear System Software Cache   (light: wipes OS temp files, ~1-2 min)
   +-- Rebuild Database              (heavy: re-indexes the whole SSD)

How long it takes, and when to worry

A pure 'Clear System Software Cache' is quick — a minute or two, plus the reboot. If you escalate to 'Rebuild Database,' the clock depends entirely on how much is on your drive: a lightly loaded console rebuilds in a few minutes, while a stuffed 8TB SSD can take the better part of an hour. A progress bar that sits at a single percentage for several minutes on a large, full drive is not frozen; it is working. The rule is the same either way: do not interrupt it. GuideRealm's 2025 walkthrough makes the same point, because it is the one mistake that turns a maintenance task into a repair job.

Clear System Software Cache vs. Rebuild Database

Inside option 6 you are handed two buttons, and the internet cannot keep them straight. They are not the same operation, they do not take the same amount of time, and they fix different problems. Getting this distinction right is what separates a targeted fix from cargo-cult button-mashing.

What 'Clear System Software Cache' does

This is the scalpel. It deletes the operating system's temporary working files — the transient data behind UI sluggishness, hung app launches, stalled downloads, and the load-failure errors that crop up after a messy patch. It does not read your entire library, so it is fast, and it is the correct first choice for performance complaints. It leaves the content database itself alone; it is only clearing the scratch pad the OS scribbles on while it runs.

Related: PS5 vs Xbox Series

What 'Rebuild Database' does (and why it costs more)

This is the sledgehammer. Rebuild Database scans every item on the drive and constructs a fresh index of all your content — games, apps, saves, media. It is the fix for structural problems: a game icon that lingers on the home screen after you deleted the game, a library that displays the wrong metadata, content that will not appear at all. Because it walks the whole SSD, it is the slow one — minutes on a light install, up to roughly an hour on a packed 8TB drive. Sony frames it as a maintenance tool for exactly these 'the database is confused' situations, and it is safe to run, but there is no reason to sit through it when a cache clear would have done.

The 'Option 2' myth, and where it comes from

You will find tutorials — a 2026 TikTok making the rounds is the current culprit — claiming Rebuild Database is 'Option 2.' It is not. On the PS5, option 2 in Safe Mode is Change Video Output. Rebuild Database is not a top-level Safe Mode option at all; it is a sub-option nested inside option 6, right next to Clear System Software Cache. The confusion is a fossil from the PS4 and older PS5 firmware layouts, where the menu was numbered differently, dragged forward into 2026 by people copying each other instead of the console. Trust the screen in front of you: eight options at the top level, and the rebuild lives two levels deep under number six. If a guide's numbers do not match your screen, the guide is wrong, not your PS5.

This is the same failure mode that plagues cross-generation guides generally — instructions written for one box, pasted onto another. It is why our PS4-versus-Xbox-One retrospective still draws traffic from people troubleshooting hardware two generations old: the menus drift, the folklore does not.

Five Ways People Screw This Up

Every one of these lands in support forums weekly. None of them is exotic. They are the same handful of mistakes, and knowing them in advance is worth more than any amount of re-reading the steps.

The controller and power-button mistakes

Pitfall 1 — Using Rest Mode instead of a full shutdown. Rest Mode is a nap; it keeps the cache warm and Safe Mode will not engage properly. Fix: hold the power button, choose Turn Off PS5, and wait for the light to go fully dark before you start the beep hold.

Pitfall 2 — Releasing on the first beep. The first beep is just power-on. Let go there and you boot normally, then wonder why Safe Mode never appeared. Fix: keep holding through the first beep and release only on the second, about seven seconds in.

Pitfall 3 — A wireless controller that will not respond. Safe Mode kills Bluetooth. A DualSense that is not wired in does nothing, and the frozen-looking menu is simply waiting. Fix: connect the pad with a USB data cable and press the PS button once.

The wrong-menu mistakes

Pitfall 4 — Confusing the cache clear with the reset options. Options 7 and 8 — Reset PS5 and Reset PS5 (Reinstall System Software) — erase the console. They sit just below the thing you want. Fix: the cache clear is option 6, and within it, the first sub-option. Read before you press.

Pitfall 5 — Doing a full Rebuild Database when you only needed a cache clear. People pick the heavier sub-option 'to be thorough,' then sit through a forty-minute reindex for a problem a one-minute cache clear would have solved. Fix: start with Clear System Software Cache; only escalate to Rebuild Database if the symptom is structural, like a ghost icon.

The version and expectation mistakes

Pitfall 6 — Chasing a firmware version that does not exist. Guides that cite 'Version 7.00' or 'Version 9.00' are describing a PS4, or nothing. Your PS5 reports something like 26.04-13.42.00. If your Safe Mode has no 'Clear System Software Cache' sub-option, you are on genuinely old firmware — update via option 4 first, then return.

Related: PC vs Console Gaming

Pitfall 7 — Expecting the cache clear to fix hardware. Frame drops that return within minutes, fan noise like a jet engine, disc-read failures — that is hardware, and no cache operation touches it. Fix: clean the vents, check the disc drive, and accept that some problems are physical. Chasing them in Safe Mode is how a week disappears.

Troubleshooting: When It Fixes Nothing

Sometimes you do everything right and the symptom shrugs. Here is the diagnostic table, followed by the two cases worth spelling out: the officially documented one, and the one where the cache was never the culprit.

The symptom-to-fix table

The Rocket League case, straight from Epic

If you want proof this procedure is a legitimate, vendor-endorsed fix and not just forum superstition, look at Epic Games' own support documentation. For Rocket League 'load failure' errors on PS5, Epic's officially recommended first step is to clear the console cache via Safe Mode — the exact procedure in this guide. When the studio that made the game tells you to clear the platform cache, you can retire the debate about whether it 'really does anything.' It does, for this class of bug.

When it was never the cache

The most important troubleshooting skill here is knowing when to stop. If a cache clear and a database rebuild both leave your symptom untouched, the odds tilt hard toward hardware or toward a specific corrupted install. A single game misbehaving? Delete and reinstall that title; you do not need to nuke system state for one bad app. Whole-console heat and noise? That is thermals. Downloads crawling regardless of cache state? That may be your network, not your PS5 — our PS Remote Play setup guide walks through the same connectivity diagnostics that apply to a sluggish storefront. The cache clear is a first move, not a last resort, and treating it as a cure-all is how people end up performing it weekly for no benefit.

Advanced: Shader Caches, Cadence, and the Home-Screen Myth

For the people who want to understand the machine rather than just poke it: here is the nuance the step-by-step guides skip. This is also where I put the claims I could not fully verify, clearly labeled as such, because pretending otherwise is how myths get minted.

The home-screen-reset claim, examined

You will read — often, and stated as fact — that clearing the cache 'resets your home screen layout' and forces you to reorganize your game icons every time. The origin of this is anecdotal: a Reddit user in the Starfield community reported it in 2025, and it propagated. Here is the precise truth. Engadget's guide does not mention any layout reset, and neither does Sony's documentation for the 'Clear System Software Cache' sub-option. What genuinely can reshuffle your home-screen tiles is a full Rebuild Database, because reindexing the content can change the order. So the accurate statement is: a plain cache clear should leave your layout alone; a database rebuild might not. If your icons scrambled after 'just' a cache clear, you almost certainly ran the rebuild sub-option. Precision matters, and this is a case where the popular version of the fact is attached to the wrong button.

How often you should actually do this

Sony's guidance amounts to 'when you have a problem,' and that is the right cadence. There is a widespread belief that you should clear the cache after every major game update as preventive hygiene — after a big Final Fantasy XVI patch, say, or whatever GTA VI ships as its day-one download. That is overkill for a healthy console. The system manages its own caches perfectly well in normal operation; the manual clear is a remedy for when something has gone wrong, not a scheduled ritual. The one defensible exception is if you have a specific, repeating problem that a particular game's updates keep triggering — then, sure, clear it after that game patches. Otherwise you are performing maintenance the console does not need and resetting state it was using correctly.

Shader caches and the per-game question

People coming from PC ask where the shader cache clear is. On the PS5 there is no user-facing button to purge a single game's compiled shaders the way you can wipe a driver shader cache on a desktop. The system handles shader data as part of each title's managed storage, and the closest user-level action is deleting and reinstalling the game, which forces everything — shaders and app cache included — to regenerate clean. That is heavier than a system cache clear and should be reserved for a single title that is genuinely broken. For a console-wide performance question the system cache clear is the right altitude; for one corrupted game, a reinstall is. Matching the tool to the scope is, once again, the entire discipline.

The Complete PS5 Cache Runbook

Here is everything above, compressed into a single reference you can keep open on a phone while you work. Copy it, print it, tape it to the console — whatever gets you through the procedure without second-guessing which beep to release on. This is the complete working configuration for a 2026 PS5 on firmware 26.04.

The one-screen runbook

PS5 CACHE-CLEAR RUNBOOK   (firmware 26.04-13.42.00, July 2026)
=============================================================
PRE-FLIGHT
  [ ] Settings > System > System Software > Console Information
      confirm version reads 26.0x-xx   (NOT '7.00' / '9.00')
  [ ] Sync saves: Settings > Saved Data and Game/App Settings
      (cloud with PS Plus, or copy to exFAT/FAT32 USB)
  [ ] Have a USB DATA cable ready  (DualSense end = USB-C)

PROCEDURE  (~15 min for a plain cache clear)
  1.  Fully power off  (Power button > Turn Off PS5). NOT Rest Mode.
  2.  Optional soft flush: unplug AC 30-60s, replug, re-test first.
  3.  Hold Power until the SECOND beep (~7s). Release.
  4.  Wire the controller. Press the PS button.
  5.  Option 6  ->  Clear Cache and Rebuild Database.
  6.  Sub-option 1  ->  Clear System Software Cache. Confirm.
  7.  DO NOT interrupt. Let it reboot on its own.

ESCALATION  (only if the symptom survives)
  8.  Repeat, choose Sub-option 2 -> Rebuild Database
      (minutes on a light drive, up to ~1 hour on a full 8TB SSD).
  9.  Still broken? Option 3 -> Repair Console Storage.
  10. Boot-loop / black screen? Option 2 -> Change Video Output.

DO-NOT-TOUCH
  Option 7  Reset PS5                       -> WIPES the console
  Option 8  Reset PS5 (Reinstall Software)  -> WIPES + reinstalls OS

POST-FLIGHT
  [ ] Console boots to the home screen normally
  [ ] Original symptom (lag / ghost icon / load-fail) is gone
  [ ] Re-order home-screen tiles if a rebuild reshuffled them
=============================================================
COST: free. PS Plus: not required. Data lost: none (cache clear).

What to do when the runbook does not work

If you have run the cache clear, escalated to a rebuild, and repaired console storage, and the symptom is still there, you have conclusively ruled out the cache. That is useful information, not a failure. It means the problem is a specific corrupted install (delete and reinstall that one title) or hardware (thermals, the disc drive, or the SSD). Stop clearing caches at that point; you are done extracting value from this particular tool.

The one-sentence version

Power off fully, hold the button to the second beep, wire the controller, pick option 6 then 'Clear System Software Cache,' and do not interrupt it — that is the entire fix, it is free, it keeps your saves, and it lives on firmware named 26.04-something, not 'Version 9.00.' Everything else in this article exists because that one sentence keeps getting mangled in translation.