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

Somewhere between "have you tried turning it off and on again" and "ship it back to Sony" lives a maintenance ritual the PS5 hides on purpose: clearing the system software cache. It is not in Settings. It is not a toggle you can flip from the couch. It is buried in Safe Mode, behind a seven-second beep and a wired controller, in a menu Sony would plainly prefer you never open. That obscurity is deliberate, and it is also why roughly every tech outlet on the internet — Engadget, Heise, Asurion, SlashGear — published a near-identical walkthrough across 2025 and 2026. They all describe the same dance because Sony only gave us one to describe.

This guide walks the whole thing end to end: what the cache actually is, why the "boost your FPS" YouTube crowd oversells it, the exact 13-step procedure on current firmware (26.05-13.60.00, which Sony pushed out the same day this was written), and the precise moment at which clearing the cache stops being a fix and starts being denial. The Machine does not do marketing tone. Cache clearing is useful, low-risk, free, and — often — completely pointless. All four of those are true at the same time, and a guide that only tells you the first two is trying to sell you something.

What the PS5 Cache Actually Is

Before you power anything down, it is worth knowing what you are about to delete, because the word "cache" has been so thoroughly abused by phone-cleaner apps and "speed up your console" hucksters that most people assume it is either magic or dangerous. It is neither.

Cache in one sentence

The cache is the pile of temporary files the PS5's operating system writes so it does not have to recompute the same things every time you turn the console on: precompiled shader fragments, decompressed UI assets, thumbnail and box-art bitmaps, cached network handshakes, store front-end scraps, and a hundred other bits of throwaway state. When everything is working, that pile is why the interface feels instant. When part of it goes stale, ends up half-written after an interrupted download, or contradicts a system update that landed underneath it, the exact same cache becomes the reason your library takes eight seconds to draw a row of box art that used to appear the moment you scrolled to it.

Clearing the cache means telling the system to delete that temporary pile and rebuild it from scratch on the next boot. Nothing you care about lives there. Your games, saves, screenshots, trophies, and settings are stored elsewhere on the drive; the cache is scratch paper. That is the single most important fact in this entire article, and it is the reason the operation is safe enough to hand to someone who has never opened Safe Mode in their life. You are erasing the console's short-term memory, not its long-term memory.

Why Sony buried it in Safe Mode

There is no Settings path to this. None. If you have read a guide that claims you can clear the system software cache from the running operating system, that guide is either describing a different console or making it up. Sony gates the operation behind Safe Mode — a minimal recovery environment that loads before the full OS — for the same reason a mechanic drains your oil with the engine off: you cannot safely delete the files the operating system is actively using while the operating system is using them. Safe Mode boots just enough of the system to touch the storage and nothing more, which is why the cache can be cleared cleanly there and nowhere else.

This also debunks a persistent myth. Some 2026 write-ups frame the Safe Mode requirement as a PS5 quirk — "unlike the PS4, there is no Settings shortcut." That is a false contrast. Neither console ever had a Settings-based route into Safe Mode; both require the physical power button. If a fact sheet tells you the PS4 did it differently, treat everything else on that sheet with suspicion.

The symptoms it actually addresses

Engadget's guide lists the honest use cases, and they are worth repeating because they are narrow: lag while navigating the system menus, games that randomly crash back to the Home screen, online connectivity and sign-in problems, and apps that fail to launch after a system update. Notice what is not on that list — no frame-rate complaints, no "my game stutters mid-firefight," no thermal throttling. Those are hardware and software-inside-the-game problems, and no amount of cache clearing touches them. A demanding modern install like the 2026 heavyweight everyone is budgeting $79.99 for will not run one frame faster because you emptied the OS scratch folder. Cache clearing fixes the shell around your games, not the games themselves. Keep that boundary in mind and the rest of this guide will save you a lot of wasted seven-second beeps.

When to Clear Cache (and When Not To)

The best tutorial tells you when to close the tab and do nothing. Cache clearing is a diagnostic step, not routine hygiene, and treating it as a monthly ritual is how you end up cargo-culting a fix for a problem you do not have.

Good reasons to do it

