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

There is no button in the PS5's Settings menu that clears the cache. There never was. Accept that first, because roughly half the walkthroughs on the internet were written by people who never went looking. Sony's own Safe Mode support page, last revised on August 18, 2026, is blunt about it: the option lives in Safe Mode, the low-level maintenance environment you reach by physically holding the power button until the console beeps at you a second time. SlashGear, updating its own guide on November 3, 2025, says it in plainer words: you cannot manually clear the cache from the Settings menu. Everyone who tells you otherwise is describing a menu that does not exist.

The good news is that the real procedure is short, free, reversible, and safe for your saves. The bad news is that it has accreted a decade of folklore: fictitious version numbers, invented menu positions, a stubborn myth that it rearranges your home screen, and an even more stubborn belief that you should perform it after every patch like a votive offering. This tutorial does the actual thing in twelve steps, in under ten minutes of hands-on time, and then spends the rest of its length explaining why each step is there and which pieces of received wisdom to bin. The ritual is easy. The theology around it is where people go wrong. If you want the bare field-card version instead of the seminar, we keep a condensed Option 6 walkthrough for exactly that.

What Clearing the Cache Actually Does

Before you hold down any buttons, it is worth knowing what you are deleting, because the single Safe Mode label the PS5 shows you is doing two very different jobs at once, and almost every argument about this topic collapses the moment you separate them.

Two jobs hiding behind one menu label

The PS5 keeps two distinct piles of transient data. The first is the system software cache: temporary files the operating system writes while decompressing updates, negotiating HDMI and audio handshakes, painting the PlayStation Store, and staging games for launch. That is the "cache" in "clear the cache." It is a scratchpad. Deleting it costs you nothing but the few seconds it takes the OS to regenerate the pieces it still needs on the next boot. The second pile is the content database: an index of every game, save, screenshot, trophy and video clip on your internal SSD and any M.2 expansion drive. That index is what "Rebuild Database" rewrites from scratch. Sony bundles both operations behind one Safe Mode entry called "Clear Cache and Rebuild Database," and that packaging is the root cause of most of the confusion in this entire subject. They are not the same operation, they do not take the same amount of time, and nine times out of ten you want only the first.

What it fixes, and where it lives

Clearing the system software cache is the correct first move for the classic soft failures: a Store page that spins forever, a library that will not populate, post-patch stutter, launch hangs, audio dropouts, and the general feeling that the console has become gummy. Sony's Safe Mode page recommends the "Clear System Software Cache" action specifically for system feature problems and performance drops, and the 2026 how-to circuit echoes it. A widely shared 2026 YouTube walkthrough published on January 11, 2026 frames the path as Safe Mode, then "Clear Cache and Rebuild Database," then "Clear System Software Cache" — which is exactly the nested structure you will see on your own console. What none of these guides can offer you is a Settings shortcut, because there isn't one. On a PS5 the cache option is reachable only from Safe Mode, full stop.

What it cannot touch

Here is the sentence the hype videos skip: a cache clear is a software remedy, and software remedies do not fix hardware. Engadget puts it plainly, calling the cache clear a short-term fix that will not resolve underlying hardware degradation. If your fan is dying, your thermal paste has pumped out, or your SSD is failing, no amount of Safe Mode housekeeping will save you; you will clear the cache, feel better for a day, and watch the symptom crawl back. Treat the cache clear as the cheapest diagnostic you own, not as a cure. It rules software cruft in or out. When both the light clear and the heavy rebuild change nothing, you have learned something valuable: the problem is not in the scratchpad.

Prerequisites: Firmware, Cable, and Patience

This is a ten-minute job that people routinely stretch into an hour because they skipped one of three prerequisites. Sort these first and the rest is mechanical.

The firmware you should be on

