Kodi Naming Guide: Movies, TV Shows, Anime, Music & NFO Files (2026)

Kodi Naming Fundamentals

Three concepts about how Kodi scans differ enough from Plex and Jellyfin to deserve their own explanation. Skip this section and you'll keep running into the same three failures: wrong scraper for your library, content type misconfigured, and unexpected NFO files overriding your scrapes.

Scrapers, not agents

Where Plex has "agents" and Jellyfin has "metadata providers", Kodi has "scrapers" — community-maintained add-ons that query specific databases. The defaults are The Movie Database scraper for movies, The Movie Database scraper or The TVDB scraper for TV shows, and the Universal Album Scraper for music. Anime is the big exception: Kodi has no built-in anime scraper, so users install community add-ons like Hama (the same one used in Plex) for AniDB integration. Scraper choice happens per-source, not per-library. Open a Kodi video source in the file browser, edit it, and pick "Set content" to assign a scraper. The same source can be scraped by different add-ons across Kodi devices on the same network — which is one reason "my Kodi works but my friend's doesn't" is so common.

Library sources and content types

Kodi's library is built from "sources" you add manually — folders, network shares or remote paths. When you add a source, you tell Kodi what kind of content it contains (Movies, TV shows, Music videos, Music, None) and which scraper to use for that content. Mixing content types in a single source is a common cause of unmatched files: a folder containing both movies and TV shows can only be scraped as one or the other. The fix is to split mixed content into separate top-level folders, each its own source, each with its own content type. This is more rigid than Plex's per-folder library detection but more predictable once you commit to the structure.

Four rules to prevent 90% of failures

Four rules that prevent the vast majority of Kodi scanning failures: Rule 1 — One content type per source. Don't mix movies and TV shows in a single folder Kodi scrapes as "Movies". Rule 2 — Set the content type and scraper BEFORE the first scan. Changing them later requires "Refresh" plus sometimes a full database wipe to clean up old wrong matches. Rule 3 — Use sXXeYY for TV episodes, lowercase, zero-padded. Kodi accepts more variations than Plex but predictable patterns avoid scraper edge cases. Rule 4 — When a scraper repeatedly fails on a specific item, drop an NFO file next to it. NFO files override scrapers entirely — they're Kodi's escape hatch.

Need it from zero? step-by-step walkthrough.

Naming Movies for Kodi

Kodi accepts two valid movie layouts — folder-per-movie and flat. The folder pattern is recommended for the same reasons as in Plex and Jellyfin (extras, posters, NFO files), plus one Kodi-specific feature: stacked multi-part movies, which Kodi handles natively where Plex and Jellyfin don't.

Recommended folder layout

The recommended folder layout:

Movies/
├── Blade Runner (1982)/
│   ├── Blade Runner (1982).mkv
│   ├── Blade Runner (1982).en.srt
│   ├── movie.nfo
│   ├── poster.jpg
│   └── fanart.jpg
├── Dune (2021)/
│   └── Dune (2021).mkv
└── The Matrix (1999)/
    └── The Matrix (1999).mkv

Filename matches the folder name. Artwork files use Kodi's local artwork names: poster.jpg, fanart.jpg, clearart.png, landscape.jpg. Subtitles follow the convention Title (Year).en.srt, .fr.srt etc. — Kodi reads the language code from the dot-separated suffix.

The (Year) suffix isn't optional

The year in parentheses is non-negotiable for the same reasons as Plex and Jellyfin: TheMovieDB returns duplicate-title matches ordered by popularity, and Kodi will silently pick the wrong one. Format: Title (YYYY). Brackets [YYYY], dots Title.YYYY, and bare years work in some scrapers but fail in others — parentheses are universal. For movies missing on TMDB entirely (rare arthouse, regional releases), an NFO file with a manual TMDB ID is the only reliable fix. See the NFO section below.

Stacked multi-part movies (Kodi-only)

Kodi has native support for multi-part movies stored as separate files — a feature from the DVD-rip era that's still useful for very long films (LotR Extended, Once Upon a Time in America) split across discs. Use the cd1 / cd2 / partN / dvdN suffix patterns:

Movies/
└── Lord of the Rings - The Fellowship of the Ring (2001)/
    ├── Lord of the Rings - The Fellowship of the Ring (2001) - cd1.mkv
    └── Lord of the Rings - The Fellowship of the Ring (2001) - cd2.mkv

