PS5 Cache Clear 2026: 12 Steps, 10 Min, Option 6

Somewhere between the people who clear their cache every morning like it's a vitamin and the people who have never once done it in five years of ownership, there is a small, correct answer. Clearing the cache on a PlayStation 5 is a legitimate maintenance task. It fixes a specific, narrow class of problems: menus that stutter, games that refuse to launch, updates that stall for no stated reason, a store that spins forever. It is not a performance mod, it is not a frame-rate cheat, and it is not something you should be doing on a schedule. It is a wrench you reach for when a bolt is stuck.

The catch — and the reason this needs a full article instead of a tweet — is that Sony did not put the wrench in the toolbox. There is no button for this on the dashboard. To clear the system software cache on a PS5 you have to power the console fully off, hold the physical power button until a second beep, plug a controller in with a cable, and navigate a recovery menu called Safe Mode. Every credible source in 2025 and 2026 routes you through exactly that path, from Sony's own Safe Mode documentation to Engadget's how-to. That is the single most defensible fact about this whole procedure: it is a Safe Mode chore, not an in-menu cleanup tool. Internalize that and the rest is timing.

Why Cache Clearing Is a Safe Mode Chore

People arrive at this task expecting a Settings toggle, because every phone, browser, and streaming box on Earth has one. The PS5 does not. If you go digging through Settings looking for a "Clear Cache" line item, you will not find one, and the various forum posts insisting otherwise are describing either a different console or a hallucination. The only supported route is Safe Mode. Understanding why makes the whole ritual less mysterious.

There is no cache button on the dashboard

The system software cache is not user-facing data. It is scratch space the operating system uses while it is running — decoded UI assets, thumbnail data, temporary shader and store artifacts, half-built indexes. Sony's position, reflected in the menu design, is that you should never need to touch it during normal operation. The console is supposed to manage it for you. So the control lives in the recovery environment, next to the other things you only do when something is broken: rebuilding the database, repairing storage, reinstalling firmware. It is filed under "maintenance," not "settings," and that filing decision is the whole reason this is a multi-step procedure instead of a tap.

What the system software cache actually holds

Think of the cache as the console's short-term memory. When you open the dashboard, the OS keeps recently touched art and metadata close at hand so the next open is instant. When you launch a game, temporary files get staged. When you browse the store, product tiles get cached so scrolling is smooth. None of this is your data. Your save files, your installed games, your trophies, your account, your display and audio settings — those live elsewhere, in protected storage, and the cache clear does not touch any of it. This is confirmed flatly by every mainstream guide: PC Guide states clearing the cache "won't erase your saved games, personal data, or game settings," and Engadget says the same. When the cache accumulates stale or corrupt entries, the symptoms are cosmetic-adjacent: lag, hitches, load failures. Purging it forces the OS to rebuild those entries from clean sources.

What clearing it will not fix

Here is where most cargo-cult advice falls apart. Clearing the cache is a short-term remedy for software-state problems. It does not fix hardware. It will not lower a console that is thermal-throttling because of dust in the heatsink. It will not repair a failing SSD or a dying fan. It will not improve your frame rate in a game that is simply demanding — that is a job for the silicon, and if you want to understand how much silicon the PS5 actually has, our breakdown of how the PS5's GPU stacks up against the PS4 is the honest accounting. Cache clearing is triage for a confused operating system, nothing more. If your problem is physical, this procedure is a placebo, and doing it repeatedly is just theater.

Prerequisites: Firmware, Cables, 10 Minutes

Before you power anything down, get three things straight: what firmware you are on, what you are going to hold the controller with, and what state the console needs to be in. Skip any of these and you will end up standing over a beeping console wondering why the controller is dead. None of this requires a PlayStation Plus subscription, and none of it costs money — cache clearing is a free, built-in function.

Firmware: 26.05-13.60.00 or newer

