You've finally had enough of the lag. Or maybe you're moving over to VS Code or IntelliJ IDEA and you just don't need that massive folder taking up space anymore. Whatever the reason, you've realized that knowing how to remove eclipse isn't as straightforward as just hitting an "uninstall" button in your control panel. It's annoying. Eclipse is one of those old-school Java-based tools that doesn't always play by the modern rules of software installation.
If you go looking for an uninstaller.exe, you won't find one.
Because Eclipse is essentially a "portable" application—even when installed via the official installer—it tends to scatter its personality all over your hard drive like a messy roommate. You delete the main folder, but then you realize your workspace settings, your .p2 cache, and those weirdly specific Java configurations are still hanging around. Let's get into the weeds of how to actually scrub it from your machine so your system feels fresh again.
The Problem with the Eclipse Installer
Most people download the Eclipse Installer (Oomph) these days. It’s meant to make things easier, but it creates a bit of a maze. When you use the installer, it doesn't just put files in one spot. It creates a shared bundle pool. This is basically a library of plugins that different versions of Eclipse can share.
If you just drag the Eclipse icon to the Trash or hit delete on the Program Files folder, that bundle pool stays. It’s dead weight.
To really handle how to remove eclipse, you have to think like a sysadmin. You need to hunt down the metadata. You need to find the artifacts. Honestly, if you don't do this, the next time you try to install a fresh version of Eclipse, it might try to "helpfully" inherit broken settings from your old, deleted version. That’s a recipe for a headache.
Windows Users: It’s All About the Folders
Since there is no entry in "Add or Remove Programs" for many versions of Eclipse, you have to do the manual labor. First, find where you actually put the thing. Usually, it's in C:\Users\YourName\eclipse or perhaps C:\Eclipse.
Delete that folder first. Just shift-delete it. Gone.
But wait. Your user directory is still hiding secrets. Navigate to C:\Users\YourName. Look for a folder named .p2. This is the big one. It stores all those shared plugins and repository data we talked about. If you aren't planning on using any other Eclipse-based tools (like Spring Tool Suite or various specialized IDEs), delete .p2 immediately. It can easily take up several gigabytes of space over time.
Then there’s the .eclipse folder. This holds your specific configuration for the version you were running. Delete it too.
Then comes the workspace. This is where your code lives. Be careful here. You probably want to keep your projects, but if you want to wipe the slate clean, you'll need to delete the .metadata folder inside your workspace directory. That's where all your UI preferences, window layouts, and plugin states live. If you don't delete .metadata, your next IDE might get confused if you try to import that same workspace.
A Quick Word on Java
Eclipse runs on the Java Runtime Environment (JRE) or Java Development Kit (JDK). Removing Eclipse does not remove Java. If you only installed Java to use Eclipse, you might want to head over to your "Apps & Features" settings and uninstall the JDK separately. However, keep in mind that other apps—like Minecraft or some older corporate software—might still need it. Check before you nuking it.
macOS: The Library is Hiding Your Files
On a Mac, it's a bit more "Apple-fied," but the same rules apply. You probably dragged the Eclipse app to your Applications folder. Dragging it to the Trash is step one.
Step two is digging into the Library.
Open Finder, click "Go" in the menu bar, hold down the Option key, and click "Library." You're looking for ~/.p2 and ~/.eclipse in your home directory. Mac users often miss these because they are hidden files (starting with a dot). You can toggle hidden files by pressing Cmd + Shift + Period.
Check ~/Library/Preferences/ for anything starting with org.eclipse.
Search ~/Library/Saved Application State/ as well.
The Eclipse Oomph installer also likes to hide stuff in ~/.eclipse. If you find a folder named org.eclipse.oomph, kill it. It’s just tracking your installation history and preference synchronization.
Linux: Terminal is Your Friend
If you're on Ubuntu, Fedora, or any other distro, you likely installed Eclipse either by extracting a .tar.gz or via a snap/flatpak.
If you used a tarball, it's simple: rm -rf ~/eclipse (or wherever you put it).
Then, rm -rf ~/.eclipse and rm -rf ~/.p2.
If you used a Snap, use sudo snap remove eclipse.
For Flatpak, it's flatpak uninstall org.eclipse.Java.
The thing about Linux is that it's actually the easiest OS to clean up, provided you know where your home config files are. Just remember that the .p2 directory is the most common culprit for "ghost" files that stick around after the main binary is gone.
Why Does This IDE Stick Around Like This?
You might be wondering why the Eclipse Foundation hasn't made a simple uninstaller. It’s mostly about the philosophy of the software. Eclipse was designed to be modular. It’s a collection of plugins held together by a core framework (Equinox). Because it was built to be portable, it doesn't want to mess with your Registry (on Windows) or your system-level files too much.
The downside? It leaves the "cleaning up" to the user.
It’s a bit like a Lego set. You can take the castle apart, but if you don't put the bricks back in the box, they’re just going to stay on the floor where you can step on them later.
Cleaning Up the Workspace Metadata
If you're keeping your code but want to remove the "Eclipse-ness" from your projects, you need to look at the project folders themselves. Each project has a .project file and a .classpath file.
If you’re moving to IntelliJ, IntelliJ can actually read these files to import your project.
But if you’re moving to something like VS Code with a Maven or Gradle setup, those Eclipse files are just clutter. You can delete them. Just don't delete your src folder or your pom.xml / build.gradle files. Those are your actual work. Everything else is just Eclipse’s way of remembering how to build it.
Common Stumbling Blocks
Sometimes, you try to delete the Eclipse folder and Windows shouts at you that a "file is in use." This is usually because a background process is still running.
- Open Task Manager (
Ctrl + Shift + Esc). - Look for
javaw.exeor anything with "Eclipse" in the name. - Kill the process.
- Try deleting again.
Another issue is the "Long Paths" error on Windows. Eclipse creates very deep folder structures in its metadata. If Windows won't let you delete a folder because the path name is too long, try moving the folder to the root of your C: drive first, or use a tool like 7-Zip to delete it (7-Zip’s file manager handles long paths better than Windows Explorer).
Final Checklist for Total Removal
To be absolutely sure you've mastered how to remove eclipse and left nothing behind, run through this mental list:
- The Main Binary: The folder where the
eclipse.exeor Eclipse app lives. - The Config Folder: Found in your User/Home directory under
.eclipse. - The Bundle Pool: The
.p2directory in your User/Home folder. - The Oomph Cache: Usually found within the
.eclipsedirectory. - Workspace Metadata: The
.metadatafolder inside your code workspace. - Desktop Shortcuts: Don't forget to manually delete any icons you pinned to your taskbar or start menu.
- Java Environment Variables: If you set up
JAVA_HOMEspecifically for Eclipse and no longer need it, go to your system environment variables and clean those up too.
What to Do Next
Once the files are gone, give your machine a quick reboot. It’s not strictly necessary, but it clears out any temp files that might be lingering in the system's memory.
Now you have a clean slate.
If you are switching to another IDE, start by importing your source code as a "New Project from Existing Sources." Don't try to copy-paste the old Eclipse configuration files into your new tool. Let the new IDE generate its own metadata. This prevents the "it worked in my old IDE but not here" bugs that drive developers crazy.
If you’re totally done with Java development, take a look at your installed programs one last time. Removing the JDK (Java Development Kit) can save you a few hundred megabytes and reduces your attack surface for security vulnerabilities. Just make sure you really don't need it for anything else before you click uninstall.
📖 Related: The MacBook Pro Model A1708: Why This "Escape" Edition Still Has a Cult Following
Check your PATH variable too. On Windows, type "environment variables" into the start menu, click "Edit the system environment variables," then "Environment Variables." Look at the "Path" entry under System Variables. If there are references to Eclipse or specific Java bin folders you just deleted, remove those entries. It keeps your command line from getting confused when you type java -version later on.
Clean system, clean mind. You're ready to move on to whatever tool is next in your workflow.