Kodi plays them back-to-back as a single movie and scrapes them as one library entry. The matching pattern is case-insensitive and accepts cd, part, dvd, pt and a few others — but cd1/cd2 is the safest and most-documented.

Multiple versions of the same movie

Kodi doesn't have the merged multi-version feature Plex and Jellyfin offer — you can't store a 1080p and a 4K version under one library entry and have Kodi pick the right one for the client. Each file becomes its own library entry. Two workarounds: Approach 1 — Keep one version per movie in Kodi's library, and store the other versions outside the scraped source. Switch the library source manually when you want the other quality. Approach 2 — Split into two libraries (Movies-1080p, Movies-4K) with two sources. Use Kodi profiles or skin shortcuts to switch between them. More work, but lets all versions coexist in the same Kodi install. If multi-version is central to your workflow, this is the one area where Plex and Jellyfin are objectively more capable.

Movie sets and collections

Kodi supports movie sets (sometimes called "collections") — Star Wars, Marvel Cinematic Universe, Lord of the Rings — grouping movies under a single browsable collection node. Sets are populated automatically from TMDB's collection data for movies that belong to one. No naming change required; Kodi reads the collection ID from the scraped TMDB metadata. For custom sets (your own grouping not on TMDB), use an NFO file at the movie level with a <set> tag pointing to a custom set name.

Four mistakes that account for most scraping failures

1. Source content type set to "None" or wrong type. Without a content type, Kodi doesn't scan it as movies at all. 2. Year missing or in bracket form. "Inception 2010.mkv" matches by luck; "Inception [2010].mkv" fails on TMDB scraper. 3. Movie file at the source root with no folder. Works for matching but breaks artwork, NFO and stacked-part features. 4. Stale entries from a previous wrong scrape. Even after fixing names, Kodi shows the old wrong match. Solution: library context menu → "Clean library" → then re-scan.

Full examples

Movies/
├── The Matrix (1999)/
│   ├── The Matrix (1999).mkv
│   ├── movie.nfo
│   └── fanart.jpg
├── Lord of the Rings - The Fellowship of the Ring (2001)/
│   ├── Lord of the Rings - The Fellowship of the Ring (2001) - cd1.mkv
│   └── Lord of the Rings - The Fellowship of the Ring (2001) - cd2.mkv
├── Dune (2021)/
│   └── Dune (2021).mkv
└── 1917 (2019)/
    └── 1917 (2019).mkv

Compare to Plex equivalents.

Naming TV Shows for Kodi

TV is where Kodi's flexibility helps the most — multiple valid filename patterns are accepted, and the scraper is forgiving about minor variations. The trade-off: when something doesn't match, the cause is rarely obvious. This section covers the safe patterns and the cases where Kodi differs from Plex/Jellyfin.

Folder layout

Standard two-level layout: show folder, then season subfolders.

TV Shows/
├── Breaking Bad (2008)/
│   ├── tvshow.nfo
│   ├── poster.jpg
│   ├── Season 01/
│   │   ├── Breaking Bad - s01e01 - Pilot.mkv
│   │   └── Breaking Bad - s01e02 - Cat's in the Bag.mkv
│   └── Season 02/
│       └── Breaking Bad - s02e01.mkv
└── The Office (2005)/
    └── Season 03/
        └── The Office - s03e12.mkv

Show folder name: "Title (Year)". The year disambiguates remakes — The Office UK 2001 vs US 2005, House of Cards UK 1990 vs US 2013. Season folder: "Season XX" with two-digit zero-padding, or "Season 0" (or "Season 00") for specials. Kodi accepts both "Season 0" and "Season 00"; pick one and stay consistent. Unlike Plex's "Specials" folder convention, Kodi does NOT recognize a literal "Specials" folder name. Use Season 0 or Season 00.

Episode filename format

Kodi's recommended episode filename pattern: Show Name - sXXeYY - Episode Title.ext Lowercase letters, two-digit zero-padded numbers, optional episode title for readability. Kodi accepts uppercase (SXXEYY), Show.S01E01, Show 1x01, Show 101 and several other variations — but the lowercase dash-separated form is the most reliable across scrapers. The episode title in the filename is for human readability only — Kodi's scraper overrides it with the canonical title from TheTVDB or TheMovieDB. If the scraper-provided title is wrong, edit it through Kodi's GUI (right-click episode → "Information" → "Edit") or via the NFO file (covered later).

Specials in Season 0