As of August 2026, the current stable PS5 system software is version 26.05-13.60.00, released in July 2026 with the usual "improved messages and usability" boilerplate. Sony ships these stability updates on a roughly monthly cadence, so by the time you read this the trailing digits may have ticked up. That is fine — the Safe Mode layout has been stable across the recent 26.0x line. There is also an August 2026 firmware beta rolling out that mostly concerns the PS5 Pro's PSSR image-quality defaults; it does not change the cache procedure. One historical note for the record: if any guide tells you to check for "System Software Version 7.00" or "Version 9.00," close the tab. Those are PS4 version numbers. The PS5 has never used them; its versioning has always been the YY.0X-major.minor.patch format you see above.

The cable: Bluetooth is dead in Safe Mode

This is the single most common failure point, so it goes in the prerequisites and not buried in troubleshooting. Safe Mode disables Bluetooth. Your DualSense will not connect wirelessly no matter how many times you mash the PS button. You need a data-capable USB cable — the DualSense end is USB-C — running from the controller to one of the console's USB ports. SlashGear is explicit about using a wired DualSense over USB-C before pressing the PS button to continue. Grab the charging cable that came in the box; it works. If you only have a power-only cable lying around, the controller will charge but never enumerate, and you will think Safe Mode is broken when the problem is a two-dollar wire.

State: fully off, not Rest Mode

The console must be genuinely powered off. Not sleeping. Not in Rest Mode. Rest Mode — that amber or orange glow — is a low-power standby, and it is not the correct state for Safe Mode entry. SlashGear calls this out directly, and it matters because the beep sequence behaves differently from a true cold state. Turn the console off from the dashboard: press the PS button, open the Power menu, and choose Turn Off PS5. Then watch the indicator. Per Engadget, the power light blinks for a few moments before the console fully powers down; wait for it to go completely dark before you touch the physical button. That blink-then-dark transition is your green light. Budget about ten minutes for the whole exercise — the cache clear itself is fast, but powering down cleanly and entering Safe Mode is where the clock goes.

# state check — the console must be OFF, not resting.
$ ps5 --power-state
  REST_MODE            # amber glow == WRONG. Rest Mode is not Off.

# turn it off properly (from the controller):
  PS button → Power → Turn Off PS5
# indicator: white blink for a few seconds, then dark.

$ ps5 --power-state
  OFF                  # no light at all. now you may proceed.

The Menu Item, Not the Number

If you read five guides you will see the cache option called "the fifth option," "the sixth option," "option 5," and "the one near the bottom." They are not all wrong. They are describing different firmware revisions, and the disagreement is instructive rather than embarrassing. The rule that survives every revision is simple: navigate by the name of the menu item, not by its position in the list.

The current Safe Mode menu, in order

On current firmware, Sony's own documentation lists eight Safe Mode options in this order:

PS5 Safe Mode — firmware 26.05-13.60.00 (Aug 2026)
  1  Restart PS5
  2  Change Video Output
  3  Repair Console Storage
  4  Update System Software
  5  Restore Default Settings
  6  Clear Cache and Rebuild Database      ← the one you want
       ├─ Clear System Software Cache      # light: seconds–minutes
       └─ Rebuild Database                 # heavy: minutes–~1 hour
  7  Reset PS5                             # DANGER: wipes user data
  8  Reset PS5 (Reinstall System Software) # DANGER: wipes firmware too

So on today's software, Clear Cache and Rebuild Database is the sixth item. Note that it is a container: selecting it opens a second screen with two distinct actions. The one that clears cache is Clear System Software Cache. The other, Rebuild Database, is a different and heavier operation covered in its own section below. Confusing the parent entry with its children is the second-most-common mistake after the dead controller.

Why older guides say "option 5"

In an earlier PS5 layout, "Rebuild Database" was a standalone item sitting at position five, and "Repair Console Storage" lived at the bottom of the list. Sony later reordered the menu, moved Repair Console Storage up to third, and merged cache-clearing and rebuilding into the single "Clear Cache and Rebuild Database" container now at position six. That is why TechRadar describes it as the fifth option down while Sony's current page and Engadget's 2026 walkthrough put it sixth. Neither is lying; they were written against different builds. One 2026 video guide even labels it "option 5" and another labels it "option 6" — same procedure, different firmware or a transcription slip. Read the words on your screen and you will never be wrong.

Clear System Software Cache vs Rebuild Database