As of this writing the current PlayStation 5 system software is 26.05-13.60.00, which Sony shipped on July 23, 2026 as the month's second update. It followed 26.04-13.42.00, released for both PlayStation 5 and PlayStation 5 Pro on July 1, 2026. Note the version format, because it is the fastest way to spot a fabricated guide: PS5 firmware reads YY.0X-major.minor.patch, so a 2026 build starts with 26. Any tutorial that tells you to be on "Version 7.00" or "Version 9.00" is quoting PlayStation 4 numbers at you — the PS5 never used that scheme, and the mistake tells you the author is working from a decade-old copy-paste. You do not need the exact newest build to clear the cache; the option has existed since roughly late 2023. But being current means your menu layout matches this guide, and it means you have already ruled out "an update would have fixed it." Check yours before you power down:

Settings → System → Console Information

  Model:              CFI-2000 series (PS5 Slim)
  System Software:    26.05-13.60.00
  Released:           2026-07-23
  Storage:            2 TB internal (+ optional M.2)
  Cache sub-option:   present (since ~late 2023)

The cable nobody warns you about

In Safe Mode the PS5 disables Bluetooth. Your DualSense, which spends its entire normal life wireless, becomes deaf the moment you enter the maintenance screen, and the console will sit there ignoring every button press until you physically wire the pad in. A 2025 guide is explicit that the controller must be connected by a USB-C data cable in Safe Mode because the wireless link is switched off. The trap inside the trap: it must be a data cable, not a charge-only one. Plenty of the USB-C cables rattling around a living room carry power but no data lines, and they will happily light up the controller's charge indicator while transmitting nothing. If Safe Mode ignores your pad, suspect the cable before you suspect the console. The DualSense takes USB-C at the controller end; the console end can be USB-C or USB-A depending on the cable and port you use.

What you do not need

You do not need PlayStation Plus. You do not need a second controller, a PC, a phone app, a USB stick, or an internet connection. You do not need to back anything up for a plain cache clear, because it touches no game data. This is worth stating because the SEO farms love to bury a free, thirty-second operation under a checklist of things to buy. The only genuine prerequisites are a powered console, a working DualSense, and a USB-C data cable. Everything else is padding. The identical flow applies to the PS5 Pro, incidentally — the maintenance menu does not change between models, a point the PC Guide walkthrough covers for both machines. If you have spent any time in the console's other maintenance corners — say, wrangling the network stack for our Remote Play 1080p setup — the ergonomics here will feel familiar, just lower-level.

The 12-Step Cache Clear (Safe Mode Option 6)

Twelve 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 start; the beep timing in the middle is the only part that rewards rehearsal.

1. Save and quit whatever is running. A cache clear demands a full power-down, and a full power-down is not polite about unsaved progress. Anything you have not committed to a save dies with the shutdown, so close out cleanly first.
2. Power the console fully off — not Rest Mode. Press the power button, hold about three seconds, and choose "Turn Off PS5" from the on-screen prompt. Do not use Rest Mode. This is the single most common failure in the entire procedure: Rest Mode leaves the console suspended with the light glowing amber, and Safe Mode will not engage from a suspended state. Wait until the indicator stops pulsing and the fans go silent.
3. Wait for actual silence. Give it ten seconds after the fans stop. This confirms the machine is genuinely off rather than mid-shutdown. Start the beep-hold too early and you will simply reboot the console normally, which is failure mode number one dressed up as bad luck.
4. Get your USB-C data cable and DualSense ready. Do this now, before your hands are busy holding a power button, because Bluetooth is dead in Safe Mode and a controller you have to hunt for mid-procedure is a controller that makes you start over.
5. Press and hold the power button. This is the physical entry into Safe Mode. There is no Settings path to it — not on the PS5, and not on the PS4 before it. Anyone who frames "no Settings route to Safe Mode" as a PS5 quirk has invented a contrast that never existed; hardware maintenance mode has always been a power-button ritual.
6. Ignore the first beep. Roughly one second after you press, the console beeps once. That first beep is a normal boot beginning. If you release here, you get a normal boot, not Safe Mode. Keep holding.
7. Hold to the second beep — about seven seconds — then release. The second beep, around the seven-second mark, is the Safe Mode signal. Release the button the instant you hear it. This two-beep method is the consistent thread across every credible 2025 and 2026 guide: fully power off, hold to the second beep, land in the maintenance menu.
8. Connect the DualSense by USB-C and press the PS button. The console boots to a screen instructing you to connect a controller with a USB cable and press the PS button. Do exactly that. Until you press PS over the wire, the pad is inert and the menu is frozen.
9. Select "Clear Cache and Rebuild Database." On current firmware this is the sixth item in the list. Select it by its label, not its position, for reasons the numbering section below makes clear. This entry is the door to both maintenance operations.
10. Choose "Clear System Software Cache." Inside that entry you get two choices. Pick the first, "Clear System Software Cache." This is the light, roughly one-to-two-minute operation that deletes the OS scratch files. It is what "clearing the cache" means. Do not touch Rebuild Database yet — you escalate to that only if the light clear does not fix your symptom.
11. Let it finish; do not power off mid-run. The operation is quick, but treat it as do-not-disturb regardless. Interrupting a cache clear is survivable; the habit of yanking power mid-maintenance is not, because the same reflex applied to a Rebuild Database can corrupt the index you were trying to repair.
12. Let the console reboot and verify. The PS5 returns to the standard home screen on its own. Confirm your games, saves, trophies and screenshots are exactly where they were — they will be. If something is missing, you did not run a cache clear; you ran a different, heavier operation, and the troubleshooting table is where you go next.

