WindowsmacOSLinux

Where Does CudaText Store Settings?

CudaText keeps settings/user.json plus sessions and plugin configs in a settings folder: %AppData%\CudaText on Windows, ~/.config/cudatext elsewhere.

Last updated

CudaText layers JSON configs with unusual clarity. The settings_default folder ships reference files that are never read. Your real config is settings/user.json, edited by copying lines over from the default. Plugins add their own cuda_* files in the same folder.

Sessions and history round out the folder: .cuda-session files remember open documents, history.json remembers dialogs and recent files. Portable installs move the whole tree beside the executable in a data folder, which makes USB setups trivially migratable.

Where CudaText stores this, by platform

Windows
%APPDATA%\CudaText\settings\user.json

user.json for options, keys.json for hotkeys, history.json for recent files, plus per-plugin cuda_* files. Portable mode relocates everything to a data folder beside the exe.

macOS
~/Library/Application Support/CudaText/settings/user.json

Same settings tree on macOS. Sessions save per OS suffix, so session files do not transfer cleanly between platforms even though user.json does.

Linux
~/.config/cudatext/settings/user.json

Honors XDG_CONFIG_HOME when set. Plugin configs and lexer files follow the same settings folder, so one backup covers the whole customization.

Frequently asked questions

Which file do I actually edit?

Open Options, then Settings - user for user.json and Settings - default for the reference. Copy lines from default.json into user.json; only user.json is read as config, default.json is documentation.

The UI layout is messed up. What do I delete?

Delete settings/history.json (dialog positions, recent files, search strings) while CudaText is closed. For a full reset, remove user.json and the session files too; plugins keep their own cuda_* files.

Notice an outdated path? Let us know.