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

There is a genre of console advice that survives entirely on faith. Clear your cache. It gets repeated in Discord servers, in reply guys, in the third comment under every "why is my PS5 lagging" video, and it is repeated with the confidence of a man who has never once measured anything. Somewhere along the way the phrase stopped meaning a specific operation and started meaning perform the ritual and the machine will feel better.

So let us do the unglamorous thing and be precise. On a PlayStation 5 in 2026, clearing the cache is a real, built-in, free operation. It is not in Settings. It does not require a subscription, a paid app, or a USB stick full of homebrew. It lives inside Safe Mode, behind a seven-second hold and two beeps, as option 6 — labeled "Clear Cache and Rebuild Database" — and the specific sub-action you want is Clear System Software Cache. That is the entire secret. The rest of this article is about doing it correctly, understanding what it does and does not fix, and not confusing it with the heavier operation sitting right next to it.

Budget about ten minutes, most of which is waiting for the console to power down and back up. You will need a USB-C data cable and a console that is genuinely off — not resting, off. If you want the short version, jump to the twelve steps. If you want to understand why the video guides disagree with each other (5 vs. 6), why Bluetooth stops working the moment you enter Safe Mode, and why "it'll boost your FPS" is a claim nobody has ever backed with a number, keep reading.

What the Cache Actually Is

The cache, defined without hand-waving

A cache is temporary storage that trades disk space for time. Instead of recomputing or re-fetching something expensive, the system writes the result somewhere fast and reuses it. Your PS5 does this constantly and in several places at once: the system software keeps a cache of store-page assets and UI state; the graphics pipeline keeps compiled shader data so a game doesn't recompile the same shaders on every boot; individual apps keep their own caches of thumbnails, video frames, login tokens, and network responses. None of this is exotic. It is the same principle your browser uses, the same principle a CDN uses, the same principle every operating system since the 1970s has used.

The problem is that caches are, by definition, a bet: the system wagers that the cached copy is still valid. Most of the time it is. Occasionally it isn't — an entry goes stale, a write gets interrupted by a power loss, a partial download leaves a half-formed blob, or two versions of an asset collide after an update. When that bet goes bad you get the symptoms people vaguely call "the PS5 acting up": a store page that spins forever, an app that hangs on its splash screen, a game tile on the Home row wearing the wrong box art. Clearing the cache is nothing more than deleting those temporary files so the system is forced to regenerate them from the authoritative source.

What clearing it actually fixes

Be specific about the wins, because vagueness is how this advice became a cargo cult. Clearing the system software cache is a reasonable first move when: the PlayStation Store or a storefront tile refuses to load; a game or app crashes on launch or freezes on its opening screen; a download is stuck, queued, or reporting the wrong size; a deleted game's icon lingers on Home; or you hit an install or "Load Failure"-style error. That last one isn't hypothetical — Epic's own Rocket League support page tells PS5 players to clear the cache in Safe Mode as the documented fix for its "Load Failure" errors. When a first-party studio publishes "clear your PS5 cache" as an official step, you can treat the operation as legitimate rather than folklore.

What the guides won't quantify

Now the part the videos skate past. A large fraction of 2026 walkthroughs promise that clearing the cache will "boost performance," "reduce lag," or — the boldest — "increase your FPS." Every one of those claims is offered as vibe, never as a number. There is no benchmark, no before-and-after frame-time graph, no methodology. And there is a good mechanical reason to be suspicious: a game's frame rate is bounded by the GPU, the CPU, memory bandwidth, and thermals, not by whether a thumbnail cache exists. If anything, the honest expectation is the opposite of a speed-up in the short term — because once you wipe the shader and asset caches, the console has to rebuild them, so the first launch of a game afterward can stutter or load a beat slower while those caches repopulate. Clearing the cache is a correctness tool, not a performance tool. Treat every "it made my games faster" testimonial as anecdote, because that is exactly what it is.

Prerequisites: Firmware & a Data Cable

Firmware: be current, but don't overthink it

Good news that undercuts half the internet: the cache-clear procedure is essentially firmware-independent. Safe Mode's layout has been stable across the mid-2026 system software line, and the menu label you're hunting for hasn't moved since Sony added it. As of this writing the current build is the July 2026 system software — internally 26.05-13.60.00 — and if yours is older, update it first from a normal boot so you're not troubleshooting a bug a patch already fixed.

