When files are uploaded via /api/files or /api/files/from-url but not attached to an entity’s Files/Files field, they become “orphan” files, as noted in the File API documentation: “there is no place on UI where you can find any arbitrary file.” These fibery/file entities are only accessible via API (e.g., querying or downloading with fibery/secret), rendering them invisible in the Fibery UI.
This is problematic for for API-driven workflows (such as uploading images via n8n). Unattached files can accumulate, consuming storage and causing confusion if users expect UI visibility. So its important to have a UI to view all files including unattached files.
Is it true that the only option is that a developer has to query fibery/file to list all files and filter for orphan files using the API through identifying relations and and comparison of file IDs?