PS5 Cache Clear 2026: 13 Steps, 10 Min in Safe Mode

The PlayStation 5 does not have a clear-cache button, and it is not going to get one. Sony's position, unchanged since the console launched in 2020, is that a healthy machine should never need routine maintenance. That is a lovely theory. In practice, a console that spends years hoarding storefront thumbnails, half-applied patches, orphaned license tokens, and a content database that indexes an 8TB drive one row at a time will eventually produce the symptoms every owner recognizes: the store that spins forever, the game frozen on its splash screen, the download welded to 99 percent, the trophies that refuse to sync, the DualSense that lags in the menu but is perfectly fine in-game.

Clearing the cache resolves a genuinely surprising share of these. The catch is that Sony buried the tool in Safe Mode, quietly renumbered the menu across firmware revisions, and left roughly half the internet pointing you at the wrong option. As of this writing the current firmware is 26.05-13.60.00, released July 23, 2026. The procedure costs nothing, requires no PlayStation Plus subscription, deletes zero saves, and takes about ten minutes end to end. What follows is the long version - the one that actually gets the numbers right, explains why every step exists, and tells you which of the four things people call 'the cache' you are actually clearing.

What Clearing Cache Actually Means

Before you touch a power button, understand that 'clear the cache' is doing a lot of quiet work as a phrase. On a PS5 there is no single cache. There are at least three distinct layers of transient data, plus a fourth that lives inside individual games, and the fix for each is different. Guides that treat them as one thing are the reason people clear the wrong layer and conclude the whole exercise is a placebo.

Three Layers, Not One

The first layer is the volatile DRAM cache - runtime state held in the console's RAM. It stores things like the HDCP handshake with your television, controller pairing state, and audio routing. It evaporates the instant the console loses power, which means you clear it for free with a full cold boot. No Safe Mode required. This is the layer responsible for the classic 'turn it off and on again' cure.

The second layer is the system software cache - persistent scratch data the operating system parks on the SSD between sessions. Shader caches, storefront and UI assets, temporary download fragments, decompression buffers. This is the layer that Safe Mode's 'Clear System Software Cache' actually wipes, and it is the one most people mean when they say the store or the UI has gone strange.

The third layer is the content database - Sony's master index of everything installed on the machine: games, apps, media, and save metadata. It is not strictly a cache, but Sony groups it with one, and the 'Rebuild Database' sub-option regenerates it from scratch by rescanning the drive. On a PS5, whose SSD is roughly fifteen times faster than the PS4's mechanical drive, that scan is quick on an empty console and slow on a stuffed one.

What the Cache Is Not (Your Saves Are Safe)

Here is the sentence that should defuse most of the anxiety online: clearing the system software cache does not delete your games, your saves, your licenses, your screenshots, your account, your friends, or your settings. It removes disposable operating-system scratch data. The console rebuilds that data the next time it needs it. The persistent myth that clearing the cache 'resets your home screen layout' traces back to a handful of Reddit threads that conflated it with a Rebuild Database reshuffle - a different sub-option with a different, and still non-destructive, effect. Neither operation touches a save file.

The genuinely destructive tools do exist in the same Safe Mode menu, which is precisely why people get nervous. 'Restore Default Settings', 'Reset PS5', and 'Reset PS5 (Reinstall System Software)' will, respectively, revert your configuration, wipe the console, and nuke it back to a factory image. They sit one or two menu positions away from the cache tool. Respect the distance and you will be fine.

When Clearing Actually Helps

Clearing the cache is a targeted remedy, not a tune-up. It helps when the PlayStation Store loads blank tiles or spins indefinitely; when a game hangs on its logo and never reaches the main menu; when a download or update stalls at a fixed percentage; when trophies will not sync; when audio drops out or an HDMI handshake fails after switching inputs; and when the interface itself feels sludgy in menus. Engadget frames it accurately as a short-term remedy - useful for software gremlins, useless against failing hardware. What it will not do is raise your framerate. If a game runs at 30fps, a cache clear leaves it at 30fps; this is a distinctly different problem from the one that separates a base console from a PS5 Pro and its 45 percent faster GPU. Cache is about correctness, not throughput.

