PS5 Cache Clear 2026: 12 Steps, Safe Mode Only, 8 Min

Why the PS5 Cache Goes Bad

The PlayStation 5 is, underneath the glossy dashboard, a computer that lies to itself for speed. To avoid recomputing the same work twice, it keeps a working set of temporary files: decoded shader caches, database indices, thumbnail atlases, half-parsed store manifests, and the residue of every download that ever passed through it. That working set is the cache. When it is healthy it is invisible and the console feels instant. When it rots, the same console starts behaving like a machine that no longer trusts its own notes, and no amount of glaring at the screen will fix that.

People reach for a normal restart first, and a normal restart is not the same operation. A restart flushes volatile memory and reloads the operating system, but it leaves the on-disk cache exactly where it was, corruption and all. That is why a console that stutters through a reboot and then stutters again ten minutes later needs the cache cleared specifically, not merely power-cycled. The distinction is the entire reason this procedure exists.

What the cache actually is

Sony does not expose the cache as a browsable folder, and there is no supported way to inspect it. Treat it conceptually as a scratch area the operating system considers disposable, data it can regenerate from the games and system files already sitting on the SSD. Under ideal conditions the system prunes this scratch area on its own. Conditions on a console that spends its life half-asleep in rest mode, mid-download, are rarely ideal. A power cut during a write, a patch that dies at 94 percent, a rest-mode download that never finished its handshake with the content-delivery network: each one can strand a fragment. Fragments accumulate. Eventually the index disagrees with reality, and the console spends its cycles reconciling that disagreement instead of drawing your game.

The symptoms that mean it is time

The official PlayStation guidance is blunt about when to reach for this tool: clearing the system software cache is the recommended first response when the console runs slow, lags, or throws visual glitches that a normal restart will not fix. In practice the tells are a dashboard that stutters when you scroll, apps that open noticeably slower than they did a month ago, cracked or missing game art, and installs that stall for no network reason. None of these prove the cache is at fault, but the cache is the cheapest suspect to rule out, because clearing it costs eight minutes and risks nothing you care about.

What clearing does, and does not, touch

This is the part that stops people, so let us be precise. Clearing the system software cache deletes temporary files only. It does not delete your games and it does not delete your saves. Activision, of all sources, states this outright in its support material: on PS5, clearing the cache does not remove the installed game, only the temporary data around it, a distinction it draws specifically because the Xbox equivalent behaves differently. You are not wiping the console. You are telling it to bin its scratch paper and redo the arithmetic. If your PS5 already stutters in the menus, rule this out before you start blaming the hardware itself.

Prerequisites: Hardware and Software

Nothing here is exotic, but one requirement catches people out every single time, so read the list before you start rather than halfway through, standing at a dead menu with the wrong cable in your hand. The procedure has no software prerequisites you can install and no settings you can pre-configure; it is almost entirely about having the right physical objects within reach at the right moment.

Hardware you cannot skip

Two pieces of hardware are non-negotiable. The first is the console, a standard PS5, disc or Digital Edition, or a PS5 Pro. The second is a USB-C cable that carries data, because Safe Mode switches Bluetooth off and your DualSense becomes a wireless paperweight until you plug it in. The cable that shipped in the box works. A charge-only cable scavenged from a drawer may not, and that failure mode is subtle enough to earn its own entry in the troubleshooting table below. If you intend to back up first, and you should, add a USB storage drive formatted to FAT32 or exFAT, sized to hold your saves and anything else you would mourn.

Software and firmware state

There is no minimum firmware version to chase, and anyone quoting you a precise build number is guessing. Sony has shipped the cache option in Safe Mode across every current PS5 system-software release; it is not version-gated the way a new dashboard feature would be. The only software prerequisite that matters is that the console can still boot far enough to reach the Safe Mode menu, which, unless the drive itself is dying, it can. A PS5 that cannot reach Safe Mode at all has a hardware or storage problem, not a cache problem, and no amount of button-holding will fix that.

Time, expectations, and the Pro question

