PS5 Cache 2026: Clear It Right in 12 Steps, 10 Min

There is a genre of PlayStation advice with the epistemic status of a folk remedy. Clear your cache. It gets prescribed for everything: stuttering downloads, a game that boots to a black screen, an online match that refuses to connect, a console that simply feels slow in a way nobody can quantify. It is the digital equivalent of balancing your humors, and most people performing the ritual cannot tell you which cache they cleared, whether it worked, or whether the PS5 even has the cache they imagine.

So let us be precise, because precision is the whole point of this site. The PlayStation 5 has exactly one user-facing, officially supported cache-clearing operation. It lives in Safe Mode, reached by a physical button and nothing else. It is free, it needs no PlayStation Plus subscription and no internet connection, and — this is the part the panic-Googlers never believe — it does not delete your games, your saves, or your account. Everything else sold to you as a PS5 cache clear is either a power cycle wearing a lab coat, or a database rebuild filed under the wrong name.

This guide covers all of it: what the cache is at the filesystem level, the two-tier procedure (a sixty-second soft flush and the full Safe Mode clear), a twelve-step walkthrough with the reasoning behind every step, and the single most common way people sabotage their own attempt — starting from Rest Mode instead of a real shutdown. We will also settle the argument every rival guide gets wrong: whether Clear Cache and Rebuild Database is menu option five or option six. It is six, now. We will explain exactly why it moved, and why you should ignore the number anyway.

What 'Cache' Actually Means on a PS5

Before you clear something, it helps to know what it is. On the PS5 the word 'cache' gets stretched across at least three distinct things, and conflating them is why half the advice online is useless. There is the system software cache, the content database, and the per-application storage that people assume they can flush but cannot. Only the first is a cache in the strict sense, and only the first has a dedicated button.

The system software cache

The system software cache is a pile of temporary files the operating system writes while it runs: decompressed UI assets, thumbnail art, store-page fragments, shader and font scratch data, transient state left behind by apps that closed badly. It exists to make the console feel fast, and it works — until an entry gets written half-corrupt or goes stale against a new firmware build. Then you get the classic symptoms: a store that will not load, tiles with missing artwork, a download stuck at 'Queued', an app that crashes on launch for no visible reason. Clearing this cache deletes those temporary files and forces the OS to regenerate them clean. It touches nothing you care about keeping. This is the cache the Safe Mode option clears, and it is the only one Sony lets you clear on purpose.

The content database (which is not a cache)

Sitting next to the cache is the content database — an index of every game, app, save, screenshot and video clip on the drive, plus how they should be sorted, grouped and displayed. When your library shows a game as installed but it will not launch, or an installed title vanishes from the home row, or 'corrupted data' appears next to something that is plainly fine, the database has drifted out of sync with the actual files. Rebuilding it re-scans the whole SSD and writes a fresh index. It is emphatically not a cache clear, even though Sony bundled the two behind one menu label. It is slower, it is heavier, and — contrary to a widely repeated Reddit claim — it does not wipe your data. It can, however, reshuffle your home screen, which is where that myth comes from.

The per-game cache you cannot touch

Here is the one nobody wants to hear. On PS5 there is no per-application 'clear cache' button of the kind Android and web browsers trained you to expect. You cannot dive into a single misbehaving game and flush its cache. The OS manages application scratch space itself, and the only user lever that affects a specific title is deleting and reinstalling it, or (carefully, and separately) deleting its saved data. So when a guide tells you to 'clear the cache for Warzone' or 'clear the cache for Fortnite', understand what it actually means: clear the whole system cache and hope, or reinstall the game. There is no middle setting. Even thorough roundups like MakeUseOf's PS5 cache guide land on the same conclusion: the system-wide clear or a reinstall are the only real levers you have.

PS5 STORAGE, ROUGHLY
------------------------------------------------
[ System software cache ]  temp OS files      -> the ONE you can clear
     thumbnails, store fragments, shader scratch
[ Content database ]       index of everything -> Rebuild Database re-scans this
     what is installed, how it sorts/displays