For reference, here is the full Safe Mode list you will be navigating, as it stands on 2026 firmware:

PS5 SAFE MODE — firmware 26.05-13.60.00

   Restart PS5
   Change Video Output
   Repair Console Storage
   Update System Software
   Restore Default Settings
   Clear Cache and Rebuild Database   ← you want this
   Reset PS5
   Reset PS5 (Reinstall System Software)

And here is what sits behind entry six once you open it — the fork that trips up half the internet:

 Clear Cache and Rebuild Database
      ├─ Clear System Software Cache   (light · ~1-2 min · OS temp files)
      └─ Rebuild Database              (heavy · re-indexes SSD · up to ~1 hr)

The beep timing is the only part worth rehearsing. Read it as a timeline:

# Two-beep boot into Safe Mode (console already fully OFF)

t = 0s     press & HOLD the power button
t ~ 1s     BEEP #1   → normal boot starting  (IGNORE — keep holding)
t ~ 7s     BEEP #2   → Safe Mode  (RELEASE NOW)
           connect DualSense via USB-C data cable
           press the PS button to wake the menu

Expected Output: Beeps, Screens, Confirmations

A tutorial that does not tell you what success looks like is just a list of hopes. Here is what each stage should produce, so you can tell "it worked" from "it did something."

The two beeps, decoded

You are listening for a specific rhythm: a beep almost immediately on press, then silence, then a second beep about six seconds later. One beep and a normal boot means you released too early — the console is now running normally and you start over from a full power-down. No second beep ever arriving usually means the console was in Rest Mode rather than off, so it never truly powered down to begin with. The beep is not decorative; it is the console's only audible state signal during boot, and learning to read it is the difference between a ten-minute job and a frustrated half hour of guessing.

The Safe Mode screen

Land it correctly and you get a stark, low-resolution menu on a plain background — deliberately ugly, because it runs beneath the normal interface. The first thing it shows is an instruction to connect a controller by USB cable and press the PS button. Once you comply, the eight numbered options become navigable. This screen is intentionally joyless. If you are seeing your normal animated home screen with its game tiles and store banners, you are not in Safe Mode; you booted normally and need to try again.

The confirmation and reboot

Select "Clear System Software Cache" and the console works quietly for a minute or two, then reboots itself back to the ordinary home screen. There is no dramatic progress bar for the light clear and no celebratory message — the reboot is the confirmation. Your library, saves, screenshots and trophies are all present and unchanged. Roughly, the on-screen sequence reads like this:

> Clearing system software cache...
> This may take a few moments. Do not turn off the PS5.
> Cache cleared. Restarting...

[console reboots to the standard home screen]
[games, saves, screenshots, trophies: all intact]

If instead you are staring at a lengthy progress bar creeping toward one hundred percent, you did not run the cache clear — you selected Rebuild Database, the heavy operation, which is fine and safe but is not what step ten asked for. Let it finish rather than interrupting it.

Cache Clear vs Rebuild Database vs Factory Reset

