diff --git a/.wordlist.txt b/.wordlist.txt
index d717725270..e31f4635de 100644
--- a/.wordlist.txt
+++ b/.wordlist.txt
@@ -453,6 +453,7 @@ FroshTools
 Fullstack
 GBP
 GCM
+GCS
 GDPR
 GHSA
 GIFs
diff --git a/guides/hosting/infrastructure/filesystem.md b/guides/hosting/infrastructure/filesystem.md
index 3c4b04eed9..aa7806fa00 100644
--- a/guides/hosting/infrastructure/filesystem.md
+++ b/guides/hosting/infrastructure/filesystem.md
@@ -425,6 +425,22 @@ shopware:
     batch_write_size: 250
 ```
 
+### Disable last-modified version strategy for theme assets
+
+By default, Shopware appends a `?{timestamp}` cache-busting suffix to every theme asset URL by reading the file's last modified time from the filesystem. On remote filesystems such as S3 or GCS (Google Cloud Storage), this can trigger a filesystem metadata call per asset path on cache miss (for example, after a cache flush).
+
+When the default `SeedingThemePathBuilder` is active — which is the case unless you have explicitly changed `storefront.theme.theme_path_builder_id` — this timestamp suffix is redundant. The path builder already rotates the asset path on every theme compilation, which is the actual cache-invalidation event. You can disable the last-modified lookups entirely:
+
+```yaml
+# config/packages/shopware.yaml
+shopware:
+  filesystem:
+    theme:
+      use_last_modified_version_strategy: false
+```
+
+The option defaults to `true`, so existing installations are unaffected. Set it to `false` on shops with a remote theme filesystem to eliminate the extra metadata calls.
+
 ### Add your own adapter
 
 To support a storage backend Shopware does not ship with, create a Flysystem adapter (see the [official Flysystem guide](https://flysystem.thephpleague.com/docs/advanced/creating-an-adapter/)) and wrap it in an `AdapterFactory`: