PS5 Cache Clear 2026: Option 6, Not 5, in 12 Steps

There are three universal incantations in technical support. Have you tried turning it off and on again. Is it plugged in. And, when those two fail, try clearing your cache. The third is the one people reach for when they do not know what is wrong but would like to feel productive about it. On a PS5, clearing the cache is a real, documented, occasionally useful procedure — and it is simultaneously the single most cargo-culted piece of console maintenance on the internet, prescribed for ailments it cannot possibly cure by people who have never once watched it fail to cure them.

This guide does the boring, precise thing instead. You will power the console down — fully, not into Rest Mode. You will hold a button until the second beep, roughly seven seconds in. You will wire up a controller, because Bluetooth is dead in Safe Mode and nobody warns you until you are sitting there mashing an inert DualSense and questioning your life choices. Then you will select Clear Cache and Rebuild Database, which is the sixth item on the current menu, whatever your favorite guide told you, pick the light option, confirm, and let the machine restart itself.

It takes about ten minutes and twelve steps. It keeps every save, every installed game, and your account intact. And when you are finished, there is a genuine chance your problem is still sitting there, unmoved, because it was never the cache to begin with. We will get to that, too. First, the thing itself, and a small amount of respect for what the thing actually is.

What the PS5 Cache Actually Is

Cache, From the French for 'Hide'

The word is cache, from the French cacher, to hide, and it rhymes with 'cash,' not with 'cachet.' A cache is a stash of data the system keeps close at hand so it does not have to recompute or re-fetch the same thing on every single request. Your PS5 caches shader output, interface assets, store thumbnails, patch fragments, notification state, and a thousand other transient scraps whose only job is to make the machine feel instant instead of sluggish. Ninety-nine percent of the time this is invisible and correct, which is exactly how good caching is supposed to feel: like nothing.

The trouble begins on the day a cached scrap gets written badly. A half-downloaded update leaves a torn fragment behind. A thumbnail corrupts. A store page decides it already has the answer and serves you a blank rectangle for eternity. A game that patched overnight now crashes on launch because the console is faithfully feeding it stale shader data from before the patch. None of this is catastrophic, none of it touches your saves, and all of it is precisely the class of glitch that a cache clear is designed to sweep away. Engadget, in its 2025 walkthrough, describes the mechanism plainly: the console stashes temporary system data that can go bad, and clearing it resolves menu lag, random crashes, and online connectivity hiccups. It is a broom, not a scalpel.

It Is Not a Factory Reset

Say this part twice, because the internet loves to conflate the two. Clearing the cache is a maintenance action, not a reset. TechRadar and Engadget both frame it as housekeeping you perform when the machine is misbehaving, explicitly and repeatedly noting that your saved data, installed games, and account survive the procedure untouched. The genuinely destructive options — the ones that wipe the drive and reinstall the operating system — live at the very bottom of the same Safe Mode menu, numbered seven and eight, and we will label them clearly so you never fat-finger your way into a factory wipe while chasing a stutter.

The distinction matters because Safe Mode is a single room containing both the broom and the wrecking ball. People panic, scroll too far, and select Reset PS5 because it was three lines below the thing they actually wanted. Knowing the exact number of the option you need is not pedantry here; it is the difference between a two-minute tidy-up and re-downloading two terabytes of games over your home connection. Speaking of which, if you are the sort of person running a fully loaded drive, it is worth understanding how the PS5 Pro handles its storage before you start any operation that touches the database, because rebuild time scales directly with how much you have installed.

The PS5's Two Different 'Caches'

Here is the subtlety almost every guide flattens. When people say 'clear the PS5 cache,' they can mean two entirely different operations, and Sony has quietly bundled both behind one menu item. The first is the system software cache — the transient OS scraps described above, cleared in a minute or two, genuinely non-destructive, genuinely low-stakes. The second is the database: the master index the console maintains of every file, game, save, and app on the SSD, which the PS5 uses to know what it owns and where it lives.

Rebuilding the database is a heavier act. The console scans the entire drive and constructs a fresh index from scratch, which on a large or full SSD can take the better part of an hour. It is the operation that fixes phantom game icons and 'corrupted data' errors on installs you know are fine. Sony filed both under one menu line — Clear Cache and Rebuild Database — and then split them into two sub-choices once you select it. Ninety percent of the time you want only the first. We will spend a whole section on when you want the second, because picking the wrong one is the most common way this ten-minute job turns into an afternoon.

