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) 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!
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.
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.
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.