Prerequisites: Firmware, Hardware, USB Cable

This is a low-barrier procedure, but three prerequisites trip people up: being on modern firmware, having a cable that actually carries data, and understanding the one real risk before you start. Handle these first and the rest is mechanical.

Firmware and Hardware

Any PS5 works: the original disc and digital editions, the 2023 Slim revision, and the PS5 Pro all share the same Safe Mode layout. You want to be on reasonably current system software so that the menu matches the numbering in this guide. As of writing the latest build is 26.05-13.60.00 (July 23, 2026), the second of two July updates, weighing a little over 1GB and described in Sony's notes as improving on-screen messages and usability - the sort of minor stability patch Sony now ships almost monthly. If you are a version or two behind, that is fine; the cache tool has lived at option 6 since 'Repair Console Storage' joined the menu. You can confirm your version before you begin:

Settings
  > System
    > System Software
      > Console Information

        Model:            CFI-2000  (PS5 Slim, disc)
        System Software:  26.05-13.60.00
        SSD:              1 TB internal (+ M.2 optional)

If that screen shows a PS4-style number like 'Version 7.00' or 'Version 9.00', you are reading fabricated instructions from somewhere - the PS5 has never used those version strings. Real PS5 builds look like 26.05-13.60.00. Push Square and PlayStation LifeStyle both track each release if you want to confirm the current string against a dated source.

The USB Cable Requirement

This is the single most common failure point, so it gets its own subsection. Safe Mode disables Bluetooth. Your DualSense, which pairs wirelessly during normal use, is inert the moment you enter Safe Mode unless it is physically tethered. You need a USB data cable, terminating in USB-C at the controller end. Crucially, a charge-only cable - the kind bundled with cheap accessories - may deliver power without enumerating as a data device, in which case the controller charges but does nothing. Use a known-good data cable. The console's front USB-C or a rear USB-A port both work; the pad wakes when you press the PS button once it is wired.

Back Up First (The One Real Risk)

Clearing the cache is non-destructive. The risk is not the operation - it is the neighbourhood. You will be navigating a menu whose adjacent entries include 'Restore Default Settings' (option 5, directly above your target) and two full-reset options below it. A mis-click during a groggy 2 a.m. troubleshooting session is the realistic threat here, not the cache tool itself. So before you enter Safe Mode, back up saves to PlayStation Plus cloud storage or to a USB drive via Settings, Saved Data and Game/App Settings. It costs five minutes and it turns a catastrophic mis-tap into a shrug. PlayStation's official Safe Mode documentation issues the same warning in its own dry corporate register: some Safe Mode options result in loss of data, so back up first.

The 30-Second Cold-Boot Method

Before you commit to the full Safe Mode ritual, try the free version. A large fraction of the problems people blame on 'a full cache' are actually stale volatile state - the RAM layer - and that clears with a proper power cycle. This is the thirty-second fix, and it is worth ruling out first because it is faster and touches nothing on the SSD.

The Capacitor Drain

Powering the console fully off and unplugging it for a minute does more than the software shutdown does. It drains the residual charge in the power-supply capacitors, which forces every volatile register and the DRAM cache to release. This is why the trick fixes HDCP handshake failures, a controller that will not re-pair, and audio that has gone silent - all of that state lives in RAM, and RAM only truly clears when the charge is gone.

# Full cold boot - the free 'layer one' cache flush

Hold PS button          -> Control Center appears
Select Power icon       -> choose 'Turn Off PS5'
Wait for shutdown       -> fans stop, front light off (~15 s)
Unplug the AC cable     -> leave unplugged 60 seconds
Reconnect AC + boot     -> normal power-on

# Result: volatile DRAM/HDCP/pairing state flushed.
# No SSD data touched. No saves affected.