Prerequisites: Firmware, Cable, Ten Minutes

Software: Which Firmware You're On (and Why It Matters)

You do not need a specific firmware version to clear the cache; the procedure has been stable for years. But you should know which build you are running, because the firmware version is precisely what determines the menu numbering that half the guides on the internet get wrong. As of August 2026 the current system software is 26.05-13.60.00, released 23 July 2026 — the second of Sony's July builds, following 26.04-13.42.00 on 1 July. Sony ships these performance-and-stability updates on a roughly monthly cadence, and the version string decodes as year-dot-cycle-dash-major-dot-minor-dot-patch, so the 26 is simply 2026. If a guide tells you your PS5 is running 'System Software Version 9.00,' close the tab: those are PS4 numbers the PS5 has never used.

To check your own build before you begin, navigate the front-facing settings:

Settings -> System -> System Software -> System Software Update and Settings

Current build (August 2026):
  System Software   26.05-13.60.00
  Released          2026-07-23   (second July update)
  Prior build       26.04-13.42.00   (2026-07-01)

Format:  YY.0X-major.minor.patch      (26 = 2026)

Sony documents the running build and its changelog on the official PS5 system software information page, updated with each release. It is worth a glance, if only to confirm that the sluggishness you are about to fix was not already patched in last week's update — in which case the correct fix is installing that update, not clearing anything. The same firmware line is what quietly rolled out the console's enhanced PSSR upgrade across fifty-plus games, a reminder that these monthly builds do far more than the terse 'improves system performance' note suggests.

Hardware: A USB-C Data Cable, Not a Charging Cable

This is the prerequisite that ambushes people, so we are putting it in a header. Bluetooth is disabled in Safe Mode. Your DualSense pairs over Bluetooth during normal use, which means the instant you enter Safe Mode it goes deaf, and every button press vanishes into the void. Asurion states the constraint bluntly in its support walkthrough: a wireless controller cannot navigate the Safe Mode menu, so you must have a USB cable ready. You connect the DualSense to the console with the cable, press the PS button, and only then does the controller wake up as a wired device.

The trap inside the trap: it must be a data cable, not a charge-only one. Plenty of USB-C cables in the average household move power but not data — the ones that came with a battery pack, a lamp, a cheap accessory. Plug one of those in and the controller will happily charge while remaining completely unresponsive, which reads exactly like a dead controller and sends people down entirely the wrong rabbit hole. Use the cable that shipped with your PS5, or any known-good USB-C data cable, run it to the port on the top edge of the DualSense, and confirm the light bar comes alive when you press PS. There is no wireless workaround. Sony gated this on purpose.

A Note on Backups and PS Plus

Clearing the system software cache does not touch saved data, so a backup is not strictly required. But you are about to spend time in the one menu that also contains the drive-wiping options, and belt-and-braces is a cheap insurance policy. If you want the peace of mind, back up first: Settings -> Saved Data and Game/App Settings -> Saved Data (PS5) -> Cloud Storage or USB Drive. Cloud backup requires a PlayStation Plus subscription; USB backup does not and works with any FAT32 or exFAT drive.

The cache-clear procedure itself is entirely free and requires no subscription of any kind. You are using a first-party maintenance tool built into the console, not a service. Anyone telling you that you need PS Plus, a paid app, or a third-party 'PS5 cleaner' utility to clear your cache is either confused or selling something; the entire operation lives in Safe Mode, behind a button hold, at zero cost. Budget ten minutes for the whole thing — two of them for the actual cache clear, the rest for the shutdown, the beep-timing, and the reboot.

The Safe Mode Menu: All Eight Options

The Full List, Numbered the Way Sony Numbers It

Safe Mode is the PS5's back room: a stripped-down boot environment for the operations too consequential, too technical, or too rarely needed to sit in the everyday settings app. There is no in-system shortcut to it and never has been. You reach it only through the physical power button, which is itself a design decision — Sony gates its most powerful maintenance tools behind a deliberate button-hold ritual the way you would gate anything you do not want a bored child triggering by accident. Here is the complete current menu, transcribed from the official PlayStation Safe Mode page, numbered exactly as the console numbers it:

PS5 SAFE MODE  -  firmware 26.05-13.60.00   (8 options)
========================================================
 1  Restart PS5
 2  Change Video Output
 3  Repair Console Storage             <- the newer insertion
 4  Update System Software
 5  Restore Default Settings
 6  Clear Cache and Rebuild Database   <- the one you want
 7  Reset PS5
 8  Reset PS5 (Reinstall System Software)   <- the nuclear option
--------------------------------------------------------
Select 6  ->
     |- Clear System Software Cache   (light,  ~1-2 min)
     |- Rebuild Database              (heavy,  up to ~1 hr on a full 8 TB SSD)

Note the top and bottom of the list. Option 1, Restart PS5, is the harmless escape hatch — select it any time you enter Safe Mode by accident and want out. Options 7 and 8 are the destructive ones: Reset PS5 wipes your data, and Reset PS5 (Reinstall System Software) additionally strips and reinstalls the operating system. Neither is anywhere near option 6. You would have to deliberately scroll two lines past your target to reach them, which is reassuring, but worth knowing so you never do it in a hurry.

Option 5 or Option 6? Adjudicating the Dispute

Here is where the internet quietly disagrees with itself, and where a little precision saves you a lot of squinting. Open three cache guides and you will find Clear Cache and Rebuild Database described as 'the fifth option down' in some and the sixth in others. TechRadar's how-to says, in plain text, to select the fifth option down. Engadget's phrasing lands in the same place. Meanwhile, various 2025 and 2026 video tutorials count it as the sixth. This looks like sloppiness. It is not — it is a fossil record.

The resolution is Repair Console Storage, which now sits at position 3. That entry was inserted into the Safe Mode menu in a firmware update, and every option below it shifted down by one. Guides written or last updated before that insertion counted a seven-item menu in which Clear Cache and Rebuild Database genuinely was the fifth line. Guides reflecting the current eight-item menu — and the console sitting in front of you right now — put it sixth. Nobody is wrong so much as some of them are old. On any PS5 running 2026 firmware, it is option 6, full stop. Do not count lines from memory; read the label, ignore the number your guide quoted, and select Clear Cache and Rebuild Database wherever it happens to be. The label is stable even when the ordinal is not.

The Two Sub-Options Hiding Under Number 6

Selecting option 6 does not immediately clear anything. It opens a second, smaller menu with exactly two choices, and this is the fork that decides whether you are here for two minutes or an hour:

• Clear System Software Cache — the light action. Wipes transient OS data, takes one to two minutes, touches nothing you care about. This is what 'clear the cache' means ninety percent of the time, and for the vast majority of readers it is the entire job.
• Rebuild Database — the heavy action. Scans the whole SSD and reconstructs the content index from scratch. Useful for a specific class of problem, ruinous to interrupt, and slow in direct proportion to how much you have installed.

Engadget, Asurion, and TechRadar all route you to Clear System Software Cache for a routine cache clear, then OK to confirm. We will unpack exactly when the second option earns its keep further down, but hold the shape in your head now: one menu line, two very different consequences, and the light one is almost always the right one.

Clear the PS5 Cache in 12 Steps

Steps 1-4: Baseline and a Clean Shutdown

Every step below carries its rationale, because a procedure you understand is a procedure you can recover when it goes sideways.

1. Check your firmware and free space. Settings -> System -> System Software to note your build, then Settings -> Storage to note free space. Rationale: the firmware version tells you whether your guide's 'option 5' is current, and a database rebuild wants breathing room on the drive. If you are nearly full, this is your cue to know it now rather than mid-rebuild.
2. Back up your saves (optional, recommended). Settings -> Saved Data and Game/App Settings, then push to cloud or USB. Rationale: the cache clear is non-destructive, but you are about to work in the same menu as the drive-wipe options. A five-minute backup means a slip of the D-pad costs you nothing.
3. Close everything and power off fully. Press the PS button, choose Power, then Turn off PS5 — or hold the console's physical power button for about three seconds. Rationale: Safe Mode requires a cold start. Rest Mode is not 'off'; it is a low-power doze, and the console will refuse to enter Safe Mode from it. SlashGear's 2025 guide is emphatic on exactly this point: if the system slips into Rest Mode, wake it and turn it off completely before trying again.
4. Confirm the console is truly dark. Watch the light. Rationale: a pulsing or glowing indicator means Rest Mode or an in-progress shutdown, not a full power-off. Wait until the light stops entirely and the console is silent. Only a genuinely dead machine will boot into Safe Mode on the next hold.