While we're here: ignore anyone who tells you your PS5 is "on firmware 7.00" or "9.00." Those are PlayStation 4 version numbers. The PS5 has never used that scheme. Its builds are date-stamped strings like the one above, and you can read yours under Settings, System, Console Information. If a guide confidently cites a PS5 "version 9.00," the author is copy-pasting from a PS4 article and you should weight the rest of their advice accordingly.

Settings > System > Console Information

  Model              CFI-2016 (Slim, disc)
  System Software    26.05-13.60.00
  ...

# If "System Software" shows an older build, update first:
Settings > System > System Software > System Software Update and Settings
  > Update System Software

The cable: why Bluetooth won't save you

Here is the single most common way this ten-minute job turns into a thirty-minute one: people try to navigate Safe Mode with a wireless controller. Safe Mode disables Bluetooth. The moment the console boots into it, your DualSense's wireless link is dead, and pressing the PS button does nothing. You need a USB-C data cable running from the controller to one of the console's USB ports, and it has to be a cable that actually carries data — not one of the charge-only cables that ship with some accessories. If your controller's light bar doesn't respond after you press PS inside Safe Mode, the cable is the first suspect, every single time.

A truly cold console (Rest Mode is not "off")

Safe Mode can only be entered from a fully powered-down console — not Rest Mode. This trips people constantly, because Sony's default power behavior and the orange "resting" glow look, to a tired human at 1 a.m., close enough to "off." They are not. Rest Mode keeps the system in a low-power state so downloads continue and games suspend; the Safe Mode hold sequence won't fire from there. You want the console off: no light, no fan, nothing. We'll cover the exact power-down in the steps, but internalize the distinction now, because "it just booted normally" is almost always "the console was resting, not off."

• Console: any PS5 or PS5 Pro. Sony's Safe Mode flow is identical across the family — the how-to that PC Guide publishes explicitly covers both.
• Firmware: current mid-2026 system software (e.g. 26.05-13.60.00). The procedure doesn't depend on it, but update anyway.
• Cable: a USB-C data cable for the controller. Bluetooth is off in Safe Mode.
• Cost: nothing. No PS Plus, no paid app, no subscription. It is a built-in system function.
• Time: ~10 minutes for a cache clear. A full Rebuild Database is a separate, longer job.

Cache vs. Database: The Distinction

The menu that hides the cache-clear is called "Clear Cache and Rebuild Database," and that name is doing two jobs at once. Inside it are two different operations with two very different costs and purposes. Ninety percent of the confusion in this topic comes from people conflating them.

Clear System Software Cache: the light touch

This deletes the system's temporary files and forces them to regenerate. It is fast — seconds to a minute or two — and non-destructive: your games, saves, screenshots, accounts, and settings are untouched. Sony's own description is terse and honest: choose it "if you're experiencing system feature issues or performance drops." This is the surgical option. If your only symptom is a misbehaving store, a hung app, or wrong box art, this is the whole job. You do not need to rebuild anything.

Rebuild Database: the heavy one

Rebuilding the database is a different animal. It scans every piece of content on the drive and constructs a fresh index of what is installed and where it lives — think of it as defragmenting the console's understanding of its own library rather than defragmenting the disk itself. It does not delete your games or saves, but it is slow: minutes on a nearly empty console, and well over an hour on a packed 8 TB drive stuffed with modern installs. Sony recommends it for deeper symptoms — a game icon that won't leave Home after deletion, or the console failing to see content it should. It is the right tool when the library is confused, not when a cache is merely stale.

Which one you actually want

Decision rule, stated plainly: start with Clear System Software Cache, because it is nearly free in time and can't hurt. Escalate to Rebuild Database only if the cache clear didn't resolve a library-level symptom and you can spare the hour. And here is a myth to bury while we are at it — the claim that "clearing the cache reset my whole Home screen" or "logged me out." That is a Reddit-grade anecdote, and when it happens the culprit is almost always a rebuild reorganizing the library, not the lightweight cache clear. Keep the two straight and you keep your expectations straight.