Why Rest Mode Is Not Off

Every guide worth reading hammers this point, and so will I: Rest Mode is not off. In Rest Mode the console keeps RAM powered, continues background downloads, and maintains USB charging. Nothing volatile clears, and - importantly for the next section - the power button will not invoke Safe Mode from a resting console; it simply wakes it. SlashGear's 2026 explainer specifically warns that if your PS5 slips into Rest Mode by accident, you must wake it and then shut it down completely before retrying anything Safe-Mode-related. Treat Rest Mode as a nap, not a shutdown.

When the Cold Boot Is Enough

If your only symptom was a laggy controller in menus, a black screen after switching TV inputs, a one-off audio dropout, or a controller that would not reconnect, the cold boot alone often fixes it and you can stop here. Escalate to the Safe Mode cache clear when the problem survives a full power cycle - a persistently broken storefront, a game that reliably hangs on launch, a download frozen across reboots. Those live in the SSD-resident system software cache, which the cold boot does not reach.

The 13-Step Safe Mode Walkthrough

This is the core of the procedure. Thirteen steps, each with the reason it exists, because a step you understand is a step you will not fumble. Read the whole list once before you begin - Safe Mode is a text menu with no mouse, and momentum helps. The sequence below matches Engadget's consumer walkthrough and PlayStation's own support flow; it just spells out the rationale they skip.

Steps 1 to 5: Powering Down and Entering Safe Mode

1. Save your work and close every game. Rationale: Safe Mode is a cold entry. Clearing the cache never touches a save file, but a game that is mid-write to its save when you abruptly cut power can corrupt that one file. Reach a clean stopping point first.
2. Fully power off from the Control Center: hold the PS button, open the Power menu, choose 'Turn Off PS5' - not Rest Mode. Rationale: as covered above, the power button only invokes Safe Mode from a genuinely off console. From Rest Mode it just wakes the machine.
3. Wait for the console to go completely dark - fans silent, front light off, roughly 15 seconds. Rationale: pressing the power button while the console is still spinning down can trigger a normal boot instead of Safe Mode, and you will start over confused.
4. (Recommended) Unplug the AC cable for 60 seconds, then reconnect. Rationale: this folds the free cold-boot capacitor drain into the process, clearing the volatile layer before you even reach the menu. Skip it only if you are in a hurry.
5. Press and hold the physical power button on the console. Rationale: Safe Mode can only be summoned from the console itself. There is no controller shortcut and no Settings path - a point where a lot of bad guides invent a contrast with the PS4 that does not exist, because neither console has a menu route into Safe Mode.

Steps 6 to 9: Connecting the Controller and Navigating

6. Listen for two beeps. Release the button immediately after the SECOND beep - roughly 7 seconds in. Rationale: the first beep, at about 0 seconds, is a normal power-on; let go there and the console boots normally. The second beep is the Safe Mode signal. Release a moment too early and you are back to step 2. Seven seconds feels longer than you expect - count it out.
7. Connect your DualSense to the console with a USB data cable (USB-C at the pad). Rationale: Bluetooth is off in Safe Mode. A wireless controller does nothing here; only a wired data connection registers input. If the pad seems dead, suspect a charge-only cable.
8. Press the PS button once to register the wired controller. Rationale: this wakes the pad over USB and binds it as player one so the menu will accept your input. Without this press the on-screen prompt sits there ignoring you.
9. Read the menu and locate 'Clear Cache and Rebuild Database'. On current firmware it is option 6. Rationale: the position shifted across firmware revisions and older guides say option 5 - trust the label, not the number. The next section explains exactly why the count changed.

Steps 10 to 13: Clearing and Verifying