Specials, OVAs, pilot episodes, behind-the-scenes and bonus content go in "Season 0" (or "Season 00" — Kodi treats both identically). Inside, use sequential numbering: Show - s00e01.mkv, Show - s00e02.mkv. The numbering order should match TheTVDB's specials list for that show. The TVDB community curates these in a specific order (often air-date based); Kodi expects you to follow that order. If your specials feel scrambled in Kodi's UI, check TheTVDB's specials tab for the show and re-order your s00eYY numbers accordingly.

Multi-episode files

For double episodes in a single file:

Breaking Bad - s05e15-e16 - Granite State + Felina.mkv

Kodi creates a single playable item that maps to both episodes in the metadata. The range form (e15-e16) is cleaner; the alternative form (s05e15-s05e16) also works. Both extend to triple or quadruple episodes if needed (e15-e16-e17), though that's rare in practice.

Daily shows (date-based)

Daily shows (talk shows, news) without traditional season/episode numbers use the YYYY-MM-DD date format:

The Daily Show (1996)/
└── Season 29/
    └── The Daily Show - 2024-03-15.mkv

Kodi's TheTVDB scraper matches the date against the daily-show date index. Make sure the source uses the TheTVDB scraper, not TheMovieDB — TheMovieDB has limited daily-show support.

Full examples

TV Shows/
├── Breaking Bad (2008)/
│   ├── tvshow.nfo
│   ├── Season 01/
│   │   ├── Breaking Bad - s01e01 - Pilot.mkv
│   │   └── Breaking Bad - s01e02 - Cat's in the Bag.mkv
│   ├── Season 05/
│   │   └── Breaking Bad - s05e15-e16 - Granite State + Felina.mkv
│   └── Season 00/
│       └── Breaking Bad - s00e01 - No Half Measures.mkv
├── Chernobyl (2019)/
│   └── Season 01/
│       └── Chernobyl - s01e01 - 1:23:45.mkv
└── The Daily Show (1996)/
    └── Season 29/
        └── The Daily Show - 2024-03-15.mkv

Compare to Jellyfin equivalents.

Naming Anime for Kodi (with the Hama Scraper)

Kodi has no built-in anime scraper — the default TheMovieDB and TheTVDB add-ons handle anime as regular TV shows, which works for modern seasonal shonen but fails on absolute-numbered series (One Piece, Detective Conan, Bleach). The fix is Hama, the same community scraper used in Plex for anime libraries. Installing it once unlocks AniDB integration across your Kodi anime sources.

Setting up Hama (10 minutes, one-time)

Hama setup in Kodi takes about 10 minutes: 1. Download Hama from github.com/ZeroQI/Hama.bundle (the Plex bundle works for Kodi via the Kodi Hama add-on wrapper). Alternative: install "Hama" from the official Kodi add-on repository if available in your Kodi version. 2. In Kodi: Settings → Add-ons → Install from repository → Information providers → TV shows → install Hama (and Hama.bundle if listed separately). 3. Create a dedicated anime source. Add a video source pointing at your anime folder, set content type to "TV shows", and pick "Hama" as the scraper instead of TheMovieDB or TheTVDB. 4. Hama defaults to AniDB as the primary database. You can change priority order via the scraper's settings — AniDB first is recommended for absolute-numbered shows; TVDB first for shows you want in English-dub metadata. 5. Run a scrape on the source. First scrape is slow (Hama queries multiple databases) — be patient. Subsequent scrapes are much faster.

Absolute episode numbering

For absolute-numbered series like One Piece (episode 1,064), use season 01 with absolute episode numbers padded to 4 digits:

Anime/
└── One Piece [anidbid-69]/
    └── Season 01/
        ├── One Piece - s01e0001.mkv
        ├── One Piece - s01e0002.mkv
        └── One Piece - s01e1064.mkv

The [anidbid-X] suffix in the folder name forces Hama to use the AniDB entry directly, skipping fuzzy title matching. Find the ID at anidb.net by searching for the show — the ID is in the URL. The 4-digit padding isn't required for matching but keeps filesystem sort order matching playback order. Without padding, file e1064 sorts after e11 instead of after e1063, which makes browsing the folder confusing outside Kodi.

Split seasons and arcs

Modern anime split into "parts" (Attack on Titan Final Season Parts 1/2/3, Demon Slayer arcs) cause the same scraping confusion as in Plex and Jellyfin. The fix: decide which database matches your mental model of the show structure, force it via the folder ID suffix, and stay consistent across all anime.

