Skip to content

Flat Strings

Flat Strings

Flat strings are defined by a single line of text.
e.g. Big.Buck.Bunny.2008.BluRay.1080p.MP2.2.0.x264.

NfoForge will automatically use the formatter in flat mode for paths (files and folders).

Format

FileTokens are only available in flat mode when used directly in NfoForge. You'll notice that flat tokens have a single set of brackets, e.g., {movie_title}.

Usage

A token string is simply a combination of tokens and text.

What is a string?

A string is a sequence of characters. This includes letters, numbers, and symbols.

Example of a token string:

{movie_clean_title} {release_year} {edition} {re_release} {source} {resolution} {mi_audio_codec} {mi_audio_channel_s} {mi_video_dynamic_range_type_inc_sdr_over_1080} {mi_video_codec}

When filled:

Movie Name 2025 Directors Cut REPACK UHD BluRay 2160p TrueHD Atmos 7.1 DV HDR HEVC

The output will vary based on the file that is opened. If you are familiar with Radarr/Sonarr, this works very similarly.

Optional Text

You can use tokens with an optional syntax to only add text if the token is filled by the formatter. This is done with the syntax :opt=*:, where you replace the asterisk with whatever text you want.

Example of a token string with opt syntax:

{movie_clean_title} {:opt=(:release_year:opt=):} {edition} {re_release} {source} {resolution} {mi_audio_codec} {mi_audio_channel_s} {mi_video_dynamic_range_type_inc_sdr_over_1080} {mi_video_codec}

Note the token {:opt=(:release_year:opt=):}. We're using :opt=(: and :opt=): to wrap the year with parentheses. This allows for many use cases and enables a high degree of customization.

When filled with opt syntax:

Movie Name (2025) Directors Cut REPACK UHD BluRay 2160p TrueHD Atmos 7.1 DV HDR HEVC

You can see this in action in real time inside NfoForge under Settings → Movie.

Token Example

Filters

You can apply several filters to filled tokens to fine-tune your output. Each example below defines a string and shows the result before and after applying a filter. Filters are simple to use:

  • Define a filter using the | character inside the brackets, immediately after the token name: {token|filter}.
  • You can still use opt for optional text, but filters are only applied to the token value itself. The filter must be placed before opt. For example: {:opt=x:token|filter:opt=x:}.

Info

Filters work identically to their Python equivalents.

upper

{example_token} = tom

{:opt=hi :example_token|upper}

hi TOM

lower

{example_token} = TOM

{:opt=hi :example_token|lower}

hi tom

title

{example_token} = TOM

{:opt=hi :example_token|title}

hi Tom

swapcase

{example_token} = Tom

{:opt=hi :example_token|swapcase}

hi tOM

capitalize

{example_token} = tom

{:opt=hi :example_token|capitalize}

hi Tom

zfill

{example_token} = 42

{:opt=hi :example_token|zfill(5)}

hi 00042

replace

{example_token} = tom

{:opt=hi :example_token|replace("m", "mmy")}

hi tommy

You can use single or double quotes for the arguments, and any character (including commas, spaces, or quotes) can be replaced. For example:

{:opt=hi :example_token|replace(',', '-')}
{:opt=hi :example_token|replace('foo,bar', 'baz,qux')}

Chained Filters

You can chain multiple filters together by separating them with |. Filters are applied in order from left to right.

{example_token} = tom

{:opt=hi :example_token|replace("m", "mmy")|upper}

hi TOMMY

Additional Information

There are three built-in rename token strings:

  • Filename token string
    • The filename (or folder, if applicable) is shared across all trackers.
    • There can only be one of these tokens.
  • Title token string (global)
    • A single global token shared across all trackers that don't have an override.
  • Per-tracker Title token string override
    • Overrides the global title token for each tracker.