PyCharm can’t delete a project in one step. You take the project off the recent projects list from inside the IDE, then delete the folder yourself in your file manager.
JetBrains built it this way on purpose. A JetBrains Support reply states that removing a project doesn’t delete its source files, by design.
The PyCharm 2026.2 Help (August 2026) only documents the list removal, under File | Recent Projects | Manage Projects. The .idea folder, any venv and the .git folder stay on disk until the folder itself is deleted.
Anything stored outside the project root survives both steps too. Conda environments in the default envs folder are the usual example.
Does PyCharm Delete a Project or Only Remove It?
It only removes it. Taking a project off the recent projects list is all PyCharm does on its own, and no action in the IDE deletes the project folder from disk.
In a reply to a PyCharm 2021.2 user, JetBrains Support calls this intentional. The idea is that nobody should lose a project with no backup by accident.
| Action | Recent list entry | Files on disk | Undo |
|---|---|---|---|
| Remove from Recent Projects | Gone | Untouched | Reopen with Open |
| Delete folder in file manager | Stays until removed | Whole folder gone | Recycle Bin or Trash |
| Delete folder in terminal | Stays until removed | Whole folder gone | None |
| Delete .idea folder only | Stays | Settings gone, code kept | Reconfigure settings |
What a PyCharm project is made of
JetBrains Support staff describe a project as a plain folder with your source files and subfolders in it, plus a .idea folder for the project settings.
- Source files and subfolders
- The .idea folder, with files such as workspace.xml and modules.xml inside
- A venv folder, if the environment sits inside the project
- A .git folder, if the project is a Git repository
Taking the project off the list touches none of that. Deleting the root folder takes everything inside it.
Where Remove from Project View fits
Despite the name, Remove from Project View is not a deletion shortcut. According to the PyCharm 2026.2 Help, it detaches a project that was attached to a primary project in a multi-project window. Nothing gets erased.
Picking the right action
If you only want the clutter gone, remove the entry from the recent list. If you need the disk space back, delete the folder in the file manager.
A project that’s just misbehaving is a different case. Deleting only the .idea folder and reopening the project is the usual suggestion for a broken setup.
How to Remove a Project From the Recent Projects List
Close the project, then go to File | Recent Projects | Manage Projects and click the icon next to the entry. The PyCharm 2026.2 Help (August 2026) says the project then disappears from the Recent Projects menu and the Welcome screen.
- Close the project with File | Close Project, or close its window.
- Open File | Recent Projects from any open PyCharm window.
- Click Manage Projects at the bottom of the list.
- Click the icon next to the project you want gone (a gear in 2026.2).
If the Welcome screen is all you see after closing, a JetBrains Support reply points to the cog button next to the project and its Remove from recent option.
The folder stays on disk. Click Open on the Welcome screen and pick the folder to bring the project back.
One more thing about startup. PyCharm reopens the most recent project at launch by default, and that option lives on the System Settings page of the Settings dialog.
Menu wording by PyCharm version
The labels change between releases, which is why older tutorials often point at menu items you can’t find.
From 2021.1 through 2022.2 the path was File | Open Recent, plus a right-click option on the Welcome screen called Remove Selected from Welcome Screen. Version 2022.3 renamed the menu to File | Recent Projects and kept the right-click option in the docs.
From 2023.1 onward, the page on opening, reopening and closing projects describes only Manage Projects, while the Welcome screen page documents the context menu and the gear icon.
The 2026.2 Help covers both routes. Manage Projects is on the page about opening, reopening and closing projects, and the context menu and gear icon are on the Welcome screen page.
What to Check in Git Before Deleting a Project
The .git folder lives inside the project root, so deleting the folder also deletes any local commits and stashes that never reached a remote, along with every branch that exists only on your machine.
A short pass with git status in the project terminal catches most of what would be lost.
- Modified and staged files appear in the default output, per the git-status manual (unchanged since Git 2.53).
- Untracked files are listed too, marked ?? in short format. Git just doesn’t know about them yet.
- Ignored files stay hidden unless you add –ignored. Local config files and data dumps often sit there.
- Ahead and behind counts against the upstream branch show by default, which is how you spot unpushed commits.
- Stashes need –show-stash before you see how many entries exist. Plain git stash skips untracked files, per Atlassian’s Git tutorial, so check those separately.
If any of that is worth keeping, commit and push it, or copy the folder elsewhere, before deleting anything.
The remote copy is a separate matter. Local deletion leaves the GitHub repository untouched, and removing it means deleting the repository on GitHub itself.
A JetBrains Support reply adds that PyCharm’s version control mappings belong to the individual project, so a deleted project leaves nothing behind that affects the next one.
Deleting the Project Folder With Your File Manager
Close the project in PyCharm, then delete the project root folder in your operating system’s file manager. There’s no dedicated delete project action to use instead.
- Right-click the project root in the Project tool window and use Open in to reveal the folder in your system file manager.
- Close the project with File | Close Project.
- Remove the entry from the recent projects list, or it lingers as a dead link.
- Delete the folder in the file manager.
- Check that the path no longer exists, and that the folder landed in the Recycle Bin or Trash if you might need it back.
Windows
In File Explorer, select the folder and press Delete to send it to the Recycle Bin. Shift+Delete skips the bin, according to Microsoft Support.
The bin can also be switched off per drive with the “Don’t move files to the Recycle Bin” setting, and then a normal Delete is permanent. A Microsoft Tech Community reply adds that network shares don’t use the local bin at all, and that removable or cloud-synced locations can behave differently. Don’t count on a restore there.
macOS
Select the folder in Finder and press Command-Delete. It sits in the Trash until you empty it, and File, then Put Back, returns it to its original place. Apple’s Mac User Guide documents these behaviors.
Linux
Most desktop file managers offer Move to Trash, which you can recover from. The terminal command rm -r skips the Trash entirely.
Run pwd before you use it, since a wrong directory can’t be undone. If you can’t remember the flags, a quick reference of Bash commands will cover them.
What about the Delete command in the Project tool window?
The sources disagree on this one.
A JetBrains Support reply in a PyCharm 2018.1 thread says deleting the folder can’t be done from inside the IDE and points users to the file manager.
The current docs read differently. The PyCharm 2026.2 Project tool window page lists a Delete command for the selected item and warns you to use it with care, but it never says the command works on the project root.
I’d stick with the file manager for the root folder. It behaves the same on every PyCharm version.
Deleting the Virtual Environment and Interpreter Entry
A venv folder inside the project root goes away with the project. An environment stored anywhere else stays on disk until you remove it yourself.
The Python 3.14 documentation names the usual spots. One is a folder called .venv or venv in the project directory, the other a shared container such as ~/.virtualenvs.
| Environment | Typical location | Deleted with the project root |
|---|---|---|
| venv in the project | venv or .venv in the root | Yes |
| venv in a shared container | ~/.virtualenvs | No |
| Conda, default | envs folder of the Conda install | No |
| Conda, project prefix | Subfolder created with –prefix | Yes |
Removing the Python interpreter entry
- Press Ctrl+Alt+S and open Python | Interpreter, or click the Python Interpreter selector in the status bar and choose Interpreter Settings.
- Expand the interpreter list and click Show All.
- Select the interpreter you no longer need.
- Click the Remove Interpreter button.
Do this before deleting the folder, while the Interpreter page is one click away.
The PyCharm 2026.2 Help (September 2026) frames the step as removing the interpreter from the project settings. It says nothing about erasing the environment folder.
That part is a separate job, and a guide on deleting a venv folder covers it.
Deleting a Conda environment
To delete one by name, run conda env remove –name myenv, or conda remove –name myenv –all. When the environment lives outside the default envs folder, pass –prefix with the full path instead. Afterwards, conda info –envs should no longer list it.
The conda 26.9 documentation notes that –name cannot find environments placed outside the default folder, which is why the path form matters.
What stays behind after the folder is gone
Interpreter definitions don’t live in the project folder alone. JetBrains Support staff say PyCharm keeps the per-project binding in .idea/misc.xml and workspace.xml, and the global entry in the options/jdk.table.xml file of the configuration folder (a file JetBrains does not document in detail).
The PyCharm 2026.2 Help adds that interpreter paths are stored in the IDE’s per-installation configuration directory, never in .idea, and that misc.xml holds only the interpreter name (project-jdk-name).
The global entry sits in the configuration folder, outside the project, so deleting the project folder doesn’t touch it. If PyCharm can’t find the interpreter binary, it shows an Invalid environment warning, per the 2026.2 Help. And any other project that reuses the same environment breaks when the folder disappears.
So before deleting an external environment, check whether any other project points to it.
One failure mode shows up in a JetBrains Support thread. A user deleted a project folder, then hit a “project directory is not empty” error when recreating a project under the same name, and the error cleared once the Conda environment made for the project was deleted too.
That is a single user report, not documented JetBrains behavior.
What the .idea Folder Stores and When to Delete It Alone
Deleting .idea resets the project’s own settings and leaves your code alone. Those settings are a set of XML files under it, according to the PyCharm 2026.2 Help.
JetBrains Support staff suggest the reset for broken interpreter setups. Close the project, remove .idea, reopen.
What the main files hold
- workspace.xml keeps personal state, including user-specific run configurations (JetBrains Support).
- misc.xml records the interpreter chosen for the project (JetBrains Support).
- modules.xml lists the modules, and JetBrains treats it as generated and ignorable in Maven and Gradle projects (IntelliJ IDEA Help).
What a reset costs
You lose the interpreter binding and your personal run configurations, along with the other per-project IDE settings.
Your source files, the .git folder and the venv folder all stay, and the project keeps its entry in the recent projects list.
On reopening, PyCharm treats a directory without .idea as a non-PyCharm directory. It creates a new IDE project and sets up a Python interpreter, according to the 2026.2 Help.
The Configure a Python interpreter Help page says the default interpreter is applied automatically to projects that have no .idea folder. You set it under File | New Projects Setup | Settings for New Projects.
Should .idea go into Git?
For a solo project, ignore it.
IntelliJ IDEA’s documentation says the IDE moves workspace.xml to the ignore list on its own once version control is enabled. Adding the whole folder to a .gitignore file goes one step further and stops stray settings from reaching teammates.
Teams have a real alternative. A JetBrains Support article recommends sharing most of .idea and keeping out only user-specific files such as workspace.xml, and community comments under it show teams split on ignoring the whole folder. Pick one rule per repository and write it down.
Can You Recover a Deleted PyCharm Project?
Only if the folder landed in the Recycle Bin or Trash, or a copy exists elsewhere. PyCharm has no command that restores a deleted project folder.
Restoring from the Recycle Bin or Trash
On Windows, open the Recycle Bin, right-click the project folder and choose Restore. The folder returns to its original path with .idea, .git and any venv inside it.
On macOS, the Trash keeps the folder only until it is emptied. Apple Support documents a Finder setting that empties the Trash automatically after 30 days.
When the folder was deleted permanently
- Stop writing to that drive.
- Check backups and cloud version history first.
- On Windows, try Windows File Recovery, and save the recovered files to a different drive.
The first two steps come from a Microsoft Tech Community reply on permanent deletions. The Windows File Recovery step comes from Microsoft Support, which requires the source and destination drives to differ.
The same Tech Community reply says a network share needs the share’s own backup, because local tools cannot reach it, and Microsoft Support notes that Windows File Recovery does not support network shares.
What Local History can and cannot restore
Local History can’t undelete a project. The PyCharm 2026.2 Help describes restoring deleted files from the Project tool window of an open project, with revisions kept for the last 5 working days by default.
It is stored in the PyCharm system directory, outside the project, and the Help says it is cleared when you install a new PyCharm version. The Help does not describe restoring a project folder deleted outside the IDE.
In short, it works for a single file deleted inside the IDE and is unreliable for a whole folder.
Rebuilding from a remote copy
A pushed repository restores source files and branch history. Cloning the GitHub repository again works from the Welcome screen (Clone) or from VCS | Get from Version Control, per the 2026.2 Help.
Commits that were never pushed, stashes and ignored files do not come back.
The venv is the one piece not worth recovering. The Python documentation calls virtual environments disposable and says to recreate them instead of moving or copying them.
Open the cloned folder and, if it holds a requirements.txt or setup.py, PyCharm offers to build a fresh virtual environment in PyCharm from it.
FAQ About Deleting a Project in PyCharm
Why does the project folder refuse to delete?
An open project is the usual cause, so close it with File | Close Project and try again.
On macOS, a locked item also needs your confirmation before it moves to the Trash, according to Apple Support.
How do I delete the GitHub repository behind a PyCharm project?
Delete it on GitHub, in the repository settings, because PyCharm has no command for it.
Every existing clone keeps the full history after the remote disappears, so a local copy doubles as a quick backup.
Can I clear the whole recent projects list at once?
The PyCharm 2026.2 Help documents removal one project at a time, through File | Recent Projects | Manage Projects.
It describes no clear-all action, so repeat the steps for each entry.
Does PyCharm Pro delete projects differently from the free core?
No. The documented removal steps are the same in both. Since the Community and Professional editions were merged into a unified PyCharm, the 2026.2 Help refers to the paid tier as PyCharm Pro.
PyCharm Pro adds remote interpreters over SSH, Docker, Docker Compose and WSL, so check those interpreter entries when you clean up.
Checking PyCharm for Leftovers After Deleting a Project
A deleted project is fully gone only when the recent projects list and the interpreter list no longer point at its old path. Run the checks in this order.
- Recent Projects menu and Welcome screen
- Python interpreter list, expanded with Show All
- Recycle Bin or Trash, emptied last
The bin comes last because emptying it removes the only quick undo. If a check shows the wrong folder was deleted, restoring still takes one click.
The cost is disk space, since a large venv folder keeps taking it up until the bin is emptied.
The sequence matches the PyCharm 2026.2 Help as of 7 October 2026. A native delete-project action in a later release would replace the file manager step.
With the list and interpreters clean, the next job is a fresh start, and a guide to creating a new project in PyCharm covers it.
- Notepad++ Android Options: Apps That Come Close - October 21, 2026
- Data Management Services: A Practical Guide for Growing Companies - October 21, 2026
- MongoDB Cheat Sheet - October 20, 2026
