Delete Empty Folders - Remove empty folders easily and quickly - (Updated Jul 2026)


Description:
Delete Empty Folders scans any folder you choose (including all its subfolders) and finds directories that are effectively empty so they can be safely removed. It includes rich preview options, safety controls, and export features so you can see exactly what will be deleted before committing changes, and keep a record of the work performed.


How to use:

1. Select the source folder:
   Click Browse and choose the root folder you want to tidy (for example a temp, backup, or project folder) — or simply drag and drop a folder onto the window to set it. All subfolders under this location are scanned automatically.
   
   
2. Choose safety and preview options:
   Leave “Preview only — scan without deleting (recommended)” ticked to run a dry-run. This lists all folders that would be deleted without actually removing anything. Use this first, especially on a new location, to confirm the rules are behaving as expected before you perform a real cleanup.
   
   
3. Control what counts as “empty”:
   Tick “Treat as empty if only hidden/system files remain (e.g. Thumbs.db)” if you want folders that contain only small system artefacts (such as Thumbs.db or .DS_Store) to be treated as empty and removed.
   Enable “Only process folders empty for at least X days” and set the number of days to avoid touching folders that have been recently created or used. This is ideal for backup destinations or working folders where today's or this week's structure should remain untouched.
   
   
4. Protect data while deleting:
   Select “Send to Recycle Bin (instead of permanent delete)” to route deletions through the Windows Recycle Bin. This provides an extra safety net so any unexpected deletions can be easily restored (the Recycle Bin is then emptied manually whenever you're ready).
   
   
5. Skip folders with larger hidden content:
   Use “Skip if hidden files exceed X MB” when you want to avoid deleting folders that still contain significant hidden data (for example caches, logs, or application data). This prevents misclassifying a folder as empty when it still holds larger hidden files that may be important.
   
   
6. Exclude specific folders:
   Enter one or more folder names in “Exclude folders” (space- or comma-separated, e.g. .git node_modules .svn) to keep known locations out of the scan. This is helpful for preserving template structures, configuration folders, or any directory trees you always want to keep even when they are empty. Your exclude list is saved automatically for next time.
   
   
7. Run the scan and review results:
   Click “Scan / Delete” to start the operation. When running in preview mode, the Results area lists each folder with a “[PREVIEW] Would delete” message, the Results header shows a live count, and a summary reports how many folders were found, how many were skipped, and how long the scan took. You can press Cancel to stop a long scan at any time. Use “Clear” to reset the results, adjust options, and re-run until you're happy with the outcome. When ready, untick preview mode and run again to actually delete the empty folders — you'll be asked to confirm before anything is removed.
   
   
8. Export your findings:
   Click “Export to CSV” to save a structured list of folders for reporting, record-keeping, or further processing in tools like Excel. Click “Export to Text” to save a simple flat list of folder paths, ideal for documentation or quick review.
   
   

Why you would use each feature:

• Preview only: Safest way to test the rules on a new path without deleting anything.
• Treat folders with only hidden/system files as empty: Cleans up leftover Thumbs.db and similar artefacts so library and project trees look tidy.
• Only process folders empty for at least X days: Prevents you from removing structures that are part of current work or recent backups.
• Send to Recycle Bin: Adds a rollback path when reversibility is important.
• Skip if hidden files exceed X MB: Avoids deleting folders that still hold sizeable hidden data that might be needed.
• Exclude folders: Protects specific templates, configs, or skeleton folders that should always exist — and remembers them between sessions.
• Export to CSV/Text: Provides a record of what was (or would be) removed, useful for your own documentation and change tracking.