Where Does Bitwig Studio Store Projects and Settings?
Bitwig Studio splits user content in Documents from settings in LocalAppData. Library paths, settings folder, and relocation.
Last updated
Bitwig Studio keeps two roots that serve different masters. Your content, projects, library, controller scripts and packs, defaults to a Bitwig Studio folder in Documents, with every subpath relocatable from the Dashboard's Settings, Locations page. The app's own settings and caches live separately in LocalAppData\Bitwig Studio.
The Documents folder is the one that confuses people: Bitwig recreates its shell even after you relocate everything, so the leftover husk looks like a failed move. Judge by disk usage and the Locations page, not by the folder's existence. This entry documents Windows; macOS and Linux use analogous folders with their own platform paths.
Where Bitwig Studio stores this, by platform
%USERPROFILE%\Documents\Bitwig Studio
User content root with projects, library and scripts; relocate each subpath in Dashboard, Settings, Locations. The app recreates the shell folder even when everything points elsewhere. App settings and caches live separately at %LOCALAPPDATA%\Bitwig Studio. This entry covers Windows; check Locations on macOS and Linux for their equivalents.
Frequently asked questions
how do i move bitwig library to another drive
Change Dashboard, Settings, Locations to point each path at the new drive. Bitwig recreates content in the new spots on next launch. Move your existing projects, samples and packs yourself first; changing the setting does not move files, it only changes where Bitwig looks next.
why does bitwig keep recreating documents folder
The Documents folder is Bitwig's anchor and it recreates the shell on launch. Point every subpath inside it (projects, library, controller scripts) elsewhere via Settings, Locations and ignore the leftover shell. The actual disk usage follows your Locations settings, not the Documents husk.
why do my bitwig settings not apply
Your settings folder is likely under a different user or install type. Bitwig reads %LOCALAPPDATA%\Bitwig Studio for the current Windows user only. Running as admin or under another account reads that account's folder instead. Check who owns the running process before editing.
Notice an outdated path? Let us know.