Budget roughly eight minutes end to end, most of it spent watching the console restart itself while you do nothing. The procedure is byte-for-byte identical on the PS5 Pro, which launched in late 2024 with a bigger GPU and a heftier price but the same system software and the same Safe Mode menu. Whether that Pro premium was worth paying is a separate argument entirely; for cache purposes the two consoles are the same machine wearing different badges.

Understanding Safe Mode

Before the steps, understand the environment, because three of its quirks account for nearly every failed attempt: there is no shortcut, the timing is unforgiving, and the controller goes dead the instant you need it. Get these three straight in your head and the rest is mechanical.

Why there is no Settings shortcut

Here is the design decision that irritates everyone: you cannot clear the cache from the PS5's normal Settings menu. There is no toggle, no maintenance submenu, no button combination on the running console. The only route is Safe Mode, a stripped-down boot environment that sits beneath the full operating system, and the only way into Safe Mode is the physical power button. Sony did this on purpose. Safe Mode has to be reachable even when the main OS is too corrupted to trust, so it deliberately does not depend on that OS. The side effect is that a routine maintenance task now requires a cold boot and a stopwatch. There is no clever way around it, so stop looking for one.

The two-beep timing that trips everyone

The single most common failure in this whole process is a timing error, so internalize it before you touch anything. When you press and hold the power button, the console beeps immediately: that first beep only means the press was registered. It is not your cue. You keep holding for roughly seven seconds until a second beep, and that second beep is the one that means the console is booting into Safe Mode. Release on the second beep, not the first. Engadget's walkthrough confirms the seven-second hold, and seven is the number worth memorizing.

# PS5 Safe Mode entry -- the only 'config' Sony gives you
POWER_BUTTON_HOLD  = ~7 seconds (physical button, NOT rest mode)
BEEP_1  @ t = 0.0s -> 'press registered'    # IGNORE THIS ONE
BEEP_2  @ t ~ 7.0s -> 'booting Safe Mode'   # RELEASE NOW
CONTROLLER_LINK    = USB-C wired ONLY
BLUETOOTH          = disabled in Safe Mode
SETTINGS_MENU_PATH = none -- it does not exist

Why the controller has to be wired

Safe Mode runs with Bluetooth switched off, not a bug, but part of keeping the environment minimal and dependable. The practical consequence is that your DualSense, a wireless controller, cannot talk to the console until you connect it with a USB-C cable and press the PS button to bring it up on the wired link. If you have ever watched your controller die the instant the Safe Mode screen appeared, that is the reason. Keep a data cable within arm's reach before you begin, not after you are glaring at an unresponsive menu. This is not a quirk of one console revision; it applies to every PS5 and every PS5 Pro, because the restriction lives in the boot environment, not the hardware.

Back Up Your Data First

Belt and suspenders. The cache clear will not touch your saves, and you should still back up before you go anywhere near Safe Mode. This is the one step people skip and the one step that turns a bad night into a merely tedious one.

Why back up something the clear will not delete

You just read that clearing the cache leaves saves alone. True. Back up anyway, for the same reason you keep a spare key even though you rarely lock yourself out. Safe Mode sits one wrong selection away from options that do erase data. 'Restore Default Settings', 'Reset PS5', and 'Reset PS5 (Reinstall System Software)' all live in the same list, one or two rows from the cache tool. A mis-navigation with a wired controller in a hurry is exactly how accidents happen. A backup turns a catastrophic slip into a merely annoying one. Ten minutes now buys the right to be a little careless later.

Formatting the USB drive: FAT32 vs exFAT

The PS5 accepts a USB drive formatted as FAT32 or exFAT for backups. Given the choice, use exFAT. FAT32 carries a hard 4 GB per-file limit that predates this century, and a single PS5 backup blob blows past it instantly; exFAT has no practical file-size ceiling. Format the drive on a computer before it goes near the console. Each command below wipes the target drive completely, so confirm the disk identifier twice, because erasing the wrong disk is its own special kind of cache clear.