[ Games + apps ]           the actual titles   -> never touched by either op
[ Saved data ]             your progress       -> never touched by either op
[ Screenshots / clips ]    your captures       -> never touched by either op
------------------------------------------------
Clear System Software Cache -> row 1 only
Rebuild Database            -> re-indexes row 2
Reset PS5                   -> wipes rows 1-5 (the nuclear buttons)

When Clearing the Cache Actually Helps

A cache clear is a scalpel, not a prayer. It fixes a specific class of problem and does nothing at all for the rest, and the reason so many people report 'it didn't work' is that they applied it to a fault it was never going to touch. Engadget's own guide is blunt on this point: clearing the cache is a short-term remedy, and it will not reverse hardware degradation. Set your expectations accordingly before you spend ten minutes on it.

What it genuinely fixes

Reach for the cache clear when the symptom smells like stale temporary data. That includes: the PlayStation Store or a game's in-app storefront failing to load; UI corruption like missing box art or frozen tiles; downloads and updates that hang at 'Queued', 'Copying' or a stuck percentage with no network reason; apps that crash immediately on launch after a firmware update; and general post-update flakiness where the console behaves as if it half-remembers the old build. Epic Games explicitly recommends the Safe Mode cache clear as a fix for Rocket League 'load failure' errors — a rare case of a publisher officially endorsing the ritual, and a good indicator of the failure class it targets: an app that installed and patched fine but will not start.

What it will not touch

It will not fix a failing SSD, an overheating APU, a dying power supply, or a controller with stick drift. It will not speed up a console that is slow because its storage is 98 percent full — that is a capacity problem, not a cache problem, and the fix is deleting games. It will not repair a genuinely corrupted game install; that needs a reinstall. It will not cure network-layer issues like DNS failures, NAT problems or a congested regional CDN, no matter how many forum posts insist otherwise. If your Remote Play session keeps dropping, the cache is almost never the cause — our PS5 Remote Play walkthrough covers the bandwidth and port settings that actually matter there. Clearing the cache when the problem is elsewhere just wastes ten minutes and teaches you to distrust a tool that works fine within its remit.

The Rest Mode connection

There is a subtler reason to care about this procedure, and it explains why the shutdown method matters so much later. The PS5's Rest Mode is a suspend state: it keeps the system's memory and a suspended session alive on low power so you can resume instantly and finish background downloads. That is convenient, and it is also how stale state survives for weeks. A console that is 'always a little glitchy' is very often a console that has not had a true cold boot in a month because its owner only ever uses Rest Mode. Before you touch Safe Mode at all, understand that Rest Mode and a full shutdown are opposites, and that half the value of this guide is simply making the console actually turn off.

Prerequisites: Firmware, Hardware, and the Cable Nobody Mentions

This is a short list, but every item on it is a place where the procedure fails silently if you skip it. Read it before you start holding buttons.

Firmware and a version check

The Safe Mode cache sub-option arrived on PS5 in late 2023 and has been present ever since, so any reasonably updated console has it. As of this writing in August 2026, the current system software is build 26.05-13.60.00, released July 23, 2026 — the second July patch, following 26.04-13.42.00 on July 1. Sony ships these 'performance and stability' updates roughly monthly, so your build number may read higher, and that is fine; the digits do not change the procedure. Note the version format: it is 26.05-13.60.00, not 'Version 7.00' or 'Version 9.00' — those are PlayStation 4 numbers the PS5 has never used, and any guide quoting them is describing the wrong console.

Settings > System > System Software > Console Information

EXPECTED OUTPUT (example):
  Model                 CFI-2000 (Slim)
  System Software       26.05-13.60.00
  Emission code         ...

Anything in the 26.0x family (2026) has the cache option.

The cable nobody mentions