Inside the container, the two children do genuinely different jobs. Clear System Software Cache purges the OS's temporary scratch files. It is quick — seconds to a couple of minutes — and it is the correct first response to lag, hitching, and launch failures. Rebuild Database scans the entire drive and constructs a fresh index of everything installed on it; it is slower and belongs to a different symptom class (a library that is disorganized, showing ghost entries, or refusing to display installed content). Both are non-destructive. You will almost always want the cache clear first, because it is cheap and it resolves the majority of soft glitches without making you wait.

The 12-Step Walkthrough

Here is the full procedure, each step with the reason it exists. Follow it in order. The whole thing takes about ten minutes, most of which is waiting for a clean shutdown and holding a button.

1. Save and quit your game, and let cloud sync finish. The cache clear will not delete saves, but you are about to force a cold shutdown, and there is no reason to interrupt an active write. If you have PlayStation Plus, confirm cloud saves are current first. Belt and suspenders.
2. Press the PS button, open the Power menu, and choose Turn Off PS5. Every source agrees this is the correct first action — a real shutdown, not Rest Mode. Rest Mode is a standby state and will not put you into Safe Mode correctly.
3. Wait for the power indicator to stop blinking and go fully dark. Engadget notes the light blinks briefly before the console powers down. Entering the next step too early means you catch the console mid-shutdown and it simply reboots normally.
4. Get a wired DualSense and a data-capable USB-C cable ready. Bluetooth is disabled in Safe Mode, so a wireless controller is useless here. You will need the cable to navigate anything, so have it in hand before you start the beep sequence rather than scrambling for it afterward.
5. Press and hold the physical power button on the console. This begins the boot. From here, timing is the entire game — do not let go early.
6. Ignore the first beep. A single beep sounds the instant you press. That first beep is a normal boot signal. If you release now, the console boots to the dashboard and you start over.
7. Keep holding until the second beep — about seven seconds — then release. The second beep is the Safe Mode signal. Sony and Engadget both time this at roughly seven seconds after the first; MakeUseOf gives a slightly broader five-to-seven-second window. Release on beep two.
8. Connect the DualSense with the USB-C cable and press the PS button. This registers the controller over the wire so you can navigate. If nothing happens, the cable is power-only or not fully seated — swap it before assuming Safe Mode failed.
9. Select Clear Cache and Rebuild Database. On current firmware this is the sixth item, but select it by name. It opens a submenu; you are not done yet.
10. Choose Clear System Software Cache. This is the specific, non-destructive action that clears the cache. Do not pick Rebuild Database here unless that is genuinely what you came to do — it is the slower operation.
11. Confirm by selecting OK. Engadget calls this confirmation step out explicitly. The console begins clearing immediately.
12. Let it finish and restart to the dashboard. The process may restart the console once; that is normal, and you should not interrupt it. When it lands back on the sign-in screen, the cache is clear and you are done.

Safe Mode
  → 6. Clear Cache and Rebuild Database
     → Clear System Software Cache
        → [ OK ]        # confirm. non-destructive.

# UNTOUCHED : saves, installed games, trophies, accounts, settings
# PURGED    : temporary system-software cache (the junk)

Expected Output: Beeps and Boot Times

Because there is no progress bar you can screenshot and no log file you can tail, "expected output" on a PS5 means knowing the sounds and the timing well enough to tell success from a stall. Here is what a clean run looks and sounds like.

The beep-and-blink sequence

The audible feedback is the whole interface for entering Safe Mode, so learn it. One beep on press; hold; a second beep about seven seconds later; release. If you only ever hear one beep and the console boots to your home screen, you released too early — this is not a failure, just a retry. Modeled as a timeline:

# entering Safe Mode is a TWO-beep procedure, not one.
hold POWER (physical button):
  t = 0.0s   *beep*     ← first beep (normal boot). KEEP HOLDING.
  t ≈ 7.0s   *beep*     ← second beep (Safe Mode). RELEASE NOW.

# MakeUseOf window: 5–7s. Sony / Engadget: ~7s to the second beep.
# release on beep #1 → you boot to the dashboard. start over.

What the screen shows