Anime/
├── Attack on Titan [anidbid-9541]/
│   ├── Season 01/
│   ├── Season 02/
│   ├── Season 03/
│   └── Season 04/   ← Final Season Part 1
├── Attack on Titan - Final Season Part 2 [anidbid-15689]/
│   └── Season 01/   ← AniDB tracks Part 2 as its own entry
└── Demon Slayer (2019)/
    ├── Season 01/
    ├── Season 02/   ← Mugen Train + Entertainment District
    └── Season 03/

Full examples

Anime/
├── One Piece [anidbid-69]/
│   ├── Season 01/
│   │   ├── One Piece - s01e0001.mkv
│   │   └── One Piece - s01e1064.mkv
│   └── Season 00/
│       └── One Piece - s00e001 - Movie 14 Stampede.mkv
├── Attack on Titan [anidbid-9541]/
│   ├── Season 01/
│   └── Season 04/
└── Demon Slayer (2019)/
    └── Season 02/
        └── Demon Slayer - s02e01.mkv

Same scraper in Plex? Plex anime (HAMA same scraper).

Naming Music for Kodi

Music in Kodi is tag-driven first, folder-driven second — exactly like Plex and Jellyfin. The Universal Album Scraper (default in Kodi 19+) reads ID3 tags and queries MusicBrainz and TheAudioDB for artwork and metadata. Fix the tags first, worry about folder structure second.

Recommended folder layout

Recommended layout:

Music/
├── Pink Floyd/
│   ├── The Dark Side of the Moon (1973)/
│   │   ├── 01 - Speak to Me.flac
│   │   └── 02 - Breathe.flac
│   └── Wish You Were Here (1975)/
│       └── 01 - Shine On You Crazy Diamond Pts. 1-5.flac
├── Various Artists/
│   └── Pulp Fiction Soundtrack (1994)/
│       ├── 01 - Misirlou - Dick Dale.flac
│       └── 02 - Royale with Cheese - John Travolta.flac
└── Tool/
    └── Lateralus (2001)/
        ├── Disc 01/
        │   └── 01 - The Grudge.flac
        └── Disc 02/
            └── 01 - Faaip de Oiad.flac

Album year is recommended in the folder name. Multi-disc albums use "Disc XX" subfolders. Compilations use a "Various Artists" album-artist tag (Album Artist tag = "Various Artists", individual Artist tag stays as the track performer).

ID3 tags Kodi actually uses

Required ID3 tags for clean Kodi matching: Artist, Album, Title, Track Number. Strongly recommended: Album Artist (distinct from Artist on compilations), Year, Genre, Disc Number, MusicBrainz IDs. The MusicBrainz IDs (Album ID and Recording ID, embedded as ID3v2.3 TXXX frames or Vorbis comments) let Kodi's Universal Album Scraper match exactly, bypassing fuzzy title matching. Use MusicBrainz Picard to write these IDs once and Kodi's library becomes nearly bulletproof. RenameFlow's music mode reads MusicBrainz and produces accurate filenames + folder structure; it doesn't write ID3 tags. Use it after a tagger like Picard, not as a replacement.

Full examples

Music/
└── Pink Floyd/
    ├── The Dark Side of the Moon (1973)/
    │   ├── 01 - Speak to Me.flac
    │   └── 10 - Eclipse.flac
    └── The Wall (1979)/
        ├── Disc 01/
        │   └── 01 - In the Flesh?.flac
        └── Disc 02/
            └── 01 - Hey You.flac

NFO Files — Kodi's Metadata Override System

NFO files are the single biggest difference between Kodi and Plex/Jellyfin for naming. An NFO is a small XML file you place next to a video, and Kodi reads it INSTEAD of querying online scrapers. They're optional but extremely useful: they let you override wrong scraper matches, document custom collections, and pin metadata that would otherwise drift when online databases change. Plex has nothing equivalent; Jellyfin has partial support via local images and minimal XML. Kodi's NFO system is the most mature implementation in any open-source media center.

When to write NFO files (and when not to)

