> 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/guides/features/finding.md).

# Finding

Once a scan is complete, TV Rename will identify files to move/copy/rename and additional files to download/create. For episodes that are still missing, TV Rename will try and find them for you.

### Types <a href="#types" id="types"></a>

There are 7 places it could search:

* *File System* – If found, it will remove the episode from the missing list and move the file into the correct place.
  * It may look in the library or in the specified search folders
* *SABnzbd*, *uTorrent*, *qBittorrent* – If found it will mark it as downloading so you know not to try and find the item again. See [**Torrents / NZB**](https://www.tvrename.com/menu/preferences/torrents-nzb.md) for more information.
* *RSS Feed for torrent links*, *JSON Web page for torrent links* – If found then it will download the torrent file. (via uTorrent or qBittorrent) See [**RSS/JSON Search**](https://www.tvrename.com/menu/preferences/rss-json-search.md) for more information about configuration.
* *Jackett* - If you have a Jackett Server running TVR can ask it for download locations for missing files. See the [**Jackett Search**](https://www.tvrename.com/menu/preferences/jackett-search.md) section of the settings for further information.

{% hint style="success" %}
See [Preferences ](https://www.tvrename.com/menu/preferences.md)([here](https://www.tvrename.com/menu/preferences/jackett-search.md), [here ](https://www.tvrename.com/menu/preferences/rss-json-search.md)and [here](https://www.tvrename.com/menu/preferences/torrents-nzb.md)) for more information on configuring the different ways TV Rename tries to find missing files.
{% endhint %}

### Identification of files <a href="#how-to-write-a-regex-for-tv-rename" id="how-to-write-a-regex-for-tv-rename"></a>

#### How to write a Regex for TV Rename <a href="#how-to-write-a-regex-for-tv-rename" id="how-to-write-a-regex-for-tv-rename"></a>

Firstly, get acquainted with what a regular expression is - these sites will help:

* [**regexone.com**](https://regexone.com/)
* [**www.regular-expressions.info**](https://www.regular-expressions.info/)
* [**regexr.com**](https://regexr.com/)
* [**regex101.com**](https://regex101.com/)
* [**www.rexegg.com**](http://www.rexegg.com/regex-quickstart.html)

Once you understand Regular Expressions and [**‘Named Groups’**](https://www.regular-expressions.info/named.html) in particular then all you need to know is that TV Rename looks for 3 named groups:

* *s* – The series number the file relates to.
* e – The Episode number the file relates to.
* f – (optional) If specified and if it matches then this is the max episode number that the file matches. It is used for instances when a file matches multiple episodes.

For Example: ‘S01E01-03’ would indicate that the file represents Series 1 and is episodes 1-3. In this case s=1, e=1 and f=3.

#### Finding Rules <a href="#finding-rules" id="finding-rules"></a>

Note that if a file matches multiple missing files, or multiple files match one missing episode no action is taken. TV Rename will raise a warning in the log files and allow the user to manually link the file to the missing episode.

{% hint style="info" %}
Further information can be found [**here**](https://www.tvrename.com/menu/options-menu/filename-processors.md).
{% endhint %}


---

# 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/guides/features/finding.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.