Steps 5-8: Into Safe Mode

5. Grab a USB-C data cable. Have it in hand before you start the hold. Rationale: Bluetooth dies in Safe Mode, so the controller must be wired, and hunting for a cable mid-procedure is how people accidentally let the console idle back to sleep. Use a data-capable cable, not a charge-only one.
6. Press and hold the power button. On the powered-off console, press and hold the physical power button. Rationale: there is no software path to Safe Mode. This physical hold is the only door, by design.
7. Release on the SECOND beep. You will hear one beep the instant you press. Keep holding. About seven seconds later you will hear a second beep — release immediately. Rationale: the first beep is a normal boot; the second is Safe Mode. Let go on the first and you have simply turned the console on the ordinary way and must start over. Engadget, Asurion, and TechRadar all describe this identical timing, and it is the single most-repeated instruction in the entire genre for good reason.
8. Wire the DualSense and press PS. Connect the controller to the console with the USB cable, then press the PS button. Rationale: this is the moment the controller registers as a wired input and the menu becomes navigable. If nothing lights up, your cable is charge-only — swap it.

Steps 9-12: Clear, Restart, Verify

9. Select option 6, Clear Cache and Rebuild Database. Scroll to it by label, not by memorized number. Rationale: on current firmware it is the sixth line, but read the words — Clear Cache and Rebuild Database — so a stale guide's 'fifth option' cannot misdirect you into Restore Default Settings.
10. Choose Clear System Software Cache, then OK. From the two sub-options, pick the first and confirm. Rationale: this is the light, non-destructive action that clears transient OS data in a minute or two. Do not select Rebuild Database unless you have a specific reason, which the next section spells out.
11. Let it restart, untouched. The console will clear the cache and reboot on its own. Do not power it off, unplug it, or intervene. Rationale: interrupting any Safe Mode maintenance operation risks corrupting the very data you are trying to protect — Asurion warns explicitly that interrupting the process can corrupt your data. Sit on your hands.
12. Verify the fix, and only then consider escalating. Boot normally and reproduce whatever was broken. Rationale: if the glitch is gone, you are finished — do not 'also rebuild the database just in case,' because that is cargo-cult maintenance. If the glitch survives, the cache was never the culprit, and now you have earned the right to try a rebuild or a reinstall of the specific misbehaving app.

Twelve steps, roughly ten minutes, and the only genuinely irreversible thing in the room stayed two menu lines away the entire time. For the reader keeping score, this is the same discipline that separates a PS5 from the console it replaced — the architectural leap from the PS4 included a wholesale change in how the system indexes storage, which is exactly why the rebuild-database step behaves so differently across the two generations.

What Success Looks Like

The Screen You Should See

Safe Mode is deliberately ugly. It is a low-resolution, text-forward environment with none of the console's usual polish, which throws people who expect the glossy dashboard. That plainness is the point: it is a recovery console, not a storefront. Here is, in essence, the sequence of screens you should encounter, from the moment the controller wakes to the automatic restart:

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

  6.  Clear Cache and Rebuild Database        <- select this

      +----------------------------------+
      |  Clear System Software Cache      |   <- pick this
      |  Rebuild Database                 |
      +----------------------------------+

  Clear System Software Cache?
  This will not delete your saved data.     [ OK ]   [ Cancel ]

  ...clearing...
  The PS5 will restart automatically.

If your screen matches that shape, you did it right. The absence of any progress bar during the clear itself is normal for the light action — it is fast enough that Sony did not bother animating it. The console simply goes dark and comes back to the sign-in screen a moment later.

Timings: One Minute vs. One Hour

Manage your expectations by which sub-option you chose. The two operations live at opposite ends of the duration spectrum:

OPERATION                       TYPICAL DURATION      SAFE TO INTERRUPT?
----------------------------------------------------------------------
Clear System Software Cache     ~1-2 minutes          effectively instant
Rebuild Database (light lib)    a few minutes         no
Rebuild Database (full 8 TB)    up to ~1 hour         absolutely not
----------------------------------------------------------------------
Whole procedure, cache only     ~10 minutes end-to-end (incl. shutdown + reboot)