# Windows -- exFAT format via diskpart (run as Administrator)
diskpart
list disk
select disk 2          # confirm THIS is the USB drive, not your OS disk
clean
create partition primary
format fs=exfat quick label=PS5BACKUP
assign
exit

# macOS -- exFAT format via diskutil
diskutil list
diskutil eraseDisk ExFAT PS5BACKUP /dev/disk4   # confirm disk4 = the USB drive

# Linux -- exFAT format (exfatprogs installed)
lsblk                                   # identify the USB device, e.g. sdb
sudo umount /dev/sdb1                    # unmount if auto-mounted
sudo mkfs.exfat -n PS5BACKUP /dev/sdb1  # write a fresh exFAT filesystem

Running the on-console backup

With the drive formatted and plugged in, the backup itself lives in the normal operating system, not Safe Mode. The path is fixed, and worth writing down before you power off:

Settings
  > System
    > System Software
      > Back Up and Restore
        > Back Up Your PS5     (choose games, apps, saves, settings)

Let it finish completely before you begin the Safe Mode procedure. A backup interrupted halfway is worth less than no backup at all, because it tempts you into trusting it. Cloud saves, if you have PlayStation Plus, are a second belt on top of these suspenders, but they do not cover local app data or system settings, so the USB backup still earns its place.

The 12-Step Cache-Clear Procedure

This is the whole job. Twelve steps, roughly eight minutes, most of it automatic. Read all twelve once before you start so nothing surprises you mid-reboot, then work through them in order without improvising.

The twelve steps, in order

1. Fully power the console down, not rest mode. From the running dashboard, hold the power button and choose 'Turn Off PS5', or hold the physical button until it shuts down completely. Why: Rest mode keeps the temporary files live and the system merely suspended; Safe Mode can only be reached from a genuine cold-off state.
2. Wait for every light to go fully dark. Give it several seconds until the power indicator is off, not pulsing. Why: A pulsing light means the console is still suspended, and the button hold will behave unpredictably from there.
3. Press and hold the physical power button. The button on the console body, not the one on the controller. Why: Safe Mode is a boot-time environment with no software or controller shortcut into it; the physical button is the only door.
4. Ignore the first beep. The console beeps the instant you press. Why: That beep only acknowledges the press; release now and the console simply powers on as normal, dumping you back at square one.
5. Keep holding about seven seconds until the second beep, then release. Why: The second beep is the Safe Mode trigger; release on it and the console boots into Safe Mode instead of the standard operating system.
6. Connect the DualSense with a USB-C cable and press the PS button. Why: Bluetooth is disabled in Safe Mode, so only a wired controller can move through the menu.
7. Select Option 6, 'Clear Cache and Rebuild Database'. On older firmware this entry sits at Option 5. Why: This is the menu item that contains the cache tool; its position shifted by one between firmware generations, so trust the label over the number.
8. Choose 'Clear System Software Cache'. Do not choose 'Rebuild Database' unless you specifically want it. Why: 'Clear System Software Cache' removes temporary system files only; 'Rebuild Database' is a heavier, separate operation that re-indexes your whole library.
9. Confirm the action. Why: There is no undo, but nothing here deletes games or saves, so the confirmation is a formality rather than a gamble.
10. Do not touch anything while it works. Why: Interrupting a cache flush mid-write is precisely how you create the corruption you came to remove.
11. Let the console restart several times. Two or three reboots in a row is expected. Why: The system reboots to flush and reinitialize; multiple restarts are normal behavior, not a fault.
12. Boot to the home screen and test the problem game or app. Why: The symptom was the whole point; confirm it is actually gone before you declare the job done.

Why the option number moved from 5 to 6

Older PS5 guides, and older firmware, put the cache tool at Option 5. On current system software it is Option 6, one row lower, because Sony inserted and reordered entries over successive updates. This is exactly why you should navigate by the label, 'Clear Cache and Rebuild Database', rather than muscle-memorizing a number. If your menu shows it at 5, you are on older firmware and nothing is wrong; select it there. The official Safe Mode documentation tracks the current layout, and a 2026 video walkthrough shows it in its current position if you would rather watch than count.