Here is the requirement that trips up more people than any other: Safe Mode disables Bluetooth. Your DualSense will not connect wirelessly once the console boots into Safe Mode, no matter how many times you press the PS button in frustration. You must physically wire the controller with a USB data cable — the DualSense end is USB-C, and the console end is whatever your model exposes (USB-A on the front for most units, USB-C on the newer Slim front port). Use a real cable, not a charge-only one; a surprising number of bundled and third-party cables carry power but no data, and they will leave you staring at an unresponsive menu. Have this cable in hand before you begin, because you will need it the moment Safe Mode appears.

What you do not need

You do not need PlayStation Plus. You do not need an internet connection — the cache clear is entirely local, and you can and arguably should do it with the console offline to rule out network noise. You do not need a USB drive, a second controller, or a factory reset. You do not need to back anything up for the cache clear itself, because it deletes nothing you own; that said, backing up saves to the cloud or a USB stick before any Safe Mode work is cheap insurance and generally good hygiene. And you do not need a Settings menu path to Safe Mode, because there is not one — on both PS5 and PS4, Safe Mode is reachable only by the physical power button. Guides that claim the PS5 hid a Settings route that the PS4 had are inventing a contrast that never existed.

Two Levels of Cache Clear: Soft Flush vs. Safe Mode

There are two operations people call 'clearing the cache', and they are not the same thing. One is a soft flush that clears volatile memory in about a minute with zero risk. The other is the real, on-disk system cache clear inside Safe Mode. Start with the light one; escalate only if it does not help. A third, heavier operation — Rebuild Database — lives in the same menu and gets its own section, because it solves a different problem.

The soft flush (volatile state)

Fully powering the console down flushes its RAM and clears transient runtime state. Unplugging the power cord for thirty to sixty seconds goes a step further, draining the residual charge in the capacitors so the next boot is genuinely cold. This is not the on-disk cache clear, and it is dishonest to call it one — but it is legitimately a 'cache flush' in the colloquial sense, it resolves a lot of transient glitches, and it carries no risk whatsoever. It is the correct first move.

The Safe Mode cache clear (on-disk)

When the soft flush is not enough, the Safe Mode operation deletes the actual temporary files on the SSD. This is the officially supported cache clear, the one behind the Clear Cache and Rebuild Database menu entry. It is still non-destructive to your games and saves, it just reaches deeper than a power cycle. It takes under a minute once you are in the menu, and it forces the OS to rebuild its temporary files from scratch on the next boot.

Choosing between them

Match the tool to the failure. The table below is the decision you are actually making; the two sections that follow are the step-by-step for each. If you want the stripped-down version of the Safe Mode route without the theory, our condensed twelve-step PS5 cache guide is the companion to this one.

Method 1: The 60-Second Power-Cycle Flush

Do this first, always. It fixes a meaningful share of 'my PS5 is acting weird' complaints, it cannot hurt anything, and if it works you have saved yourself the Safe Mode dance entirely. It clears volatile memory, not on-disk cache, so set expectations accordingly — but it is the correct opening move.

The steps

1. Close what you are running. Quit the active game or app from the home screen so nothing is mid-write when the console powers down.
2. Hold the PS button on the controller to open the Control Center, then select the power icon to open the power options.
3. Choose 'Turn Off PS5' — not 'Enter Rest Mode'. This is the entire point. Rest Mode preserves the state you are trying to clear.
4. Wait for the console to fully power down. The indicator light blinks while it shuts down, then goes completely dark. Do not proceed while it is still blinking.
5. Unplug the power cord from the back of the console (or the wall).
6. Wait 30 to 60 seconds. This drains the residual charge in the capacitors so the next boot is genuinely cold rather than a fast restart off leftover state.
7. Reconnect the power cord and power the console on normally with the power button or the controller's PS button.

Why the wait matters

The thirty-to-sixty-second pause is not superstition. Modern power supplies hold enough charge to keep parts of the board alive for several seconds after you pull the cord; if you replug immediately, the system never fully lost power and the volatile state you were trying to dump may survive. Waiting lets the capacitors bleed out so the boot is clean. This is, incidentally, the only cache-clearing move the PlayStation 4 ever had — as Activision's cross-platform support note points out, the PS4 has no cache menu at all, so the full power-off-and-unplug was the whole procedure there. The PS5 kept it and then added a real menu option on top.

