How to Remove Packages on Ubuntu 26.04, 24.04 and 22.04

APT gives you more control than a graphical app store when you need to remove packages on Ubuntu without guessing what happens to dependencies, cached downloads, or leftover system configuration files. The same workflow applies on Ubuntu 26.04, 24.04, and 22.04, whether you are cleaning up a desktop install, a server, or a minimal image.

That matters when you need to remove one package cleanly, remove a package and its dependencies, clear old APT downloads, or figure out why apt uninstall does not work on Ubuntu. In practice, that means knowing when to use apt remove, apt purge, apt remove --autoremove, apt autoremove, apt autoclean, and apt clean, plus how to preview removals and check reverse dependencies with Ubuntu 26.04 output examples.

Ubuntu 26.04 uses the newer APT 3 summary format in the example outputs below. Ubuntu 24.04 and 22.04 still show the older The following packages will be REMOVED wording, but the command behavior is the same across all supported Ubuntu LTS releases. If you need to confirm which release you are running first, check Ubuntu version.

Remove Packages on Ubuntu with APT

Use the command that matches the cleanup level you want. apt remove keeps package-managed conffiles in place, apt purge removes them, and apt remove --autoremove removes the target package plus anything APT already considers autoremovable.

Command	Removes the package	Removes system conffiles	Removes now-unused dependencies	Best use
sudo apt remove package-name	Yes	No	No	Uninstall software but keep package-managed settings under /etc/
sudo apt purge package-name	Yes	Yes	No	Reset a package completely at the system level
sudo apt remove --autoremove package-name	Yes	No	Yes	Remove a package and APT’s current autoremovable set after review
sudo apt autoremove	No	No	Yes	Clean up dependencies left behind from earlier removals

• Use apt remove when you may reinstall the package later and want to keep package-managed system settings.
• Use apt purge when you want Ubuntu to remove the package and its conffiles from /etc/.
• Use apt remove --autoremove only after a preview shows every autoremovable package is safe to delete.
• Use apt autoremove later when you have already removed packages and want APT to clean up the leftovers.

Ubuntu does not ship an apt uninstall subcommand. For package removal on Ubuntu, use apt remove for a standard uninstall and apt purge when you also want the package’s system conffiles removed. Older scripts may use apt-get remove package-name, which targets the same APT package database; apt get remove with a space and apt-get uninstall are not valid command forms.

Remove One Ubuntu Package with apt remove

The standard uninstall command removes the package itself but leaves any package-managed conffiles behind. The example below uses mc (Midnight Commander), which makes that difference easy to verify. The -y flag auto-confirms this small example removal; omit -y when you want to review APT’s prompt interactively.

These commands use sudo because APT changes the system package database. If your account does not have admin access yet, add a new user to sudoers on Ubuntu or run the commands as root.

sudo apt remove -y mc

Relevant output on Ubuntu 26.04 includes:

WARNING: apt does not have a stable CLI interface. Use with caution in scripts.

REMOVING:
  mc

Summary:
  Upgrading: 0, Installing: 0, Removing: 1, Not Upgrading: 43
  Freed space: 1,653 kB

(Reading database... 190004 files and directories currently installed.)
Removing mc (3:4.8.33-1.1build1)...

On Ubuntu 24.04 and 22.04, the same command still works, but APT prints the older The following packages will be REMOVED format instead of the new REMOVING summary block.

Verify that the package is gone but its conffile is still present:

dpkg -l mc | tail -n 1
test -e /etc/mc/mc.menu && echo conffile-present || echo conffile-absent

After apt remove, you should see residual-config state plus the remaining conffile:

rc  mc             3:4.8.33-1.1build1 amd64        Midnight Commander - a powerful file manager
conffile-present

Purge Ubuntu Package Configuration Files with apt purge

Use apt purge when you want Ubuntu to remove package-managed conffiles as well as the package itself. This is the right choice when you want a clean reinstall or no longer need the package’s system-level configuration under /etc/.

sudo apt purge -y mc

Relevant purge output on Ubuntu 26.04 includes:

WARNING: apt does not have a stable CLI interface. Use with caution in scripts.

  mailcap  mc-data
Use 'sudo apt autoremove' to remove them.

REMOVING:
  mc*

Summary:
  Upgrading: 0, Installing: 0, Removing: 1, Not Upgrading: 43
  Space needed: 0 B / 113 GB available

(Reading database... 189913 files and directories currently installed.)
Purging configuration files for mc (3:4.8.33-1.1build1)...