The cache clear is over almost before you register it. The database rebuild is the one that tests your patience, and its length is not a bug — the console is genuinely walking the entire drive. On a lightly populated 1 TB console it may finish in minutes; on a stuffed 8 TB drive it can run close to an hour. During a rebuild you may see a progress percentage that appears to stall for long stretches. It has not frozen. Large directory trees index in bursts. The correct response to a rebuild that looks stuck is to make a cup of tea, not to pull the plug — pulling the plug is the one action guaranteed to make things worse.

Clear Cache vs. Rebuild Database

Clear System Software Cache: The Light Touch

Reach for Clear System Software Cache first, always, because it is fast, safe, and fixes the most common complaints. Its remit is the transient operating-system layer: the interface stutters, the app that refuses to open, the store page frozen on a spinner, the crash that started the day after a patch landed. These are corrupted-scrap problems, and sweeping the scraps away is exactly the right prescription. It is the maintenance equivalent of clearing a browser cache — quick, cheap, and reversible in the sense that there is nothing to reverse.

Epic Games formalizes this in its own support documentation. For the notorious Rocket League 'Load Failure' error on PS5, Epic's official first-line fix is precisely this Safe Mode cache clear — a rare case of a third-party publisher endorsing a console maintenance step by name. When the developer of the game tells you to clear the system software cache, you clear the system software cache. It is one of the few situations where the folk remedy is also the vendor-sanctioned one.

Rebuild Database: The Re-Index

Rebuild Database is a different animal with a narrower job. It does not delete data; it rebuilds the index of your data, scanning every file on the SSD and constructing a fresh catalogue of what exists and where. You want it when the console's understanding of its own contents has drifted out of sync with reality: a game you deleted whose icon still haunts the Home row, a 'Corrupted Data' error on an installation you know is intact, features that behave as though files are missing when they plainly are not.

Asurion's guidance draws the line cleanly — it recommends Rebuild Database specifically when a game icon remains on Home after the game has been deleted, and for scanning the drive to create a new database when system features misbehave. This, incidentally, is the real source of a persistent myth: people report that clearing the cache reset their home screen layout, and blame the cache clear. It was almost certainly the rebuild that reshuffled their tiles, because re-indexing can reorder how content presents. The light cache clear does not touch your layout. If your Home screen rearranged itself, you ran the heavy option, whether you meant to or not.

A Symptom-to-Action Cheat Sheet

Keep this within reach the next time something acts up, and resist the urge to run both operations reflexively. Match the tool to the symptom:

SYMPTOM                                    ->  DO THIS
----------------------------------------------------------------------
UI stutter, slow menus, app won't launch   ->  Clear System Software Cache
Crashes started right after an update       ->  Clear System Software Cache
Store page or download stuck on a spinner   ->  Clear System Software Cache
Rocket League 'Load Failure'                ->  Clear System Software Cache (Epic-endorsed)
Deleted a game but its icon still lingers    ->  Rebuild Database
'Corrupted Data' on a known-good install     ->  Rebuild Database
System features acting as if files missing   ->  Rebuild Database
Install stuck at 'Copying...' indefinitely   ->  Clear cache first, THEN rebuild
Nothing is actually, measurably wrong        ->  Close the menu. Go play something.

The last row is not a joke. The most overprescribed maintenance on the platform is the rebuild-for-no-reason, performed monthly by people who have decided it is good hygiene. It is not hygiene; it is an hour of unnecessary drive scanning in search of a problem that does not exist. Run these operations when you have a symptom, not on a calendar.

Five Pitfalls, and How to Escape Them

The Beep You Released On

Pitfall 1: releasing on the first beep. This is the classic. You hold the button, hear a beep, let go, and the console boots normally into the dashboard — no Safe Mode in sight. The fix is patience: keep holding through the first beep and release only on the second, roughly seven seconds in. There are exactly two beeps and you want the later one. If you overshoot and keep holding well past the second beep, you risk triggering a full power-off instead; the window is generous but not infinite. Aim for releasing the instant the second beep sounds.