Expected result

The console boots to the sign-in screen as usual, typically a few seconds slower than a Rest Mode wake because it is doing a full cold start. Downloads that were stuck often resume; a store that would not load frequently loads; minor UI weirdness clears. If the problem is gone, stop here — you did not need Safe Mode. If it persists, the temporary files on disk are the likely culprit, and it is time for Method 2.

Method 2: Clearing the System Software Cache in Safe Mode (12 Steps)

This is the real thing — the officially supported cache clear. It requires the physical power button, a wired controller, and a little patience with a beep. Follow the steps in order; the rationale for each is why the procedure works when a careless version of it fails.

Powering all the way down

Safe Mode can only be entered from a genuine cold state. If the console is in Rest Mode, or worse, still 'off' but holding charge, the boot sequence will not arm the Safe Mode timing and you will just get a normal startup. So the first job is a true shutdown, verified by a dark indicator light.

The two-beep entry

You enter Safe Mode by holding the console's physical power button — not the controller — through two beeps. The first beep is the console powering on; the second, about seven seconds later, is the signal that it is booting into Safe Mode instead of normally. Release at the second beep. Let go early and you get a normal boot; that single mistake accounts for most 'it will not enter Safe Mode' complaints.

Clear System Software Cache

Here is the full procedure, twelve steps, each with the reason it is there.

1. Save and quit your game. The cache clear reboots the console, and anything unsaved dies with it. Rationale: this operation is non-destructive to stored saves, but it will not rescue progress you never wrote to disk.
2. Hold the PS button and open the power options. Rationale: this is the only route to a true shutdown; the console has no 'off switch' that bypasses the menu on the software side.
3. Select 'Power', then 'Turn Off PS5'. Do not select 'Enter Rest Mode'. Rationale: Rest Mode keeps memory and a suspended session alive, which defeats the entire purpose and prevents Safe Mode from arming.
4. Wait for the indicator light to stop blinking and go fully dark. Rationale: the console is only truly off when the light is out; a blinking light means it is still shutting down and is not ready for the button hold.
5. Optionally leave it off for 30 seconds. Rationale: a brief pause drains volatile state so you get the benefit of Method 1 folded into this one.
6. Connect the DualSense with a USB data cable. Rationale: Safe Mode disables Bluetooth, so a wireless controller is dead weight; only a wired one responds. Confirm the cable carries data, not just power.
7. Press and hold the console's physical power button — and keep holding. Rationale: a single tap boots normally; Safe Mode needs a sustained hold through the timing window.
8. Release at the SECOND beep, about seven seconds in. Rationale: the first beep is power-on, the second is the Safe Mode signal. Let go on the first and you boot normally; hold past the second and you are fine, but seven seconds is the mark.
9. Press the PS button on the wired controller to continue. Rationale: Safe Mode waits for you to identify the controller over USB before it shows the menu.
10. Select 'Clear Cache and Rebuild Database'. On current firmware this is option 6. Rationale: this is the branch that contains the cache clear — read the label, because the number has moved across firmware revisions (more on that below).
11. Choose 'Clear System Software Cache'. Not 'Rebuild Database' — that is the heavier sibling in the same submenu. Rationale: 'Clear System Software Cache' is the light, fast, non-destructive operation you came for; it deletes temporary OS files only.
12. Let it clear and reboot. Rationale: the console removes the temp files and restarts to the sign-in screen; do not interrupt it. When you are back at sign-in, it is done.

The menu you are navigating — documented on Sony's own PS5 Safe Mode support page — looks like this. Note the numbering, and note that the thing you want is behind a submenu, not a top-level button:

