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

Somewhere in a support thread, right now, a stranger is telling you to clear your PS5 cache. They are half right. Clearing the cache is a genuine procedure, it is free, it deletes none of your data, and it occasionally fixes exactly the thing that is wrong with your console. It is also prescribed like a folk remedy for problems it cannot possibly touch, described with menu numbers that do not match your screen, and wrapped in at least three pieces of received wisdom that are simply false.

This is the version that is technically correct. It covers the standard PS5, the Digital Edition, the 2023 Slim, and the PS5 Pro, all of which behave identically here. It uses the current 2026 firmware and the current Safe Mode layout, and it tells you at each step why you are doing the thing, because a procedure you do not understand is a procedure you will eventually do wrong. Budget fifteen minutes. Expect to lose nothing.

What the Cache Actually Is

Before you power anything down, it is worth knowing what you are about to delete, because the word doing the heavy lifting here is dangerously vague.

The word cache is doing a lot of work

On a PC, cache is a specific thing you can point at: a folder, a file, a browser store you can open and inspect. On the PS5 it is an umbrella term for transient data the operating system writes to keep the interface fast and the games loading quickly. Sony documents almost none of it. There is no file browser, no storage inspector that itemises it, no way to see how large it has grown. You are trusting a sealed appliance to know which of its own scratch files are disposable, and then to dispose of them on command. That is the entire transaction.

The official menu item is worded with unusual care. It does not say Clear Cache. It says Clear System Software Cache. The phrase system software means the operating system, not your library. This is the console equivalent of clearing a browser cache while leaving your bookmarks, passwords, and history untouched, except you never get to see the contents and you have to reboot into a recovery mode to do it.

What Sony actually stores, and what it will not confirm

Sony has never published a manifest of the PS5 cache. What we can infer from behaviour is that it holds regenerable transient data: decompressed asset staging, shader and pipeline caches, download scratch files, the thumbnail and tile art the home screen paints, temporary system state left behind by the last few sessions. None of that is precious. All of it can be rebuilt from the game data and the OS image that remain on the drive. That is precisely why clearing it is safe.

What it is emphatically not: your saved games, your screenshots and clips, your installed titles, your account, your trophies, your settings, or your friends list. The Clear System Software Cache option touches none of those. Later in this guide you will meet its heavier sibling, Rebuild Database, which is also non-destructive but does far more work. Only a genuine Reset wipes the console, and that is a different menu item entirely, several rows away, which we will flag so you never fat-finger it.

Why clearing it is closer to a reboot than a purge

Here is the deflationary truth that the support threads bury: clearing the system software cache is much closer to a supervised reboot than to a hard delete. The OS discards temp files it can regenerate, then restarts and regenerates them. Your first boot afterward is slightly slower because the console is repainting caches it just threw away. Then it is normal again. If your mental model is a hard drive being scoured, correct it. The correct model is a cluttered desk being swept clean so the OS can lay its papers out fresh. Powerful for a narrow class of bug. Useless for anything mechanical.

Prerequisites and Hardware

This is a hardware procedure gated behind a physical button, so the prerequisites are unusually literal. You cannot do any of this from the couch with a wireless pad, and there is no app, no setting, and no purchase that changes that.

Firmware: you are on 26.04-xx whether you look or not

As of early July 2026, the current PS5 system software is 26.04-13.42.00. Sony ships small performance-and-stability updates roughly monthly, so by the time you read this your console may report a version a hair higher; that is expected and changes nothing about the steps below. You can confirm yours under Settings, System, System Software, Console Information, and cross-check against the official PlayStation system software information page.

The version string is not random. It parses like this:

PS5 system software version format

  26 . 04 - 13 . 42 . 00
  |    |    |    |    |
  |    |    |    |    +--  patch     (small fixes)
  |    |    |    +-------  minor      (feature-level)
  |    |    +-----------   major      (branch build)
  |    +----------------   platform   (internal train)
  +---------------------   year       (20YY -> 26 = 2026)

