> For the complete documentation index, see [llms.txt](https://knowledge.themeware.design/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://knowledge.themeware.design/knowledge-base/basic-knowledge/images/create-default-folder-for-media.md).
# Create default folder for media
In the Shopware 6 Media Manager, you will usually find various **default folder**s for different media types. If one or more of these folders are missing, you can easily create them yourself.
## Create default folder for CMS media
1. **Go to Media Management** in Admin under **Content > Media**. (1) (2)
2. Click on **"Add new folder"** in the top right-hand corner. (3)
3. Give the folder a suitable **name** (e.g. "CMS Media").
4. Select the **"Settings"** option in the context menu  of the new folder. (4) (5)
5. In the **"Default media location for"** field, select for which kind of media the folder should be used – e.g. **"cms\_page (Layout)"**. (6)
6. Save the change. (7)
The new folder will now be used automatically for the selected block – e.g. when uploading images in CMS elements.
---
# 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://knowledge.themeware.design/knowledge-base/basic-knowledge/images/create-default-folder-for-media.md?ask=&goal=
```
`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.