> For the complete documentation index, see [llms.txt](https://docs.rhinofcp.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.rhinofcp.com/datasets/removing-a-dataset-version.md).

# Removing a Dataset Version

How to remove a dataset version

Follow these steps to delete a dataset version.

{% stepper %}
{% step %}

#### Open the Datasets page

Go to the page that lists your datasets.
{% endstep %}

{% step %}

#### Find the dataset version

If needed, use the search fields at the top right.

* Use **Search Name** to search by dataset name.
* Use **Search Description** to search by dataset description.

Each dataset appears with a row for each version. Find the version you want to delete.
{% endstep %}

{% step %}

#### Open the menu for the version

Select the three-dot menu on the right side of the version row, shown below.

![](https://content.gitbook.com/content/ydySyCBmy6F7NnGn4bPa/blobs/6x6eIJpSpDL2eZ09jT5K/12987199149213)
{% endstep %}

{% step %}

#### Remove the dataset version

Select **Remove dataset**.

Repeat these steps for each version you want to remove. When you delete the last version, the dataset is fully deleted.
{% endstep %}
{% endstepper %}

#### Remove from the object page

You can also remove a dataset or dataset version directly from the **Datasets** page by selecting **Remove dataset**.


---

# 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.rhinofcp.com/datasets/removing-a-dataset-version.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.