How to Clean DBeaver Cache & Temporary Files
Location & Quick Verdict
%AppData%\DBeaverData\workspace6\.metadata\Cache, Code Cache, and logs
DBeaver stores workspace index caches, extension download staging packages, GPU font atlas buffers, and diagnostic logs inside %AppData%\DBeaverData\workspace6\.metadata.
Why Package Tarballs, Symbol Indexes & Build Artifacts Pile Up in DBeaver Cache & Temporary Files
Developer toolchains, language package managers, and modern IDEs cache every downloaded dependency version, pre-compiled wheel/crate tarball, C++/Rust incremental build target, and Language Server Protocol (LSP) AST index inside %AppData%\DBeaverData\workspace6\.metadata\Cache, Code Cache, and logs. Because dependency lockfiles evolve every week, historical versions from old branches remain cached indefinitely—turning DBeaver Cache & Temporary Files into a multi-gigabyte graveyard of thousands of small files.
Thousands of small cache entries inside %AppData%\DBeaverData\workspace6\.metadata\Cache, Code Cache, and logs also degrade Windows Defender real-time filesystem scanning and slow down backup indexing. Cleaning DBeaver Cache & Temporary Files reclaims 1.5 GB – 9.5 GB of SSD capacity while preserving your active source code repositories, .env secrets, SSH keys, and workspace configurations.
# Inspect current disk footprint of DBeaver Cache & Temporary Files (Read-Only)
$target = "$env:APPDATA\DBeaverData\workspace6\.metadata\Cache, Code Cache,"
Get-ChildItem -Path $target -Recurse -Force -ErrorAction SilentlyContinue |
Measure-Object -Property Length -Sum |
Select-Object Count, @{Name="SizeGB";Expression={[math]::Round($_.Sum / 1GB, 2)}}
Manual Cleaning Instructions
- 1 Completely close DBeaver and verify no background helper processes remain active in Windows Task Manager.
- 2 Press Windows Key + R, type %AppData%\DBeaverData\workspace6\.metadata into the Run dialog, and press Enter.
- 3 Open the Cache, Temp, or Logs subdirectories, select the cached files (Ctrl + A), and press Shift + Delete.
- 4 Relaunch DBeaver (or use SWEEPR Cleaner to purge all DBeaver cache directories automatically in one click).
Note: If Windows alerts that a file is in use or locked by a background process, close the associated task in Task Manager before deleting, or use SWEEPR Cleaner to release locked handles safely.
Sub-Folders & Cache Locations Breakdown for DBeaver Cache & Temporary Files
Modern Windows applications and system services split their disk footprint across multiple sub-directories (`Cache_Data`, `Service Worker\CacheStorage`, `Code Cache`, `GPUCache`, and `Crashpad\reports`). Review which sub-folders inside DBeaver Cache & Temporary Files are safe to purge and which files remain protected:
| Sub-Folder / Cache Location | Storage Role | Typical Footprint | Deletion Safety |
|---|---|---|---|
| %AppData%\DBeaverData\workspace6\.metadata\Cache, Code Cache, | Content-Addressable Package Tarballs, Wheels & Build Artifacts | 1.5 GB – 9.5 GB | 🟢 100% Safe (Re-downloads on Build) |
| %AppData%\DBeaverData\workspace6\.metadata\Cache, Code Cache,\wrapper\dists / _cacache | Historical Toolchain Distributions & Integrity Blobs | 1.5 GB – 15.0 GB | 🟢 100% Safe |
| %AppData%\DBeaverData\workspace6\.metadata\Cache, Code Cache,\logs & crashpad | Compiler Diagnostics, Daemon Logs & Crash Snapshots | 150 MB – 2.5 GB | 🟢 100% Safe |
| Source Repositories, .env Files & SSH/API Keys | Working Git Trees, Local Databases & Credentials | Protected | 🔒 Protected — Never Touched |
Frequently Asked Questions
Is it safe to delete DBeaver Cache & Temporary Files?
Yes, 100% safe. Cleaning DBeaver's cached data and old logs frees 1.0 GB – 7.5 GB of disk space with zero impact on your SSH keys, database connections, or editor settings.
How much storage space will cleaning DBeaver Cache & Temporary Files free up?
Users typically reclaim 1.5 GB – 9.5 GB on Windows 10 and Windows 11 systems depending on update frequency and active cache retention in %AppData%\DBeaverData\workspace6\.metadata\Cache, Code Cache, and logs.
Will cleaning DBeaver Cache & Temporary Files break my active local development projects?
No. Installed dependencies inside your project workspaces remain intact. Cleaning DBeaver Cache & Temporary Files only clears the global download cache and historical build artifacts; any package needed in the future is transparently fetched on demand.
Where is DBeaver Cache & Temporary Files located on Windows 10 and Windows 11?
It is stored at %AppData%\DBeaverData\workspace6\.metadata\Cache, Code Cache, and logs. You can paste that path directly into the Windows Run dialog (Win + R) or File Explorer address bar to inspect it.
Manual File Explorer vs. 1-Click SWEEPR Cleanup
| Feature | Manual Deletion | SWEEPR Cleaner |
|---|---|---|
| Locked File Handling | Fails on locked processes | Safe background release |
| Accidental Deletion Risk | Moderate (easy to delete wrong folder) | Zero (strict rules & hashes) |
| Safety Undo Rollback | None (Shift+Del is permanent) | 7-Day Automatic Rollback |
| Time Required | 10–20 minutes per app | < 60 seconds across 40+ areas |
Related Windows Cleanup Guides & Hidden Space Hogs
Clean DBeaver Cache & Temporary Files Automatically
SWEEPR Cleaner safely clears DBeaver Cache & Temporary Files along with 40+ other hidden app folders and leftover files in one click—covering up to 5 devices (Windows, Mac, Android & iOS) with a 7-day undo safety net.