Reach for the cache clear when the console's interface misbehaves in ways that survive a normal restart. Specifically: the dashboard scrolls like it is underwater; the PlayStation Store or your library shows stale, missing, or duplicated tiles; you cannot sign in to PSN despite a working connection; an app that ran fine yesterday now bounces you to Home on launch, usually right after a system update dropped overnight. These are precisely the symptoms of a corrupted or mismatched cache, and they are the reason Epic's support team officially recommends a Safe Mode cache clear for the "load failure" errors that plague Rocket League after updates. When the shell is broken and a plain reboot did not fix it, the cache is a legitimate first suspect.

Bad reasons (the performance myth)

Now the part the algorithm-chasing video guides bury. A wave of 2026 creator content frames cache clearing as a way to "increase performance," "fix lag" in-game, or "boost your FPS." This is, to put it in the politest technically-accurate terms available, nonsense. Clearing OS temporary files cannot raise a game's rendering performance, because the game's rendering performance is a function of the GPU, the CPU, the memory bandwidth, and the code the developer shipped — none of which are stored in the system cache. What these videos are actually measuring, when they measure anything at all, is the placebo of a fresh reboot plus the confirmation bias of a viewer who wanted it to work. If your game runs badly, the cache is the wrong tool. If your console interface runs badly, it might be the right one. The distinction is the entire ballgame.

The 30-second triage

Before you commit to the full Safe Mode procedure, run this triage. First, fully restart the console the normal way (not Rest Mode — more on that shortly) and see if the problem survives; most transient glitches die here and never needed Safe Mode at all. Second, ask whether the problem is the shell or the game — if it is one specific game misbehaving, check for a game patch and verify the install before blaming the OS. Third, ask whether anything changed recently: a system update, a yanked power cable, a storage drive that filled up. Cache corruption almost always has a cause, and if you can name the cause you can usually predict whether clearing it will help. Only if the problem is interface-level, survives a reboot, and is not attributable to a single game's bug should you bother booting into Safe Mode. Everything below assumes you have passed that triage.

Prerequisites and Requirements

This is a ten-minute job with a two-item shopping list, but one of those two items trips up more people than every other step combined. Read this section before you power anything off.

Software: firmware and version numbers

Any current PS5 will do — the original disc model, the Digital Edition, the Slim revision, or the PS5 Pro. The procedure is identical across all of them. What matters is that you are on modern firmware, because the "Clear System Software Cache" sub-option as a distinct choice arrived in the late-2023 firmware era and has been present ever since. As of this writing the current build is 26.05-13.60.00, the second July 2026 update, whose official patch notes read, in full corporate deadpan, "We've improved the messages and usability on some screens." The prior build, 26.04-13.42.00, shipped July 1. Sony pushes these "performance and stability" maintenance updates roughly monthly, so your exact patch number will drift; the layout will not.

A warning about version numbers you will see in the wild: if any guide tells you to "check that you are on System Software Version 7.00" or "Version 9.00," close it. Those are PlayStation 4 version numbers. The PS5 has never used them. Its firmware follows a YY.0X-major.minor.patch scheme — the 26.05 you see today decodes to the fifth tracked branch of the 2026 line. Anyone quoting single-digit PS5 firmware versions is copying a PS4 article and swapping the console name, and you should not trust their menu paths either.

Hardware: the cable is the catch

Here is the requirement that ambushes people. In Safe Mode, Bluetooth is disabled. Your DualSense will not pair wirelessly no matter how many times you mash the PS button. You must physically wire the controller to the console, and the cable has to actually carry data — a charge-only cable will power the light bar and do nothing else. On a standard DualSense the console-end is USB-A (or USB-C on newer front ports) and the controller-end is USB-C. The DualSense Edge and the disc-drive-less models are no different here. This is the number-one reason people give up halfway through, standing in front of a Safe Mode menu they cannot navigate. Have a known-good data cable in hand before you start.

PRE-FLIGHT CHECKLIST -- CLEAR SYSTEM SOFTWARE CACHE
---------------------------------------------------
[ ] PS5 / PS5 Digital / PS5 Slim / PS5 Pro  (any model)
[ ] System software  26.05-13.60.00  (or newer)
[ ] USB-A/USB-C data cable  (NOT charge-only)
[ ] DualSense or DualSense Edge controller
[ ] Console FULLY powered off  (indicator dark, no orange)
[ ] ~10 minutes free; no PlayStation Plus required; no fee
[ ] Optional: note your current HDMI resolution/HDCP,
    in case video output needs re-setting afterward

