> For the complete documentation index, see [llms.txt](https://www.tvrename.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://www.tvrename.com/menu/options-menu/filename-processors.md).

# Filename Processors

<figure><img src="https://3508557057-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fx0gPeIfHpbgTioNust1M%2Fuploads%2FW8CsGB2ZsLXkqUEQm3WG%2Fimage.png?alt=media&amp;token=83c24e35-7717-442d-9940-bbebed69ce90" alt=""><figcaption></figcaption></figure>

In much the same way that the ***Filename Template Editor*** is used to process the names of files being moved to the media library so ***Filename Processors*** is used to inform TV Rename what filenames to look out for when searching for missing files.

To really understand the contents of the Regex column above, you need a working knowledge of [Regular Expressions](https://regexone.com/).

Once you have figured out what's going on you can see that all the regular expressions capture the season and episode number of a show from the filename. Each one can work on just the filename: -

> ShowName S01E07.avi

or on the whole path: -

> C:/files/ShowName/S01E07.avi

The expressions are evaluated in order (top down). Use `Move Up` and `Move Down` to change the order, `Add` and `Delete` to add or remove an expression, and `Defaults` to put back the original list (TV Rename asks you to confirm first).

Each expression can be toggled on and off (**Enabled**), as can the ability to process a full path (**Full Path**).

Each expression has a Notes field which can be used to remind the user why the expression was added.

The bottom of the window lets you test the expressions. Choose what to test against:

* **Test Folder:** – the files in a folder you pick with `Browse...`.
* **Torrent Queue** – the files your torrent program is currently downloading.
* **Text:** – a file name you type in.

**Show:** sets the show to test against. Tick **Test All** to test every expression; otherwise only the expressions selected in the list above are tested.

For each file the results show the **Filename**, the **Show(s)**, the **Season** and **Episode** found, and the **Rule** (expression) that matched.

In all likelihood you will find it unnecessary to make changes here. Only if a new, totally unrecognisable file name structure appeared would it be necessary, and then there would probably be discussion about it in the forum.


---

# 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://www.tvrename.com/menu/options-menu/filename-processors.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.
