Cache pruning

[aspasia-patron]

yazi --debug output

Version: 25.4.8

Please describe the problem you're trying to solve

There's no clean way of pruning yazi's cache directory. While limiting cache size is an option, deleted image previews will evict old yet existing previews, thus making yazi experience slower.

Would you be willing to contribute this feature?

• Yes, I'll give it a shot

Describe the solution you'd like

Yazi should track file updates and prune preview cache.

Additional context

No response

Checklist

• I have searched the existing issues/discussions
• The latest nightly build doesn't already have this feature

[github-actions]

Hey @aspasia-patron, I noticed that you did not correctly follow the issue template. Please ensure that:

• The requested feature does not exist in the newest nightly build.
• The debug information (yazi --debug) is updated for the newest nightly.
• The non-optional items in the checklist are checked.

Issues with needs info will be marked ready once edited with the proper content, or closed after 2 days of inactivity.

[hankertrix]

Already supported with yazi --clear-cache.

[aspasia-patron]

Already supported with yazi --clear-cache.

Doesn't even work with permanent cache_dir

You've changed the default cache directory, for your data's safety, please clear it manually:

Seemingly just deletes all cached previews instead of pruning

[aspasia-patron]

Deleting & repopulating cache_dir doesn't solve the problem. it makes yazi even slower compared to limiting cache size since it'll only regenerate previews for a smaller number of files, depending on cache size, preview settings etc.

[sxyazi]

Yazi should track file updates

The cache file name is a one-way irreversible MD5 hash, and the criteria that different preloader plugins use to determine if the cache is valid may vary – it depends on how the plugin implements its preload() method. In this case, how should file updates be tracked?

[aspasia-patron]

how should file updates be tracked?

Deleting image previews on file actions, i.e delete or trash-put, is a much easier approach as a starting point.

[aspasia-patron]

Yazi can clear cached previews similar to how media players clear icc, shaders cache for files that weren't accessed in the last day or two upon limiting cache_dir limits.

[sxyazi]

There's no plan to have this feature built-in, because it would double the I/O operations, that is, for every file deletion operation, a new deletion or cache check I/O operation would need to be initiated.

But, you should be able to implement it through the plugin system by subscribing to the trash and delete events - when these events are received, you can use ya.file_cache() to obtain the cached path corresponding to the deleted file's URL, and then delete the file at that path.

[github-actions]

I'm going to lock this issue because it has been closed for 30 days. ⏳
This helps our maintainers find and focus on the active issues. If you have found a problem that seems similar to this, please file a new issue and complete the issue template so we can capture all the details necessary to investigate further.