Current stable  : 26.04-13.42.00   (early July 2026)
Previous month  : 26.04-13.40.00   (June 2026)
Cadence         : ~monthly 'performance and stability'

A myth to kill before it spreads: you will see people cite PS5 System Software Version 7.00 or Version 9.00 as though those are recent. They are not PS5 numbers at all. Those are PS4 firmware versions. The PS5 has used the 20YY-prefixed format since launch and has never shipped a plain 7.00 or 9.00. If a guide quotes you a two-digit PS5 firmware, distrust the rest of it. You do not need any specific version to clear the cache; Safe Mode has existed since day one, and the Clear System Software Cache sub-option arrived in a late-2023 update and has been present ever since.

The hardware you actually need, which is mostly a cable

The full kit is short, and one item on it catches almost everybody out:

• A PS5. Standard, Digital Edition, Slim, or PS5 Pro; the Safe Mode path is identical on all four, and third-party step-by-step walkthroughs such as the PC Guide PS5 and PS5 Pro walkthrough confirm the Pro uses the same sequence.
• A DualSense or DualSense Edge controller.
• A USB cable that carries data, not merely power. The controller end is USB-C. The console end is USB-A or USB-C depending on which front port you use.

The cable is the whole game. In Safe Mode, the PS5 disables Bluetooth. A wireless controller does absolutely nothing at the Safe Mode menu; it will not wake, will not bind, will not move the cursor. You have to wire it in and press the PS button to register it as player one. And it must be a data cable: a charge-only cable will light the controller and fool you into thinking it is connected while the menu ignores every input. If you own the flat white cable that shipped in the PS5 box, use that; it is data-capable.

You do not need PlayStation Plus. You do not need to be signed in. You do not need an internet connection for the cache clear itself, though Safe Mode's update option obviously needs the network. And you do not need to buy anything. If you have wandered past a listing for a twenty-to-fifty-dollar PS5 optimiser or booster app, understand two things: the cache clear it is imitating is a free built-in function, and you could not sideload such an app onto a locked console even if you wanted to. While you have the console open and the cables out, it is a fine moment to check the rest of your setup, from your PS5 capture-card and HDMI chain to your storage headroom.

Pre-flight checklist

Run this before you touch the power button. Skipping it is how five-minute jobs become twenty-minute ones:

PRE-FLIGHT  (tick all before starting)

