storage.list() does not return custom file metadata (only system fields)

[thewh1teagle]

Bug report

• I confirm this is a bug with Supabase, not with my own application.
• I confirm I have searched the Docs, GitHub Discussions, and Discord.

Describe the bug

When uploading a file with custom metadata (e.g. metadata: { filename: "My Real Filename.txt" }), the .list() method only returns system metadata fields (eTag, size, mimetype).
Custom metadata is not included, even though it is stored correctly in storage.objects (and retrievable via .info()).

To Reproduce

Steps to reproduce:

1. Upload a file with custom metadata:

   const { data, error } = await supabase.storage
     .from("bucket")
     .upload("path/file.txt", file, {
       metadata: { filename: "My Real Filename.txt" },
     });

2. List files:

   const { data } = await supabase.storage.from("bucket").list("path");
   console.log(data[0].metadata); // only shows system fields, no custom filename

3. Fetch file info:

   const info = await supabase.storage.from("bucket").info("path/file.txt");
   console.log(info.data.metadata); // shows custom fields as expected

Expected behavior

storage.list() should return both system and custom metadata, not just system fields.
This would avoid needing N .info() calls for N files, which has a significant performance impact.

System information

• OS: macOS
• Browser: Chrome
• supabase-js: 2.50.0
• Node.js: v22.18.0

Additional context

Confirmed that custom metadata exists in storage.objects.
.info() retrieves it correctly, but .list() omits it.
This looks like a storage server issue rather than a storage-js issue.

It would also be very useful to have a first-class way to update custom user metadata after upload (for example, renaming the filename field in metadata without re-uploading the file).

[robksawyer]

Yeah, I'm not able to get metadata to save on the files at all. Even when using the service client.

[noook]

I think this migration should do the trick, at least for the v2 search method:

(Obviously, in a new file, this is just a diff with the latest version of the method)

diff --git a/migrations/tenant/0039-add-search-v2-sort-support.sql b/migrations/tenant/0039-add-search-v2-sort-support.sql
index a325c0d..8a181a5 100644
--- a/migrations/tenant/0039-add-search-v2-sort-support.sql
+++ b/migrations/tenant/0039-add-search-v2-sort-support.sql
@@ -65,7 +65,7 @@ BEGIN
                     updated_at,
                     created_at,
                     NULL::timestamptz AS last_accessed_at,
-                    NULL::jsonb AS metadata
+                    '{}'::jsonb AS metadata
                 FROM storage.prefixes
                 WHERE name COLLATE "C" LIKE $1 || '%%'
                     AND bucket_id = $2
@@ -83,7 +83,7 @@ BEGIN
                     updated_at,
                     created_at,
                     last_accessed_at,
-                    metadata
+                    user_metadata || metadata AS metadata
                 FROM storage.objects
                 WHERE name COLLATE "C" LIKE $1 || '%%'
                     AND bucket_id = $2

[dominicbachmann]

Is there an official workaround for problem?