# Improving the Files Field: Naming, Sharing, and Organization **URL:** \ **Category:** Ideas & Features\ **Tags:** files\ **Created:** [March 21, 2025, 2:54pm UTC](https://community.fibery.io/t/improving-the-files-field-naming-sharing-and-organization/8486 "2025-03-21T14:54:21Z")\ **Posts on this page:** 20\ **Page:** 1
**Author:** ![Edan](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/edan/32/11187_2.png) [@Edan](https://community.fibery.io/u/Edan)\ **Post date:** [March 21, 2025, 2:54pm UTC](https://community.fibery.io/t/improving-the-files-field-naming-sharing-and-organization/8486/1 "2025-03-21T14:54:22Z")
Right now, the **File** field is pretty painful to work with — so much so that we’re using a janky workaround involving automations and Google Drive just to handle basic use cases. Two improvements to seriously level up the file-handling experience in Fibery: * * * **Download All** Downloading files one by one gets brutal fast. If an entity has more than a few files, it’s a slog. A simple Download All option would be a huge time-saver. **Easier Access & Sharing** Accessing files via API, Make, or Zapier involves extra hoops. You first need to fetch the file details (`secret` and `id`), then make a separate call to the `api/files` endpoint just to upload or download. Even then, you face roadblocks since there’s no file `url` field to work with. A temporary, time-limited URL (like [Notion’s 1-hour link](https://developers.notion.com/reference/file-object)) would make file handling much smoother and still keep things secure. * * * These two enhancements would remove a ton of friction and reduce the need to duct-tape other tools just to handle basic workflows. Would love to see Fibery take a step forward here! ---
**Author:** ![Edan](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/edan/32/11187_2.png) [@Edan](https://community.fibery.io/u/Edan)\ **Post date:** [April 5, 2025, 1:47am UTC](https://community.fibery.io/t/improving-the-files-field-naming-sharing-and-organization/8486/2 "2025-04-05T01:47:16Z")
The more I work with the **Files** field, the more friction I’m running into. A few improvements that would make a big difference: - **Field Renaming** : You can’t rename the Files field — it’s always just **Files** , which isn’t ideal for real-world workflows. - **Multiple File Fields** : Unlike other fields, you can’t add more than one Files field to an entity. This makes it hard to separate and organize different types of files. A practical example to tie it all together: An e-commerce brand using Fibery to manage product inventory, with Product and Variant databases. - In the **Product** DB, you’d want one Files field for **Licenses & Certificates** (PDFs like GS certificates or SKU labels) and another for **Product Images** — keeping them separate makes managing and finding files much easier. - In the **Variant** DB, you’d want the same logic — one field for variant-specific images and another for supporting docs like awards or compliance files. This type of file structure unlocks powerful automation workflows — especially when connected to tools like **Make**. Imagine pulling images or certificates into flows that update inventory, sync with third-party tools, or generate assets automatically. To unlock all of this, the Files field needs a few key improvements and a bit more flexibility. ---
**Author:** ![RonMakesSystems](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/ronmakessystems/32/14122_2.png) [@RonMakesSystems](https://community.fibery.io/u/RonMakesSystems)\ **Post date:** [April 5, 2025, 10:03am UTC](https://community.fibery.io/t/improving-the-files-field-naming-sharing-and-organization/8486/3 "2025-04-05T10:03:19Z")
I’ll add one more: Downloading all files from the entity menu (not from the files field). Where it downloads all files from all file fields. Plus accessible in bulk action across entities. Then you can click on 10 entities then download files and it all gets downloaded your computer. Bonus if the files are in nested folders by entity + by files field. ---
**Author:** ![mdubakov](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/mdubakov/32/10_2.png) [@mdubakov](https://community.fibery.io/u/mdubakov)\ **Post date:** [April 5, 2025, 12:06pm UTC](https://community.fibery.io/t/improving-the-files-field-naming-sharing-and-organization/8486/4 "2025-04-05T12:06:20Z")
As I mentioned several times, Files in Fibery are very poor. In fact they are still a result of our very early prototype iteration and we did not change it since 2021. We will fix it around May/June. ---
**Author:** ![gasby](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/gasby/32/11429_2.png) [@gasby](https://community.fibery.io/u/gasby)\ **Post date:** [April 11, 2025, 11:47am UTC](https://community.fibery.io/t/improving-the-files-field-naming-sharing-and-organization/8486/5 "2025-04-11T11:47:38Z")
Can you share any previews on how the Files will change? 🤓 ---
**Author:** ![mdubakov](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/mdubakov/32/10_2.png) [@mdubakov](https://community.fibery.io/u/mdubakov)\ **Post date:** [April 11, 2025, 5:21pm UTC](https://community.fibery.io/t/improving-the-files-field-naming-sharing-and-organization/8486/6 "2025-04-11T17:21:51Z")
Not yet, we will start design only in May ---
**Author:** ![interr0bangr](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/interr0bangr/32/8089_2.png) [@interr0bangr](https://community.fibery.io/u/interr0bangr)\ **Post date:** [April 30, 2025, 2:32pm UTC](https://community.fibery.io/t/improving-the-files-field-naming-sharing-and-organization/8486/7 "2025-04-30T14:32:41Z")
Hey @mdubakov, is the file improvement work still on the schedule for May? Running into scenarios this week that could really use multiple, separate file fields on a single entity (like “Site Assessment Photos” and “Design Drawings”), or alternatively, a way to filter/sort/organize the files within a single file field so users can find the files relevant to them. ---
**Author:** ![mdubakov](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/mdubakov/32/10_2.png) [@mdubakov](https://community.fibery.io/u/mdubakov)\ **Post date:** [April 30, 2025, 2:34pm UTC](https://community.fibery.io/t/improving-the-files-field-naming-sharing-and-organization/8486/8 "2025-04-30T14:34:29Z")
> [@interr0bangr](#): > > is the file improvement work still on the schedule for May? I hope we will start in May, still in plans for Q2 anyway. ---
**Author:** ![Sppam\_Kontrol](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/sppam_kontrol/32/12112_2.png) [@Sppam\_Kontrol](https://community.fibery.io/u/Sppam_Kontrol)\ **Post date:** [October 5, 2025, 1:51am UTC](https://community.fibery.io/t/improving-the-files-field-naming-sharing-and-organization/8486/9 "2025-10-05T01:51:00Z")
Any update on the development and release? @mdubakov ---
**Author:** ![mdubakov](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/mdubakov/32/10_2.png) [@mdubakov](https://community.fibery.io/u/mdubakov)\ **Post date:** [October 6, 2025, 6:44am UTC](https://community.fibery.io/t/improving-the-files-field-naming-sharing-and-organization/8486/10 "2025-10-06T06:44:24Z")
Development started 2 weeks ago, I hope we will start releasing something in 2 weeks ---
**Author:** ![Sppam\_Kontrol](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/sppam_kontrol/32/12112_2.png) [@Sppam\_Kontrol](https://community.fibery.io/u/Sppam_Kontrol)\ **Post date:** [October 7, 2025, 3:39am UTC](https://community.fibery.io/t/improving-the-files-field-naming-sharing-and-organization/8486/11 "2025-10-07T03:39:05Z")
Hopefully this to be release soon. We are literally drowning from external users who are not uploading the required files since we are unable to set required fields for each files. We are even unsure if we need to use other thirdparty solutions just to get the forms submission right and have the hassle to migrate the values manually back to the fibery app. ---
**Author:** ![mdubakov](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/mdubakov/32/10_2.png) [@mdubakov](https://community.fibery.io/u/mdubakov)\ **Post date:** [October 7, 2025, 7:15am UTC](https://community.fibery.io/t/improving-the-files-field-naming-sharing-and-organization/8486/12 "2025-10-07T07:15:26Z")
> [@Sppam\_Kontrol](#): > > We are literally drowning from external users who are not uploading the required files since we are unable to set required fields for each files. Here it is unlikely that Required option for File field will be released in nearest future, so far demand is not high and we are prioritizing other things, like Gallery View ---
**Author:** ![Sppam\_Kontrol](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/sppam_kontrol/32/12112_2.png) [@Sppam\_Kontrol](https://community.fibery.io/u/Sppam_Kontrol)\ **Post date:** [October 7, 2025, 5:38pm UTC](https://community.fibery.io/t/improving-the-files-field-naming-sharing-and-organization/8486/13 "2025-10-07T17:38:45Z")
Required under the file field setting is not critical. I think we can set that as part of the FORMS to make it required. ---
**Author:** ![bear](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/bear/32/12872_2.png) [@bear](https://community.fibery.io/u/bear)\ **Post date:** [October 7, 2025, 8:12pm UTC](https://community.fibery.io/t/improving-the-files-field-naming-sharing-and-organization/8486/14 "2025-10-07T20:12:08Z")
Thanks for the clarity posts like these provide. Very useful to know what’s coming and when so I can anticipate on it - of course some things take longer than anticipated that’s normal. ---
**Author:** ![mdubakov](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/mdubakov/32/10_2.png) [@mdubakov](https://community.fibery.io/u/mdubakov)\ **Post date:** [October 23, 2025, 1:30pm UTC](https://community.fibery.io/t/improving-the-files-field-naming-sharing-and-organization/8486/15 "2025-10-23T13:30:30Z")
> [@interr0bangr](#): > > Running into scenarios this week that could really use multiple, separate file fields on a single entity (like “Site Assessment Photos” and “Design Drawings”) Released today > [@October 23, 2025 / sauropod Multiple Files Fields per Database and some unexpected improvements](https://community.fibery.io/t/october-23-2025-multiple-files-fields-per-database-and-some-unexpected-improvements/9871): > > Multiple Files Fields per Database Now (and finally!) you can add multiple File Fields to any database and define whether each field allows one or many files. Previously, only a single File Field was supported, which created several annoying limitations. This update removes that restriction and our hands are free to improve files support in Fibery further person_getting_massage. Some new small things related to files in this release: Refined the File Field UI (a little bit) Added … ---
**Author:** ![mdubakov](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/mdubakov/32/10_2.png) [@mdubakov](https://community.fibery.io/u/mdubakov)\ **Post date:** [October 23, 2025, 1:31pm UTC](https://community.fibery.io/t/improving-the-files-field-naming-sharing-and-organization/8486/16 "2025-10-23T13:31:24Z")
> [@Edan](#): > > **Multiple File Fields** : Unlike other fields, you can’t add more than one Files field to an entity. This makes it hard to separate and organize different types of files. Released today > [@October 23, 2025 / sauropod Multiple Files Fields per Database and some unexpected improvements](https://community.fibery.io/t/october-23-2025-multiple-files-fields-per-database-and-some-unexpected-improvements/9871): > > Multiple Files Fields per Database Now (and finally!) you can add multiple File Fields to any database and define whether each field allows one or many files. Previously, only a single File Field was supported, which created several annoying limitations. This update removes that restriction and our hands are free to improve files support in Fibery further person_getting_massage. Some new small things related to files in this release: Refined the File Field UI (a little bit) Added … ---
**Author:** ![mdubakov](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/mdubakov/32/10_2.png) [@mdubakov](https://community.fibery.io/u/mdubakov)\ **Post date:** [November 13, 2025, 2:23pm UTC](https://community.fibery.io/t/improving-the-files-field-naming-sharing-and-organization/8486/17 "2025-11-13T14:23:01Z")
> [@Edan](#): > > **Field Renaming** : You can’t rename the Files field — it’s always just **Files** , which isn’t ideal for real-world workflows. Now you can rename files > [@November 13, 2025 / tulip Fibery Mobile (private beta), Share Space without sharing its data, Insert Views into Whiteboards,](https://community.fibery.io/t/november-13-2025-fibery-mobile-private-beta-share-space-without-sharing-its-data-insert-views-into-whiteboards/9997): > > Today’s release is modestly packed with assorted features from many areas. Enjoy! tulip Fibery Mobile (private beta) We’re excited (really!) to share the first private beta version of the Fibery mobile app for iOS and Android. We’ve re-worked navigation, added push notifications (make sure to turn them on in settings), and refreshed parts of the interface for a better mobile experience. It’s still work in progress, and some areas aren’t fully optimised yet. Your feedback will help us refine … ---
**Author:** ![Edan](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/edan/32/11187_2.png) [@Edan](https://community.fibery.io/u/Edan)\ **Post date:** [January 8, 2026, 9:42pm UTC](https://community.fibery.io/t/improving-the-files-field-naming-sharing-and-organization/8486/18 "2026-01-08T21:42:04Z")
Any chance these improvements could be pushed a bit further? 🙃 One major limitation with Fibery files is that they can’t be exposed publicly, even temporarily. That makes it hard to fetch assets for automations and external workflows. In Notion, we had a solid setup for social media planning, invoicing and more. **Social media example** : Content lived in Notion, and once a post was marked ready, it triggered an automation that sent the payload to a Make or Zapier webhook. From there, everything published automatically to the relevant social platforms. Notion solves the file access issue by exposing files for 60 minutes per fetch, which works great for automations. Their approach is documented here: [Notion API Reference File Object](https://developers.notion.com/reference/file-object#:~:text=Tips%20*%20Each%20time%20you%20fetch%20a,To%20refresh%20access%2C%20re%2Dfetch%20the%20file%20object). Something similar in Fibery would unlock a lot of powerful workflows. ---
**Author:** ![Viktar\_Zhuk](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/viktar_zhuk/32/1934_2.png) [@Viktar\_Zhuk](https://community.fibery.io/u/Viktar_Zhuk)\ **Post date:** [January 9, 2026, 10:05pm UTC](https://community.fibery.io/t/improving-the-files-field-naming-sharing-and-organization/8486/19 "2026-01-09T22:05:54Z")
Hi @Edan , You can achieve smth similar atm if you use our API with API Tokens. When you reference a file to get the binary (e.g. using file-secret) via /api/files/… you actually get a 302 redirect to a signed public url with life span of a one week. So in you script or in 3rd party platform you can grab this URL instead of doing an actual redirect. ```auto Request URL https://vz-edge.fibery.io/api/files/f44b0484-fd0c-4c86-9d71-47e52d167702 Request Method GET Status Code 302 Found Remote Address Location https://d1f4u7smwbtn85.cloudfront.net/vz-edge.fibery.io/beaf15ff-ba88-42fa-9928-1a17faf05c9d?response-content-disposition=inline%3B+filename%3D%22purity.png%22&response-content-type=image%2Fpng&Expires=1768600932&Key-Pair-Id=KGJPFJ6T4AGSL&Signature=Ykkqd8cc3ybmpbZd8WK9OJvqdCQxQYQ5j63GaIGoPsz8v6MGKxl7E8J01IDmqWwVYgh-69yicdV2%7E9EcfVHRhZOYdrKH%7EifPyvJhp6CMU1CT-aANLuFFN%7EutgKLrOXzNAdtNKQe4dZxoSTn1Y8EBgINQ2ECEEcN1HJK0fnwGzCdtxyJG%7EpV91wlGEE6ljI1WnXkM3GPmrLeldf41D17HgGrk%7EztxM4ztAE8HLLoOv3oJhKRVBPts222rufeF7mrCyhiQdVejo8p4fPiumHcpD0tpFT18Q%7E40FV0QZGkXCZw%7ENwppMkfvrrbc-ECYGxKyUrkO-WO1RNYBV6eSc-6hLA__ ``` We will consider adding additional route in /api/files to make such signed urls via json request/response and maybe will support it in /api/graphql. ---
**Author:** ![Edan](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/edan/32/11187_2.png) [@Edan](https://community.fibery.io/u/Edan)\ **Post date:** [January 12, 2026, 10:15pm UTC](https://community.fibery.io/t/improving-the-files-field-naming-sharing-and-organization/8486/20 "2026-01-12T22:15:41Z")
Thanks! After posting this I actually found the solution in your docs. I got it working, but still think this needs to be way more accessible for non-technical users. Also wondering if there’s a better approach. Right now it takes three API calls just to get the entity, its description, and the file binary/URL. ![CleanShot 2026-01-12 at 17.11.17](https://us1.discourse-cdn.com/flex020/uploads/fibery/original/2X/9/9aecc29a5d27861c8d5cbac16581ec80559a463f.png) [Next page](https://community.fibery.io/t/improving-the-files-field-naming-sharing-and-organization/8486.md?page=2)