Pitfall 2: the console keeps dozing into Rest Mode. You try to enter Safe Mode and the machine either does nothing useful or wakes into its normal low-power state. The cause is that it was never fully off. SlashGear's warning is the fix restated: wake the console, choose Power -> Turn off PS5, wait for the light to die completely, and only then begin the hold. Safe Mode boots from cold iron, not from a nap.

The Cable Nobody Mentions

Pitfall 3: the controller is 'dead' in Safe Mode. You reach the menu, press buttons, and nothing happens. The controller is not broken — Bluetooth is off in Safe Mode, so a wireless DualSense is inert by design. Wire it with a USB cable and press the PS button. This single unmentioned fact accounts for a startling share of 'my PS5 is bricked' panic posts.

Pitfall 4: the cable is charge-only. A subtler version of the same trap. You wired the controller, the light bar even glows as it charges, and it still does not respond. Your cable moves power but not data. Swap it for a known-good USB-C data cable — the one that shipped with the console is a safe bet — and the controller will register as a wired input. If in doubt, test the suspect cable by using it to transfer a file to a phone or PC; if the device only charges and never mounts, that cable will never work in Safe Mode either.

Clearing the Wrong Thing

Pitfall 5: running the rebuild when you needed the cache clear (or vice versa). Selecting Rebuild Database for a simple UI stutter buys you an hour of drive scanning to fix a problem a two-minute cache clear would have solved. Selecting Clear System Software Cache for a phantom deleted-game icon does nothing, because that is a database-index problem the light clear cannot reach. Read the symptom-to-action table above and match the operation to the fault. When genuinely unsure, run the light cache clear first — it is fast and harmless — and escalate to a rebuild only if the symptom survives.

Pitfall 6: expecting a broom to fix a broken leg. Engadget is explicit that cache clearing is a short-term remedy for software glitches and will not fix hardware degradation. If your console overheats, throttles, ejects discs at random, or throws storage errors that return within minutes of every clear, you are not looking at a cache problem. You are looking at failing storage, a thermal issue, or a dying drive, and no amount of Safe Mode housekeeping will patch physical hardware. Clearing the cache four times in a row is not troubleshooting; it is repeating an incantation and hoping the god was merely distracted.

Troubleshooting: Ten Failure Modes

The Table

Ten ways this goes wrong, and the fix for each. Most map back to the pitfalls above, collected here for fast reference when you are standing in front of a misbehaving console.

When the Cache Was Never the Problem

The most useful troubleshooting instinct is knowing when to stop. If you have cleared the cache, rebuilt the database, and the fault persists, the cache was a red herring and you are wasting Safe Mode cycles. Escalate deliberately: reinstall the single misbehaving game or app rather than nuking the whole system; check Settings -> Storage for a drive that is alarmingly full or throwing errors; and if you have an add-in M.2 SSD, consider that the fault may live there rather than on the internal drive. Only after all of that has failed does the bottom of the Safe Mode menu — Reset PS5, and as a last resort Reset PS5 (Reinstall System Software) — become a reasonable conversation. Those are for a corrupted OS, not a corrupted thumbnail.

The Rocket League Special Case

One symptom deserves its own note because a publisher put it in writing. Rocket League's 'Load Failure' on PS5 has an official Epic-sanctioned first step, and it is this exact cache clear. If that is your specific error, do not overthink it: full power-off, hold to the second beep, wire the controller, option 6, Clear System Software Cache, OK, restart, relaunch. If Load Failure survives a clean cache clear, the next suspects are a corrupted game install (reinstall Rocket League) or a server-side outage that no local maintenance can address. Check the status page before you rebuild your entire database over a problem that lives on Epic's servers, not your SSD.

Advanced Tips the Guides Skip

Stop Clearing Cache After Every Update

A whole subculture insists on clearing the cache — or worse, rebuilding the database — after every system update, as ritual maintenance. Sony's actual guidance, and common sense, says otherwise: run these operations when you have a problem, not on a schedule. The cadence that matters is Sony's own monthly firmware releases, which quietly fold in the stability fixes people imagine they are achieving by hand. If you update promptly, you are already getting the benefit. Reserve Safe Mode for symptoms. A database rebuild performed 'just to be safe' every month is an hour of drive wear and waiting in exchange for nothing measurable, month after month.

Rebuild Time Scales With Your SSD

