> For the complete documentation index, see [llms.txt](https://support.charlla.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://support.charlla.io/en/userguide/library/delete.md).
# Delete videos
Select several videos with the checkboxes and delete them all at once.
{% hint style="danger" %}
* If you delete a video that is used on a product detail page, **it will no longer play on that page.**
* Deleting a video does not remove the Displayer code you added to the product detail page.
* The leftover code shows up as blank space on the page.
* To fix this, remove the leftover Displayer code from the page.
{% endhint %}
In the video list, select the checkboxes and click **\[Delete]** at the top.
Deleted videos **cannot be recovered.** Double-check the selected videos before you delete them. Click **\[Delete]** in the pop-up to delete them permanently.
---
# 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://support.charlla.io/en/userguide/library/delete.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.
