Ubuntu APT Package Cache (/var/cache/apt/archives)

Bottom Line: It is 100% safe to delete the APT package cache using sudo apt clean. Doing so will NOT uninstall any programs on your Ubuntu or Debian system.

What is the APT Package Cache Folder?

Located at /var/cache/apt/archives, this directory is used by the APT package manager on Ubuntu, Debian, Linux Mint, and Pop!_OS.

Whenever you run sudo apt install or update packages via Software Updater, APT downloads the raw .deb installer-folder)-folder)-folder)-folder)-folder)-folder)-folder)-folder)-folder)-folder)-folder)-folder)-folder)-folder)-folder)-folder)-folder)-folder)-folder)-folder)-folder)-folder)-folder) files into this folder before installing them. However, APT never automatically deletes these .deb installers after installation. Over months of software updates, /var/cache/apt/archives accumulates gigabytes of obsolete package installers.

Can You Delete /var/cache/apt/archives?

✅ Yes, it is completely safe to delete.

• Installed programs stay 100% intact: The actual installed software binaries live in /usr/bin and /usr/lib, not in the cache archive.
• Auto-download on reinstall: If you ever reinstall a package in the future, APT will simply fetch a fresh .deb from Ubuntu repositories.

How to Safely Clean Up APT Cache

Method 1: Using Built-in APT Clean Command (Recommended)

Open your terminal and run:

sudo apt clean

What it does: It completely empties /var/cache/apt/archives (except for the lock file and partial directory), instantly reclaiming 1 GB to 10 GB+ of disk space.

Method 2: Remove Obsolete Packages Only

If you want to keep cached .deb files for currently installed apps while deleting packages that are no longer available in repos:

sudo apt autoclean

Method 3: Autoremove Unused Orphaned Dependencies

To delete leftover library dependencies that were installed automatically but are no longer needed by any app:

sudo apt autoremove --purge

Related Guides

• Learn about deleting Ubuntu Snap package cache.
• How to clean up Linux /var/log.
• Check if you can clean Docker overlay2.