# Orphan Files from API Uploads Inaccessible in UI
**URL:** https://community.fibery.io/t/orphan-files-from-api-uploads-inaccessible-in-ui/8668
**Category:** Bugs & Issues
**Tags:** files
**Created:** [April 27, 2025, 7:10am UTC](https://community.fibery.io/t/orphan-files-from-api-uploads-inaccessible-in-ui/8668 "2025-04-27T07:10:56Z")
**Posts on this page:** 2
**Page:** 1
### Author:  [@Yuri\_BC](https://community.fibery.io/u/Yuri_BC)
#### Post date: [April 27, 2025, 7:10am UTC](https://community.fibery.io/t/orphan-files-from-api-uploads-inaccessible-in-ui/8668/1 "2025-04-27T07:10:56Z")
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?
---
### Author:  [@Chr1sG](https://community.fibery.io/u/Chr1sG)
#### Post date: [April 27, 2025, 7:47am UTC](https://community.fibery.io/t/orphan-files-from-api-uploads-inaccessible-in-ui/8668/2 "2025-04-27T07:47:15Z")
What is the context?
Why would you want to upload files but not attach them to an entity?