After the second beep you get a mostly black screen with the Safe Mode option list and a prompt to connect a controller with a USB cable and press the PS button. Once the controller is recognized, you navigate the numbered list, drill into Clear Cache and Rebuild Database, pick Clear System Software Cache, and confirm. There is a brief working state, possibly a restart, and then the standard sign-in screen. TechRadar's phrasing is that the console restarts back to the dashboard, ideally with performance back to where it should be. If you land on the dashboard, it worked — there is no separate "success" dialog to hunt for.

How long each path takes

The cache clear itself is quick: seconds to a minute or two, because it is deleting temporary files, not scanning storage. A pseudo-log of a clean run:

[safe-mode] controller: USB link established (bluetooth disabled)
[cache]     clearing system software cache …
[cache]     done.               elapsed 00:00:47
[system]    restarting …
[dashboard] up — sign-in prompt. performance: back to baseline.

If you instead chose Rebuild Database, throw that timing out the window. Rebuild scales with how much of your drive is used — it can run from a few minutes on a near-empty console to roughly an hour on a large, full drive. A rebuild that appears "stuck" for a long stretch on a packed multi-terabyte SSD is very often just working; do not power-cycle it in a panic.

Rebuild Database: The Heavier Sibling

Since it lives in the same menu container and shares a screen with the cache clear, Rebuild Database deserves its own treatment. People conflate the two constantly, and while both are non-destructive, they solve different problems and cost very different amounts of time.

What rebuild actually does

Rebuild Database scans every file on the console's storage and constructs a fresh database describing what is installed and where it lives — a re-index. SlashGear's explainer frames it as a defragmentation-adjacent housekeeping pass for the console's content index. It is the modern descendant of a ritual PS3 and PS4 owners cargo-culted for a decade, and unlike most inherited superstitions this one is actually real and actually useful for the right symptom. It does not delete games or saves; it rebuilds the map that tells the OS where those things are.

When to use it instead of the cache clear

Reach for Rebuild Database when the problem is organizational rather than glitchy: installed games missing from your library, content stuck showing as "corrupted" or half-installed, the library sorting or displaying wrong, or general sluggishness that a cache clear did not resolve. The correct escalation order is cache first, rebuild second. Clear the system software cache, reboot, and see if the problem survives. If it does, and the symptom is library- or index-shaped, then rebuild. Doing it the other way around means waiting up to an hour before trying the thirty-second fix.

Timing on multi-terabyte drives

The single most important expectation to set: rebuild time is a function of used storage, not a fixed number. A lightly loaded console rebuilds in minutes. A console with a large internal drive plus a stuffed M.2 expansion slot — the PS5 supports drives up to 8TB — can take the better part of an hour. During that time the console may look frozen. It is not. Leave it alone. Interrupting a rebuild mid-scan is one of the few ways to turn a harmless maintenance task into an actual problem.

5 Common Pitfalls (and Fixes)

Almost every failed cache-clear attempt traces to one of a handful of mistakes. Here are the five that account for the overwhelming majority, each with the fix.

Releasing on the first beep

The number-one failure. You press, you hear a beep, you let go — and the console boots normally to your dashboard. That first beep is not the Safe Mode signal. Keep holding through it and wait for the second beep about seven seconds in. Fix: press and hold continuously, count to seven or so, release only after beep number two. If in doubt, hold longer rather than shorter; releasing late still lands you in Safe Mode, releasing early does not.

A wireless or power-only controller

The second-most-common pitfall, and the most frustrating because everything looks fine. You are in Safe Mode, but the controller does nothing. Bluetooth is disabled here by design, so a wireless connection will never register. And a charge-only USB cable will power the controller without carrying data, which looks identical to a working setup right up until you press PS and nothing happens. Fix: use a known-good data USB-C cable, seat it firmly at both ends, then press the PS button.

Clearing from Rest Mode

Trying to enter Safe Mode from that amber Rest Mode glow instead of a true power-off. The beep behavior is not reliable from standby. Fix: from the dashboard, PS button → Power → Turn Off PS5, and wait for the light to go fully dark before holding the power button.

Picking the parent entry and stopping

Selecting Clear Cache and Rebuild Database and assuming the job is done. That is only the container. Fix: after selecting it, choose the sub-option Clear System Software Cache, then confirm OK. If you do not reach a confirmation, you have not cleared anything.

