Where Does Acode Store Projects and Settings?
Acode edits files wherever you open them, with settings.json in-app and terminal setups backupable.
Last updated
Acode is an editor, not a vault. Your code lives wherever you opened it: device folders, SFTP servers, or Termux paths. The app remembers open files and folders between launches but owns none of them.
Settings live inside the app, editable as JSON from the settings screen, alongside plugins, themes, and keybindings. The built-in Alpine terminal keeps its own setup with backup and restore for packages and shell config. Back up the terminal separately from your code.
Where Acode stores this, by platform
Your project folders (edited in place) + in-app settings.json
Open folders stay referenced, not copied. Tweak behavior in settings.json from Settings. Use the terminal's own backup and restore for its Alpine setup. Uninstalling wipes settings, plugins, and terminal data, never your project files elsewhere.
Frequently asked questions
Where are my Acode files saved?
Exactly where you opened them. Acode edits in place across local storage, SFTP, and Termux paths. Check the sidebar folder root for the current project location. Nothing hides in an Acode data folder.
How do I back up Acode settings and terminal?
Copy settings.json content from the settings screen for editor prefs, and run the terminal's backup feature for its packages and shell setup. Reinstall plugins from the store afterwards since those travel separately.
Notice an outdated path? Let us know.