Identify the field and the source of the correction
If a manually corrected title or tag changes again in Emby, begin with one item. Record the intended value, the current value and the operation after which it changed. A library scan, an identification change and an image refresh are different operations, so name the actual trigger rather than describing every change as a rescan.
Open the item in Metadata Manager and check that it is the intended movie, episode or series level. An edit on a series does not automatically describe every episode. Keep any current provider identifiers and local metadata inputs in private notes before changing them; they can explain why a refresh selects a different result.
Save the edit before leaving the page
Emby’s Metadata Manager documentation explicitly requires saving metadata edits. Make the smallest intended correction and use Save before navigating away. Return to the item and confirm the value persisted. This first check separates an unsaved browser form from a later refresh that actually overwrites a saved field.
For a title, compare the exact displayed text. For a tag used by your own workflow, compare its spelling and the item level where it was saved. Avoid editing unrelated plots, images and identifiers during this test. Several simultaneous edits make it difficult to tell which part of the workflow did or did not persist.
Choose a field lock with an understood scope
Emby documents individual field locks and an item-level lock for preserving edits through refresh. Choose the narrow scope that reflects your intention. If only one custom field must remain fixed, understand why you would lock the whole item before doing so. A broad lock can complicate later expectations that other metadata will update normally.
Tags can also participate in server access rules. If a tag is used for a household access policy, preserve its intended spelling and review the affected user separately. A saved metadata value and a verified access result are separate checkpoints. Do not treat an attractive library display as evidence that every user sees the intended collection.
Repeat the original trigger on the same item
After saving and applying the intended lock, repeat the operation that previously changed the value. Inspect that exact field again. If it remains correct, record the field, lock scope and trigger as the verified configuration. If it changes, inspect local metadata writers and current provider behavior through Emby’s documentation before making a library-wide change.
Keep the original value and a short change record until the case is understood. This procedure addresses persistence of deliberate metadata edits. It does not repair inaccessible video, authorize a stream or establish that a server’s content restrictions have been independently tested.
Questions answered
Why did my edited title vanish when I left Metadata Manager?
First confirm that Save was used. Emby documents saving as required before leaving the page.
How can I preserve one custom field through a refresh?
Emby provides field locks as well as a whole-item lock. Save the intended value, choose the appropriate scope, then repeat the same refresh as a controlled test.
Sources & further reading
Official references for the subjects discussed. Service terms and device software can change.