PS5 SAFE MODE  (firmware 26.05-13.60.00, 2026)
------------------------------------------------
  1  Restart PS5
  2  Change Video Output
  3  Repair Console Storage          <- inserted in 2024; pushed the rest down
  4  Update System Software
  5  Restore Default Settings
  6  Clear Cache and Rebuild Database <- SELECT THIS (a submenu)
         |- Clear System Software Cache   <- then THIS (light, under 1 min)
         |- Rebuild Database              <- the heavy one (see next section)
  7  Reset PS5
  8  Reset PS5 (Reinstall System Software)
------------------------------------------------
Controls: wired DualSense only. Read labels, not slot numbers.

When the cache clear runs and completes, the on-screen sequence is unremarkable, which is how you know it worked:

EXPECTED ON-SCREEN OUTPUT

> Clear Cache and Rebuild Database
> Clear System Software Cache
    Clearing the system software cache...
    [progress spinner, a few seconds]
> Restarting...
> [PS5 boots to the user sign-in screen]

No confirmation dialog boasts 'cache cleared'. The reboot IS the confirmation.
Games, saves, screenshots and accounts are all still present.

Why option 6 and not option 5

You will find reputable guides — SlashGear among them — that call this menu option 5. They are not wrong; they are old. The earlier PS5 Safe Mode menu had seven items, with Clear Cache and Rebuild Database at position 5. Then Sony inserted a new entry, Repair Console Storage, at slot 3, and every option below it slid down by one: the cache branch went from 5 to 6. This is precisely why we keep telling you to read the label rather than memorize a number. Sony has reordered this menu before and will do it again, and a guide pinned to a slot number ages badly the day the layout changes. The label Clear Cache and Rebuild Database has been stable throughout. Follow that. The sibling article that titles itself around 'option 6' is describing the current 2026 layout — accurate today, and the reason we lead with 6.

Rebuild Database: The Heavier Sibling

Sitting next to the cache clear in the same submenu is Rebuild Database, and because they share a menu label people run it thinking it is 'a stronger cache clear'. It is not. It solves a different class of problem, it takes far longer, and it is worth understanding on its own terms so you deploy it when it helps and skip it when it does not.

What rebuild actually does

Rebuild Database scans every file on the internal SSD — and on any M.2 expansion or external USB drive you have connected — and constructs a fresh index of all that content: what is installed, what saves exist, how everything sorts and groups on the home screen. It is the console equivalent of a librarian re-shelving the entire collection and rewriting the catalog. Crucially, it does not delete or modify the files themselves. Your games, saves, screenshots and clips survive intact. What can change is presentation: the home row may reorder, recently-played sorting may reset, and this cosmetic reshuffle is the real source of the persistent 'rebuilding wipes your layout' myth. Nothing is wiped; it is re-indexed.

How long it takes

Unlike the cache clear, this one is not quick, and the duration scales with how much is on the drive — specifically the number of files, not just the gigabytes. A near-empty console finishes in a few minutes; a stuffed 2TB internal SSD paired with a multi-terabyte M.2 expansion can run close to an hour. The PS5 Pro, with its larger standard drive, tends toward the long end simply because owners fill it — if you are weighing that machine, our PS5 Pro versus base PS5 breakdown covers the storage differences that feed straight into rebuild times, and step-by-step guides like PC Guide's confirm the identical flow applies to the Pro. The one rule that matters: do not power off mid-rebuild. Interrupting it can leave the database in a worse state than when you started.

When to run it

Run Rebuild Database when the symptom points at the index, not the cache: installed games missing from the library, a title that shows as installed but will not launch, 'corrupted data' warnings on files that are actually fine, saves not appearing, or external/M.2 games greyed out. Run it with the relevant expansion drive connected so it gets indexed too. Do not run it as a reflex after every update — that is cargo-cult maintenance. Sony's actual guidance, and ours, is to run these tools when you have a problem they address, not on a calendar.

Five Ways People Screw This Up

The procedure is simple, which is exactly why people botch it — they skim, they assume, they let go of the button early. Here are the failures we see most, grouped by when they happen, each with the fix.

Before you start

