Brave Browser Using 800GB Disk for Caching? WHAT???

by | Apr 11, 2026 | Misc | 0 comments

On my system with 128GB memory, I have many open tabs for months without rebooting. Recently I had 650 open tabs causing my 1TBSSD to choke! Here is how to clear disk space caused by Brave, since closing it and rebooting really does not completely fix the issue, apparently there are issues with Brave.

Brave is chewing 800 GB because of accumulated cache, downloaded media, site‑storage blobs, and especially service‑worker caches (not cleared by normal “Clear browsing data”). With 600 tabs it can easily grow into hundreds of gigabytes over time.

Why 800 GB is plausible

  • Brave (like Chromium) stores Cache, Service Worker CacheStorage, IndexedDB, video‑stream temp files, and extensions‑data under AppData\Local\BraveSoftware\Brave‑Browser\.
  • Service‑worker caches and streaming fragments often aren’t removed when you clear “Cached images and files” in settings, so they silently pile up.

Safe folders you can purge (Run as Admin)

From:
C:\Users\Administrator\AppData\Local\BraveSoftware\Brave‑Browser\User Data\Default\ (or your profile name)

  1. Normal Cache
    • Path:
      …\Default\Cache\
    • Delete all contents (do not delete the Cache folder itself).
    • This is safe; browser will rebuild it on next load.
  2. Service Worker CacheStorage (biggest space hog)
    • Path:
      …\Default\Service Worker\Cache Storage\
    • Delete everything inside this folder.
    • These are cached service‑worker assets and are not removed by normal “Clear browsing data.”
  3. IndexedDB / Site data that lives in subfolders
    • Paths like:
      …\Default\IndexedDB\
      …\Default\Local Storage\
      …\Default\Local Storage\leveldb\
    • You can delete these but it may log you out of some sites or reset some site‑specific data; Brave will recreate them as needed.
  4. Temporary media / hidden .tmp files
    • Brave sometimes writes streaming video / audio chunks as hidden .tmp files directly in:
      …\Default\
    • If you see huge files there (use dir /a /s or a tool like WinDirStat), delete them while Brave is fully closed.
  5. Extensions and WebApp data
    • Paths such as:
      …\Default\WebApps\
      …\Default\Extensions\
    • These are mainly code and local data; you can delete them but you may lose some extension‑specific state or web‑app offline data.

What NOT to delete (critical)

  • Do not delete the top‑level folders:
    • User Data\
    • Default\
    • Or whole Brave‑Browser\ folder.
  • Keep Bookmarks, Preferences, Secure Preferences, and History files if you want to keep profiles, passwords, and setup.

How to prevent this going forward

  1. Flush Brave data regularly
    • In Brave:
      brave://settings/clearBrowserData → Cached images and files, All time → Clear data.
    • Also periodically hit brave://settings/content/all?sort=data-stored to see per‑site storage and clear big ones.
  2. Limit Brave cache size (via Chromium flags)
    • Brave exposes Chromium‑style cache limits, but they’re not in UI. You can experiment with:
      brave://flags/#cache-max-size to cap disk cache (e.g., 10–20 GB).
  3. Consider reducing open tabs
    • 600 tabs keep a lot of site‑data, service workers, and cached resources pinned in place; either close, pin‑tab, or use a tab‑manager extension so you load fewer tabs into memory.

Brave should be fully closed before you manually delete any folders inside AppData\Local\BraveSoftware\Brave-Browser\.

Why it’s safer to close Brave first

  • Many of the folders you want to nuke (like Cache, Service Worker\Cache Storage, IndexedDB, etc.) are actively read from and written to while Brave is running.
  • If you delete files while Brave has them open, you can end up with:
    • Locked files that won’t delete cleanly.
    • Inconsistent state that may cause crashes or weird behavior when you restart.

What you should do

  1. Fully exit Brave
    • Right‑click the Brave icon in the taskbar → Close all windows, and confirm no Brave processes are still listed in Task Manager under Processes.
  2. Then delete safe folders
    • Examples of folders it’s safe to clear when Brave is closed:
      • …\Default\Cache\ contents
      • …\Default\Service Worker\Cache Storage\ contents
      • …\Default\IndexedDB\ contents
      • …\Default\Local Storage\ / Local Storage\leveldb\
      • Any large .tmp or data‑blob files in Default\
    • Don’t delete the parent folders themselves (keep User Data\, Default\, and Brave-Browser\ in place).
  3. Reopen Brave afterward
    • Brave will rebuild the cache and runtime data as needed; sites may be a bit slower to load the first time, but you shouldn’t lose core settings or passwords if you left the config files.

So: stop Brave → delete selected subfolder contents → restart Brave is the clean, safe pattern.

why would cache save in those folders when brave is closed, should i just clear all brave cache first?

Why cache stays on disk when Brave is closed

Brave saves cache (images, CSS/JS, some media) to disk so it doesn’t have to re-download everything every time you restart the browser. These files are meant to persist even when Brave is shut down, so they can be reused quickly on the next launch.

However, normal cache ≠ all storage:

  • Things like Cache, Service Worker\Cache Storage, IndexedDB, and Local Storage can survive restarts and keep growing if you never manually clear them.
  • The built‑in “Clear browsing data” option doesn’t always touch service‑worker caches and some temp‑blob storage, so those silently pile up.

Should you clear all Brave cache first?