Time, cost, and what you keep

The cache clear itself is close to instantaneous — one to two minutes including the automatic reboot. Budget ten minutes for the whole ritual once you account for powering down, waiting for the drive to spin down, finding the cable, and booting back up. It costs nothing. It does not require a PlayStation Plus subscription. And critically, it keeps everything: your installed games, saved data, trophies, screenshots, and settings all survive untouched, because — one more time — the cache is scratch paper. That non-destructive nature is exactly what separates this from the two nuclear options at the bottom of the same menu, which we will map next so you never fat-finger the wrong one.

Clear Cache vs. Rebuild vs. Reset

The Safe Mode menu is a loaded gun with the safe options and the destructive options sitting a few pixels apart. Confusing them is the one way to turn a harmless maintenance job into a data-loss event, so this section exists to make sure that never happens to you.

The three-way distinction

Three operations get conflated constantly, and they sit on a spectrum from "trivial" to "catastrophic." Clear System Software Cache deletes OS temporary files and keeps every last thing you own — it is the subject of this guide and the mildest thing in the menu. Rebuild Database is heavier: it scans the entire drive and constructs a fresh index of all your content, which also keeps your data but can take a very long time on a full drive. Reset PS5 is the nuclear option: it wipes user data and returns the console to factory state. These are not interchangeable, and the guides that treat "clear cache" and "reset" as loose synonyms are doing their readers a genuine disservice.

The full Safe Mode menu, mapped

Here is the current Safe Mode layout in full, so you can see exactly where the cache option lives and, just as importantly, what surrounds it. Cache clearing is a sub-option of item 6 — it is not a top-level entry, and it is emphatically not item 2, whatever a certain widely-copied fact sheet claims. Item 2 is Change Video Output. Anyone who tells you Rebuild Database or cache clearing is "option 2" has never actually been in this menu.

PS5 SAFE MODE -- MENU MAP  (firmware 26.05-13.60.00)
----------------------------------------------------
1. Restart PS5
2. Change Video Output
     - Change Resolution
     - Change HDCP Mode
3. Repair Console Storage
4. Update System Software
     - Update from Internet / USB Storage Device
5. Restore Default Settings
6. Clear Cache and Rebuild Database          <-- HERE
     - Clear System Software Cache   (light, ~1-2 min)
     - Rebuild Database              (heavy, up to ~1 hr)
7. Reset PS5                          (WIPES user data)
8. Reset PS5 (Reinstall System Software)  (WIPES all)
----------------------------------------------------
You want 6 -> Clear System Software Cache. Nothing lower.

Why the difference matters

The practical upshot: pick the lightest tool that could plausibly fix your symptom. Clear System Software Cache first, because it is fast and non-destructive. Only escalate to Rebuild Database if the cache clear did not help and your symptom is index-flavored — the classic tell is a deleted game whose icon stubbornly remains on the Home screen, which is a database problem, not a cache problem, per Sony's own description of the two operations. And be aware of a myth that has circulated since the Starfield era: that clearing the cache "resets your Home screen layout." It does not. Sony does not document that behavior and Engadget does not either. What actually reshuffles your Home row is a full Rebuild Database re-index — a different, heavier operation that people ran in the same sitting and then blamed on the cache. If your tiles move, the rebuild moved them, not the cache clear.

The Full Procedure: 13 Steps

Everything up to now was context. This is the operation. Follow the steps in order; each one carries a short rationale so you understand why it exists rather than blindly obeying a list. The whole thing splits into three phases: power down, boot to Safe Mode, and clear the cache.

Phase 1 — Power down (Steps 1–3)