If you prefer the long form, sudo apt remove --purge mc is equivalent to sudo apt purge mc.

Run the same verification command again after the purge:

dpkg -l mc | tail -n 1
test -e /etc/mc/mc.menu && echo conffile-present || echo conffile-absent

After apt purge, the package record is gone and the conffile has been removed:

un  mc             <none>       <none>       (no description available)
conffile-absent

Remove Ubuntu Packages and Dependencies with apt remove --autoremove

When you want to remove a package and clean up dependencies APT no longer needs, use apt remove --autoremove after a preview. The example below uses nmap, which pulls in separate support packages that APT can remove in the same pass.

sudo apt remove --autoremove --dry-run nmap

Start with a dry run so you can see the full removal set before anything changes:

WARNING: apt does not have a stable CLI interface. Use with caution in scripts.

Reading package lists...
Building dependency tree...
Reading state information...
Solving dependencies...
REMOVING:
  libblas3  liblinear4  mailcap  mc-data  nmap  nmap-common

Summary:
  Upgrading: 0, Installing: 0, Removing: 6, Not Upgrading: 0
Remv nmap [7.98+dfsg-1]
Remv liblinear4 [2.3.0+dfsg-5build2]
Remv libblas3 [3.12.1-7ubuntu1]
Remv mailcap [3.75ubuntu1]
Remv mc-data [3:4.8.33-1.1build1]
Remv nmap-common [7.98+dfsg-1]

The exact dependency list varies by package and system history. In this example, mailcap and mc-data appear because the earlier mc purge left them autoremovable, which is why you should review the full list instead of assuming --autoremove only affects the named package. If the dry run looks correct, repeat the command without --dry-run to perform the removal:

sudo apt remove --autoremove nmap

Preview Ubuntu Package Removal Before You Commit

Previewing a removal matters most when the target package is shared, transitional, or part of a larger toolchain. These checks tell you what APT plans to remove, what depends on the package, and which system files the package owns before you commit to the change.

Check Reverse Dependencies Before Removing an Ubuntu Package

apt-cache rdepends lists packages that depend on the target package or on the implementation it pulls in. This is a good check before you remove something that might be part of a wider Ubuntu meta-package. Use APT for normal removals instead of dpkg --remove, because APT resolves dependency changes while dpkg is a lower-level package tool.

apt-cache rdepends telnet

On Ubuntu 26.04, relevant output begins like this:

telnet
Reverse Depends:
  ubuntu-standard
    inetutils-telnet
 |zssh
    inetutils-telnet
 |tucnak
    inetutils-telnet
 |ser2net
    inetutils-telnet
 |procserv
    inetutils-telnet

If a shared package appears in several dependency chains, use a dry run before you remove it so you can see the exact impact on your machine.

Ubuntu 24.04 and 22.04 can format some reverse-dependency lines differently, but the decision is the same: treat shared or meta-package dependencies as a signal to preview the removal before confirming it.

List Ubuntu Package Configuration Files Before You Purge

If you want to know exactly which package-owned system files will disappear during a purge, list them first. This is especially useful before you remove packages that write into /etc/.

dpkg -L mc | grep '^/etc/'

The grep filter keeps the output focused on system configuration files. If you want to adapt the pattern, you can use the grep command in Linux to narrow longer package lists.

/etc/mc
/etc/mc/edit.indent.rc
/etc/mc/filehighlight.ini
/etc/mc/mc.default.keymap
/etc/mc/mc.emacs.keymap
/etc/mc/mc.ext.ini
/etc/mc/mc.menu
/etc/mc/mc.vim.keymap
/etc/mc/mcedit.menu
/etc/mc/sfs.ini
/etc/mc/mc.keymap

Clean Up Unused Ubuntu Dependencies and APT Cache

apt autoremove, apt autoclean, and apt clean solve different cleanup jobs. apt autoremove deletes now-unused packages, apt autoclean removes obsolete downloaded .deb files, and apt clean clears the entire package cache.

Remove Orphaned Dependencies with apt autoremove

Run apt autoremove after standard removals when APT tells you some automatically installed packages are no longer required. Start with a dry run so you can review the cleanup set before APT changes the installed package list.

sudo apt autoremove --dry-run

APT prints a REMOVING list on Ubuntu 26.04, while Ubuntu 24.04 and 22.04 use the older The following packages will be REMOVED wording. Continue only when every package belongs to cleanup you intended; old kernels, desktop helpers, or packages from earlier unrelated work are reasons to stop and review. When the list is safe, run the interactive cleanup command:

sudo apt autoremove