Three operations live near each other in Safe Mode, they escalate sharply in cost, and confusing them is how a routine tune-up turns into a data-loss story. Know exactly which lever you are pulling.

Clear System Software Cache — the light touch

This is the one you came for. It deletes temporary OS files and nothing else: no games, no saves, no settings, no accounts. It finishes in a minute or two, needs no backup, and carries essentially no risk. Because it is so cheap, it is the correct first response to nearly every soft symptom — store hangs, sluggish menus, post-update stutter, a game that suddenly refuses to launch. Epic Games, for instance, officially recommends exactly this Safe Mode cache clear to fix Rocket League "load failure" errors on PS5. When in doubt, this is the lever.

Rebuild Database — the SSD re-index

The second sub-option is a different animal. Rebuild Database scans your entire drive and reconstructs the content index from scratch — every game, save, screenshot and clip re-catalogued. It does not delete your data, but it rewrites the map of it, and on a full drive that takes real time: up to roughly an hour on a packed 8TB M.2. Use it when the light cache clear did not help and you suspect the index itself is corrupt: games showing as "corrupted" that are fine, install sizes reading wrong, content that exists but will not appear. One genuine side effect worth flagging, because it feeds a myth: after a rebuild, your home-screen tiles may re-sort, since the interface repaints itself from the freshly rebuilt index. That reshuffle is the rebuild's doing, not the cache clear's — the widely repeated claim that "clearing the cache rearranges your home screen" is a misattributed forum anecdote, and the light cache clear leaves your layout alone.

The nuclear options you should not touch

Below entry six sit "Reset PS5" and "Reset PS5 (Reinstall System Software)." These are factory wipes. They erase everything and exist for selling the console or recovering from catastrophic corruption, not for chasing lag. The reason to be precise about the menu is that a panicked user scanning for "reset the cache" can easily land on "Reset PS5" and detonate their library. There is no cache problem on earth that is solved by a factory reset you did not intend. If you find yourself hovering over entry seven to fix stutter, stop and go back to six. The console is a sealed appliance by design — part of the trade-off we get into in our PC-versus-console breakdown — and that design means the maintenance tools are blunt. Respect the blast radius.

Why Guides Disagree on the Option Number

Search this topic and you will find guides swearing the cache option is number five, others insisting it is number six, and a few confidently placing "Rebuild Database" at number two. They cannot all be right, and understanding why they differ is the thing that inoculates you against following the wrong one.

Why it is six now, and was five before

The Safe Mode list is not frozen; Sony edits it. Older PS5 firmware presented seven maintenance options, with "Clear Cache and Rebuild Database" sitting at position five. Current firmware presents eight, with the same entry at position six. Nothing was renamed — an item was inserted above it, and everything below slid down by one. A 2025 guide that points you to the "sixth" Safe Mode option and a 2024 guide that says "fifth" can both be honest and both be describing the same button; they were simply written against different firmware. This is exactly why SlashGear and the video guides tend to quote the label "Clear Cache and Rebuild Database" rather than a number.

The "Repair Console Storage" insertion

The specific culprit is "Repair Console Storage," which Sony slotted in at position three. Insert one item at slot three and every item from the old slot three onward gains a number: old five becomes new six. That is the entire mystery. It is not a conspiracy, a regional difference, or a sign your console is broken — it is an off-by-one produced by a menu edit, immortalised by every guide that hard-coded the number instead of the name.

Cite the label, not the number

The operational takeaway is a rule you can apply forever: on a menu that Sony reorders between firmware versions, trust the label and never the position. Look for the words "Clear Cache and Rebuild Database," wherever they happen to sit today. And be especially wary of any guide claiming Rebuild Database is a top-level "Option 2" — on current firmware, option two is "Change Video Output," and Rebuild Database is not a top-level item at all; it is a sub-option nested inside "Clear Cache and Rebuild Database." A guide that gets that wrong is a guide that has never opened the menu it is describing. The PS4 handled this differently still — it had no dedicated cache-menu option, forcing a full power-off-and-unplug to flush anything, one of many small divergences we catalogue in our PS5-versus-PS4 hardware comparison.