1. Save and quit everything, then fully close all apps. Rationale: Safe Mode is going to delete files the running system may have open. Backing out cleanly first avoids clearing a cache mid-write, which is how you turn a harmless clean-up into a corrupted temp file that causes the very problem you were trying to fix.
2. Power the console fully off — press the PS button, open the control center, choose Power, and select "Turn Off PS5." Do not choose "Enter Rest Mode." Rationale: this is the trap that sinks more attempts than any other. Rest Mode is not "off"; it is a low-power sleep with the system state preserved in memory, and Safe Mode will not engage from it. The cache you are trying to clear stays exactly where it is. The console must be genuinely powered down, which the guides from Engadget, Heise, and SlashGear all stress in near-identical language for a reason.
3. Wait for the indicator light to go completely dark. Rationale: the drive needs a moment to spin down and the power state to settle. If the light is still pulsing orange, you are in Rest Mode, not off — hold the console's power button for roughly ten seconds to force a full shutdown, then wait again. No orange, no glow, nothing: only then proceed.

Phase 2 — Boot to Safe Mode (Steps 4–7)

POWER-DOWN + SAFE MODE BOOT  (never from Rest Mode)
---------------------------------------------------
t = 0s    Press and HOLD the console power button
t ~ 0s    BEEP #1  -> normal power-on   (KEEP HOLDING)
t ~ 7s    BEEP #2  -> Safe Mode boot    (RELEASE NOW)
          Screen: "Connect the controller using a
                   USB cable, and then press the
                   PS button."

4. Press and hold the power button on the console itself — not the controller. Rationale: you can turn the PS5 off with the controller, but you cannot boot it into Safe Mode with the controller. Safe Mode is a physical-button-only path by design, so it cannot be triggered accidentally by software. Put your finger on the actual console.
5. Keep holding through the first beep, and release only on the second beep — about seven seconds in. Rationale: the first beep is a normal power-on; if you let go there, the console boots straight to the standard dashboard and you have accomplished nothing. The second beep, roughly seven seconds after you started holding, is the Safe Mode signal. Engadget, Heise, and Asurion all cite the same ~7-second, second-beep timing. Count it out if you have to.
6. Wire the controller to the console: data cable into a USB port, USB-C end into the DualSense. Rationale: Bluetooth is off in Safe Mode, so a wireless controller is inert here. The cable must carry data, not just charge. If the light bar flashes but the menu does not respond, your cable is charge-only — swap it. This single requirement is why so many people stall out staring at a menu they cannot move through.
7. Press the PS button to register the controller over USB. Rationale: plugging in is not the same as pairing. The button press is what tells Safe Mode to accept input from this controller. The on-screen prompt — "Connect the controller using a USB cable, and then press the PS button" — is literal, not decorative. Once it registers, the numbered menu becomes navigable.

Phase 3 — Clear the cache (Steps 8–13)

8. Select option 6, "Clear Cache and Rebuild Database." Rationale: this is the gateway to both maintenance operations. It is item six on the list, not item two — ignore any guide that says otherwise, because it has copied its menu order from somewhere that was never in this menu. Selecting it opens the two sub-options.
9. Choose "Clear System Software Cache" — the first, lighter sub-option. Rationale: this is the actual target of this entire guide. It deletes OS temporary files and nothing else. The second sub-option, Rebuild Database, is the heavy re-index you only want if the cache clear fails to help; do not select it now unless you have time to spare and an index-flavored symptom.
10. Read the confirmation dialog, then select OK. Rationale: the console tells you, in writing, that saved data and installed games are unaffected. Reading it is not optional pedantry — it is your last checkpoint to confirm you are on the cache sub-option and not one of the destructive Reset entries a few lines below. Confirm only once you have verified the header says "Clear System Software Cache."
11. Let the console do its thing and restart on its own. Rationale: the cache step is near-instant and typically does not even show a progress bar; the console may blank to black briefly and then reboot. Do not power it off manually during this window. Interrupting a cache operation is one of the few ways to actually cause the corruption you were trying to clear.
12. Sign back in and verify the original problem is gone. Rationale: the whole point was to test a hypothesis — "a bad cache is causing this." Reproduce the steps that triggered your symptom. If the lag, crash, or sign-in failure is gone, you were right and you are done. If it persists, you have learned something valuable: the cache was not the cause.
13. If it is still broken, repeat Steps 1–7 and this time choose Rebuild Database instead — then, if that also fails, stop and move to troubleshooting. Rationale: Rebuild Database is the logical next rung because it addresses the index rather than the temp files, and it is still non-destructive. Budget up to an hour on a large or full drive. If neither the cache clear nor the rebuild fixes it, the cache was never your problem, and continuing to clear it is superstition. The troubleshooting table below is where you go next.