Pitfall 1 — Starting from Rest Mode. This is the big one, and every serious guide flags it. If the console is suspended rather than fully off, Safe Mode either will not arm or you will clear nothing meaningful because the suspended state is still alive. Fix: wake the console, hold the PS button, choose Power > Turn Off PS5, and wait for the indicator light to go fully dark before you touch the power button. SlashGear's guide makes the same point: if it slips into Rest Mode instead of powering off, wake it and shut it down completely before retrying.

Pitfall 2 — A charge-only USB cable. You get into Safe Mode, press the PS button, and nothing happens, so you conclude the controller is broken. It is not; the cable carries power but no data. Fix: use a known-good USB data cable. If you are unsure, the cable that came with the console is a safe bet; many cheap third-party cables are charge-only.

During the procedure

Pitfall 3 — Releasing at the first beep. The console beeps once when it powers on and again about seven seconds later for Safe Mode. Let go on the first beep and you get a normal boot every time. Fix: keep holding through the first beep and release only on the second, roughly seven seconds in. If in doubt, hold a beat longer.

Pitfall 4 — Picking the wrong submenu item. Inside Clear Cache and Rebuild Database there are two buttons, and people in a hurry hit Rebuild Database when they wanted the quick cache clear, then panic when it runs for forty minutes. Fix: for a cache clear, choose Clear System Software Cache. Only choose Rebuild Database if you actually have an indexing problem — and if you start it, let it finish.

After the reboot

Pitfall 5 — Expecting it to fix an unrelated fault. You clear the cache, the black-screen-on-a-specific-game problem persists, and you declare the whole exercise useless. The exercise was fine; the diagnosis was wrong. Fix: match the tool to the symptom. Corrupted game install? Reinstall the game. Network failure? Check DNS and your connection. Overheating or crashing under load? That is hardware, and no cache clear reverses it — Engadget is explicit that this remedy does not address hardware degradation. A sixth, honorable-mention pitfall: clearing the cache 'to be safe' after every single update. It is harmless but pointless, and it trains you to reach for a fix before you have identified a problem.

Troubleshooting Table

When the procedure itself misbehaves, or when the cache clear does not produce the result you hoped, this table maps the symptom to the likely cause and the actual fix. Work down it in order of how common the cause is.

The table

Reading the symptoms

The pattern to internalize: entry-into-Safe-Mode failures are almost always the beep timing or Rest Mode; in-menu failures are almost always the cable; and post-clear disappointment is almost always a misdiagnosis. If you find yourself repeating the cache clear a third time hoping for a different result, stop — the repetition is telling you the cache was never the problem.

When none of it works

If you have cleared the cache, rebuilt the database, and reinstalled the offending game and the fault survives all three, you are likely looking at hardware or at a system-software corruption deeper than the cache. The next escalation is Restore Default Settings (option 5, non-destructive to your data), and only after that the destructive Reset PS5 (Reinstall System Software). Do not jump to the nuclear options first; they are slower, they erase things, and they are almost never what a cache-shaped problem needs.

Advanced: Rest Mode, Rebuild Cadence, and the Caches Sony Hides

Once you understand the mechanism, a few habits keep the console healthy without the ritual. This section is for people who would rather prevent the glitch than clear it.

Killing Rest Mode entirely

If your console is the 'always slightly glitchy' type and you use Rest Mode constantly, the single most effective change is to stop. Set the console to power off fully instead of suspending, and you get a true cold boot every session — which flushes volatile state for free, every time, and dramatically cuts the frequency of the problems that send people to Safe Mode. The relevant setting lives under power management:

Settings > System > Power Saving > Set Time Until PS5 Enters Rest Mode

  During Media Playback ......  Don't Put in Rest Mode
  During Gameplay ............  Don't Put in Rest Mode

Then shut down with:  PS button > Power > Turn Off PS5   (not Rest Mode)

Effect: every boot is cold. Volatile-cache glitches drop sharply.

The trade-off is honest: you lose instant resume and background downloading while 'off'. If those matter to you, keep Rest Mode and just perform Method 1 once a week. Either works; the point is to break the weeks-long uptime that lets stale state accumulate.

