Where Does SuperCollider Store Config and Quarks?
SuperCollider splits state between ~/.config/SuperCollider (startup file, quarks config) and ~/.local/share/SuperCollider (quarks, recordings, synths).
Last updated
SuperCollider follows the XDG split between config and data, and each side has a distinct job. The config folder holds the startup file and IDE preferences. The data folder holds downloaded quarks, recordings, archived synthdefs, and extensions.
That division guides every fix. Boot behavior trouble points at the startup file; missing-library trouble points at the quarks folder. The sclang config records interpreter paths, so moving machines with different layouts means re-checking those entries.
Where SuperCollider stores this, by platform
~/.config/SuperCollider
startup.scd plus IDE prefs and quark config. A broken startup file blocks boot, so rename it to isolate problems. Extensions here load before anything else.
~/.local/share/SuperCollider
Downloaded quarks, recordings, synthdefs, and user extensions. Copy with SuperCollider closed to migrate; reinstall quarks through the language when versions differ.
~/Library/Application Support/SuperCollider
Same config/data split on macOS under Library. The app bundle itself holds no user state, so reinstalls never touch your setup.
Frequently asked questions
Where does the startup file live?
Edit the startup file (startup.scd) in the config folder. It runs on every boot, so server options, MIDI init, and helper functions belong there. A broken startup file explains most boot failures; rename it to test.
How do I migrate quarks to a new machine?
Reinstall them with Quarks.install after copying the config; downloaded quarks live under the userLibrary, not in the app bundle. Recordings and synthdefs copy over as plain files.
Notice an outdated path? Let us know.