The three-second sanity check before you confirm

Before you press confirm on step 9, take three seconds to read the highlighted line back to yourself. You are looking for the word Cache, not the word Reset and not the word Restore. The destructive options share the same list and the same drab typography, and the wired controller makes it easy to overshoot by a row. This single habit, read the label then confirm, prevents the only genuinely bad outcome this procedure can produce. Nobody has ever regretted the extra three seconds; plenty have regretted skipping them.

Clear Cache vs. Rebuild Database

The submenu offers two operations that guides constantly conflate. They are not the same, they take wildly different amounts of time, and picking the wrong one wastes anywhere from a minute to several hours. Understanding the difference is the mark of someone who actually knows what the tool does rather than parroting a video.

What 'Clear System Software Cache' does

This is the light-touch option and the one this whole tutorial is about. It discards temporary system files, the transient scratch data described at the top of this article, and nothing else. It finishes in seconds to about a minute, touches no game data, and is the operation the official support material names as the primary fix for system-feature issues and performance drops. If your complaint is menu lag, glitches, or apps that open slowly, this is your tool and you can stop here. It is the console equivalent of emptying a wastebasket, not renovating the house.

What 'Rebuild Database' does

Rebuild Database is the heavier hammer. Instead of discarding scratch files, it scans every piece of content on the drive and constructs a fresh index, a new database describing every game, app, and save the console can see. Think of it as the console re-cataloguing its entire library from scratch. Because the work scales with how much you have installed, it can run from a few minutes to well over an hour on a stuffed 2 TB drive. It is the correct choice for a different class of problem: games that appear missing or duplicated, corrupt-content warnings, or a disc the console refuses to recognize. It is overkill for simple slowdowns, and running it when a cache clear would do is how people convince themselves the process takes forever.

When to use which

When in doubt, clear the cache first, because it is faster and non-destructive, and only escalate to a rebuild if the specific library-level symptoms above persist afterward. The two are complementary, not interchangeable.

Expected Output at Each Stage

A console is not a terminal; you will not get a scrolling log. But each stage does present a predictable screen, and knowing what 'normal' looks like is how you tell progress from a hang. The blocks below approximate what you should see, so you can match your screen against them rather than guessing.

The Safe Mode boot screen

After the second beep and a black interval, the Safe Mode menu appears. The exact enumeration shifts between firmware versions, which is why the cache tool has drifted between Option 5 and Option 6, but it looks approximately like this:

PS5 SAFE MODE   (numbering varies by firmware version)
 1. Restart PS5
 2. Change Video Output
 3. Update System Software
 4. Restore Default Settings
 5. Clear Cache and Rebuild Database   [older firmware]
 6. Clear Cache and Rebuild Database   [current firmware]
      |-- Clear System Software Cache   (SELECT THIS)
      |-- Rebuild Database
 7. Reset PS5
 8. Reset PS5 (Reinstall System Software)

The cache-clear progress screen

Selecting 'Clear System Software Cache' drops you into a brief progress screen. For a cache clear it is genuinely brief, seconds rather than minutes, and the wording is a variation on the following:

Clearing system software cache...
Do not turn off the PS5.

