> For the complete documentation index, see [llms.txt](https://support.audacityteam.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://support.audacityteam.org/au3/troubleshooting/resetting-audacity.md).

# Resetting Audacity

## Resetting from within Audacity

You can reset Audacity by going to the following menus:

* To reset the toolbars only: **View -> Toolbars -> Reset Toolbars**
* To reset everything: **Tools -> Reset Configuration**

## Purging the settings folder

If you cannot open Audacity or want a more thorough cleanup, you can also delete the configuration files manually. They can be found in the following locations:

* Windows: `C:\Users\<yourname>\AppData\Roaming\audacity\`
* macOS: `~/Library/Application Support/audacity/`
* Linux: `~/.config/audacity/`\
  Additionally, the XDG folders `~/.cache/audacity`, `~/.local/share/audacity` and `~/.local/state/audacity` are used on Linux.

{% hint style="info" %}
**Hint:** These folders usually are hidden by default. You may need to show hidden files, or access their path directly, to access them.
{% endhint %}

You can delete all contents of the folder to get Audacity back to "factory settings". Alternatively, you can also only delete certain elements of it:

* **audacity.cfg** is responsible for all preferences
* **pluginregistry.cfg** contains a registry of all plugins and whether they can be used.
* **pluginsettings.cfg** contains last used settings of effects as well as user presets.

Additionally, you may find some other files and folders there, eg. for macros, custom themes or plugins. These can also be deleted though, typically deleting the audacity.cfg and pluginregistry.cfg is enough in most troubleshooting scenarios.


---

# 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.audacityteam.org/au3/troubleshooting/resetting-audacity.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.