Expected Output: What Each Screen Says

A tutorial that does not show you what success looks like is asking you to guess. Here is exactly what the console presents, so you can match it against your own screen and know, unambiguously, whether the operation took.

The dialog text, verbatim

After you select "Clear System Software Cache" from under option 6, the console presents a confirmation panel. It is deliberately reassuring, and it is worth reading in full because it is the console itself promising you that this is non-destructive:

[ Clear Cache and Rebuild Database ]

   > Clear System Software Cache
     Rebuild Database

----------------------------------------------------
Clear System Software Cache

Deletes temporary system files. Your saved data
and installed games are not affected.

                    [ OK ]      [ Cancel ]

If your screen instead warns you about deleting user data, erasing accounts, or reinstalling system software, stop immediately and cancel — you have drifted down to one of the Reset entries. The cache dialog never threatens your data, because it never touches it.

The sequence after you hit OK

Selecting OK kicks off a short, quiet sequence. There is no dramatic progress bar for the cache step specifically — it is fast enough that Sony did not bother with one — so do not panic at the brief black screen. Here is the expected flow from confirmation to Home:

EXPECTED SEQUENCE AFTER SELECTING "OK"
----------------------------------------------------
1. Brief black screen            (under ~5 seconds)
2. OS temp files deleted         (no bar; near-instant)
3. Automatic restart             (normal PS5 boot chime)
4. Sign-in screen -> Home
   -> No games removed.
   -> No saved data touched.
   -> Settings intact.

How to know it worked

Success here is defined by absence, not by a triumphant confirmation screen — the console does not congratulate you. You know it worked if, after the automatic reboot, the symptom that sent you into Safe Mode is gone: the menus scroll cleanly, the store loads, sign-in completes, the app launches. That is the entire signal. If everything looks normal but your original problem persists, the operation still "succeeded" — the cache was cleared exactly as designed — it just was not the culprit. Do not clear it a second and third time hoping for a different result; a cleared cache is a cleared cache, and repetition changes nothing.

Common Pitfalls and Their Fixes

Every one of these has stranded someone mid-procedure. None of them is complicated once you know the shape of it. Here are the five that account for the overwhelming majority of failed attempts, with the fix for each.

The beep and cable mistakes

Pitfall 1 — releasing on the first beep. You hold the power button, hear a beep, let go, and the console boots to the normal dashboard. You did not do anything wrong except stop early. The fix is discipline: fully power down again and hold through the first beep until the second beep at about seven seconds. If you have trouble judging it, count "one-one-thousand" to seven after you start holding.

Pitfall 2 — the dead controller. You are in Safe Mode, the controller's light bar is on, and nothing on the menu responds. This is almost always a charge-only cable or a Bluetooth-only expectation. Bluetooth is disabled in Safe Mode, full stop, so wireless will never work here. The fix is a known-good data cable, plugged into both the console and the DualSense's USB-C port, followed by a press of the PS button to register it.

The Rest Mode trap

Pitfall 3 — trying to enter Safe Mode from Rest Mode. You "turned off" the console but the light is still glowing orange, and holding the power button does odd things or nothing useful. Rest Mode is a sleep state, not an off state, and Safe Mode will not engage from it. The fix: from the running system, choose Power then "Turn Off PS5" explicitly, or hold the console's power button for about ten seconds to force a hard shutdown. Wait for the light to go fully dark — no orange, no white — before you begin the seven-second hold. This is the single most common failure in the entire procedure, which is why three separate major guides call it out by name.

The "it did nothing" pitfall

Pitfall 4 — expecting a performance miracle. You cleared the cache to "boost FPS" or fix in-game stutter, and unsurprisingly, nothing changed. The cache does not govern game performance; the GPU and the game's own code do. The fix is to redirect your effort: check for a game patch, verify the install, look at your storage and thermals. If your console is genuinely slower than it should be across the board, that is a different investigation than a cache clear — and worth understanding how the PS5's custom SSD, roughly 15x faster than the PS4's drive, is supposed to behave when it is healthy.