[####################]  100%

Preparing system... restarting.

The restart sequence

Then the console reboots, and reboots again. This is the stage that panics people. Two or three PlayStation-logo cycles in a row is expected and documented behavior, not a boot loop:

[power LED]  solid -> off,  screen black
[reboot 1]   PlayStation logo -> black
[reboot 2]   PlayStation logo -> home screen
# 2-3 reboots here is NORMAL (see PlayStation Safe Mode docs)

If it cycles more than three or four times, or hangs on a black screen for several minutes with no logo, skip ahead to the troubleshooting table. But give it a full three minutes before you decide anything is wrong, because impatience at this exact moment is how good clears get turned into bad ones.

Common Pitfalls and Fixes

Almost every failed cache clear is one of six mistakes. Here they are, grouped by where in the process they bite, each with the fix. If your attempt went sideways, it is very likely on this list.

Timing and beep mistakes

Pitfall 1, releasing on the first beep. You press, you hear a beep, you let go, and the console boots normally into the dashboard. That first beep was only the press acknowledgement. Fix: Power fully off and try again, this time holding through the first beep for the full seven seconds until the second beep.

Pitfall 2, holding past the second beep. Overhold and some consoles will interpret the long press as a power-off request, dropping you back to a dead console. Fix: Listen for exactly two beeps and release on the second; do not keep clamping the button to be sure.

Controller and cable mistakes

Pitfall 3, expecting the controller to work wirelessly. You reach Safe Mode, the menu is right there, and the DualSense does nothing. Fix: Connect it by USB-C and press the PS button; Bluetooth is off in this mode, full stop.

Pitfall 4, a charge-only USB-C cable. The controller is plugged in and still dead because the cable carries power but no data. Fix: Use a data-capable cable, the one that shipped with the console is the safe default, and press the PS button again.

Menu and process mistakes

Pitfall 5, selecting Rebuild Database or a Reset option by reflex. The list is cramped and the labels are similar. Rebuild merely wastes time; a Reset can wipe you. Fix: Read the highlighted label for the word 'Cache' before confirming, every single time.

Pitfall 6, pulling power during the multi-restart. The repeated reboots look like a loop, so someone yanks the plug and creates real corruption. Fix: Leave it alone for a full three minutes; two or three reboots are normal and interrupting them is the actual danger.

Troubleshooting Table

When the procedure misbehaves, the cause is almost always in one of two buckets: you could not get cleanly into Safe Mode, or the console did something after the clear that you did not expect. The table covers both, with the likely cause and the specific fix for each.

Boot and Safe Mode failures

These are the entry-stage problems: timing, cables, and the menu itself. They feel like the console is broken; they are almost always procedure errors that cost nothing to correct once you know what to look for.

Post-clear behavior

These are the after-effects: reboots, missing-looking data, or a symptom that stubbornly survives. Most are harmless and expected; one or two point at a deeper hardware issue the cache was never going to fix.

The full symptom table

Advanced Tips

The basic clear covers the common case. If you are the sort who wants the console genuinely clean, or you keep ending up back in Safe Mode, these go further than the eight-minute routine.

Chain a cache clear into a database rebuild

For a deep clean when a console has been misbehaving for weeks, run the two Safe Mode operations back to back: 'Clear System Software Cache' first, then re-enter Safe Mode and run 'Rebuild Database'. The first discards the corrupt scratch data; the second rebuilds the content index on top of the now-clean state, rather than re-indexing around old garbage. It is slower, budget up to an hour for the rebuild on a large library, but it is the most thorough reset short of wiping the drive, and it still keeps your games and saves intact.

Fix the rest-mode habits that rot the cache

If you clear the cache and the sludge returns in a week, look at how the console sleeps. Downloads and updates that run in rest mode and get interrupted, by a power blip, a router reboot, or the console dropping its connection, are a prime source of the fragments that become cache rot. Letting large updates finish while the console is fully awake, and giving it a clean full shutdown now and then instead of eternal rest mode, measurably reduces how often you end up back here. This matters more if you push the hardware hard, for instance when capturing gameplay at 4K60, where a flaky cache can surface as dropped frames in your encoder rather than menu lag.

Rule out the SSD before you blame the cache again

A cache clear is a diagnostic, not just a fix. If it helps for a day and then the slowdown comes straight back, the cache was a symptom, not the disease. Recurring sluggishness that survives repeated clears points at storage that is filling up or wearing out, or at thermals throttling the system under load. The same logic applies to streaming setups: if Remote Play stutters no matter how often you clear, the bottleneck is your network or the drive, not temporary files. Fix the real cause; do not keep prescribing aspirin for a broken leg.

Game-Specific Cache Fixes

Sometimes the console is fine and one game is broken. A few titles are notorious enough that their publishers name this exact procedure in their own support docs, which is the strongest possible endorsement that it works.

Rocket League and other Epic titles

Epic Games explicitly recommends the Safe Mode cache clear to troubleshoot Rocket League load-failure errors on PS5, the error where the game refuses to load past a certain point. If a specific Epic title hangs on launch while the rest of the system is healthy, this is the sanctioned first step. Epic's own support resources walk through it, and it is worth doing before you resort to a full reinstall, which costs you the entire download all over again.

Call of Duty and Activision's clarification

Activision supports cache clearing as a troubleshooting step and takes the trouble to draw a distinction that trips up a lot of players: on PS5, clearing the cache does not delete the game itself, only the temporary files around it. The point matters because the Xbox cache procedure behaves differently, and players moving between platforms assume the two are equivalent. They are not, which is a small, precise example of the platform-level divergences catalogued in our PlayStation-versus-Xbox breakdown. Activision's support portal covers the game-side steps if the system clear alone does not resolve a Call of Duty issue.

When the game, not the system, is the problem

If a system cache clear does not fix a single misbehaving game, the corruption lives in that game's own installed data, not the system scratch area. The escalation ladder is simple: clear the system cache, then rebuild the database, which re-indexes that title, and only then delete and reinstall the game data. Your saves survive all three steps, especially if they are backed up or synced to the cloud. Reinstalling is the nuclear option precisely because it is the slowest, not because it is the most dangerous, and jumping to it first is a waste of bandwidth you will resent on a metered connection.

The Complete Reference Card

Everything above, compressed onto a single card you can screenshot. If you have done this once, you will never need the prose again, just this block and the two beeps.

The one-block runbook

# ============================================================
# PS5 CACHE CLEAR -- COMPLETE RUNBOOK (2026)
# Standard PS5 and PS5 Pro. ~8 minutes. Destroys nothing you value.
# ============================================================

PRECONDITIONS
  console      = PS5 (disc/digital) or PS5 Pro (late 2024)
  cable        = USB-C, DATA-capable (in-box cable is fine)
  backup_drive = USB, exFAT preferred over FAT32 (4 GB file cap)
  firmware     = current system software (no version gate)

BACKUP (optional, recommended)
  Settings > System > System Software > Back Up and Restore > Back Up Your PS5

ENTER SAFE MODE
  1. Turn OFF the PS5 fully (NOT rest mode)
  2. Hold the physical power button
  3. beep #1 @ 0s   -> ignore
  4. beep #2 @ ~7s  -> release
  5. Connect DualSense via USB-C, press PS button

CLEAR
  6. Option 6: 'Clear Cache and Rebuild Database'  (Option 5 on old firmware)
  7. Select:   'Clear System Software Cache'   # NOT 'Rebuild Database'
  8. Confirm
  9. Allow 2-3 automatic restarts (normal)

VERIFY
  10. Boot to the home screen
  11. Launch the problem game/app; confirm the symptom is gone

GUARANTEES
  deletes = temporary system files only
  keeps   = installed games, saves, accounts, settings
# ============================================================

Decision rules in plain terms

Three rules cover almost every case. First: if the whole console is sluggish or glitchy, clear the system cache, because it is fast and safe. Second: if games look missing, duplicated, or corrupt, rebuild the database instead. Third: if a clear helps for only a day before the problem returns, stop clearing and check the SSD, the thermals, and how full the drive is, because the cache was the symptom, not the cause. Everything else is a variation on those three.

The Machine's closing note

Sony could have put this behind a single button in Settings and spared everyone the stopwatch and the second beep. It did not, and it will not, because Safe Mode's whole value is that it works when the normal OS cannot be trusted, a defensible reason for an indefensible amount of friction. So memorize the seven seconds, keep a data cable in the drawer, and treat the cache clear as routine maintenance rather than an emergency. It deletes nothing you value, it takes eight minutes, and it is the cheapest fix in the entire PlayStation ecosystem. When in doubt, the official Safe Mode page and a good 2026 video walkthrough will show you the same steps, in the same order, with the same two beeps.