PS5 Cache 2026: Clear It Right in 12 Steps, 10 Min

There is a particular kind of person who, when a PlayStation 5 starts stuttering, immediately reaches for a factory reset as though the console were a misbehaving router. There is another kind who does nothing, waits, and hopes it heals itself. Both are wrong, and both descend from the same ancestral instinct that had a generation blowing into Nintendo cartridges in 1989 — a ritual that accomplished nothing except depositing corrosive saliva onto the pin connectors. Console maintenance has always been more folklore than engineering. Clearing the cache on a PS5 is one of the rare cases where the folk remedy is also the correct one, provided you do it the way Sony actually documents rather than the way a forum post from 2021 told you to.

Here is the thesis, stated plainly so you can leave now if it is all you needed: clearing the cache on a PS5 is a Safe Mode maintenance action, not a Settings-menu toggle. There is no Clear Cache button hiding in the Settings tree. You cannot do it from the home screen. You have to power the console all the way down, boot into Safe Mode by holding the power button until the second beep, connect a controller with an actual cable, and select Clear Cache and Rebuild Database — the sixth option — then Clear System Software Cache. That is the entire job. It is free, it does not require PlayStation Plus, and it will not touch your saves or your games.

What follows is the long version: what the cache actually is, why clearing it fixes what it fixes, the twelve-step procedure with the reasoning behind every step, the difference between the light action and the heavy one, and a troubleshooting table for when the ritual does not take. Sony's own Safe Mode support page — updated on 18 August 2026 — is the primary source throughout, cross-checked against Activision Support, Asurion, and the German-language guide at Heise online. Where they disagree, we say so.

What Clearing Cache Actually Does

Before you touch the power button, understand what you are about to delete, because the menu bundles two very different operations behind one door and most of the confusion in this topic starts there.

The cache and the database are two different things

The menu Sony makes you use is called Clear Cache and Rebuild Database, and the and is doing real work. These are two separate operations sharing one entrance, and conflating them is the single most common reason people run the wrong one and then complain that clearing the cache did nothing.

The system software cache is scratch space. It is the pile of temporary files the console generates while it runs: shader fragments, decompressed asset chunks, partial downloads, thumbnails, store-page assets, and the general detritus of an operating system that would rather keep something on the SSD than fetch or recompute it. When that scratch space goes stale or internally inconsistent — a half-written file here, a mismatched shader there — the symptoms are the ones everyone recognizes: an app that spins forever and never opens, audio that crackles, a UI that treats every button press as a polite suggestion, a PlayStation Store that refuses to load. Clear System Software Cache deletes that scratch space. The console regenerates it on the next boot from a clean state. Nothing you own lives inside it.

The database is a different animal. It is the index — the console's internal card catalogue of what is installed, where it physically lives on the drive, what belongs to whom, and how the whole thing should be sorted and displayed. When the index drifts out of sync with reality — an entry pointing at a game that finished uninstalling, an icon that never updated, a library that has decided one of your games no longer exists — you do not want to wipe scratch files. You want Rebuild Database, which walks the entire drive, inspects what is actually there, and reconstructs the index from the ground up. That is why the rebuild is slow and the cache clear is fast.

What it actually fixes — and the retro parallel

Clearing the system software cache is the correct first response to transient software misbehaviour: games or apps that will not launch, hangs on the loading screen, stutter that appeared after a big system update, streaming apps throwing errors, the store timing out, downloads that stall at a suspiciously round percentage. None of these are hardware problems, and none are save-data problems. They are the console tripping over its own temporary files, and wiping those files clears the trip hazard.

If you have been near consoles long enough, you already understand this ritual even if you never named it. This is the direct descendant of the PS3's database rebuild, which Sony shipped for exactly the same reason: file systems accumulate cruft, indexes drift, and periodically you need to sweep the floor. Go back further and it is the same instinct that had people reformatting PS1 and PS2 memory cards, deleting the corrupted block that ate a save, curating fifteen precious blocks of storage like a medieval scribe rationing vellum. The difference between then and now is that the modern version is a documented, non-destructive maintenance action rather than a gamble. It is the exact opposite of blowing into a cartridge — a folk remedy that felt productive, achieved nothing, and slowly corroded the contacts. Clearing the cache is the folk remedy that happens to be genuine engineering.