Yes—you can and probably should clear Brave’s cache first, especially before you start manually deleting folders in AppData\Local\BraveSoftware\:

  1. Clear via Brave UI (safe, recommended first step)
    • Open Brave → Menu → Settings → Privacy and Security → Clear browsing data.
    • Choose All time and tick Cached images and files (and optionally cookies/site data if you’re okay with log‑outs).
    • Click Clear data.
    • This removes the “normal” cache and most of the low‑hanging bulk, often liberating many GBs before you ever touch the folders directly.
  2. Then delete folders manually (optional extra cleanup)
    After clearing via Brave and closing it completely, you can safely delete the contents of:
    • …\Default\Cache\
    • …\Default\Service Worker\Cache Storage\
    • …\Default\IndexedDB\
    • …\Default\Local Storage\leveldb\
      Brave will rebuild these as needed, but this catches the leftover service‑worker and temp blobs that Brave’s own “Clear browsing data” often misses.

Practical workflow for your 800 GB case

  1. Open Brave → brave://settings/clearBrowserData → Cached images and files → All time → Clear data.
  2. Fully close Brave (no Brave processes in Task Manager).
  3. Then delete the cache‑related folders inside ...\Brave-Browser\User Data\Default\ as described.
  4. Restart Brave; it may be a bit slower for the first page‑loads, but you shouldn’t lose core settings or passwords.

If you want to keep most of your profiles and logins but still keep disk usage sane, just clear cache on every shutdown from now on via Settings → Privacy and Security → Clear browsing data → On exit

800 GB is not normal and strongly suggests Brave is leaking or mis‑behaving on that Windows Server 2019 box with 663 tabs. Clearing via the normal “Clear browsing data” often leaves behind service‑worker caches and temp blobs, which is why it didn’t help much.

Here’s how to limit Brave’s disk explosion going forward and keep it under control.

1. Immediate “damage control”

While Brave is fully closed (no Brave processes in Task Manager):

  1. Blow out the big offenders under:
    C:\Users\Administrator\AppData\Local\BraveSoftware\Brave‑Browser\User Data\Default\
    • Delete contents of:
      • Cache\
      • Service Worker\Cache Storage\
      • IndexedDB\
      • Local Storage\leveldb\
      • Any huge .tmp or data‑blob files in Default\
    • Keep the parent folders (User Data, Default, Brave‑Browser) and config files like Bookmarks, Preferences, Local State.
  2. Hold a “breaking‑clean” option as backup
    • If Brave keeps mis‑behaving, you can:
      1. Export bookmarks.
      2. Back up User Data\Default\Preferences (or a profile‑copy).
      3. Delete BraveSoftware\Brave‑Browser\ entirely, then reinstall Brave.

This will cut the 800 GB by a huge chunk.

2. Ways to limit Brave’s disk growth

A) Force Brave to clear data on exit

Enable “Clear browsing data on exit” so Brave doesn’t silently accumulate GBs:

  • In Brave:
    Settings → Privacy and security → Clear browsing data on exit → Turn on.
  • Choose what to clear:
    • At least Cached images and files.
    • Optionally Cookies and other site data if you don’t mind re‑logging in.

This alone can prevent long‑term ballooning on a box that rarely reboots.

B) Manually limit cache size (Chromium‑style)

Brave doesn’t expose a GUI cache‑size cap, but you can limit it via Chromium flags:

  • In Brave’s shortcut, add a flag to limit disk cache:
    "C:\Program Files\BraveSoftware\Brave-Browser\Application\brave.exe" --disk-cache-size=10737418240
    → sets a hard limit of 10 GB disk cache.
  • You can ramp this up (e.g., 21474836480 for 20 GB) but keep it far below your free disk space.

(If you want, paste your Brave shortcut path and I’ll give you the exact command line tailored to your install.)

C) Reduce active storage per tab

With 663 tabs, each tab can carry gigabytes of site‑data, service workers, and temp files:

  • Use Memory Saver or Sleeping Tabs‑style behavior:
    • Settings → System → Performance → enable Memory Saver (it frees inactive tabs more aggressively).
  • Periodically prune or archive tabs:
    • Save frequently used tabs as bookmarks and close tabs you only use occasionally.
    • Use a tab‑manager or extension to only keep “active” tabs in memory.

3. Structural tweaks for a “always‑on” server

Because this is a Windows Server 2019 box with 128 GB RAM that rarely reboots:

  • Consider moving Brave’s user data off C: to a larger drive
    • You can symlink AppData\Local\BraveSoftware to another drive, or move User Data and then symlink it back.
    • This keeps Brave from hammering your system SSD while you still control practical limits via flags and on‑exit cleanup.
  • Monitor Brave’s disk writes
    • Watch Resource Monitor → Disk tab while Brave is open to see if it’s writing a lot of small files to BraveSoftware constantly.
    • If it’s doing heavy, constant writes even when idle, that’s a sign of a bug; you may want to open a report on Brave’s GitHub or community forum.

4. If you still see huge growth

If after:

  • clearing folders manually,
  • enabling “Clear browsing data on exit”,
  • and capping --disk-cache-size,

Brave still grows to hundreds of GB in a short time, treat it as a bug and:

  • Test with a new profile (delete User Data\Default\ and let Brave recreate it).
  • If the new profile stays sane, something was corrupted in the old profile; if it still balloons, file an issue on Brave’s GitHub with disk‑usage logs.