Common Pitfalls and How to Fix Them

Six ways this goes sideways, and the fix for each. Every one of them is a conceptual mistake rather than a hardware fault, which means every one is avoidable once named.

Confusing Rest Mode with off, and the cable that lies

Pitfall 1 — the amber-light trap. Rest Mode is not off. If the power indicator is glowing amber or slowly pulsing, the console is suspended, and Safe Mode will not engage. Fix: hold power three seconds, choose "Turn Off PS5," and wait for the fans to stop and the light to go fully dark before you begin the beep-hold. Pitfall 2 — the charge-only cable. A USB-C cable that carries power but not data will charge your DualSense while leaving it mute in Safe Mode, because Bluetooth is off and the pad has no data path to the console. Fix: use a known-good data cable; if the controller charges but the menu ignores it, swap cables before you swap anything else.

Fumbling the beep, and reaching for the wrong lever

Pitfall 3 — releasing on beep one. The first beep is a normal boot starting. Let go there and you boot to the home screen, not Safe Mode. Fix: keep holding through the silence to the second beep at about seven seconds, then release. Pitfall 4 — grabbing Reset PS5. Scanning for anything that says "reset" and landing on entry seven wipes the console. Fix: the words you want are "Clear Cache and Rebuild Database." If a menu choice warns about deleting all data, you are in the wrong place; back out.

Believing the folklore, and expecting miracles

Pitfall 5 — the "clear after every update" ritual. There is a superstition that you should flush the cache after every patch. Sony's actual guidance is symptom-driven — do it when you have a problem, not on a calendar. Clearing a healthy cache accomplishes nothing but a reboot and a few seconds of the OS rebuilding files it needed anyway. Fix: run it on symptoms, not schedule. Pitfall 6 — expecting it to fix hardware. If the real problem is a failing fan, degraded thermal paste, or a dying SSD, the cache clear buys you a placebo day and then the symptom returns. Fix: treat a clear that does not stick as evidence the fault is hardware, and pivot to cooling, storage health, or service — as Engadget notes, this procedure does not touch hardware degradation.

Troubleshooting Table: 10 Failure Modes

When something misbehaves, match the symptom to the row. Most of these are the pitfalls above caught in the act; a couple are genuine escalations.

Boot and beep problems

The top of the table covers the ways you fail to reach Safe Mode at all — almost always a timing or power-state error rather than a fault.

Menu and labeling problems

The middle rows are the numbering confusion made concrete — the fix is always to navigate by label.

When it didn't fix anything

The bottom rows are the escalation path — light clear, then heavy rebuild, then hardware.

Advanced Tips for 8TB Drives and Power Users

If you have moved past the basics — a stuffed expansion drive, a firmware-update workflow, or a single misbehaving game — a few refinements save real time.

Timing the rebuild on a full drive

The light cache clear is size-independent; it deletes a small, fixed pile of OS files in a minute or two whether your drive is empty or full. Rebuild Database is not. It scales with content, because it re-catalogues every item, and on a maxed 8TB M.2 packed with hundred-gigabyte open worlds it can run close to an hour. Two practical consequences follow. First, never start a rebuild ten minutes before you need the console; start it when you can walk away. Second, a rebuild that appears frozen near completion is usually just grinding through the largest installs last — a single sprawling world like the endlessly-postponed Grand Theft Auto VI represents a lot of files to index. Patience beats a panicked power-off, which is the one input that can actually corrupt the index.

Pairing cache clears with firmware updates

Sony ships "performance and stability" firmware on a roughly monthly cadence — 26.04-13.40.00 in June, 26.04-13.42.00 on July 1, 26.05-13.60.00 on July 23. Most updates are uneventful. Occasionally a large one leaves stale scratch files behind and the console feels off for a day. The disciplined move is not to pre-emptively clear the cache after every patch — that is the folklore this guide keeps swatting down — but to keep the cache clear in your back pocket as the first response if a specific update introduces stutter. Update first, observe, and only clear if a real symptom appears. You are using the tool as a targeted fix, not a nervous tic.

Game-level caches and their limits

