How To Uninstall Eclipse | Remove It Cleanly

Eclipse can be easy to remove, but the right method depends on how it got onto your computer in the first place. Some people installed it with the Eclipse Installer. Others grabbed a ZIP file, unzipped it, and ran it from a folder. On Linux, it might have come from a package manager, a tarball, Snap, or Flatpak.

That difference matters. If you skip it, you can end up with a half-removed app, leftover start menu entries, or old settings that keep showing up after a reinstall. You can also wipe out project files by mistake if your workspace lives inside the Eclipse folder.

This walkthrough shows the clean way to remove Eclipse on Windows, Mac, and Linux, plus what to delete, what to leave alone, and how to start fresh without losing code you still need.

How To Uninstall Eclipse On Windows, Mac, And Linux

Before you remove anything, close Eclipse and make sure no background process is still using the folder. If you have projects stored inside your workspace, copy them somewhere else first. A backup takes a minute. Rebuilding lost code does not.

Windows

On Windows, there are two common setups. If Eclipse was installed through the Eclipse Installer or shows up in Windows app lists, start with the normal Windows removal flow. Microsoft’s page on uninstalling apps and programs in Windows shows the standard path through Settings.

If Eclipse does not appear there, you likely ran it from an extracted folder. In that case, deleting the Eclipse installation folder removes the app itself. Then check your desktop shortcuts, Start menu entries, and taskbar pin. Those can stay behind even after the program files are gone.

Many Windows users also keep their workspace in a separate folder such as C:\Users\YourName\eclipse-workspace. Delete that only if you are sure you do not need the projects, launch settings, or local history inside it.

Mac

On a Mac, Eclipse often sits in the Applications folder as Eclipse.app. Apple’s page on deleting or uninstalling apps on Mac shows the normal removal path. If Eclipse came as a drag-and-drop app, moving it to the Bin removes the main app bundle.

That is only part of the cleanup. Your workspace may live in Documents, your home folder, or a custom folder you picked on first launch. If you plan to reinstall Eclipse and want a blank start, remove the workspace and old settings too. If you plan to keep your projects, leave the workspace alone and just remove the app.

Linux

Linux is less uniform. If you installed Eclipse with a package manager, remove it with that same tool. If you unpacked a tarball by hand, delete the Eclipse directory you created. Then check your home folder for hidden Eclipse data and old launcher entries.

A lot of Linux setups leave user data under the home directory even after the main app is gone. That is handy during upgrades. It is less handy when you want a full reset.

What To Remove And What To Keep

Eclipse is not one single file. It is usually a mix of the app itself, a workspace, caches, install metadata, and plug-ins. Delete the wrong item and you can lose code. Delete too little and old settings come right back on the next install.

Use this table as your sorting map before you send anything to the trash.

Item	Typical Location	Delete It?
Eclipse program folder	Custom install folder, Applications, or extracted ZIP directory	Yes, if you want the app gone
Workspace folder	Custom path such as eclipse-workspace	Only if you do not need projects or local settings
Project files stored inside workspace	Inside workspace subfolders	No, unless you have a backup and want them removed
Start menu or desktop shortcuts	Windows profile and Start menu entries	Yes
Mac app bundle	/Applications/Eclipse.app	Yes
User cache and config data	Hidden folders in your home directory	Yes, if you want a clean reinstall
Installer metadata or bundle pool	Installer-managed folders	Yes, if no other Eclipse install still uses it
Java JDK or JRE	System-wide Java install	No, not unless you want Java removed too

Removing Plug-ins And Packages Inside Eclipse First

If your goal is not “erase Eclipse from my computer” but “get rid of extra stuff I added,” use Eclipse’s own uninstall path before you touch folders. The official Eclipse page on uninstalling software shows the built-in route: open the installation details window, pick the installed software you no longer want, and run the uninstall step from there.

That works well for added features, plug-ins, and packages installed through Eclipse itself. It does not replace removing the whole app from your system. It just strips out pieces inside the installation.

This is the better choice when:

• You want to keep Eclipse but remove one toolset.
• A plug-in is broken and you want to roll it back.
• You are trying to slim down an old install instead of starting over.

If Eclipse still launches and behaves well enough to open menus, do this step first. It keeps the install tidier and cuts down on orphaned plug-in files.

Leftover Folders That Often Stay Behind

When people say “I uninstalled Eclipse, but it still remembers everything,” this is usually the reason. The app may be gone, but user data is still sitting in place. On the next install, Eclipse picks it up and looks just like the old setup.

These leftovers usually live in one of three places:

• Your chosen workspace folder
• Hidden folders in your home directory
• Installer-managed caches or bundle pools

Common names include .eclipse, .p2, and an old workspace folder with your project metadata inside it. If you want a blank reinstall, remove those too after backing up any code you still need.

Be extra careful with the workspace. Some developers store projects inside it. Others point Eclipse to projects stored elsewhere. If your code lives outside the workspace, deleting the workspace removes settings and metadata but leaves the source files alone. If your code lives inside the workspace, deleting it removes the source files too.

Problem After Removal	Likely Cause	What To Do
Eclipse still appears in app lists	Installer entry or package record still exists	Remove it from the system uninstall tool or package manager
Old projects show up after reinstall	Workspace folder was left in place	Delete or rename the old workspace after backup
Old plug-ins return	User metadata or bundle pool still exists	Remove hidden Eclipse data and installer cache
Broken icons or shortcuts remain	Shortcut files were not removed	Delete desktop, Dock, menu, or launcher entries by hand
Reinstall opens the same layout	Config files were kept	Clear hidden config folders in your home directory
Projects vanished	Workspace held the source files	Restore from backup or version control before doing more cleanup

A Clean Reinstall Without Old Baggage

If your real goal is a fresh Eclipse install, treat uninstalling as a two-part job: remove the program, then remove the data you do not want carried over.

A clean reset usually looks like this:

1. Export or back up any projects not already in Git or another version control system.
2. Close Eclipse.
3. Remove the main Eclipse installation from your system.
4. Delete old shortcuts and launcher entries.
5. Delete or rename the workspace folder if you want a blank start.
6. Delete hidden Eclipse metadata and cache folders in your home directory.
7. Install a fresh copy and point it at a new workspace.

Renaming the old workspace is a nice middle ground. You get a fresh install without tossing anything right away. If the new setup works and you do not need old metadata, you can remove the renamed folder later.

Mistakes That Wipe Out Code

The biggest mistake is assuming the workspace is just temporary app data. Sometimes it is. Sometimes it contains the whole project tree. If you created projects with the default path and never changed it, there is a good chance your code sits inside the workspace folder.

Another mistake is removing Java when you only meant to remove Eclipse. Eclipse can be deleted on its own. Java is a separate install in many setups. Leave it alone unless you want it gone.

One more trap: deleting shared installer caches while another Eclipse install still uses them. If you run more than one Eclipse package on the same machine, check that those caches are not shared before you clear them out.

When Deleting The Folder Is Enough

For a lot of people, Eclipse was never “installed” in the classic sense. They downloaded a package, extracted it, and launched the executable from that folder. In that setup, deleting the Eclipse folder removes the app. Then you just tidy up any shortcuts and decide whether the workspace should stay or go.

That is why uninstalling Eclipse can feel odd compared with removing a normal desktop app. Sometimes it behaves like a standard installed program. Sometimes it behaves like a portable folder with a workspace next to it. Once you know which setup you have, the cleanup is pretty simple.