> For the complete documentation index, see [llms.txt](https://docs.cherryai.com.cn/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.cherryai.com.cn/docs/en-us/pre-basic/settings/data-settings/storage.md). # Change Storage Location ### Where is it stored by default? Cherry Studio stores data in the user directory according to system conventions: * **macOS**:`~/Library/Application Support/CherryStudio` * **Windows**:`%APPDATA%\CherryStudio`(that is, `C:\Users\\AppData\Roaming\CherryStudio`) * **Linux**:`~/.config/CherryStudio` You can also check it at:
### Change storage location If your C drive / system drive is running low on space, or you want to put Cherry Studio's data **all on one encrypted disk / external hard drive**, you can change the default storage location. > Note: changing the location will **move all conversation history, assistants, knowledge bases** and other data; before proceeding, **it is strongly recommended to back up first**([WebDAV](/docs/en-us/pre-basic/settings/data-settings/webdav.md) / [S3](/docs/en-us/pre-basic/settings/data-settings/s3-compatible.md) either is fine). * **Change path**: \[Settings] → \[Data] → \[Data Directory] → \[Application Data] migration button *** #### 💡 Get help and submit feedback If you encounter any questions or bugs during configuration or use, or have suggestions for feature improvements, please refer to the official channels provided in [Feedback and Suggestions](/docs/en-us/question-contact/suggestions.md) . --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.cherryai.com.cn/docs/en-us/pre-basic/settings/data-settings/storage.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.