You don't need NFO files for everything — the scrapers handle 90% of matches correctly. The four scenarios where NFO files are worth the time: 1. The scraper picks the wrong movie/show and "Edit" in Kodi's UI won't stick (common on shows with many remakes). 2. A movie or show isn't on TMDB/TVDB at all (regional releases, fan edits, niche content). 3. You want custom collection groupings beyond what TMDB offers (your own "Best 90s Sci-Fi" set, for example). 4. You're storing metadata you can't lose — Kodi's library can be rebuilt from NFO files alone if the database corrupts. For libraries under 200 items, NFO files are usually overkill. For libraries above 1,000 items where you've spent time correcting metadata, they're insurance.

movie.nfo — the most useful NFO

Movie NFO format. Place the file next to the movie with the name movie.nfo (or Title (Year).nfo matching the video filename — both work, movie.nfo is the convention):

<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<movie>
  <title>Blade Runner</title>
  <originaltitle>Blade Runner</originaltitle>
  <year>1982</year>
  <plot>A blade runner must pursue and terminate four replicants...</plot>
  <runtime>117</runtime>
  <mpaa>R</mpaa>
  <genre>Science Fiction</genre>
  <genre>Thriller</genre>
  <director>Ridley Scott</director>
  <actor>
    <name>Harrison Ford</name>
    <role>Rick Deckard</role>
  </actor>
  <uniqueid type="tmdb" default="true">78</uniqueid>
  <uniqueid type="imdb">tt0083658</uniqueid>
  <set>
    <name>Blade Runner Collection</name>
  </set>
</movie>

The <uniqueid type="tmdb"> field forces Kodi to use the specific TMDB entry instead of fuzzy matching the title. This is the single most useful tag — if you only write one thing in your NFO files, write this.

tvshow.nfo — show-level overrides

TV show NFO files go in the show root folder, named tvshow.nfo. Format similar to movie.nfo but with show-level fields:

<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<tvshow>
  <title>Breaking Bad</title>
  <year>2008</year>
  <plot>A high school chemistry teacher diagnosed with cancer...</plot>
  <genre>Crime</genre>
  <genre>Drama</genre>
  <uniqueid type="tvdb" default="true">81189</uniqueid>
  <uniqueid type="tmdb">1396</uniqueid>
  <uniqueid type="imdb">tt0903747</uniqueid>
  <status>Ended</status>
  <studio>AMC</studio>
</tvshow>

The <uniqueid type="tvdb"> is the most reliable lock for TV shows since TheTVDB is Kodi's default TV scraper for most users.

Per-episode NFO (rarely needed)

Per-episode NFO files are rarely needed — the show-level NFO + scraper-fetched episode metadata covers most cases. Use them only when a specific episode is mismatched and refreshing the show doesn't fix it. Format: place Show - s01e01.nfo next to the video file:

<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<episodedetails>
  <title>Pilot</title>
  <season>1</season>
  <episode>1</episode>
  <aired>2008-01-20</aired>
  <plot>Walter White, a struggling high school chemistry teacher...</plot>
  <uniqueid type="tvdb" default="true">349232</uniqueid>
</episodedetails>

Advanced metadata tags

Beyond the basic <title>, <year>, <plot> tags, Kodi understands a rich set of metadata fields that let you customize how items appear in your library. The most useful for power users: <originaltitle> — the title in the original language, displayed in info pages alongside the localized title. Critical for foreign films where the local distributor title differs significantly from the original (think Spirited Away vs Sen to Chihiro no Kamikakushi). <sorttitle> — overrides the default sort behavior. Use it to force "The Matrix" to sort under "M" instead of "T", or to group sequels together regardless of their canonical titles. Example: sorting all Mission: Impossible films as "Mission Impossible 01", "Mission Impossible 02" etc. <tagline> — the short marketing tagline shown below the title (think "In space, no one can hear you scream"). Adds polish to your library's info pages. <status> for TV shows — "Continuing", "Ended" or "Returning Series". Lets Kodi's skin show appropriate indicators on show cards. <premiered> — the official first-airing date. Useful for anthology shows or anime where the scraper's date is wrong. <fileinfo> blocks — pre-cached file metadata (codec, resolution, audio language tracks). Useful if you build NFO files programmatically and want to skip Kodi's first-scan media analysis.

Multiple rating sources side by side

Kodi 19+ supports multiple ratings sources displayed simultaneously. Add a <ratings> block with as many sources as you want:

<ratings>
  <rating name="imdb" max="10" default="true">
    <value>8.1</value>
    <votes>826543</votes>
  </rating>
  <rating name="themoviedb" max="10">
    <value>8.2</value>
    <votes>9876</votes>
  </rating>
  <rating name="rottentomatoes" max="100">
    <value>89</value>
    <votes>410</votes>
  </rating>