Pitfall 5 — clearing the cache repeatedly. It did not work the first time, so you did it three more times. A cleared cache is already empty; clearing an empty cache accomplishes exactly nothing, and each repetition just wears down your patience. The fix is escalation, not repetition: move up to Rebuild Database once, and if that fails too, accept that the cache was never the problem and consult the troubleshooting table. Doing the same harmless thing over and over and expecting a different outcome is not maintenance; it is a coping mechanism.

Troubleshooting Table

When the procedure itself misbehaves — or when it runs perfectly and your symptom survives anyway — this table maps the observation to its most likely cause and the correct next move. Work top to bottom; the boot-and-controller failures are the ones you will hit most often.

Reading the table

The left column is what you actually observe, not what you assume is wrong. Match your symptom there first, then read across. "Escalate" always means move to the next-heaviest tool, never repeat the same one.

Boot and controller failures

The top four rows are the mechanical failures — the ones that stop you before you ever reach the cache option. Every one of them traces back to the same two root causes: the console was not fully off, or the controller could not talk to Safe Mode. Nail those two and the boot phase becomes routine. If you are seeing a black screen instead of the menu (row seven), that is your TV and the console disagreeing about resolution or HDCP; Change Video Output under option 2 is the escape hatch, and it is one of the few legitimate reasons to touch item 2 at all.

When to escalate past cache

The bottom half of the table is where you accept that the cache was a red herring. A stuck game icon is a database problem. A drive that will not finish rebuilding is a capacity-and-patience problem, not a fault. A looping cache operation points at genuinely corrupted system files, which is a firmware reinstall's job, not a cache clear's. Recognize when your symptom has walked out of cache territory and stop trying to solve a plumbing problem with a dust cloth.

Does It Actually Fix Anything?

Time for the honest accounting, because a guide that only tells you how to do a thing and never whether it was worth doing is half a guide.

What the evidence says

Cache clearing genuinely fixes a specific, real class of problems: interface-level glitches caused by stale or corrupted temporary files, particularly after a botched update or an interrupted download. Engadget's framing is the most sober in the field and worth adopting as your own — it is "a low-risk way to rule out the simple stuff before you start digging into bigger fixes." That is exactly right. It is a cheap, fast, non-destructive first move that occasionally resolves the problem outright and, when it doesn't, cleanly eliminates one variable so you can stop suspecting it. Epic recommending it for Rocket League load failures is a concrete, documented case of the operation earning its keep.

The hardware it can't fix

Now the ceiling. Engadget is equally blunt that cache clearing does not fix hardware degradation, and neither does anything else in the Safe Mode menu. A dying SSD, a failing fan, a coil-whining power supply, degraded thermal paste — none of these care about your temp files. If your console is crashing under thermal load, artifacting, or throwing storage errors, you are looking at a physical problem, and the most productive thing a cache clear can do is confirm the problem is physical by failing to fix it. Consoles are hardware on a clock; there is no successor on the calendar before roughly 2028, which means the PS5 in your cabinet has to survive on maintenance and honesty about its limits, not on ritual.

The honest verdict

Clearing the PS5 cache is worth doing when the symptom is interface-level and survives a reboot, worth skipping when the symptom is a game's frame rate or a hardware fault, and never worth doing on a schedule for its own sake. It is a diagnostic, not a tune-up. Used that way — as the first, free, harmless step in a real troubleshooting chain — it is one of the more useful hidden tools Sony ships. Used as a superstition, it is a seven-second beep in exchange for nothing. It is the same console whether you are weighing it against a rival that is now separated by a $150 gap or just trying to get your store page to load; maintenance is maintenance, and the cache clear is the cheapest maintenance there is.

Advanced Tips

If you have done this before and want to be systematic about it, here is how to think about cache clearing as one rung on a ladder rather than a standalone spell.

The escalation ladder

Every option in Safe Mode sits on a spectrum from harmless to total. The disciplined approach is to start at the top and stop at the first rung that fixes your symptom — never skip straight to a Reset because a video made it look decisive. Print this and tape it inside the cabinet:

ESCALATION LADDER  (least -> most destructive)
=====================================================
Clear System Software Cache   keeps EVERYTHING
Rebuild Database              keeps everything
Restore Default Settings      resets settings only
Repair Console Storage        scans/repairs the SSD
Reset PS5                      WIPES user data
Reset + Reinstall Software     WIPES everything
=====================================================
Rule: stop at the first rung that fixes it.
Never start below the rung your symptom justifies.

Pairing cache clears with network resets

A large share of "my PS5 is broken" reports are actually network problems wearing an interface costume — sign-in failures, store timeouts, downloads that stall at 99%. If a cache clear does not resolve a connectivity symptom, the highest-value next move is usually not a database rebuild but a network reset: rebuild your internet connection settings, and if you run a custom DNS, temporarily revert to automatic to rule it out. Treat cache-and-network as a paired diagnostic — clear the cache to eliminate stale local state, reset the connection to eliminate stale network state, and only then start suspecting the hardware. Doing both takes fifteen minutes and eliminates two entire categories of cause.

For PS5 Pro and 8TB drives

The procedure is identical on the PS5 Pro — the same option 6, the same sub-options, the same seven-second beep. Where the Pro and any heavily-loaded console differ is Rebuild Database, not the cache clear. On a full drive approaching the 8TB M.2 ceiling, a rebuild re-indexes a genuinely enormous amount of content and can run up to an hour or beyond; that is expected, not a hang, and powering off mid-rebuild is a real way to cause damage. The cache clear, by contrast, is drive-size-independent and finishes in a minute or two regardless of how packed your storage is, because it is only touching the small OS temp partition, not your library. If you are a Pro owner tempted to rebuild "just to be thorough," weigh the hour against the near-certainty that the cache clear already did whatever cheap fixing was available.

The Complete Procedure Reference

Everything above, distilled into a single block you can print, screenshot, or keep open on a phone while you work. This is the whole operation with the reasoning stripped out — the reasoning is above if you need it.

The copy/paste checklist

COMPLETE PROCEDURE -- CLEAR PS5 SYSTEM SOFTWARE CACHE
=====================================================
 0. Save and quit games. Fully close all apps.
 1. PS button -> Power -> "Turn Off PS5"
      (NOT "Enter Rest Mode")
 2. Wait for the indicator light to go fully dark.
 3. Press and HOLD the console's power button.
 4. Keep holding past BEEP #1.
 5. RELEASE on BEEP #2 (~7 seconds in).
 6. Wire the controller: data cable to console,
      USB-C end into the DualSense.
 7. Press the PS button to register it over USB.
 8. Choose option 6: Clear Cache and Rebuild Database.
 9. Choose: Clear System Software Cache.
10. Read the dialog, confirm header, select OK.
11. Let the console restart on its own -- do not
      power off during the operation.
12. Sign in. Reproduce your symptom to verify.
13. Still broken? Repeat 1-7, choose Rebuild Database
      instead (up to ~1 hr). Still broken after that?
      The cache was never the cause -- see the
      troubleshooting table.
=====================================================
Keeps: games, saves, trophies, screenshots, settings.
Cost: nothing. PS Plus: not required. Time: ~10 min.

Firmware and source notes

Verified on system software 26.05-13.60.00, the second July 2026 update, against Sony's own Safe Mode support documentation and cross-checked against Engadget, Heise, Asurion, and SlashGear. All five describe the same Safe Mode workflow, the same ~7-second second-beep timing, and the same "Clear System Software Cache" confirmation. Where a source disagrees with the on-console reality — single-digit PS4-style version numbers, cache clearing listed as "option 2," or claims that it resets your Home layout — the console wins and the source is wrong. Firmware version numbers will drift with Sony's roughly monthly updates; the menu layout in this guide has been stable since the late-2023 firmware era.

Final word

Clearing the PS5 cache is a genuinely good first move and a genuinely bad panacea, and holding both ideas at once is the whole skill. It is free, fast, non-destructive, and hidden in Safe Mode behind a beep because Sony would rather you never needed it. Reach for it when the interface glitches and survives a reboot. Skip it when the problem is a frame rate or a fan. And when it does not work, believe the console instead of the ritual — a cleared cache that changed nothing is not a failure to clear harder, it is information. Take the information and move up the ladder.