Mistaking cache clear for a reset

Some users, spooked by the word "clear," avoid the whole procedure fearing data loss — while others recklessly grab Reset PS5 (option 7) thinking it is a bigger, better cache clear. Both are wrong. Clear System Software Cache and Rebuild Database are non-destructive; Reset PS5 wipes user data and Reset PS5 (Reinstall System Software) nukes the firmware too. Fix: know the difference cold. Options 7 and 8 are not maintenance — they are the demolition crew. Do not confuse the wrench for the wrecking ball.

Troubleshooting: 10 Symptoms and Fixes

When the procedure misbehaves, the cause is almost always mechanical — timing, cabling, or picking the wrong menu item. This table maps the symptom you are staring at to the most likely cause and the fix.

When it is not the cache at all

If you have cleared the cache, rebuilt the database, checked your cabling, and the problem persists, stop clearing things. Persistent crashes in one title point to a bad install. System-wide instability across every game points at storage health or thermals, in which case the honest next steps are Repair Console Storage (Safe Mode option 3, also non-destructive) and, physically, checking that the console is not choking on dust. Cache clearing is a first responder, not a surgeon.

Does the PS5 Pro Change Anything?

Short answer: no. The cache-clearing procedure is identical across every current PS5 SKU. If a guide implies the Pro needs a special method, it is padding.

Identical method across every model

PC Guide's 2026 write-up covers the base PS5 and the PS5 Pro in one breath, presenting a single unified method for both — same Safe Mode, same second-beep entry, same Clear Cache and Rebuild Database container, same non-destructive Clear System Software Cache sub-option. The disc-drive Slim, the digital Slim, and the $899 PS5 Pro all behave the same way here, because Safe Mode and the system cache are firmware-level constructs that do not care which GPU is underneath. If it runs current PS5 software, this procedure applies unchanged.

The August 2026 PSSR beta wrinkle

The one place the Pro diverges is unrelated to caching. The August 2026 firmware beta flips "Enhance PSSR Image Quality" on by default for PS5 Pro owners and extends the upscaler's reach to games that were never explicitly patched for it — the same broad rollout we covered when the upgraded PSSR reached 50-plus games for free. That is an image-quality change, not a maintenance change. Clearing the cache does not touch it and does not need to. If someone tells you to clear the cache to "enable" PSSR, they have crossed two unrelated wires.

Disc, digital, Slim, Pro — same wrench

Because the distinction keeps coming up: the presence or absence of a disc drive changes nothing about this procedure. The disc drive is peripheral hardware; the cache is software. Whether you paid for the optional drive or not, whether you own the original launch unit or the latest revision, the twelve steps above are the twelve steps. There is exactly one method, and you now know it.

Real-World Triggers: Rocket League and Crashes

Abstract advice is easy to ignore, so here are the concrete situations where clearing the cache is the documented, publisher-endorsed fix rather than a shot in the dark.

Epic's Rocket League "Load Failure"

The cleanest real-world example is Epic Games' support documentation, which explicitly instructs PS5 players hitting Rocket League "Load Failure" errors to clear the console's cache via Safe Mode. This matters because it is not an enthusiast blog guessing — it is the game's own publisher naming cache clearing as the remedy for a specific, reproducible error. When a first-party support page routes you to Safe Mode, you can stop wondering whether the procedure is legitimate.

Publisher support docs converge on the same steps

Epic is not alone. Activision Support documents the very same PS5 cache-clearing workflow for its titles, which is quietly significant: it means major publishers are maintaining their own PS5 troubleshooting documentation alongside Sony's, and independently arriving at the identical Safe Mode path. When Sony, Engadget, TechRadar, SlashGear, MakeUseOf, PC Guide, Epic, and Activision all describe the same second-beep-into-Safe-Mode routine, the process is about as consensus-verified as console maintenance gets. There is no secret better method being withheld.

When the cache is not the culprit

The flip side of documented triggers is documented non-triggers. If a game crashes only in one specific level, or only in online multiplayer, or only after a particular patch, that is a content or server problem, not a cache problem, and clearing the cache is a waste of ten minutes. Use the trigger list as a filter: soft, system-wide, recently-appeared glitches are cache-shaped. Sharp, specific, single-title bugs usually are not.

