Preserve one repeating mismatch
If a corrected Jellyfin title returns to the same wrong value after refresh, keep one item as the example. Record the displayed title before editing, the intended title and the action after which it changes back. Do not refresh every library immediately; a repeating single-item result is easier to trace than a collection changed by several different operations.
Inspect the media directory from the server’s perspective and look for its local NFO file. A client showing the movie does not tell you whether the directory contains sidecar metadata. Keep a private copy of that small file before editing it, especially when another application also maintains the same media folder.
Check the input with documented priority
Jellyfin documents that local NFO metadata is read and takes priority over remote metadata providers. It also specifies different filenames for different media levels, such as tvshow.nfo for a series and a filename matching an episode for episode metadata. A correct remote match may therefore coexist with an older local title that is reapplied.
Read the relevant file as text and compare only the fields involved in the mismatch. Look for repeated tags that could map to the same internal field. Jellyfin documents that the last such tag wins. Avoid deleting every unfamiliar field just to make one title change; the file may contain useful identifiers, artwork references or metadata maintained by another tool.
Choose which application owns the correction
If the local NFO is intended to be authoritative, correct the relevant field there using the supported format, then refresh the same item and inspect the result. If another program writes that file, make the corresponding change in that program’s workflow as well. Otherwise the next export may restore the old value.
Jellyfin’s NFO saver is a separate library option for writing metadata out. Reading an existing NFO and enabling future writes are different decisions. Decide whether you actually want the server to modify files in the media directory before granting write access or enabling a saver. A read-only library can still be an intentional playback arrangement.
Verify persistence without changing the whole collection
Compare the item after the targeted refresh and again after the next ordinary scan. Record whether the intended title persists and whether the NFO itself changed. If it changes again, identify which application or scheduled process wrote it rather than treating each recurrence as a new online database error.
Keep the original backup until the result is understood. This procedure addresses metadata precedence, not damaged video or stream authorization. The expected outcome is a clear owner for the item’s metadata and a correction that survives the actual refresh route you use.
Questions answered
Can an online metadata refresh override every local NFO value?
Jellyfin documents local NFO metadata as having priority. Inspect the sidecar input when the same local value keeps returning.
Does reading NFO metadata mean Jellyfin must write to my movie folder?
No. Reading existing metadata and enabling the library’s NFO saver are separate choices. Grant write access only for the operations you intend to use.
Sources & further reading
Official references for the subjects discussed. Service terms and device software can change.