</ratings>

Kodi's default skins display the "default" rating prominently and let you cycle through the others in the info dialog. For libraries where you've curated which sources you trust, this is a meaningful quality-of-life upgrade over the single-source rating that comes from the scraper.

Music NFO files (artist, album, track)

Music has its own NFO format with three levels — artist, album and per-track. The artist-level NFO goes in the artist folder root, named artist.nfo:

<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<artist>
  <name>Pink Floyd</name>
  <disambiguation>British rock band</disambiguation>
  <formed>1965</formed>
  <disbanded>2014</disbanded>
  <genre>Progressive Rock</genre>
  <musicBrainzArtistID>83d91898-7763-47d7-b03b-b92132375c47</musicBrainzArtistID>
</artist>

The MusicBrainz Artist ID lets Kodi's music library link to the canonical entry without fuzzy matching — extremely useful for artists with common names or multiple acts. Album-level NFO (album.nfo in the album folder) accepts similar fields plus <title>, <year>, <musicBrainzAlbumID>. Per-track NFO is rarely used; Kodi's tag-driven music model handles tracks via ID3 tags rather than NFO files.

Common NFO pitfalls

Four mistakes that break NFO files in practice: 1. Invalid XML — unescaped &, < or > characters inside <plot> or <title> tags. The fix: wrap text content in <![CDATA[...]]> or escape manually (&amp;, &lt;, &gt;). 2. Wrong encoding — NFO files MUST be UTF-8. Some Windows text editors save as Windows-1252 by default, which corrupts non-ASCII characters (accents, Cyrillic, Japanese). Use a UTF-8-aware editor (VS Code, Sublime Text, Notepad++). 3. Missing XML declaration — the first line <?xml version="1.0" encoding="UTF-8" standalone="yes"?> is required. Without it, some Kodi versions silently skip the file. 4. NFO conflicts with scraped metadata — if both an NFO and a scraper provide data for the same field, Kodi defaults to the NFO. This is usually what you want but occasionally surprises users who don't realize their NFO is overriding online updates. To go back to scraped data, delete the NFO and refresh.

How NFO files sit next to your media

Movies/
└── Blade Runner (1982)/
    ├── Blade Runner (1982).mkv
    ├── movie.nfo               ← TMDB ID locked
    └── poster.jpg

TV Shows/
└── Breaking Bad (2008)/
    ├── tvshow.nfo              ← TVDB ID locked
    ├── Season 01/
    │   ├── Breaking Bad - s01e01 - Pilot.mkv
    │   └── Breaking Bad - s01e01.nfo   ← per-episode override (rare)
    └── Season 02/

Don't want to hand-write NFOs? or use Filebot's nfo writer.

Kodi Naming Troubleshooting

Six failures cover roughly 85% of Kodi naming complaints. Each has a predictable cause and a clear fix.

The 60-Second Alternative

Everything above is the manual way: understand the scrapers, type the right filenames, write NFO files for stubborn cases. Worth doing once for a fresh library. Painful for a 2,000-file library inherited from years of unstructured downloads.

The manual way

By hand, a Kodi library rename takes about 30 to 60 seconds per item — checking the title, formatting the year, getting the sXXeYY pattern right, and writing NFO overrides for the few problem cases. A 2,000-file library is a long weekend.

The 60-second way

RenameFlow does the rename in seconds. Drop a folder, the parser detects whether it's movies / TV / anime, queries TMDB / TheTVDB / AniDB / MusicBrainz in parallel, and shows the Kodi-compliant rename preview. Confirm and the renames happen locally on your disk via the File System Access API — no upload. Free for the first 15 files per day; one-time 49 EUR for unlimited use. For NFO file generation, RenameFlow doesn't write NFOs directly — but it produces filenames that scrape cleanly with default Kodi scrapers, which eliminates the need for NFOs in 90% of cases. For the remaining 10%, hand-writing the NFO is a one-time cost.

See RenameFlow pricing.

Kodi Naming — Frequently Asked Questions

→ See all RenameFlow FAQs

Continue Reading

• → Plex naming guide (the equivalents)
• → Jellyfin naming guide
• → Step-by-step renaming walkthrough
• → All RenameFlow FAQs

Official references: Kodi naming video files (official wiki) · Kodi NFO files (official wiki) · Hama scraper on GitHub