10. Select 'Clear Cache and Rebuild Database', then choose 'Clear System Software Cache'. Rationale: this is the light, safe, seconds-long operation that removes OS scratch data only. Its sibling, 'Rebuild Database', is the heavier tool you probably do not need yet - save it for the specific cases in the Rebuild section below.
11. Confirm with OK. Rationale: this is the point of no return, except there is nothing to undo - no saves, licenses, or installs are affected, so the confirmation is a formality rather than a warning.
12. Let it run. If the console reboots on its own, do not interrupt it. Rationale: a mid-clear reboot is normal and expected. Pulling power during the operation is one of the very few ways to actually cause damage, so keep your hands off the plug.
13. Verify from the home screen: open the PlayStation Store, then launch a recently played game. Rationale: the first store open re-fetches tiles and will be briefly slower - that is the cache rebuilding, not a failure. A clean, prompt game launch confirms the clear did its job.

Here is the whole navigation compressed into a reference card you can glance at while the console is beeping at you:

POWER OFF (controller)
   PS button -> Power -> Turn Off PS5

ENTER SAFE MODE (console)
   press & HOLD the power button
     beep #1  @ ~0 s   -> IGNORE (normal boot)
     beep #2  @ ~7 s   -> RELEASE NOW

CONNECT
   DualSense --USB-C data cable--> console USB port
   press PS button once (wakes the wired pad)

NAVIGATE
    Clear Cache and Rebuild Database
        -> Clear System Software Cache
        -> OK
   (console may reboot itself: let it)

Option 5 or Option 6? The Menu Moved

If you have watched a 2026 YouTube walkthrough or read TechRadar's how-to, you have been told the cache tool is 'option 5' or 'the fifth option'. If you open PlayStation's official support page, it is option 6. Both are describing the same tool. Only one matches the menu currently on your screen, and the discrepancy is the single most confusing thing about this entire procedure. Here is the resolution.

The Menu Grew an Option

Sony inserted a new entry - 'Repair Console Storage' - into the Safe Mode menu at position 3. Everything below it shifted down by one. 'Clear Cache and Rebuild Database', which historically sat at position 5, became position 6. Guides written before the change, or copied from older guides without checking, still say 5. Guides checked against a current console, including Sony's own, say 6. The tool did not move in any meaningful sense; the list around it grew. This is exactly the kind of undocumented reshuffle that makes console troubleshooting feel like folklore, and it is why every careful guide - including this one - tells you to select by label.

Navigate by Label, Not Number

The rule is simple and firmware-proof: ignore the number, read the words. You are looking for the entry that literally says 'Clear Cache and Rebuild Database'. Whether it is the fifth or sixth line on your particular build, the label is stable. This is not pedantry - Sony has demonstrably renumbered this menu at least once, and there is no reason to assume they are done. A guide that hard-codes 'press 5' is a guide with an expiry date. TechRadar and several video tutorials fell into exactly this trap; PlayStation's official Safe Mode reference is the tiebreaker because Sony updates it when the menu changes.

What Each Adjacent Option Does

Since you will be staring at all eight entries, here is the full current menu with a note on which are safe and which will ruin your evening. Learn the two immediately around your target especially: option 5 reverts settings, and option 7 wipes the console.

PS5 SAFE MODE  (firmware 26.05-13.60.00)

 Restart PS5
 Change Video Output
 Repair Console Storage      <- inserted; bumped everything below +1
 Update System Software
 Restore Default Settings    <- one slip above your target
 Clear Cache and Rebuild Database   <<< YOU ARE HERE
     |- Clear System Software Cache    (seconds, safe)
     |- Rebuild Database               (minutes-to-hour, safe)
 Reset PS5                   <- wipes the console
 Reset PS5 (Reinstall System Software)

Clear Cache vs. Rebuild Database

Option 6 is a menu, not a button, and it contains two sub-options that people conflate constantly. 'Clear System Software Cache' and 'Rebuild Database' do different jobs, take wildly different amounts of time, and fix different symptoms. Choosing wrong wastes an hour or fails to fix your problem. Here is how to pick.

What Rebuild Actually Does

