Is it a good idea to use Dropbox Sync for Project and local media/framestore?

I’m a solo Creative/Flame artist (tbh I don’t use Flame nearly as much these days) in a big media company with a huge Dropbox for business account and since the new 2026.2.2 release, and the updated database options, would it be feasible to have my framestore/project living in a locally synced Dropbox folder? DB is great for ‘make online only’ etc, so in my head it makes sense, and would make for easy archiving and media management. Until now I’ve been running 100% just off my 4tb MBP, no NAS or anything - so obviously the almost endless storage size on DB is a tempting thought? My projects are pretty small mostly, especially lately. :grimacing:

edit: with Finn chiming in below and clearly knowing more, I defer to his judgement.

I don’t see why it wouldn’t work.

1 Like

i dont think it would be recoverable.

Flame project folder e.t.c requires hard-link support and stuff like that, and its many many many small files - now maybe it works and it restores fine, but chances are dropbox even just slightly interfers with some atomic copy operations or whatever and is constantly starting to sync on millions of small files on every autosave .

From what i have seen how flame deals with the project files and media caches like a file-based-database i think it sounds like a recipe for absolute disaster.

probably you want to look at logik projekt which is made for stuff like that

2 Likes

Thanks Finn, tbh I’m a bit of a one-man operation here and not really doing big, long weeks-long projects like I used to - just short, quick grades, tweaks and green screens etc so as long as i can archive before I make files “online only” I think that might be good enough?

I just wouldnt put these files in a synced folder that dropbox is scanning due to the above, i would totally put archives on dropbox for safety .

2 Likes

I would not recommend to do this.

3 Likes

Agreed. Don’t do that.