Where Does OpenBuilds Store Data?
OpenBuilds CONTROL keeps uploads in Electron userData with machine state on controllers. Exact folder casing stays medium confidence.
Last updated
OpenBuilds CONTROL stores uploads in Electron userData with machine state on controllers. Macros persist in app storage without published filenames. Exact folder casing follows convention without vendor confirmation.
G-code stages in upload trees verified in source. Profiles live in Chromium storage with UI exports. Quote mechanism confidently with OS paths carefully.
Where OpenBuilds stores this, by platform
%APPDATA%\OpenBuildsCONTROL
Electron userData with verified upload suffix plus machine state on controllers. Exact casing follows convention unconfirmed. Macros lack published filenames.
~/.config/OpenBuildsCONTROL
XDG twin of the Electron tree with identical upload behavior. Controller state stays firmware-side. Same medium confidence on casing.
Frequently asked questions
How do I back up OpenBuilds settings?
There is no verified portable config to copy. Macros live in app storage without published filenames while G-code stages in upload folders. Export through UI flows rather than file copies.
Where are OpenBuilds machine profiles?
They live on Grbl firmware rather than app files. Profiles and UI prefs stay in Chromium storage with source-verified upload dirs. Quote mechanism confidently with folders carefully.
What is the OpenBuilds data folder?
Through userData plus upload suffix verified in source with OS prefixes inferred from Electron standards. Exact casing stays medium confidence without vendor docs. Check live paths per install.
Notice an outdated path? Let us know.