'Rebuild Database' does not clear anything in the cache sense. It scans every item on the drive and constructs a fresh content database - the index the OS uses to know what is installed and where. It is the tool for a console that has lost track of itself: games that appear installed but will not launch, a library showing phantom or missing entries, external USB-SSD titles that vanished from the home screen, downloads stuck because the license index desynced. It is completely non-destructive - it re-reads your data, it does not delete it - but it is slow, because a rescan of a large SSD is a lot of I/O.

Clear Cache vs. Rebuild: A Decision Table

Use the light tool first, escalate to the heavy one only if the light tool fails. In practice: clear the cache for interface and store weirdness; rebuild the database for library and install weirdness.

The 8TB Time Cost

Timing is the practical difference. 'Clear System Software Cache' finishes in roughly 10 to 40 seconds plus a reboot. 'Rebuild Database' scales with how full your drive is: a lightly used console rebuilds in a few minutes, but a completely full 8TB M.2 expansion can take the better part of an hour. Modern installs make this worse every year - a single title like the eye-wateringly large GTA 6 preload can eat a hundred-plus gigabytes on its own, and every gigabyte is more to reindex. Do not start a Rebuild ten minutes before you need the console, and never, under any circumstances, pull power partway through - an interrupted rebuild is the rare way to actually corrupt the database you were trying to repair.

Game-Level Caches: Warzone to Rocket League

Sometimes the system cache is fine and a single game is the problem. Individual titles maintain their own shader and asset caches, and those live inside the game's own data, out of reach of Safe Mode. When one specific game misbehaves while everything else is healthy, you clear at the game level, not the system level.

Call of Duty and Warzone

The Call of Duty family is the poster child for shader-cache trouble, because it rebuilds a large shader cache on the PS5 and that cache can corrupt after updates - producing crashes, texture glitches, or a hang on the loading screen. The in-game tools are your first move here: reinstalling shaders and, as a heavier step, restoring the game's factory settings. Both are inside the game's own options, not the console menu.

# Call of Duty (Warzone / Black Ops line)
Options > Graphics  > 'Restart Shaders Installation'
Options > Account & Network > 'Restore Factory Settings'

# Rationale: rebuilds the per-title shader cache the
# PS5 system cache clear does NOT touch.

Fortnite and Rocket League

Not every game exposes a cache button. Fortnite has no native clear-cache control on PS5; the reliable reset is to delete and reinstall, which is safe because progression and cosmetics are account-side, not stored locally. Rocket League is the interesting case: Epic's own support documentation explicitly directs PS5 players hitting the dreaded 'Load Failure' error to clear the console's system software cache via Safe Mode - the exact procedure in this guide. It is one of the rare instances of a publisher officially blessing the Safe Mode cache clear as the fix.

# Rocket League 'Load Failure' - Epic's official PS5 fix
PS5 Safe Mode
  >  Clear Cache and Rebuild Database
       > Clear System Software Cache
       > OK

# Fortnite - no native cache tool
  > delete + reinstall (progress is account-side, safe)

Epic spells this out in its Rocket League Load Failure support article, which is worth citing precisely because it is a first-party source confirming that the generic Safe Mode clear resolves a specific, reproducible game bug.

The Delete-and-Reinstall Nuclear Option

When a single game still will not behave after a system cache clear and its own in-game resets, deleting and reinstalling it is the correct escalation. On a PS5's fast SSD the reinstall is quick, and - this is the part people forget - your save data survives, because saves are stored separately from the game install (in the cloud with PlayStation Plus, and in the console's own save-data storage). You are discarding a corrupted install, not your progress. Reserve this for the one stubborn title; there is no reason to reinstall your whole library.

Expected Output: A Successful Clear

Because Safe Mode gives you almost no feedback, people worry mid-process that something has gone wrong. It usually has not. Here is exactly what a successful clear looks and feels like, so you can tell 'working as intended' from 'actually stuck'.

What You See On-Screen

After you confirm 'Clear System Software Cache' with OK, the screen shows a brief progress indicator, then the console typically restarts on its own. There is no celebratory confirmation dialog - Sony's Safe Mode is aggressively terse. The reboot IS the confirmation. Do not read the self-restart as a crash; it is the expected final step.

