Today, the Gallery view only works with the Files field, and Files only accept uploaded files. Because of this, using Gallery forces file uploads even when the media already exists publicly elsewhere.
This creates unnecessary storage usage.
Real use case: social media management
In social media workflows, media usually lives in tools like Canva or Google Photos. These tools provide public share links with rich embeds (including full video playback).
Example: Canva public “watch” links
The link already embeds the full video
The video can be updated in Canva
The same link always reflects the latest version
If Gallery supported embeds:
I could store only the link
The Gallery card could render the embed
Any update in Canva would automatically reflect in Fibery
No re-upload, no duplicated files, no wasted storage
Right now, the only options are:
Upload the full media file, or
Upload a placeholder file (e.g. thumbnail)
Both consume storage that is not actually needed.
Feature request:
Allow links inside the Files field, or
Allow Gallery view to render embeds from a URL field
Treat embeds as first-class media, not limited to Rich Text
This would better support social media, marketing, and design workflows, while avoiding unnecessary file storage.
This sounds like it may be better served as an enhancement to the existing URL field, allowing it to show a thumbnail/embed of the third-party content.
And then being able to also use these in places like Gallery view.
That said, I think it’s also worth considering allowing links directly in the “Files” field, not only via a separate URL field.
In real marketing workflows, it’s very common to deal with large media files (2GB+ videos, for example). In those cases, forcing an upload to Fibery doesn’t make much sense, both in terms of storage cost and friction. Being able to reference a file via URL would avoid unnecessary uploads and workarounds.
My real-world flow looks like this:
I receive videos from clients
Sometimes they send files, sometimes links
Depending on size, I either upload or just reference the media
I’m currently migrating from Notion to Fibery
In Notion, the Files field accepts both uploads and URLs, but:
URLs don’t render embeds
Gallery view only really works when files are uploaded
In Fibery today, something similar happens, but with the added limitation that the Files field doesn’t accept URLs at all, which forces uploads or placeholder hacks.
If the Files field could accept both uploads and URLs, and the Gallery view could render embeds when a URL is present, that would cover most real use cases:
Small files → upload
Large or external media → link
No duplicated media
No extra fields just to work around limitations
I’ve already migrated ~50% of my system to Fibery, and these differences show up a lot in marketing workflows.
I can adapt what’s needed (extra fields, scripts, etc.), but this feels like a case where native support would have a big impact.