If you do need a rebuild, understand what governs its length: total installed data, not raw capacity. An 8 TB drive holding 400 GB rebuilds far faster than a 1 TB drive that is 95 percent full. The console indexes what exists, so the relevant number is occupancy, not the sticker on the SSD. This is also why the modern install-size arms race matters for maintenance — a single contemporary blockbuster can eat a hundred-plus gigabytes, and a library of them turns a rebuild into a genuinely long operation. If you are the sort of person pre-loading something the size of Rockstar's next open world, budget accordingly: rebuild before you fill the drive, not after, and never during a download.

Safe Mode Is a Diagnostic Ladder, Not a Big Red Button

The smartest way to read the eight-option menu is as a ladder of escalating severity, climbed only as far as the problem forces you. Restart PS5 (1) fixes transient nonsense. Update System Software (4) fixes anything a patch has already addressed. Clear Cache and Rebuild Database (6) fixes corrupted transient data and stale indexes. Restore Default Settings (5) resets configuration without touching data. And only at the very top of the severity scale do Reset PS5 (7) and the reinstall variant (8) wipe the slate. Climb one rung at a time and stop the moment the problem clears. People who leap straight to a reset for a UI stutter are using a wrecking ball to hang a picture. This console is built to last most of a decade — worth remembering, given that the PlayStation 6 is still years out, so the machine you are maintaining today is the machine you will be maintaining for a long while yet. Treat it like the diagnostic ladder it is.

The Complete Maintenance Routine

The Copy-Paste Checklist

Here is the entire procedure distilled into a single reference block. Copy it to a note, verify it against your own firmware build, and you will never again need to reconcile three contradictory guides at 1 a.m. while your controller sits there refusing to respond.

# PS5 CACHE-CLEAR + MAINTENANCE ROUTINE
# Verified against firmware 26.05-13.60.00, August 2026
# Cache clear is free, non-destructive, keeps all saves/games/account.

PRECHECK
  1. Settings -> System -> System Software   -> note build (should read 26.05-xx)
  2. Settings -> Storage                     -> note free space (rebuild wants headroom)
  3. Optional: Settings -> Saved Data        -> back up to cloud (PS+) or USB

POWER DOWN   (fully -- NOT Rest Mode)
  PS button -> Power -> Turn off PS5          (or hold console power ~3 s)
  Wait until the light stops pulsing and goes fully dark.

ENTER SAFE MODE
  Hold console power button
     BEEP #1  at press            (keep holding)
     BEEP #2  at ~7 s             (release NOW)
  Wire the DualSense (USB-C DATA cable) -> press PS button

CLEAR THE CACHE
  Option 6:  Clear Cache and Rebuild Database
     -> Clear System Software Cache -> OK      (~1-2 min, auto-restart)

REBUILD  (ONLY if a symptom persists)
  Option 6 -> Rebuild Database -> OK           (up to ~1 hr; DO NOT power off)

VERIFY
  Boot normally -> reproduce the old bug.
  Gone?      -> done. Do not rebuild 'just in case.'
  Still bad? -> the cache was never the problem.
                Reinstall the app / check storage health / then, last resort,
                Option 7 (Reset PS5) or Option 8 (Reset + reinstall OS).

# THE NUMBERING NOTE:
#   Guides saying 'option 5' predate Repair Console Storage (now option 3).
#   On 2026 firmware the cache line is OPTION 6. Read the label, not the number.

That block is the whole article compressed to something you can act on without re-reading a word of the prose around it. The prose exists to explain why each line is there; the block exists for the next time your console misbehaves and you have no patience for explanation.

Sources and Further Reading

The procedure above is triangulated from the primary sources in the 2025–2026 record. Sony's official Safe Mode documentation is the authority on the menu itself and the button-hold timing. Engadget's cache guide supplies the clearest end-to-end text walkthrough and the honest framing that this is a short-term remedy, not a hardware fix. TechRadar's how-to is the concise editorial explainer — and, usefully, the artifact that still calls this the fifth option down, letting us date the menu shift. Asurion's support walkthrough pairs the cache clear with the rebuild and draws the cleanest line between the two, and Epic's Rocket League Load Failure article is the rare publisher endorsement of the exact procedure. For the running firmware build, Sony's system software information page is updated with every release. Where the guides disagreed, we deferred to the console in front of us, running 26.05-13.60.00, which numbers Clear Cache and Rebuild Database as option six and settles the argument.