What it will not do — the myths, dismissed

Because misinformation travels faster than a support page, here is what clearing the cache does not do. It does not delete your games. It does not delete your saves. It does not sign you out permanently, revoke licences, or touch your PlayStation Plus status — and you do not need PlayStation Plus to run it; the whole procedure is free and offline. It is not a factory reset; the two Reset PS5 options that sit lower in the same Safe Mode menu are the factory reset, and they are a different, destructive animal entirely.

The most persistent myth is that clearing the cache resets your home-screen layout. It does not. That claim is a forum anecdote, and the confusion is understandable: the heavier Rebuild Database operation can re-sort how content is arranged, because it is literally rebuilding the sort index — but even that re-sorts rather than wipes, and it is not the cache clear. If your home screen looks rearranged after maintenance, you ran the database rebuild, not the cache clear, and nothing was lost. Clearing the system software cache is about as risky as emptying a browser's temporary files, and for the same reasons.

Prerequisites

Physically this is a short list, and it is short on purpose, because Safe Mode is a deliberately austere environment that loads almost nothing.

Hardware you need

• A PS5 — any of them. The launch standard and Digital Edition, the 2023 Slim (standard or Digital), or the PS5 Pro. The procedure is identical across the range; only the disc slot and storage capacity differ, and neither matters here.
• A DualSense controller. The one that came in the box is fine. Its charge level is irrelevant, because you are about to wire it in anyway.
• A USB data cable — not a charge-only cable. This is the part people get wrong. The standard PS5, Slim, and Pro charge the DualSense over USB-C, so you want a USB-C cable (USB-A to USB-C, or USB-C to USB-C, depending on which port you use). It must carry data. Many cheap cables and most bundled charging cables move power but not data, and a power-only cable will happily charge the pad while leaving Safe Mode completely deaf to it.
• Mains power. Obvious, but: do not do this on a console you are about to unplug, and do not run it during a thunderstorm on a circuit you do not trust.

Why wired at all? Because Bluetooth is disabled in Safe Mode. The wireless stack the DualSense normally uses is not loaded in this minimal boot environment. This is the number-one reason a first-timer ends up standing in front of a perfectly healthy console, mashing an unresponsive controller and cursing. In Safe Mode the cable is not optional — it is the only way the console can hear the pad. Every source agrees, from Sony's page to Asurion's 2026 walkthrough, which spells out that the controller must be connected with its USB cable before you press the PS button.

Software and firmware versions

You do not need to install anything. You need to know two things about your firmware, mostly so the internet does not mislead you.

First, PS5 system software in 2026 runs on the 26.0x line, shipped as monthly stability patches — the mid-2026 builds sat in the 26.05 / 13.60.00 range, released 23 July 2026, with a newer monthly patch likely live by the time you read this. You do not need a specific version to clear the cache; the Safe Mode option has existed since launch and the procedure has not meaningfully changed. Sony's official Safe Mode page was last updated on 18 August 2026 and remains the canonical reference.

Second — and this is a trap that plagues copy-pasted guides — ignore any instruction that mentions version 7.00 or version 9.00. Those are PS4 system-software numbers. The PS5 has never used them. Any 2026 guide telling you to check your PS5 for version 9.00 was written by someone laundering an old PS4 article, and you should distrust the rest of it accordingly. If a guide cannot get the platform's version scheme right, it has not seen the console it claims to describe.

Time budget, power, and what to close first

Budget your time by which action you plan to run. Clear System Software Cache is fast — seconds to about a minute, because all it does is delete files and let the console regenerate them. Rebuild Database is slow — anywhere from a couple of minutes on a nearly empty console to roughly an hour on a full 8 TB drive, because it must inspect every installed item. If you have bolted on a large M.2 SSD and stuffed it, plan for the long end.

