> For the complete documentation index, see [llms.txt](https://docs.cherry-ai.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.cherry-ai.com/docs/en-us/pre-basic/settings/default-models.md).

# Default Model Settings

Cherry Studio often needs to "pick a model to use" in many scenarios (for example, helping you name a conversation, optimize prompts, or do translations), so it’s impossible to ask you every time, "Which model should I use?"**Default model settings**This is telling Cherry Studio:**Which model to use when I don’t specify it clearly**.

> Note: these are the models used by the "behind-the-scenes helpers",**and the model used for chatting with you can be different**. The main chat model is set separately in each assistant.

## What do the 4 default models each control?

### Default assistant model

* **Used by whom**: when you create a new assistant but don’t specify a model, this model is used automatically
* **How to choose**: choose a conversation model you use often, that is stable and reasonably priced

### Fast model

* **Used by whom**: for all internal tasks that are "lightweight and don’t require top-tier intelligence", including:**Topic naming**、**Search keyword extraction**、**Automatically generate a title when exporting messages**etc.
* **How to choose**: use**an inexpensive, fast**model; there’s no need to use the most powerful model

### Translation model

* **Used by whom**: the "one-click translate" feature in the chat box / drawing / translation pages;[Text Selection Assistant](/docs/en-us/cherry-studio/preview/selection-assistant.md) translation operations in
* **How to choose**: any ordinary conversation model will do; if you do a lot of Chinese-English translation, the DeepSeek or Claude series works better

## Recommendation in one sentence

If you don’t want to dig into it, just fill in the following:

| Field                   | Recommended                                                                                                                                        |
| ----------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------- |
| Default assistant model | Your most frequently used conversation model                                                                                                       |
| Fast model              | An inexpensive, fast model                                                                                                                         |
| Translation model       | Any conversation model that can follow instructions will do (you can also choose a dedicated translation model, such as the qwen-mt series models) |

If you’re unsure, keep everything on the default settings. After using it for a while, if you find something is lacking, come back and adjust it.

***

### 💡 Get help and submit feedback

If you encounter any questions, bugs, or have suggestions for feature improvements during configuration or use, please refer to [Feedback and Suggestions](/docs/en-us/question-contact/suggestions.md) the official channels provided there.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.cherry-ai.com/docs/en-us/pre-basic/settings/default-models.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.