Is there a way invalidate cached assets?

Help
1

I’m using Directus with the S3 driver (MinIO) and trying to understand how asset cache invalidation works for transformed images.

From what I can see:

  • Image transformations requested via
    /assets/{file-id}?width=…&quality=…&format=…
  • Are stored directly in the same bucket
  • With hashed filenames that appear to encode the transformation parameters
  • There is no separate .cache/ directory or prefix when using S3 / MinIO

Each unique combination of transform parameters generates a new derived object, and these objects persist indefinitely.

Questions

  1. Is there any built-in way to invalidate or purge transformed asset variants?
  2. Is there a recommended strategy to avoid cache bloat other than strictly limiting transform presets?

Tech stack & Version’s used:
Docker self-hosted: 11.14.0
Minio community edition with s3 driver

2

There’s currently no built-in way to purge previously generated thumbnails no. In production environments I’d indeed recommend to rely on presets exclusively, so you don’t end up with bad actors blowing up your file storage.

I’ve jotted down your comment on a feature request on our end for future consideration. Thanks! :slight_smile:

3

Thanks for the clarification and for logging the feature request. In long-running setups, unmanaged asset variants can increase storage costs over time, so any future cleanup support would be greatly appreciated.