Some problems live below the OS, inside a single title. Rocket League's "load failure" is the canonical example, and Epic's own fix is the Safe Mode cache clear you already know. Activision similarly routes Call of Duty players to cache and file clearing across platforms. The pattern is worth internalising: when exactly one game misbehaves while everything else is fine, a system cache clear is the cheap first swing, and it is often enough.

# Epic's official fix for Rocket League "load failure" on PS5
# epicgames.com → Rocket League → load-failure-errors

1. Fully power down the PS5 (NOT Rest Mode)
2. Boot Safe Mode (two-beep method)
3.  Clear Cache and Rebuild Database
4.     └─ Clear System Software Cache
5. Relaunch Rocket League

The limit: a system cache clear cannot fix a corrupt game install. If clearing the cache does not resolve a single-game fault, the next step is deleting and reinstalling that title specifically, not escalating to a factory reset of the whole console.

The Complete PS5 Maintenance Runbook

Everything above, distilled into a decision procedure you can run without re-reading the article. Print it, bookmark it, or memorise the shape of it.

The symptom-driven decision tree

Start from the symptom, not the tool. Soft symptom — store won't load, menus sluggish, post-patch stutter, one game hanging? Do the light "Clear System Software Cache" first; it is two minutes and zero risk. Symptom persists after the light clear, or you see phantom "corrupted" data and wrong install sizes? Escalate to Rebuild Database and budget up to an hour on a full drive. Symptom survives both? Stop clearing things. You have proven the fault is not software, and the next moves are hardware — cooling, SSD health, or service. Never jump to Reset PS5 for a performance complaint; a factory wipe is for selling the console, not speeding it up.

The cadence reality check

Run this on symptoms, not on a schedule. There is no evidence and no Sony guidance supporting a "clear after every update" habit; the official posture is to reach for maintenance when a problem appears. A quarterly glance is plenty for a healthy console: if nothing is wrong, do nothing. The cache is a scratchpad, not a filter that clogs. Treating it as routine hygiene wastes your time and teaches you nothing, whereas treating it as a diagnostic — run it, see if the symptom clears, learn where the fault lives — turns ten minutes into actual information.

The complete runbook

Here is the whole thing as a single reference block, firmware baseline included:

# PS5 CACHE MAINTENANCE RUNBOOK — 2026
# Firmware baseline: 26.05-13.60.00 (2026-07-23)
# Applies to: PS5 and PS5 Pro (identical flow)

ENTRY (physical only — no Settings path):
  1. Fully power OFF (not Rest Mode); wait for silence
  2. HOLD power → BEEP #1 (ignore) → BEEP #2 (~7s, release)
  3. Wire DualSense via USB-C DATA cable; press PS button

WHEN TO RUN:
  - stutter / hangs after a big patch
  - store or library won't load
  - one game throws "load failure" (e.g. Rocket League)
  - audio / HDMI handshake glitches

LIGHT (do this first):
  Safe Mode →  Clear Cache and Rebuild Database
            → Clear System Software Cache
  cost: ~1-2 min   risk: none   data loss: none

HEAVY (only if light didn't fix it):
  Safe Mode →  Clear Cache and Rebuild Database
            → Rebuild Database
  cost: up to ~1 hr on a full 8TB   risk: none   data loss: none
  side effect: home-screen tiles may re-sort

DO NOT:
  - use  Reset PS5 for a cache problem (wipes everything)
  - trust the option NUMBER; trust the LABEL
  - expect it to fix failing hardware (Engadget)
  - clear on a schedule; clear on a symptom

SOURCES:
  playstation.com Safe Mode page (updated 2026-08-18)
  slashgear.com PS5 cache guide (updated 2025-11-03)
  engadget.com PS5 cache guide (hardware caveat)

That is the entire discipline. The PS5 cache clear is a two-minute, zero-risk, no-cost operation hidden behind a two-beep ritual and a USB-C cable, mislabeled by half the internet and mythologised by the other half. Do the light clear on a symptom, escalate to a rebuild only if it does not stick, and never mistake either for a factory reset. Everything else is folklore — and folklore, unlike a cache, does not clear itself.