Before you start, get the console into a clean state. Fully quit any running game rather than leaving it suspended in rest mode. Do not clear the cache in the middle of a download or a system update — let it finish or cancel it deliberately first, because interrupting a system update from Safe Mode is how you turn a five-minute chore into a full reinstall. And make sure the power is stable, because the one genuinely bad moment to lose power is mid-rebuild. A console grinding through half a million games (fine — half a dozen, but it feels like more when you are waiting for something like GTA 6's November 19 launch to finish patching) is a console you do not want to yank the cord on.

The 12-Step Procedure

Twelve steps sounds like a lot for delete some temporary files, and it is, because half the steps are about getting into Safe Mode correctly and the other half are about not fat-fingering a factory reset on the way past it. Every step below has a reason attached. Do them in order.

The twelve steps, in order

Follow the sequence exactly; the rationale for the two trickiest moments is expanded in the subsections beneath this list.

1. Fully power off the console — not rest mode. From the home screen press the PS button, open the Power menu, and choose Turn Off PS5; or hold the physical power button on the front of the console for about three seconds and select Turn Off PS5. Rest mode is not off. Safe Mode can only be armed from a true cold state, and a console in rest mode will simply wake when you press the button instead of arming the sequence. Get this wrong and nothing else works.
2. Wait for the power indicator to go completely dark. Give it several seconds after the light stops pulsing. If the light is still doing anything, the console is still doing something, and pressing the button now will just wake it. Patience here costs five seconds and saves a restart.
3. Press and hold the physical power button — and keep holding. Not a tap. A sustained hold. You are going to hold straight through the first beep, which is the part people cannot bring themselves to do because every instinct screams it beeped, release. Do not release.
4. Ignore the first beep — it is a decoy. That first beep fires the instant you press and only confirms the console registered the press and is beginning a normal boot. If you release here, the PS5 boots to the home screen and you start over. Treat the first beep as the trap it is.
5. Release on the second beep — roughly seven seconds in. Activision's support article pins the hold at about seven seconds to the second beep, which is a good number to count against. The moment you hear that second beep, release immediately. The console displays Preparing to enter Safe Mode and boots the minimal maintenance environment. One beep is a normal boot; two beeps is Safe Mode.
6. Connect the DualSense with a USB data cable. Plug one end into the controller and the other into a USB port on the console. Wired, physically, cable and all — because Bluetooth is off in this environment, the pad is invisible until it is tethered.
7. Press the PS button to bind the controller. The cable is necessary but not sufficient; you still press the PS button once so Safe Mode registers this controller as the active input. If the menu does not respond after you press it, that is your cable or your port, not your console.
8. Read the Safe Mode menu before you touch the D-pad. You are now looking at a numbered list of maintenance options. Do not autopilot. The option you want sits in the middle of the list, and the two most destructive options on the entire console — the factory resets — sit directly below it.
9. Select Clear Cache and Rebuild Database — the sixth option on current firmware. Note the exact label. It is not a generic Clear Cache; it is Clear Cache and Rebuild Database, and on the 2026 26.0x builds it is the sixth entry. Always read the label rather than blindly counting, because Sony has reordered Safe Mode across firmware revisions and the Reset options are its immediate neighbours. Selecting it opens a sub-menu.
10. Choose Clear System Software Cache in the sub-menu. This is the light, fast, non-destructive action — the one you almost always want. It deletes the temporary system files and nothing else. The German guide at Heise names these exactly — Cache leeren und Datenbank neu aufbauen, then Systemsoftware-Cache leeren — if you are ever staring at a non-English console.
11. Confirm with OK. Sony, Activision, and Asurion all end the sequence the same way: a final OK confirmation. The operation runs immediately and usually completes in seconds to a minute; do not panic if it is nearly instant, because there is genuinely little to delete.
12. Let it finish, then restart the PS5 and re-test the original symptom. When it completes, the console returns to Safe Mode or reboots; from Safe Mode, choose Restart PS5. Then — the step everyone skips — actually reproduce whatever sent you here. Launch the app that would not open, load the game that hung. Verifying is how you know whether you are done or need to escalate to a rebuild.

Why the second beep is the whole trick

The entire difficulty of this procedure is compressed into steps three through five, and it is a timing problem, not a technical one. The console gives you two audio cues. The first fires immediately and means normal boot. The second fires around seven seconds later and means Safe Mode. Because the first beep arrives exactly when your instinct expects a result, most failures happen right there: the finger lifts on cue one and the console boots normally. Train yourself to treat the first beep as noise and the second as signal. Count one-thousand-one to one-thousand-seven after you feel the button engage. When in doubt, hold slightly longer rather than shorter — releasing too early drops you to the home screen, which is annoying but harmless, whereas the failure modes on the other side are just as recoverable. There is a rhythm to it, and it becomes automatic after exactly one successful attempt.

Why the controller must be wired

Steps six and seven exist because Safe Mode is a stripped boot environment that does not load the Bluetooth stack. Your DualSense, which normally pairs wirelessly, is simply not on the guest list. This is not a fault, a low battery, or a broken pad — it is by design, and it is the most common false alarm in the entire process. Connect the cable first, then press PS. The cable carries the input; the PS press tells Safe Mode which controller is driving. If nothing happens, ninety percent of the time the culprit is a charge-only cable masquerading as a data cable. Here is the whole flow as one breadcrumb, from a dark console to done:

[ console fully off — power LED dark ]
   ↓ hold POWER ............ BEEP #1  (~0s)   keep holding
   ↓ hold POWER ............ BEEP #2  (~7s)   RELEASE → Safe Mode boots
   ↓ connect DualSense with a USB DATA cable
   ↓ press PS button to bind the controller
   ↓ Safe Mode menu
      →  Clear Cache and Rebuild Database
           → Clear System Software Cache
                → OK  → done

Clear Cache vs Rebuild Database

Behind option six sit two actions with very different weights and very different jobs. Choosing correctly is most of the skill, and the sub-menu looks like this:

Clear Cache and Rebuild Database          (Safe Mode · option 6)
 ├─ Clear System Software Cache           light  · seconds   · safe · DO THIS FIRST
 └─ Rebuild Database                      heavy  · up to ~1h · scans the entire SSD

Clear System Software Cache — the light action

This is the one you reach for first, ninety percent of the time. It deletes the operating system's temporary scratch files and lets the console rebuild them cleanly on the next boot. It is fast, it is safe, and it targets exactly the failure mode most people actually have: transient software misbehaviour. App will not open, audio glitches, UI lag, store errors, a download stuck at a stubborn percentage — this is the tool. Because it only removes regenerable temporary data, there is no meaningful risk. Nothing you own lives in the cache, so nothing you own can be lost by clearing it.

Rebuild Database — the heavy action

Rebuild Database is the sledgehammer, and it solves a different problem. It scans the entire storage drive, examines every installed application and its metadata, and reconstructs the content index from what it actually finds. Use it when the index is wrong: games missing from your library that you know are installed, incorrect or blank icons, content sorted into nonsense, absurd load times that suggest the console is hunting for things it cannot find in its own catalogue. It is non-destructive to your games and saves — it rebuilds the index, it does not delete the content — but it is slow, scaling with how much you have installed: minutes on a lean console, up to roughly an hour on a full 8 TB drive. It can also legitimately re-sort your home screen, because it is rebuilding the sort order; that is expected behaviour, not data loss, and it is the real source of the clearing-cache-rearranged-my-screen myth.

Decision matrix — which, when

If you are unsure, run the light one first, reboot, and re-test; escalate to the rebuild only if the symptom survives. You lose nothing by trying the fast, safe action before the slow one.

IF   stutter · audio glitches · app/store won't open · laggy UI
THEN Clear System Software Cache          (light, ~1 min)

IF   games missing · wrong/blank icons · huge load times · broken library
THEN Rebuild Database                     (heavy, minutes → ~1h)

IF   both, or unsure
THEN light clear first → reboot → re-test → escalate to Rebuild only if needed

The general principle is the one that governs all console maintenance and, frankly, most of computing: apply the least invasive fix that could plausibly work, verify, and escalate only on failure. People who lead with the sledgehammer are the same people who, a generation ago, would have reformatted an entire memory card to fix a single corrupted save.

What You Should See

You cannot screenshot Safe Mode — it exists below the layer that takes screenshots — so here is what the correct path looks like rendered as text, ready to match against your screen so you know you are in the right place.

The Safe Mode menu you should see

After the second beep and the wired controller, you land on the numbered maintenance list. It looks like this, with the target option and its dangerous neighbours marked:

──────────────  Safe Mode  ──────────────
 1  Restart PS5
 2  Change Video Output
 3  Update System Software
 4  Restore Default Settings
 5  (entry varies by firmware build)
 6  Clear Cache and Rebuild Database      ← SELECT THIS
 7  Reset PS5                             ← danger: factory reset
 8  Reset PS5 (Reinstall System Software) ← danger: full wipe
──────────────────────────────────────────

Note the caution baked into the layout: Reset PS5 and Reset PS5 (Reinstall System Software) are the two entries directly beneath the cache option, and they are the genuine factory-reset nukes. This adjacency is exactly why we keep telling you to read the label rather than muscle-memory your way down the list.

The sub-menu and the OK confirmation

Selecting Clear Cache and Rebuild Database drops you into the two-item sub-menu. Choose Clear System Software Cache, and the console asks you to confirm. The confirmation is a plain OK. There is no dramatic progress theatre for the light action — it may complete almost instantly, which is correct, not broken.

→ Clear Cache and Rebuild Database
   → Clear System Software Cache
        "Clear the system software cache?"   [ OK ]   [ Cancel ]
        ...clearing...
        Done. Returning to Safe Mode.

Timings and beep cadence you should expect

The beep cadence is the part worth internalizing, because it is the only feedback you get during the blind portion of the procedure:

press POWER ─┬─ 0s    BEEP #1   normal boot begins   (DO NOT release)
             └─ ~7s   BEEP #2   Safe Mode arming      (RELEASE now)

Clear System Software Cache : seconds → ~1 min
Rebuild Database            : ~minutes → ~1 hour (full 8 TB drive)

If your console makes only one beep and boots to the normal home screen, you released too early — go back to step one. If it powers off entirely, you held too long. There is a rhythm to it, and it is forgiving once you have felt it once.

Common Pitfalls

Almost every failed cache-clear is one of the following. None of them are your console's fault, which is the good news, because it means all of them are fixable in under a minute.

Beep and power pitfalls

Pitfall 1 — Releasing on the first beep. You hear a beep, you let go, the console boots normally, and you conclude Safe Mode is broken. It is not; you released on the decoy. Fix: hold through the first beep and only release on the second, roughly seven seconds in. Count it out if you have to.

Pitfall 2 — Holding too long and power-cycling. Overcorrecting from pitfall one, you clamp the button like it owes you money and the console powers back off. Fix: release the instant you hear the second beep. The window after beep two is generous but not infinite.

Pitfall 3 — Entering from rest mode instead of a cold boot. You turned it off but really left it in rest mode, so the power button just wakes it. Fix: fully power off (Power menu → Turn Off PS5) and wait for the light to go completely dark before you start the hold.

Controller and connection pitfalls

Pitfall 4 — Expecting the controller to work wirelessly. This is the big one. Bluetooth is disabled in Safe Mode, so a wireless DualSense is inert no matter how hard you press the PS button. Fix: connect the controller with a USB cable, then press PS. Every source — Sony, Activision, Asurion — is explicit that the cable comes first.

Pitfall 5 — Using a charge-only cable. The pad's light comes on, so the cable works, but the menu ignores every input. Charge-only cables carry power but no data. Fix: swap to a known USB data cable. If your phone syncs to a computer over it, it carries data; if it came free with a power bank, be suspicious.

Pitfall 6 — A dead USB port or a loose seat. Front ports occasionally get flaky, and a not-quite-seated USB-C plug reads as no connection. Fix: reseat firmly, try the other USB port, and confirm the connector clicks home.

Wrong-option and expectation pitfalls

Pitfall 7 — Hunting for Clear Cache in Settings. There is no such toggle. This is a Safe Mode maintenance action and nowhere else. Fix: stop looking in Settings; it is a Safe Mode job, full stop, as Sony's current wording confirms. TechRadar's guide — first published in January 2022 and last refreshed on 8 August 2026 — still points readers to the same second-beep Safe Mode method for precisely this reason.

Pitfall 8 — Picking a Reset option by accident. The cache option and the two factory-reset options are neighbours. Autopiloting down the list is how someone clears their cache and wipes their console instead. Fix: read the label. You want Clear Cache and Rebuild Database, then Clear System Software Cache. If a screen ever warns you it will delete users or content, you are in the wrong place — back out.

Pitfall 9 — Doing it mid-download or mid-update. Interrupting a system update from Safe Mode can escalate into a reinstall. Fix: finish or cancel any download or system update before you power down to start this.

Troubleshooting

When the fix does not take, the failure is almost always diagnostic — the symptom is telling you which tool you actually needed. Here is the table.

The troubleshooting table

That is ten rows, comfortably past the eight this kind of article owes you, and they cover essentially every way the procedure goes sideways.

When cache clearing is the wrong tool

Clearing the cache is a software-hygiene action, and it is useless against hardware faults. If your console is overheating and shutting down, throwing storage read errors, showing display corruption that survives a reboot, or making noises a fan should never make, no amount of cache clearing will help — you are looking at thermal paste, a failing drive, or an HDMI problem, and the maintenance ritual is a distraction from a repair. Likewise, network problems that live in your router or your ISP will not yield to a cache clear, however satisfying the ritual feels. Match the tool to the failure class: software glitch, software fix; hardware fault, hardware fix.

The escalation path

When cache clearing does not resolve a genuine software problem, escalate in order of increasing invasiveness, verifying at each stop: Clear System Software Cache → Rebuild Database → Restore Default Settings → Reset PS5. Restore Default Settings resets system settings without deleting your games and saves and is a sane intermediate step; the Reset options are the factory nukes and belong at the very end, ideally after you have confirmed a current backup. Never start at the end. The person who factory-resets to fix a stutter is the person who demolishes the house to fix a squeaky door.

Advanced Tips

Once you own the basic ritual, the rest is knowing when to invoke it, which titles provoke it, and what lethal options share the menu.

A sane maintenance cadence

You do not need to clear the cache on a schedule the way some people compulsively purge browser history. The cache exists to make the console faster; nuking it constantly just means the console spends its life regenerating scratch files. The rational cadence is symptom-driven with a light periodic touch: run Clear System Software Cache when something misbehaves, or opportunistically after a run of big system updates, and run Rebuild Database occasionally — quarterly is plenty — if your library has started to feel sluggish or disorganized. Here is that policy as a config you can keep:

# ps5-maintenance.cadence — a schedule, not a superstition
monthly:
  - clear_system_software_cache     # light; e.g. after heavy patch weeks
quarterly:
  - rebuild_database                # heavy; if the library feels sluggish
on_symptom:
  app_won't_open      → clear_system_software_cache
  game_missing_icon   → rebuild_database
  persistent_crash    → clear_cache → restore_default_settings → (last) reset
never:
  - blow_into_the_disc_slot         # this is not 1989

Game-specific triggers

Some games are notorious cache offenders, and their own support teams will tell you to do exactly this. Epic Games explicitly recommends clearing the PS5 cache when Rocket League fails to load — a first-party pointer straight to the same Safe Mode procedure. The live-service giants are the same story: Call of Duty and Warzone accumulate enough local scratch data that Activision maintains its own cache-clearing article, last updated in 2026, mirroring Sony's sequence — the USB controller step and the final OK confirmation included. If a single big live-service title is misbehaving while the rest of the console is fine, clearing the cache is a rational first move before you start deleting and redownloading tens of gigabytes.

The same logic applies to any enormous, frequently patched install. When a game the size of a small operating system updates every week — the fate awaiting anyone who preloads something like GTA 6 for its November 19 launch — the cache is where update cruft accumulates, and a periodic light clear is cheap insurance against launch-day weirdness.

The nuclear options next door

Since you are going to be in Safe Mode anyway, learn the neighbourhood so you never wander into the wrong house. Directly below the cache option live Reset PS5 and Reset PS5 (Reinstall System Software). The first restores the console to factory state, deleting users, games, and saves. The second does that and wipes the system software itself, requiring a reinstall from USB or network — the option of absolute last resort, used when the console will not boot at all. Neither has anything to do with routine maintenance. Know they are there, know they are one slot away from what you want, and treat the whole lower region of the menu as a marked hazard. If you want the broader argument about why console owners tolerate this kind of maintenance friction at all, we laid it out in the console-versus-PC ledger — and if you are weighing whether the PS5 was even a meaningful jump worth maintaining, the PS5's leap over the PS4 lays out the specifics.

The Complete Runbook

Everything above, compressed into a single working configuration you can follow without re-reading the prose. Screenshot it, print it, tape it to the console — whatever gets you through Safe Mode without a Reset accident.

The one-screen runbook

PS5 CACHE-CLEAR RUNBOOK  ·  Safe Mode  ·  firmware 26.0x
=======================================================
PRECONDITIONS
  [ ] DualSense + USB DATA cable (not charge-only)
  [ ] Console idle: no download, no update, no active game
  [ ] Mains power stable

SHUTDOWN
   1. PS button → Power → Turn Off PS5   (or hold front POWER ~3s → Turn Off)
   2. Wait until the power indicator is fully dark

ENTER SAFE MODE
   3. Press & HOLD the front POWER button
   4. BEEP #1 at ~0s ....... keep holding
   5. BEEP #2 at ~7s ....... RELEASE → "Preparing to enter Safe Mode"

CONNECT
   6. Plug the DualSense into the console with the cable
   7. Press the PS button to bind the controller

CLEAR
   8. Select  Clear Cache and Rebuild Database
   9. Select Clear System Software Cache
  10. Confirm OK
  11. Let it finish (seconds → ~1 min); it returns to Safe Mode
  12. Restart PS5 and re-test the original symptom

ESCALATION (only if step 12 still fails)
  Rebuild Database → Restore Default Settings → Reset PS5 (last resort)

The printable checklist

If you want the short-order version — the checklist stripped of all rationale — here it is in one breath, which is also the consensus procedure across Sony, SlashGear (last updated 3 November 2025), and Heise (published 26 August 2025, updated 9 August 2026):

1. Fully power off the PS5 and wait for the light to go dark.
2. Hold the power button; release on the second beep (~7s).
3. Connect the DualSense with a USB data cable; press PS.
4. Select Clear Cache and Rebuild Database (option 6).
5. Select Clear System Software Cache; confirm OK.
6. Restart and re-test. Escalate to Rebuild Database only if needed.

For a leaner, checklist-first companion to this piece — same procedure, less lecture — see our condensed option-6 walkthrough. And because Safe Mode is not the only PS5 maintenance skill worth owning, our step-by-step Remote Play setup covers the other feature people most often fight with.

The verification pass

You are not finished when the cache clear completes; you are finished when the original symptom is gone. Reboot, reproduce the exact failure that sent you here, and watch. If the app opens, the stutter is gone, the store loads — done, and you spent ten minutes to avoid a reinstall. If it persists, you now have a clean, known baseline from which to escalate to a database rebuild, and you have already ruled out the cheapest cause. That is the whole discipline: least invasive fix, verify, escalate. It is the exact opposite of blowing into the cartridge and hoping. The PS5 will misbehave again eventually — they all do — and when it does, you now own the one ritual that actually works.