When the packages came from a third-party repository, remove a PPA from Ubuntu after the package cleanup so APT stops offering packages from that source.

Remove Obsolete Package Files with apt autoclean

Use apt autoclean when you want Ubuntu to delete only cached .deb files that are no longer downloadable from your configured repositories. It is the safer cache cleanup option when you still want to keep current package downloads around.

sudo apt autoclean

On a clean cache or a system with no obsolete packages, the command is quiet apart from the standard APT status lines:

Reading package lists...
Building dependency tree...
Reading state information...

Clear the Full APT Cache with apt clean

Use apt clean when disk space matters more than keeping cached downloads. This removes all downloaded .deb files from /var/cache/apt/archives/ and forces Ubuntu to fetch them again the next time you install or reinstall a package.

sudo apt clean
ls -la /var/cache/apt/archives/

After a full cache cleanup, the listing should mainly show the lock file and the partial directory. Dates, sizes, and inode totals vary by system:

total 48
drwxr-xr-x 3 root root 36864 Mar 21 09:18 .
drwxr-xr-x 4 root root  4096 Mar 21 09:18 ..
-rw-r----- 1 root root     0 Jan 29 13:37 lock
drwx------ 2 _apt root  4096 Mar 21 09:18 partial

Troubleshoot Package Removal on Ubuntu

Most package-removal problems come down to one of four causes: the package is already gone, the package name is wrong, the package is too important to remove casually, or the package database needs repair. These checks help you separate those cases quickly.

Restore a Removed Ubuntu Package

If you removed the wrong package, reinstall it with the normal APT install command. This restores the package itself immediately, but it does not bring back custom system conffiles that were already purged.

sudo apt install -y mc
dpkg -l mc | tail -n 1

Verify that the package is installed again:

ii  mc             3:4.8.33-1.1build1 amd64        Midnight Commander - a powerful file manager

Fix Unable to Locate Package Errors on Ubuntu

If Ubuntu responds with E: Unable to locate package package-name, the name is wrong, the package lists are stale, or you are using the command name instead of the actual package name. Start by checking the installed list with a keyword rather than the full package name; for a broader inventory workflow, list installed packages on Ubuntu.

apt list --installed 2>/dev/null | grep -i '^mc/'
sudo apt update

A valid match shows the exact package name before the slash, and apt update refreshes the package lists if they are stale:

mc/resolute,now 3:4.8.33-1.1build1 amd64 [installed]
Hit:1 http://au.archive.ubuntu.com/ubuntu resolute InRelease
Hit:2 http://security.ubuntu.com/ubuntu resolute-security InRelease
Reading package lists...
Building dependency tree...
Reading state information...

Fix apt uninstall Invalid Operation Errors

If you try apt uninstall, APT stops before making changes because uninstall is not a supported operation. On Ubuntu 26.04, the error uses APT 3 wording:

apt uninstall mc

Expected output:

WARNING: apt does not have a stable CLI interface. Use with caution in scripts.

Error: Invalid operation uninstall

Ubuntu 24.04 and 22.04 use the older E: Invalid operation uninstall wording. In either case, replace the command with sudo apt remove package-name or sudo apt purge package-name.

Check Essential Status Before Removing Core Ubuntu Packages

APT blocks many essential packages, but you should still check before you experiment with core components. dpkg is a good example of a package that Ubuntu marks as required and essential.

apt-cache show dpkg | grep -E '^(Essential|Priority):' | head -2

Expected output:

Priority: required
Essential: yes

A blank result here does not automatically make a package safe to remove. Packages such as sudo, desktop meta-packages, and kernel packages can still be disruptive even when they are not marked with Essential: yes.

Repair Broken Dependencies After Package Removal on Ubuntu

When a removal leaves APT in a broken state, start with a diagnostic check before you repair anything. dpkg --audit reports half-installed or half-configured packages, and no output means the package database is currently clean.

dpkg --audit

A healthy system prints no output. If the command returns package names or half-configured states, repair those package database issues before continuing.

If dpkg --audit reports problems, repair the dependency graph with the standard fix command:

sudo apt install -f

After the repair completes, rerun dpkg --audit. If you still see no output, the package database is back in a consistent state.

Conclusion

Package removal on Ubuntu is more predictable now, whether you need a quick uninstall, a full purge, or a cache cleanup. If the package came from a third-party source, remove a PPA from Ubuntu after the package cleanup, then update packages via Ubuntu command line so the remaining system stays current. If you prefer a visual workflow, install Synaptic Package Manager on Ubuntu.