> 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/jp/pre-basic/settings/data-settings/storage.md).

# 保存場所を変更

### デフォルトの保存先はどこですか？

Cherry Studio はシステムの規定に従い、データをユーザーディレクトリに保存します：

* **macOS**：`~/Library/Application Support/CherryStudio`
* **Windows**：`%APPDATA%\CherryStudio`（つまり `C:\Users\<你的用户名>\AppData\Roaming\CherryStudio`）
* **Linux**：`~/.config/CherryStudio`

以下の場所でも確認できます：

<figure><img src="https://3776196818-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F0Ut5BptC3t8CtSU1UWpM%2Fuploads%2Fgit-blob-8c52107a7383ab61795cb90c74c4eb5f64b4f0b6%2Fimage%20(31).png?alt=media" alt=""><figcaption></figcaption></figure>

### 保存場所を変更

Cドライブ／システムドライブの空き容量が少ない場合、または Cherry Studio のデータを **まとめて暗号化ディスク／外付けハードディスクに移したい場合は**、デフォルトの保存場所を変更できます。

> 注意：保存場所を変更すると **すべての会話履歴、アシスタント、ナレッジベース** などのデータが移動されます；操作前に **事前のバックアップを強くおすすめします**（[WebDAV](/docs/jp/pre-basic/settings/data-settings/webdav.md) / [S3](/docs/jp/pre-basic/settings/data-settings/s3-compatible.md) のどちらでも構いません）。

* **パスを変更**：【設定】→【データ】→【データディレクトリ】→【アプリデータ】の移行ボタン

***

#### 💡 ヘルプの取得とフィードバックの送信

設定や使用中に疑問、バグ、または機能改善の提案がある場合は、 [フィードバックと提案](/docs/jp/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/jp/pre-basic/settings/data-settings/storage.md?ask=<question>&goal=<user_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.
