[Plugin GUI] Delete Extra Files

[dunhill]

Delete Extra Files is a plugin designed to help users delete files contained within the data folder of each book, as well as the data folder itself.

This tool provides a simple graphical interface for locating and securely and efficiently deleting the contents of the data folder.

Key Features
Data Directory Scan: Scans the library to locate and list which books contain files stored within the data folder.

Interactive and Selective GUI: Features a clear list view with support for multiple selections, individual checkboxes, and quick Select All/Deselect All controls to maintain complete control over what is deleted.

File and Folder Cleanup: Deletes files within the data folder and the data folder itself to free up physical disk space.

Case Conflict Reporting: Clearly detects and reports case conflicts within the interface, making them visible for review and manual resolution.

Cross-platform and localized: Fully compatible with Linux, macOS, and Windows with built-in translation support (i18n).

How to use: Install the plugin in Calibre.

Open the tool from your toolbar or menu to run an automatic library scan.

Review the list of books and files within the data folder (selected by default).

Click the delete button to remove the selected items from physical storage.

[JSWolf]

Reading the title of this thread, I was hoping this would scan your Reader and delete orphaned files.

[dunhill]

Originally Posted by JSWolf

Reading the title of this thread, I was hoping this would scan your Reader and delete orphaned files.

That's a very fair point! Given the name, it's easy to see why one might think of the e-reader device itself.

However, Delete Extra Files focuses exclusively on the host side—its main goal is to help you reclaim disk space by cleaning up the leftover files, logs, and bulky data directories left behind inside individual book folders within your local calibre library on your computer.

Cleaning up physical e-readers (like orphaned files on a connected Kindle or Kobo) is a whole different beast due to how tightly closed proprietary file systems can be. For device-side maintenance, specialized device plugins (like Kobo Utilities) are usually the way to go. But who knows? Maybe device-side scanning could inspire a future project ! Thanks for sharing the thought!

[PeterT]

What's different from the built in Calibre "Library Maintenance" function (found in the Library button), that allows you to not only validate the integrity of the calibre database but also remove files / directories in the file system that are not in the database?

[dunhill]

Originally Posted by PeterT

What's different from the built in Calibre "Library Maintenance" function (found in the Library button), that allows you to not only validate the integrity of the calibre database but also remove files / directories in the file system that are not in the database?

That's a fantastic question! calibre's built-in 'Library Maintenance' is a great tool, but it serves a fundamentally different purpose.

calibre's native check looks for completely orphaned files on the hard drive that have no record at all in the database. However, 'extra files' and book-level data directories are actually tracked by calibre's database (list_extra_files). Because of that, the built-in maintenance tool completely ignores them, treating them as valid parts of the book record.

Delete Extra Files fills that exact gap by:

Allowing you to target those registered extra files and bulky data folders to actively reclaim disk space.

Providing an interactive, multi-select GUI with checkboxes so you have granular, book-by-book control over what gets deleted, rather than an automated all-or-nothing global sweep.

Catching and highlighting case-sensitivity conflicts.

So while built-in maintenance handles database-vs-disk discrepancies, this plugin gives you direct control over storage optimization and library hygiene!

[BetterRed]

Does this plugin take heed of the Names to ignore & Extensions to ignore settings in Check library, viz:



BR

[JSWolf]

I know with a Kindle (not MTP as I don't know an MTP Kindle well enough) and Kobo, that you do have access to the drive and can delete extra files/directories.

Would you like to create a plugin to all the extra files on a Kindle or Kobo to be removed? I cannot speak for other Reader brands.

[dunhill]

Originally Posted by BetterRed

Does this plugin take heed of the Names to ignore & Extensions to ignore settings in Check library, viz:

Attachment 225537

BR

That's a great observation! No, the plugin doesn't use the 'Names to ignore' or 'Extensions to ignore' settings, and intentionally so.

Those configuration fields belong exclusively to calibre's global 'Check Library' tool, which scans the file system for completely unindexed, orphaned files that have no record in the database.

In contrast, Delte Extra Files operates directly on files and folders that are formally tracked by calibre's database via its API (list_extra_files / list_data_files). Because it focuses strictly on managing those registered book-level extra files and data directories, it doesn't need global ignore rules.

Keeping it completely separate from calibre's native maintenance settings ensures there's no interference with core functions, keeping the tool fast, focused, and safe to use!

[BetterRed]

I'd be very surprised if Calibre formally tracks the content of a book's 'data' subfolder via its database.

I make extensive use of the 'data' subfolder feature, have done since the day (literally) it was released. And because it didn't exist at that time, I do not use the Manage data file feature… still don't.

I manage the content of the 'data' folders using: Windows File Explorer, zabkat's xplorer², LopeSoft's FileMenu Tools, and AHK scripts.

And, afaik there can only be one subfolder in a calibre book folder, and it must be named 'data', anything else will generate this error in Check Library… unless it's in the Names/Extensions to ignore.



BR

[dunhill]

Thanks for sharing your thoughts and feedback

You're completely right that those folders can be managed externally. However, calibre does actually have native, formal support for this.

If you go to 'Edit metadata' -> 'Manage data files', calibre explicitly allows you to add and manage files inside a book's data directory, tracking them right inside its internal database (which is why APIs like list_extra_files exist in the first place).

That's actually why this plugin handles both scenarios so well:

It cleans up the formal database-tracked extra files and data directories created through calibre's native interface.

At the same time, thanks to its physical disk cleanup layer, it also sweeps away any untracked leftovers or empty folders dropped by external tools or custom scripts.

So whether calibre knows about the file or an external tool put it there, the plugin ensures your hard drive stays clean

At the end of the day, that's really what this plugin is all about. While external management is an option, doing it manually across a large library to find and purge bulky data folders and leftover files is tedious. This plugin simply automates that cleanup with a clear GUI, saving you from hunting them down one by one

Thanks again for the input!

[BetterRed]

Please tell me which table(s) in metadata.db the content of the 'data' folders is recorded - i.e. the file and folder names therein?

All the files and folders I have in my 'data' folders were created by external tools, and they all show up in the Manage data folder dialogue.

I suggest you find another translation tool, the one you're using is generating misleading statements and far too many colloquialisms .

BR

[dunhill]

Hi BetterRed
You are completely correct. My previous wording regarding "database references" was inaccurate and poorly translated, and I apologize for the confusion.
To clarify: the plugin does not interact with any tables in metadata.db. It operates exclusively at the file system level to help manage and delete the contents within a book's data folder (as well as the folder itself), and it also reports case-sensitivity conflicts.
Thank you for pointing out the technical error and helping keep the description accurate. I appreciate your feedback
Best regards