Advanced Tips: Cadence and the Bluetooth Trap

Once you know the procedure, the interesting questions are about restraint and edge cases. Here is what separates competent maintenance from ritual.

How often to actually do this

Almost never on a schedule. Sony's real cadence, reflected across every official touchpoint, is "when you have a problem" — not weekly, not after every update, not as prophylaxis. The internet's insistence that you should clear the cache after every major system update is overstated; the update process already handles what it needs to. Clearing a healthy cache does nothing but force the OS to rebuild files it was perfectly happy with, which if anything makes the next few minutes slightly slower while it re-warms. Treat this like a fire extinguisher: know exactly where it is, and touch it only when there is smoke.

The rest-mode and power-cycle alternative

For the mildest glitches, you do not need Safe Mode at all. A large fraction of "my PS5 feels off" complaints clear up with a plain full power cycle — turn the console entirely off (again, not Rest Mode), wait thirty seconds, and boot it back up. That flushes volatile memory without touching the system software cache and takes under a minute. Try that first. Escalate to the Safe Mode cache clear only when a simple reboot does not stick. It is the cheaper tool, and the disciplined move is to exhaust cheap tools before expensive ones.

The Bluetooth-off gotcha

A genuine 2026 footgun worth knowing: the August firmware line changed how the "Turn Off Bluetooth" accessory setting behaves. If you disable Bluetooth in Settings, the console can no longer enter Rest Mode, and HDMI link support drops as well. This is unrelated to cache clearing but lives in the same neighborhood of "undocumented power-state surprises," and it is exactly the kind of thing that makes a console seem broken when it is behaving as designed. If your PS5 suddenly refuses Rest Mode, check whether Bluetooth got switched off before you go anywhere near Safe Mode. And if you are the type who enjoys knowing where the platform is headed next, our look at when the PS6 actually lands is the sober version of that conversation.

The Complete Working Checklist

Everything above, compressed into one reference you can glance at while the console beeps. Preconditions, the entry sequence, the decision tree for which sub-option to pick, and the two options you must never touch by mistake.

The whole ritual as one config

# ps5-cache-maintenance.conf — the whole ritual on one screen

precondition:
  power_state : OFF            # NOT rest_mode (amber glow)
  controller  : wired_usb_c    # bluetooth is dead in safe mode
  firmware    : 26.05-13.60.00 or newer

enter_safe_mode:
  hold_power_until : "second beep (~7s)"
  then            : "press PS button on the wired controller"

route_by_symptom:
  menus_lag | crash_on_launch | failed_update | load_failure:
    path : "6 → Clear System Software Cache"   # TRY THIS FIRST
    risk : none                                # non-destructive
    time : "under 2 min"

  corrupt_library | missing_installs | index_errors:
    path : "6 → Rebuild Database"              # heavier re-index
    risk : none                                # non-destructive
    time : "minutes … ~1 hour (scales with used storage)"

  wont_boot | storage_errors:
    path : "3 → Repair Console Storage"        # before you Reset
    risk : none
    time : "varies"

never_touch:
  - "7  Reset PS5"                  # wipes EVERYTHING. not a cache tool.
  - "8  Reinstall System Software"  # nukes the firmware too.

The decision tree in one sentence

Full power cycle first; if that fails, Safe Mode → Clear System Software Cache; if the symptom is library-shaped, Rebuild Database; if the console will not boot or shows storage errors, Repair Console Storage; and never, ever confuse any of those with Reset. That single chain covers ninety-plus percent of the situations that send people looking for this article.

The one thing to remember

If you retain nothing else: this is a Safe Mode maintenance task, not a settings toggle. Power off completely, hold to the second beep, wire the controller, select Clear Cache and Rebuild Database by name, choose Clear System Software Cache, confirm OK. Your saves are safe, your games are safe, and in about ten minutes you will know whether the cache was your problem or whether you need to go looking somewhere the wrench does not reach. For the full menu reference and the official beep timing, keep Sony's Safe Mode page bookmarked — it is the one source that updates when the menu does.