A rebuild cadence that is not cargo-cult

You do not need to rebuild the database on a schedule, and doing it 'after every update' is folklore. A sane cadence is: rebuild when you observe an index symptom (missing games, sort chaos, phantom 'corrupted data'), and optionally once after you have deleted and reinstalled a large batch of games, since mass install/uninstall churn is what actually fragments the index. Otherwise leave it alone. The database is not a filter that clogs; it is an index that only needs rebuilding when it has drifted.

Related tools people confuse with cache clearing

Two neighbors in the Safe Mode menu get mistaken for cache tools. Repair Console Storage (option 3, the entry that shifted the cache option down to 6) checks the SSD's file structure for errors and repairs them — useful for genuine storage corruption, overkill for a stale thumbnail. Restore Default Settings (option 5) resets system settings without deleting your games or saves, a gentler step than a full reset when settings themselves are the suspect. Neither is a cache clear, and reaching for them first is how a five-minute problem becomes an afternoon. Keep firmware current too, since many 'glitches' are just bugs Sony already patched — the same monthly cadence that shipped 26.05-13.60.00 also fixes the faults people blame on the cache, a dynamic we traced in our note on how the PS5 Pro's PSSR upgrade arrived as a free firmware update.

The Complete Cache-Hygiene Configuration

Here is the whole thing distilled into a reference you can act on without re-reading the article — a settings checklist, a command-style crib sheet for the Safe Mode sequence, and the one-line rule to remember.

The cache-hygiene checklist

Treat this like a config file for how you run the console. Adopt the top block permanently; use the bottom block only when a symptom calls for it.

# ps5-cache-hygiene.conf  --  2026

[permanent]
firmware              = keep current    # 26.05-13.60.00 or newer, monthly
rest_mode.gameplay    = off             # cold boots flush volatile state
rest_mode.media       = off
weekly_habit          = full power-off + unplug 60s   # the soft flush
backup.saves          = cloud or USB before any Safe Mode work

[on_symptom]                            # run ONLY when the fault matches
store/UI corruption   -> Clear System Software Cache
app crash on launch   -> Clear System Software Cache
missing/greyed games  -> Rebuild Database (drive connected)
sort/library chaos    -> Rebuild Database
corrupted data warning-> Rebuild Database, then reinstall if needed
game-specific fault   -> delete + reinstall THAT game (no per-game cache exists)

[never]
reset_ps5             = only as genuine last resort (this ERASES the drive)
clear_after_update    = no  # folklore; clear on a problem, not a calendar

Quick-reference command sheet

The Safe Mode cache clear, compressed to the sequence your hands actually perform:

# PS5 SAFE MODE -- CLEAR SYSTEM SOFTWARE CACHE (quick reference)

1.  Quit game/app
2.  PS button > Power > Turn Off PS5        # NOT Rest Mode
3.  Wait: indicator light OFF (dark, not blinking)
4.  Connect DualSense via USB DATA cable    # Bluetooth is off in Safe Mode
5.  Hold console power button ............... [ beep #1 = power on ]
6.  Keep holding ~7 s ...................... [ beep #2 = Safe Mode ] -> release
7.  Press PS on the wired controller
8.  Select: Clear Cache and Rebuild Database # slot 6 on 2026 firmware
9.  Select: Clear System Software Cache      # the LIGHT one
10. Wait for reboot to sign-in = DONE

# Non-destructive. Free. No PS Plus. No internet required.
# Games, saves, screenshots, accounts: all retained.

The one rule

If you remember nothing else: turn the console fully off, hold to the second beep, wire the controller, and select by label — 'Clear Cache and Rebuild Database', then 'Clear System Software Cache' — never by slot number. Rest Mode is the enemy, the second beep is the signal, the cable carries data, and the label is stable while the number is not. Do that and the ten-minute procedure works the first time, which is more than most people who type 'how to clear cache on ps5' into a search bar can say. For the broader context of how this console stacks up against its predecessor, our PS5 versus PS4 comparison is the long view; this guide is the maintenance manual.