if symptom in {store won't load, app hangs, wrong box art, stuck download}:
    -> Clear System Software Cache          # seconds, non-destructive
elif symptom in {deleted game still on Home, library not detected}:
    -> Clear System Software Cache first
    -> if unresolved: Rebuild Database       # 1 hour+ on a full 8TB drive
elif console won't boot / storage errors:
    -> Repair Console Storage (option 3)     # different tool entirely
else:
    -> do nothing; the cache is not your problem

Safe Mode: The Hidden Menu

The eight-item menu, in order

Safe Mode is the PS5's minimal boot environment — the equivalent of a PC's recovery console. It loads the least amount of system software needed to perform maintenance, which is precisely why it can clear caches and reinstall firmware without the running OS getting in the way. As of the 2026 system software it presents eight options, and the order matters because the numbering is the source of a genuine internet argument (more on that below). Straight from Sony's official Safe Mode support page, top to bottom:

PS5 SAFE MODE
  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   <-- you are here
        - Clear System Software Cache
        - Rebuild Database
  7  Reset PS5
  8  Reset PS5 (Reinstall System Software)

Note options 7 and 8: those are the nuclear ones that wipe your console. They sit one and two rows below the thing you want. This is another reason to read labels, not muscle-memory a cursor position — a stray press past your target lands you dangerously close to a factory reset.

Why it isn't in Settings

A fair question: if this is a routine maintenance task, why bury it behind a beep sequence instead of putting it in Settings like everything else? Because a cache clear has to happen with the caches not in use. You can't cleanly delete the system's working temp files while the full OS is running and actively reading and writing them. Safe Mode boots a stripped environment where those files are dormant, so they can be removed and regenerated safely. Engadget makes the same point in its how-to: Safe Mode is not reachable from the Settings menu, by design. It is not Sony hiding a feature; it is the feature requiring a context the normal OS can't provide.

The two-beep entry sequence

Entry is a two-stage hold, and confusing the two stages is another classic failure. First you power the console fully off — Sony's instruction is to hold the power button for about three seconds until it shuts down. Then, from off, you press and hold the power button again: you'll hear one beep the instant you press, and a second beep about seven seconds later. Release on that second beep. The console boots into Safe Mode, at which point you connect the controller by USB and press PS. Do not release on the first beep — that just powers the console on normally, which is how people end up back at the Home screen wondering what they did wrong.

POWER-OFF (first):  hold ~3s  ------------------>  console OFF (no light)

SAFE MODE (second): press & hold
    t=0s   BEEP #1  (fires immediately on press)   -- keep holding --
    t~7s   BEEP #2  (release NOW)                  -- Safe Mode boots --

    release on BEEP #1  = normal power-on   (wrong)
    release on BEEP #2  = Safe Mode         (right)

Clearing the Cache in 12 Steps

Here is the whole procedure, end to end, with the reason each step exists — because a step you understand is a step you won't skip. Nothing here costs money, and nothing here deletes your games or saves.

Steps 1–4: Power the console fully down

1. Save and quit whatever's running. Close your game or app to the Home screen. Safe Mode is a cold-boot environment; anything suspended in Rest Mode won't survive the power-down cleanly, and you don't want an interrupted write becoming the next corrupt cache entry.
2. Power the console off — not Rest Mode. Press the power button once and choose "Turn Off PS5," or hold the power button for about three seconds until it shuts down. Safe Mode can only be entered from a full power-off. The orange resting glow is not off.
3. Wait for the indicator light to stop blinking and go dark. The light pulses while the console writes final state to disk, then goes out. Engadget's guide is explicit about waiting for the blinking to stop — start the hold too early and the sequence won't register.
4. Get your USB-C data cable ready. Plug it into a front USB port now, before you start the hold, so you are not fumbling once Safe Mode is up. Bluetooth is disabled in Safe Mode; the controller must be wired.

Steps 5–8: Enter Safe Mode

5. Press and hold the power button. From the fully-off state, hold it down and keep holding. This initiates the Safe Mode boot rather than a normal one.
6. Listen for two beeps. One fires the instant you press; the second comes about seven seconds later. The second beep is the signal that the console is entering Safe Mode, not booting normally.
7. Release on the second beep. Not the first. Releasing on the first beep powers the console into the normal OS, and you'll have to start over.
8. Connect the controller by USB and press the PS button. Plug the DualSense into the console with your data cable and press PS to pair it in wired mode. This is the only way to get input in Safe Mode with Bluetooth off.

Steps 9–12: Clear the cache and confirm

9. Select option 6, "Clear Cache and Rebuild Database." Read the label; don't trust the number blindly (some older guides say 5). The label is stable across firmware; the position shifted when Sony added "Repair Console Storage." More on that next section.
10. Choose "Clear System Software Cache." This is the sub-option that empties the cache. Do not pick "Rebuild Database" unless you specifically intend the hour-long library rebuild. This is the surgical, seconds-long operation you came for.
11. Confirm with "OK." The console asks you to confirm; select OK. It is a one-press guard against an accidental selection — Activision's support write-up calls out this final confirmation explicitly.
12. Let it finish and restart. The clear completes in seconds; the console then returns to the Safe Mode menu. Choose "Restart PS5" (option 1) to boot normally. You are done — the temp files are gone and will regenerate on next use.

Expected Output, Screen by Screen

The PS5 has no terminal, no log you can tail, no exit code. The closest thing to "output" is what each screen says, so here is what you should see at each gate — and what it means if you see something else.

The Safe Mode landing screen

After the second beep and a PS-button press on the wired controller, you land on the eight-item Safe Mode list. If you instead see the normal Home screen, you released on the first beep or the console was in Rest Mode, not off. Back up and repeat the power-down.

[ Safe Mode ]
  Connect the controller using the USB cable,
  then press the PS button.

  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
  7  Reset PS5
  8  Reset PS5 (Reinstall System Software)

The Clear Cache and Rebuild Database sub-menu

Selecting option 6 opens a two-item sub-menu. This is the fork that matters: one is fast and one is slow. Pick the first.

[ Clear Cache and Rebuild Database ]

> Clear System Software Cache      # <-- fast, seconds, non-destructive
  Rebuild Database                 #     slow, up to 1hr+, non-destructive

  --> confirm prompt:
      "Clear the system software cache?"
              [ OK ]     [ Cancel ]

What "done" looks like

There is no progress-bar drama for a cache clear — the operation is quick enough that it often flashes past and drops you back to the Safe Mode menu. That silent return is the success state. Don't go hunting for a "Cache cleared successfully" banner; the PS5 does not editorialize. From there, select option 1, "Restart PS5," and let it boot normally. Your first app or store visit afterward may take a beat longer as fresh cache entries get written — expected, not a bug.

Option 5 or 6? The Numbering War

If you watch three 2026 video guides you may hear three answers about which number to press. One says option 5. One says option 6. A third splits the difference by not saying a number at all. They are not all wrong — they are describing different menu layouts from different points in time, and the reconciliation is genuinely simple.

Where the "5" came from

For most of the PS5's life, Safe Mode was a seven-item menu, and "Clear Cache and Rebuild Database" sat at position 5:

OLD LAYOUT (7 items)
  1  Restart PS5
  2  Change Video Output
  3  Update System Software
  4  Restore Default Settings
  5  Clear Cache and Rebuild Database   <-- "5"
  6  Reset PS5
  7  Reset PS5 (Reinstall System Software)

Every guide and screenshot from that era says "option 5," and those articles never got updated. They are not lying; they are stale.

Where the "6" came from

Sony later inserted Repair Console Storage as a new option 3. Everything below it shifted down by one. "Update System Software" went from 3 to 4, "Restore Default Settings" from 4 to 5, and "Clear Cache and Rebuild Database" from 5 to 6 — which is exactly where the current official support page lists it. One insertion near the top of the list re-numbered everything beneath it. That is the whole mystery.

DELTA:  insert "Repair Console Storage" at slot 3
        => every item below shifts +1
        => Clear Cache and Rebuild Database:  5 -> 6

Why you should ignore the number entirely

The lesson isn't "6 is right and 5 is wrong" — it is that a position is a fragile thing to memorize when Sony can renumber the list with a firmware update. The label is stable. "Clear Cache and Rebuild Database" has read the same for years, regardless of what number precedes it. So the editorial-safe instruction, the one that survives the next menu change, is: read the words, count nothing. If you are on current firmware it is 6; if you are on something older it may be 5; either way you are looking for the same six words.

Six Pitfalls That Waste Your Ten Minutes

Confusing the two sub-options

The number-one mistake: opening option 6 and reflexively selecting "Rebuild Database" because it sounds more thorough, then sitting through an hour you didn't need. If your goal is a cache clear, the sub-option is Clear System Software Cache, full stop. Rebuild is a separate tool for a separate problem. Read both lines before you press X.

Trusting Rest Mode and charge-only cables

Two hardware-adjacent traps account for the majority of "it didn't work" reports. First, the console was resting, not off, so the hold never triggered Safe Mode — power it fully down and wait for the light to die. Second, the controller was on a charge-only cable or on Bluetooth, so it never registered input in Safe Mode — use a USB-C data cable. Between these two you have covered the overwhelming majority of failed attempts.

Releasing on the first beep

The hold is roughly seven seconds and there are two beeps. Let go on the first and you have simply turned the console on. This feels like the procedure "not working" when in fact you exited a beep early. Wait for the second beep, then release.

Expecting a benchmark that never comes

If you clear the cache expecting your frame rate to jump, you will be disappointed, and then you'll clear it again, and again, chasing a number that was never on the table. Cache clearing fixes correctness bugs — stuck stores, hung apps, bad art. It is not a performance mod. The "it boosted my FPS" testimonials are anecdote; treat them as such.

Clearing when the real fix is elsewhere

Not every problem is a cache problem. A console that won't boot or throws storage errors wants Repair Console Storage (option 3), not a cache clear. A network issue wants a router power-cycle and a wired test, not Safe Mode. Reaching for the cache clear as a universal remedy is how you burn twenty minutes without touching the actual cause.

Pulling the plug mid-operation

A cache clear is quick, but if you escalate to a Rebuild Database, do not yank power or force-off during the hour it runs. Interrupting a rebuild is a good way to manufacture the exact database corruption you were trying to fix. If you start it, let it finish — plug into a stable outlet, and if yours is flaky, wait for a better time.

Troubleshooting Table

Symptom, cause, fix

Most failures here are one of a small handful of things, and almost all of them are user-side rather than a broken console. Work down the table before you assume hardware.

When the second beep never comes

Usually this is a grip problem or a console that wasn't fully off. Also possible on an aging unit: a failing power button that registers the hold intermittently. If you can enter Safe Mode sometimes but not others, and you have ruled out Rest Mode, suspect the button hardware rather than your technique.

When nothing improved

If a clean cache clear changed nothing, that is information: your problem was never in the cache. Move up the ladder — Rebuild Database for library confusion, Repair Console Storage for boot and storage faults, a plain network power-cycle for connectivity. Don't re-clear the cache five times expecting a different result; you already know the word for that.

Advanced: Rebuilds & Power-Cycles

When a rebuild is actually worth the hour

Rebuild Database earns its runtime in specific cases: a deleted game whose icon won't leave Home, a library that under-reports installed titles, corrupted-data prompts that survive a cache clear, or Home rows that render inconsistently. It rebuilds the index, not the data, so your saves and installs are safe — but budget the time honestly. On a lightly used console it is minutes; on an 8 TB drive packed with modern installs — a couple of 150 GB open-world games like the ones people were pre-loading around GTA 6's $79.99 launch — it is an hour or more. Start it when you can walk away.

The full power-cycle: the method PS5 inherited

There is an older, blunter cache-adjacent trick worth knowing, because it is what the PlayStation 4 forced you to do. The PS4 had no menu option to clear cache at all — Activision's cross-platform support page documents that the only way to force it was to power the console fully off and unplug the power cord from the back for a minute or two, draining residual state. The PS5 inherited that behavior as a supplement: a genuine cold power-cycle (off, unplug ~30–60 seconds, replug) clears volatile state that even Rest Mode preserves. It is not a substitute for the Safe Mode cache clear, but as a first, zero-risk step for a glitchy console it costs nothing. If you are curious how far the hardware has come since that era, we ran the generational GPU math on PS5 vs. PS4 — the short version is the newer box hides its maintenance behind a friendlier menu, but the underlying "turn it off and on" logic never left.

The cargo cult, and how to inoculate against it

The reason "clear your cache" metastasized into universal advice is that it is safe — it rarely makes things worse, so it gets recommended for everything, and occasionally the thing it was recommended for really was a stale cache, which reinforces the ritual. Break the loop by matching the tool to the symptom. Cache clear for stale temp state. Rebuild for library confusion. Repair Console Storage for boot and storage faults. Power-cycle for volatile glitches. Network reset for connectivity. If you can name the symptom, you can pick the right tool — and you'll stop performing maintenance as superstition. The same discipline applies to the rest of your PlayStation housekeeping; it is the mindset you would bring to getting 1080p Remote Play working in twelve steps rather than randomly toggling settings until something sticks.

The Complete Runbook

The whole procedure in one block

Copy-paste-able, if only the PS5 had a paste buffer. Here is the entire operation as a single runbook you can keep on a phone while you work.

# PS5 CACHE CLEAR — FULL RUNBOOK (2026 firmware)
# Cost: $0.   Time: ~10 min.   Data loss: none.

PREREQUISITES
  [ ] PS5 or PS5 Pro on current system software (e.g. 26.05-13.60.00)
  [ ] USB-C DATA cable for the controller (Bluetooth is OFF in Safe Mode)
  [ ] Console fully OFF (not Rest Mode)

POWER DOWN
  1. Quit game/app to Home
  2. Turn Off PS5 (button once -> "Turn Off PS5", or hold ~3s)
  3. Wait for the indicator light to stop blinking and go dark
  4. Plug the USB-C cable into a front port

ENTER SAFE MODE
  5. Press & HOLD the power button
  6. BEEP #1 on press ... keep holding ...
  7. BEEP #2 (~7s) -> RELEASE here
  8. Connect controller via USB, press PS button

CLEAR THE CACHE
  9.  Select 6: "Clear Cache and Rebuild Database"   (label, not number)
  10. Select "Clear System Software Cache"           (NOT Rebuild Database)
  11. Confirm: OK
  12. Restart PS5 (option 1)

ESCALATION (only if the cache clear didn't fix it)
  - Library confused (ghost icons)  -> Rebuild Database        (~1hr on full 8TB)
  - Won't boot / storage errors     -> Repair Console Storage   (option 3)
  - Volatile glitch                 -> cold power-cycle, unplug 30-60s

A pre-flight checklist

Before you power down, confirm the three things that cause ninety percent of failures: the console is off and not resting; you have a data cable, not charge-only; and you know you are pressing the label, not memorizing a number. Get those right and the other nine steps are just waiting.

How often is sane

Cadence question, answered without superstition: clear the cache reactively, when you have a symptom it plausibly addresses — a hung store, a crashing app, bad art. There is no benefit to a weekly prophylactic cache clear; you are just forcing the console to rebuild temp files it was about to reuse. Treat it as a tool you reach for when something is wrong, not a chore on a calendar. And if you find yourself doing it constantly, the cache isn't your problem — you'll be running this same dance for years yet, because there is no PS6 on the 2026 calendar to bail you out with a fresh box.

The Machine's Verdict

Does it work?

Yes, for what it is actually for. Clearing the PS5's system software cache is a legitimate, Sony-sanctioned, zero-cost operation that resolves a real class of bugs: stale temp state manifesting as stuck stores, hung apps, and wrong artwork. It is endorsed as an official troubleshooting step by parties as different as Activision and Epic, which is about as close to consensus as console-maintenance advice gets. Ten minutes, no money, no data loss.

Do it when — and only when

What it is not is a performance mod, a lag-killer, or a monthly ritual, no matter how many 2026 videos imply otherwise with a straight face and no benchmark. The honest framing — the one every reputable written source (Engadget, MakeUseOf, PC Guide) sticks to and the video hype skips — is that this is practical troubleshooting, not a system tune-up. Clear the cache when you have a symptom it fits. Read the label, not the number. Use a data cable. Wait for the second beep. And when it doesn't fix your problem, take that as a diagnosis rather than a reason to do it again. That is the entire discipline, and it is the difference between maintaining a console and performing a rain dance in front of it.