Where Does Companion Store Config?
Bitfocus Companion keeps button pages, connections and triggers in a config database in home. Paths per OS and backup routine.
Last updated
Companion centers on a config database holding button pages, device connections and triggers. The web admin reads and writes that store. Companion modules ship with the install.
That database design makes the export zip the reliable move. Raw folder copies work when versions match exactly. Keep Companion releases aligned across the move or buttons misfire.
Where Companion stores this, by platform
%APPDATA%\companion
Button pages, connections and triggers in a database below one root. Prefer the in app full export zip for moves. Raw copies need matching Companion versions on both ends.
~/Library/Application Support/companion
Same database role on Mac. Back up through the web admin export before upgrades. Module helpers stay with the install rather than this folder.
~/.config/companion
Identical layout on Linux under home. Pair database backups with notes on device IPs, since network targets differ between studios.
Frequently asked questions
How do I back up Companion?
Use Export Full Configuration inside Companion to download a zip with pages, connections and triggers. Import it on the new machine with a matching Companion version. Copying raw files works too but the export stays consistent across releases.
Where are my buttons?
In the Companion database inside its config folder, edited through the web admin rather than text files. Buttons reference connection instances by id, so keep both sides together on every move.
Notice an outdated path? Let us know.