[ ] Controller charged enough to bind        (cable powers it, but check)
[ ] DATA-capable USB-C cable located         (not charge-only)
[ ] Console fully accessible from the front   (front USB port reachable)
[ ] No active downloads/installs mid-flight   (let them finish first)
[ ] TV input/volume set so you can hear beeps  (you navigate by beep #2)
[ ] 15 minutes free, and patience for a reboot (do NOT rush a flush)
[ ] Know your goal: light 'Clear Cache', NOT 'Rebuild', NOT 'Reset'

Data at risk : NONE for Clear System Software Cache
Data at risk : NONE for Rebuild Database
Data at risk : EVERYTHING for Reset PS5 (option 7) -- do not select it

The Option-6-Not-5 Problem

If you only remember one thing from this article, make it this: the menu number you were told is probably wrong, and it does not matter, because you should be reading the label instead.

The full Safe Mode menu, numbered

On current firmware, the PS5 Safe Mode menu presents eight options in this exact order, per Sony's own official Safe Mode support page:

PS5 SAFE MODE  (firmware 26.04-xx, 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 one
       |
       +-- Clear System Software Cache     (light: OS temp files)
       +-- Rebuild Database                (heavy: re-index the SSD)
  7  Reset PS5                             (WIPES the console)
  8  Reset PS5 (Reinstall System Software) (WIPES + reflashes OS)

Rule: trust the LABEL 'Clear Cache and Rebuild Database',
      not the digit in front of it.

So on a 2026 console it is Option 6. Read the label, count nothing, and you will never be wrong.

Why half the internet says Option 5

Because half the internet is not lying; it is quoting an older or a different layout. The variable row is number 3, Repair Console Storage. It does not appear on every configuration or every firmware branch. When it is absent, every row beneath it slides up by one, and Clear Cache and Rebuild Database lands at position 5. That is why reputable guides disagree: some counted a menu with Repair Console Storage present, some counted one without it. Engadget's widely cited walkthrough sidesteps the trap entirely by not numbering the option at all and simply instructing you to select Clear Cache and Rebuild Database by name. That is the correct habit. Menu numbers on a console that updates monthly are a promise nobody at Sony made to you.

Ignore the number, read the label

There is a second, subtler confusion worth defusing here, because it appears in otherwise careful writeups. Rebuild Database is not a top-level menu option, and it is certainly not Option 2. Option 2 is Change Video Output, the tool you use when your TV shows a black screen because a resolution handshake went sideways. Rebuild Database lives one level down, inside Clear Cache and Rebuild Database, as one of its two sub-options. If a guide tells you to select Rebuild Database from the main Safe Mode list, it has flattened a two-level menu into one and you should assume it got other things wrong too. Open the labelled row, then choose the sub-option. That is the shape of the thing.

The 12-Step Procedure

Here is the whole job, twelve steps, each with the reason attached so you can tell a normal pause from a real fault. Read all twelve once before you start; several of them are timing-sensitive and you do not want to be reading step 4 while you are supposed to be listening for beep two.

Steps 1 to 4: power down and into Safe Mode

1. Quit everything and fully power the console off. Close your game, then either hold the power button until the console beeps and shuts down, or open the control centre, choose Power, and select Turn Off PS5. Rationale: the cache clear runs from a recovery boot path, which means the OS has to be genuinely off, not merely idle. This is not a background task you trigger from the dashboard.
2. Wait for the power indicator to go completely dark. Give it ten seconds after the light stops. Rationale: a light that is still pulsing or glowing means Rest Mode, which is a suspended-state limbo, not off. Trying to enter Safe Mode from Rest Mode either wakes the console normally or misfires. Dark light, or nothing happens right.
3. Press and hold the physical power button, and keep holding. Do not tap it. Hold it down and do not let go yet. Rationale: there is no Settings menu that opens Safe Mode. None. This is true of the PS5 and it was equally true of the PS4, so ignore any guide that frames the missing Settings shortcut as a PS5 quirk. Safe Mode is a firmware-level boot path reachable only by holding this button.
4. Listen for two beeps. Release on the SECOND one. You will hear a beep the instant you press, and a second beep roughly seven seconds later. Let go of the button on that second beep. Rationale: releasing on the first beep boots the console normally into your dashboard and you will have to start over. The second beep is the actual Safe Mode trigger. Sony documents the interval as about seven seconds; count it by feel.

The timing is the part people fumble, so here it is as a sequence you can rehearse in your head:

SAFE MODE ENTRY -- power button timing

  t=0.0s   press and HOLD
  t=0.0s   [BEEP #1]  <- normal-boot beep; keep holding, do NOT release
  ...      (hold through the silence, ~7 seconds)
  t=7.0s   [BEEP #2]  <- Safe Mode beep; RELEASE now
  t=7.5s   screen switches to the Safe Mode background

  Released on BEEP #1  -> normal boot        (wrong; power off, retry)
  Released on BEEP #2  -> Safe Mode menu      (correct)

Steps 5 to 8: wire the pad and navigate

5. Connect the DualSense to the console with the USB cable. USB-C into the controller, the other end into a front USB port on the console. Rationale: Bluetooth is off in Safe Mode. Until this cable is in, your controller is furniture.
6. Press the PS button on the controller. One press. Rationale: the cable supplies power, but the PS button is what registers the pad as player one and hands you the cursor. No press, no control.
7. Find Clear Cache and Rebuild Database in the list. It is Option 6 on current firmware, possibly 5 on an older layout without Repair Console Storage. Rationale: you were warned about the number; you are reading the label. Do not select Restore Default Settings above it or Reset PS5 below it.
8. Select it. Press X on the row. Rationale: this opens the two-item sub-menu. You have not changed anything yet; you have merely opened a drawer.

Steps 9 to 12: clear, confirm, and let it reboot

9. Choose Clear System Software Cache. Not Rebuild Database. Rationale: this is the light, fast, OS-temp-file flush that Sony recommends for, in its exact words, system feature issues or performance drops. Rebuild Database is the heavy re-index you do not need for a first attempt. If you pick the wrong one you will not damage anything, but you will be waiting a great deal longer.
10. Confirm with OK. A single confirmation appears; select OK. Rationale: there is no second are-you-sure. One OK and the flush begins. Engadget's guide notes the same single-confirmation flow: select Clear System Software Cache, confirm with OK, and the process starts.
11. Let the console clear and reboot. It may restart more than once. Do not pull the power. Rationale: the flush writes and reboots; interrupting a write mid-flush is one of the few ways to cause the exact corruption this procedure exists to prevent. Sit on your hands.
12. Wait out a slightly longer first boot. The dashboard may take longer than usual to paint, and the first game you open may load a beat slower. Rationale: the OS is regenerating the temp files and shader caches it just discarded. This happens once. After that first slow boot, everything is normal, and if the cache was your problem, it is now gone.

Expected On-Screen Output

A console has no terminal, so expected output here means the exact sequence of screens and the rough time each one takes. If what you see matches this, you are fine. If it stalls somewhere off this map for many minutes, jump to the troubleshooting table.

The Safe Mode boot screen

After you release on beep two and the display resyncs, you should see a plain dark background with the numbered list. It is deliberately ugly; Safe Mode is a recovery environment and looks nothing like your dashboard. Expect roughly this:

[ screen after releasing on BEEP #2 ]

  Safe Mode
  Connect the controller using the USB cable,
  then press the PS button.

  ( after you wire the pad and press PS )

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

The clear-cache confirmation and progress

Select Option 6, then Clear System Software Cache, then confirm. The sequence and timing look like this. Note that the light cache clear generally does not show a long progress bar the way a Rebuild does; it flushes and reboots, and the visible evidence is the reboot itself:

[ clear system software cache -- expected sequence ]

  Clear Cache and Rebuild Database
    > Clear System Software Cache
    > Rebuild Database

  select: Clear System Software Cache

  Confirm
    Clear the system software cache?
    [ OK ]   [ Cancel ]

  select: OK

  --> screen goes dark, console reboots
  --> (may reboot more than once)         ~30-90 seconds
  --> PlayStation logo, then Home screen
  --> first boot slightly slower than usual (normal)

  TOTAL, entry to Home:  ~2-4 minutes
  Data deleted:          none

The return to Home

You land back on your normal dashboard. Your games, saves, screenshots, layout, and account are all present and unchanged. If you specifically ran Clear System Software Cache and nothing else, your home screen tiles are in the same order you left them. Anyone who told you the cache clear rearranges your home screen has confused it with Rebuild Database, which is the next section's whole point.

Clear Cache vs Rebuild Database

These two sub-options live behind the same menu row and get used interchangeably in casual advice, which is a mistake. They do different jobs, take wildly different amounts of time, and Sony recommends them for different symptoms.

Two buttons, two very different jobs

Clear System Software Cache is the light one. It discards regenerable OS temp files and reboots. On any drive it is a matter of a minute or two. Rebuild Database is the heavy one. It walks the entire SSD, reads the metadata of everything installed, and constructs a fresh index of all content on the system. On a modest drive that is a few minutes. On a full 8TB M.2 expansion it can run up to around an hour. Both are non-destructive; neither deletes a save. But one is a quick sweep and the other is a full inventory, and you should not reach for the inventory when a sweep is what the situation calls for.

When to escalate to Rebuild

Rebuild Database is your second move, not your first. Escalate to it when the light cache clear did not resolve the symptom, or when the symptom itself points at the database: a game icon that lingers on Home after you deleted the game, corrupted-data warnings, folders that will not populate, or a library that displays inconsistently. Sony's guidance for Rebuild specifically covers cases like an icon that remains on Home after deletion. That is a database problem, and re-indexing is the correct tool. If you are going to run it, start it when you can leave the console alone, because on a large full drive you are committing to a long, uninterruptible pass.

The home-screen-reshuffle myth

Now the correction. A persistent claim holds that clearing the cache resets or rearranges your PS5 home screen. It does not. That belief comes from two places, and neither is the cache clear. First, Rebuild Database rebuilds the content index, and that re-index can legitimately reshuffle the order of tiles, so people who ran the combined menu, or ran Rebuild by mistake, saw their layout change and blamed the cache. Second, there is a well-travelled Reddit anecdote tied to a specific big title where a user's layout shifted; it was never reproduced as a documented behaviour and Sony has never claimed the cache clear touches your layout. Attribute the reshuffle to Rebuild, or to coincidence, and move on. The light clear leaves your tiles where you left them.

5 Common Pitfalls

Almost every failed cache clear is one of these five, and all five are self-inflicted and reversible. Here they are with the fix attached.

Wireless pad, dead menu, and the Rest Mode trap

Pitfall 1: the controller does nothing. You are in Safe Mode, you press buttons, the cursor does not move. This is not a broken console; it is Bluetooth being disabled in Safe Mode. Fix: connect the DualSense with a data USB-C cable and press the PS button. If it still does nothing, your cable is charge-only, which is Pitfall 2.

Pitfall 2: the cable is charge-only. The controller light is on, so it looks connected, but the menu ignores it. Fix: swap to a data-capable cable. The white cable from the PS5 box works. Many cheap third-party cables carry power but not data, and they will waste ten minutes of your life before you suspect them.

Pitfall 3: the console was in Rest Mode, not off. You held the button, nothing entered Safe Mode, or the console simply woke to the dashboard. Fix: fully power the console off first and wait for the indicator to go dark before you begin the press-and-hold. Rest Mode is the single most common reason Safe Mode entry misfires, and it is the villain behind a surprising share of the slowdowns people are trying to fix in the first place.

Wrong sub-option, longer wait

Pitfall 4: you selected Rebuild Database by mistake. No harm done to your data, but you have now committed to a re-index that can run for the better part of an hour on a full drive. Fix: let it finish. Do not yank the power to escape it, because interrupting Rebuild mid-pass is genuinely riskier than letting it run. Next time, read the sub-menu twice and choose Clear System Software Cache.

Pulling power, and other self-inflicted wounds

Pitfall 5: you interrupted a reboot. The console restarted during the flush, you assumed it had hung, and you pulled the plug. This is the one pitfall that can actually cause the corruption the whole exercise was meant to prevent. Fix: never interrupt. If you already did and the console now refuses to boot cleanly, go back into Safe Mode and run Rebuild Database; if that fails, your remaining escalations are Update System Software and, as a last resort, the destructive Reset options. Prevention is trivial: when the screen goes dark and the console reboots one or more times, that is the procedure working, not failing.

Troubleshooting Table

When reality departs from the expected output, this table is the map. It is ordered roughly from cannot-start to did-not-work.

If you cannot get into Safe Mode

The entry sequence is timing-based and audio-based, so the failures cluster around the beeps and the cable. Work down the first few rows before you conclude anything is wrong with the hardware.

If the clear did not fix it

A cache clear that changes nothing is not a failed clear; it is a correct clear applied to the wrong problem. The lower rows point you at the real cause, which is frequently storage headroom, thermals, or an application-level fault rather than the OS cache at all.

The Rocket League Case

The strongest argument that this procedure is real, and not merely folklore, is that a major publisher documents it as an official fix. That publisher is Epic, and the game is Rocket League.

Why Epic tells you to do this

Epic's own support material instructs PS5 players hitting a Rocket League Load Failure error to boot into Safe Mode, open Clear Cache and Rebuild Database, and select Clear System Software Cache. You can read it in the Epic Games Rocket League support article. This matters because it is a first-party endorsement of the exact steps in this guide, aimed at a specific, reproducible symptom. When a stale or half-written OS temp file trips a game's loader, flushing that cache genuinely clears the fault. This is the procedure working as designed.

The symptoms cache-clearing actually addresses

Generalise from the Rocket League case and you get the honest indication list. Clearing the system software cache is worth trying when the symptom smells like transient OS state gone stale: a single game that suddenly will not load after previously working, interface sluggishness that appeared out of nowhere, odd behaviour immediately following a firmware update, glitches that survive a normal reboot but have no obvious hardware cause. These are the cases Sony gestures at with the phrase system feature issues or performance drops. The cache clear is cheap, fast, and non-destructive, so for this class of bug it is a reasonable first move.

The symptoms it will not touch

Now the counterweight, and it is the part the cure-all crowd never says out loud. Engadget frames the cache clear correctly as a short-term remedy, not a fix for hardware degradation, and that framing is the whole ballgame. If your PS5 is loud under load, running hot, crashing during demanding scenes, throttling, or throwing storage errors, a cache clear is a placebo. Those are symptoms of thermals, a tired fan, dried thermal paste, a filling or failing SSD, or a struggling power supply, and no amount of temp-file flushing addresses any of them. Likewise, if your complaint is online lag or stutter in a streamed session, that is a network problem living between your router and the server, not cache; our PS Remote Play setup guide is a better use of your time than Safe Mode. Match the tool to the fault. The cache clear has a narrow, real job, and pretending otherwise just wastes your afternoon.

Advanced Tips and Cadence

Once you understand what the clear does and does not do, the advanced material is mostly about restraint: doing it less often, reaching for a cheaper move first, and understanding why you cannot be more surgical than an all-or-nothing flush.

How often is actually worth doing this

Not on a schedule. There is a persistent piece of advice that you should clear the cache after every major update or once a month as hygiene, and it is overstated. Sony's real cadence, encoded in its own wording, is when you have a problem. The cache is not sludge that accumulates and slows you down over time; it is working state that the OS manages continuously. Clearing it pre-emptively buys you nothing but a slower next boot. Do it when a specific, persistent symptom points at it. Ritualising it is cargo-cult maintenance.

The cheaper first move: a real cold boot

Before Safe Mode, try the move that fixes a startling share of laggy-PS5 complaints: a genuine full power-off and cold boot, not Rest Mode. Rest Mode suspends the system and any open game into a held state, and that held state is exactly where a lot of slowdown and weirdness breeds. A true cold boot, holding the power button until the console fully shuts down, then starting it fresh, flushes volatile memory and clears the suspended session without ever entering Safe Mode. It costs sixty seconds. If a cold boot fixes it, you never needed the cache clear, and you have learned that Rest Mode was the culprit all along. Try the cheap thing first.

What is probably in that cache

Since Sony will not tell you, here is a reasoned inference from observed behaviour. Treat this as an educated model, not a spec sheet:

PS5 SYSTEM SOFTWARE CACHE -- inferred contents (not Sony-documented)

  shader / pipeline cache   -- compiled GPU state, rebuilt on next run
  asset staging             -- decompressed data held between sessions
  download scratch          -- partial/temporary install-time files
  UI tile + thumbnail cache  -- home-screen art the dashboard paints
  handshake / HDCP state     -- display + copy-protection negotiation
  notification / queue state -- pending toasts, telemetry buffers

  Property: ALL regenerable from installed data + OS image
  Property: none of it is your saves, clips, or accounts
  Caveat  : inferred from behaviour, NOT confirmed by Sony

Notice what you cannot do: inspect it, size it, or selectively clear one category. The PS5 is a sealed appliance, and the cache clear is deliberately all-or-nothing. That is the same design philosophy that makes the console reliable and boring in equal measure, and it is exactly the trade a PC does not make; if the closed-box model frustrates you, that tension is the subject of our PC versus console breakdown. On a console you get a button that says clear the cache, and you get to trust it. That is the deal.

Complete Maintenance Config

Everything above, compressed into one self-contained reference you can act on without re-reading the article. This is the whole decision tree, the cadence, and the do-not list in a single block.

The full decision tree

Start at the top with the symptom and follow the branch. The ordering is deliberate: cheapest and safest first, destructive last.

PS5 MAINTENANCE -- decision tree (2026, firmware 26.04-xx)

START: console is slow / laggy / a game won't load / post-update glitch

 1. COLD BOOT (not Rest Mode)
      hold power -> full shutdown -> restart fresh
      fixed?  -> DONE  (Rest Mode was the culprit)
      no      -> step 2

 2. CLEAR SYSTEM SOFTWARE CACHE   (Safe Mode -> Option 6 -> sub-option 1)
      light, ~1-2 min, deletes nothing
      fixed?  -> DONE
      no      -> step 3

 3. REBUILD DATABASE              (Safe Mode -> Option 6 -> sub-option 2)
      heavy, up to ~1 hr on full 8TB, deletes nothing
      fixed?  -> DONE
      no      -> step 4

 4. CHECK THE REAL CAUSE
      free storage low?   -> delete/move titles
      hot / loud / crashy? -> thermals: clean, re-paste, service
      one app only?        -> reinstall that app; publisher cache steps
      network stutter?     -> router / connection, NOT the cache
      fixed?  -> DONE
      no      -> step 5

 5. LAST RESORTS (DESTRUCTIVE -- back up saves first)
      Update System Software (Option 4)
      Reset PS5 (Option 7)                  <- WIPES console
      Reset PS5 + Reinstall (Option 8)      <- WIPES + reflashes OS

The maintenance checklist

The cadence and the guarantees, stated once so you never have to wonder:

CADENCE
  Clear cache      : only when a specific symptom points at it
  Rebuild database : only if the cache clear did not help, or ghost icons
  Cold boot        : whenever the console feels sluggish (do this first)
  Routine schedule : NONE -- pre-emptive clearing buys nothing

GUARANTEES
  Clear System Software Cache : keeps games, saves, clips, accounts
  Rebuild Database            : keeps games, saves, clips, accounts
  Cost                        : free -- no PS Plus, no app, no purchase
  Works on                    : PS5, Digital, Slim, PS5 Pro (identical)

The copy-paste-free reference card

And the pocket version, for when someone in a group chat asks you how to do this and you do not want to type six paragraphs: power fully off, hold the power button to the second beep at about seven seconds, wire the DualSense with a data USB-C cable and press PS, open Clear Cache and Rebuild Database (Option 6, or 5 on older layouts, read the label), choose Clear System Software Cache, confirm OK, and let it reboot without touching it. Nothing is deleted. It takes about fifteen minutes end to end. If it does not help, the problem was never the cache.

The Verdict

Clearing the PS5 cache is a good, free, harmless tool that the internet has mistaken for a cure-all. Here is where it lands.

What it is genuinely good for

It is genuinely good for a narrow, real class of bug: stale OS temp state that trips a loader, post-update flakiness, a game that suddenly will not start when it worked yesterday. Epic endorses it for a specific Rocket League failure, and that endorsement is earned. It costs nothing, risks nothing, and takes a quarter of an hour. When the symptom fits, it is the correct first move after a plain cold boot.

What it cannot fix

It cannot fix hardware. Not thermals, not a tired fan, not a failing SSD, not a straining power supply, not network lag. Prescribing a cache clear for a console that is loud, hot, or crashing under load is the technical equivalent of prescribing rest for a broken leg. If your hardware is genuinely on the way out, the honest question is not which Safe Mode option to pick but whether you are near the end of this console's life and reading our PlayStation 6 release-date outlook instead. A cache clear will not resurrect dying silicon.

The bottom line

Do it when you have a specific, persistent symptom that smells like software. Read the label, not the menu number. Wire the controller, wait for the second beep, choose the light option, confirm, and let it reboot. Do not ritualise it, do not pay for an app to imitate it, and do not expect it to fix your fan. It is free, it is safe, it is occasionally exactly right, and it is wildly overprescribed. Now you know which of those applies to you.