Images and files migration
Move your Bubble images and files into Supabase Storage
Move Bubble images and files into your Supabase Storage bucket, with every file reference rewritten in your migrated database.
Available as an add-on to your database migration project.
Why teams add this
Your database moved. Your Images and Files didn't.
Every file URL in your migrated database still points at Bubble's servers. Move the assets too and you can cancel for good.
Without unbubble.dev
- File URLs in your database still resolve to Bubble's servers
- Cancelling Bubble breaks every image and attachment in your app
- No control over storage, CDN, or access policies
- Database and assets split across two infrastructures
With unbubble.dev
- Every asset lives in your Supabase Storage bucket
- Cancel Bubble without breaking a single image or file
- Full control over storage, access rules, and CDN
- Database and assets together in infrastructure you own
How it works
Three automated steps to move your assets
Find every reference
We find all image and file references across your database, including Option Sets.
Download and re-upload
We download each image and file and re-upload them to your Supabase Storage buckets.
Rewrite URLs
We rewrite each reference to the new URL, while keeping an internal audit table with the mapping between old and new URLs.
Ready to move your images and files?
Add this to your database migration project and ship with assets fully under your control.
FAQ
Frequently asked questions
Quick answers to what people usually ask before getting started.
Where do my Bubble images and files end up?
They are stored in your own Supabase account, in a Storage bucket that you control. Your assets are not held inside unbubble.dev.
Are file references in my data updated automatically?
Yes. Every image and file URL stored on your Bubble records is rewritten in the migrated database to point at the new asset location, so your app continues to serve the right images without manual fix-up.
What kinds of assets are migrated?
Anything stored as an image or file field on a Bubble data type — uploaded images, PDFs, documents, attachments, and other binary assets. Public Bubble file URLs and private file URLs are both supported.
Do I need the database migration to use this?
Yes. Images and files migration is an add-on for the same project as your database migration. The references being rewritten live inside the migrated database, so it must be unlocked for that project first.
Will the original Bubble file URLs still work?
Bubble continues to serve the originals while your Bubble app exists, but for production traffic on your new stack, your app should be using the migrated URLs that this add-on writes into your database. We do not delete your Bubble references. We simply use them to download the images and files, then update the references in your migrated database.
Why would I want to migrate my images and files?
Even after your database is migrated, every file URL inside it still points at Bubble's servers unless you move the assets too. Move your images and files into storage you control, and you are free to shut Bubble down without your new app depending on Bubble-hosted asset URLs.