> Clearing system software cache...
  [########################] done      (~10-40 s)

> Restarting PS5...
  (screen black ~20 s, single boot chime)

> Home screen loads
  storefront tiles re-fetch on first open  (slower once: normal)
  recently-played game launches cleanly

Timing Benchmarks

Rough numbers so you know when to be patient and when to worry. These are typical, not guaranteed, and depend on model and drive fullness.

How to Confirm It Worked

The proof is behavioural, not a message. Reproduce the symptom that sent you here: if the store loaded blank, open it and watch the tiles populate; if a game hung on launch, launch it and confirm it reaches the menu; if a download was stuck, resume it and watch the percentage move. A cleared cache means the original fault is gone. If the fault survives an otherwise clean clear, the problem was never in the system cache - move to Rebuild Database, or to a game-level or hardware cause, per the troubleshooting table below.

Common Pitfalls and How to Undo Them

Almost every failed cache clear comes down to one of a handful of mistakes, and all of them are recoverable. Here are the ones that actually happen, in rough order of frequency, with the fix for each.

The Power and Input Traps

• Treating Rest Mode as off. The most common failure. The power button will not enter Safe Mode from Rest Mode - it just wakes the console. Fix: hold PS button, Power, 'Turn Off PS5', wait for the light to die completely, then hold the console power button.
• Releasing on the first beep. The first beep is a normal boot. Let go there and the console starts up normally, no Safe Mode. Fix: keep holding through beep one and release on beep two, at about the seven-second mark. Count it out loud if you have to.
• Expecting a wireless controller to work. Bluetooth is off in Safe Mode; an unwired DualSense is dead. Fix: connect a USB-C data cable (not a charge-only cable) and press the PS button once. If it still does nothing, the cable is the suspect.

The Wrong-Option Traps

• Fat-fingering option 5 ('Restore Default Settings') instead of 6. They are adjacent, and 5 reverts your settings. It keeps games and saves, so this is annoying rather than fatal, but you will be reconfiguring the console. Fix: read the label before you press X. If you already triggered it, your saves are intact; just redo your settings.
• Pulling power during a Rebuild Database. The one genuinely damaging mistake - an interrupted rebuild can corrupt the database. Fix: prevention only. Never start a rebuild when you cannot leave the console alone for an hour, and never yank the plug to 'speed things up'.

The Expectation Traps

• Believing it wipes your home screen or saves. It does not. That myth is a conflation with a Rebuild Database reshuffle, and even that does not delete saves. Fix: none needed - your data was never at risk from the cache clear.
• Clearing the cache to 'boost FPS'. 2026 is full of videos promising performance gains. Clearing cache fixes glitches, not framerate. Fix: adjust expectations. If you genuinely want more GPU horsepower, that is a hardware conversation - the kind that separates consoles in a PS5 versus Xbox Series X matchup, not a software cache clear.

Troubleshooting Table

When something goes sideways, work this table before you escalate to anything drastic. Each row is a real, commonly reported symptom, its likely cause, and the concrete fix. Start at the top; the rows are roughly ordered from most to least common.

Boot and Power Issues

Post-Clear Symptoms

When to Escalate to Rebuild or Reset

Advanced Tips: Persistent Storage and DNS

Once you have the basic clear in your muscle memory, a few adjacent techniques handle the problems the standard cache clear misses. These are the tools for the edge cases - disc playback, stubborn storefronts, and knowing when maintenance is actually due.

Persistent Storage (for Blu-ray and HDCP)

The PS5's 4K Blu-ray app maintains its own persistent storage, separate from the system cache, and it is the cache clear people never think to run. When a disc refuses to play, throws an HDCP error, or stalls on the copyright screen, the fix is not Safe Mode - it is clearing the Blu-ray player's persistent storage from within the disc app's own options, then cold-booting both the console and the television so the HDCP handshake re-negotiates from scratch. Disc drive owners should keep this one in their back pocket; digital-edition owners can ignore it entirely. PC Guide's PS5 and PS5 Pro walkthrough is a decent reference if you want the disc-specific steps laid out.

DNS and the Store Cache

Half of 'the store is broken' reports are not local cache at all - they are the console talking to a slow or misrouted content-delivery node. After you have cleared the system cache and the store still loads blank tiles or errors out, change your DNS. Point the console at a fast public resolver and force a fresh lookup; it frequently unsticks a storefront that a cache clear alone could not.

# Fix a store that stays broken after a cache clear
Settings > Network > Settings > Set Up Internet Connection
  > (your connection) > Advanced Settings
     DNS Settings:  Manual
     Primary DNS:   1.1.1.1     (Cloudflare)
     Secondary DNS: 8.8.8.8     (Google)
  > Test Internet Connection, then cold boot

Scheduling Maintenance

Sony's official line is 'clear it when you have a problem', and for most users that is correct - there is no benefit to clearing a cache that is not causing symptoms. But if your console sees heavy daily use, a light preventive cadence does no harm: a cold boot every couple of weeks, a system cache clear each quarter, a database rebuild twice a year or whenever you have just installed something enormous. The one thing to avoid is ritualistic over-clearing - clearing the cache after every single update, as some briefs suggest, is cargo-cult maintenance that wastes your time and rebuilds the exact same cache the console needs anyway.

The Complete Maintenance Configuration

To close, here is the whole thing as one reference - a maintenance schedule, a symptom-to-action map, and a single card you can screenshot. Treat the config block as a checklist, not a literal file; the PS5 has no such thing, but the cadence is exactly what a sane owner should follow.

The Quarterly Cadence

# ps5-maintenance.conf  -  a checklist, not a real file
# The Machine's cadence for a PS5 in daily use (firmware 26.05-13.60.00)

[cold_boot]           every = "2 weeks"    # full off + 60s unplug (volatile layer)
[clear_cache]         every = "3 months"   # Safe Mode  > Clear System Software Cache
[rebuild_database]    every = "6 months"   # Safe Mode  > Rebuild Database
                      or_when = [ "install > 200 GB",
                                  "storefront broken",
                                  "trophies desync",
                                  "games greyed out" ]
[persistent_storage]  clear_when = [ "blu-ray won't play", "HDCP error" ]
[dns_swap]            when = "store blank after cache clear"  # 1.1.1.1 / 8.8.8.8
[full_backup]         before = [ "any Restore/Reset", "major firmware" ]

# HARD RULES - never do these:
#   - pull AC power mid-Rebuild        (corrupts the database)
#   - treat Rest Mode as "off"         (won't enter Safe Mode)
#   - confuse  Restore Default with  Clear Cache
#   - release the power button on beep #1 instead of #2

The Symptom-to-Action Map

If you remember nothing else, remember the escalation ladder: cold boot first (free, thirty seconds), system cache clear second (Safe Mode option 6, first sub-option), database rebuild third (option 6, second sub-option, slow), game-level reinstall for a single misbehaving title, and only then the heavier Safe Mode tools. Ninety percent of problems die on the first two rungs. Climb higher only when a rung below has genuinely failed, and back up before you touch anything labelled 'Restore' or 'Reset'.

The One-Page Reference

Power fully off, not Rest Mode. Hold the console power button to the second beep at about seven seconds. Wire the controller with a USB-C data cable and press PS. Select 'Clear Cache and Rebuild Database' - option 6 on current firmware, whatever the old guides say - then 'Clear System Software Cache', then OK. Let it reboot itself. Total time, about ten minutes; total cost, nothing; total saves lost, zero. For the clean consumer version of these steps, Engadget's PS5 cache guide and Sony's official Safe Mode page are the two references worth keeping; TechRadar's how-to is fine as long as you mentally correct its option number from 5 to 6. Everything else is folklore.