How to Organize Home Videos: File Names and Metadata That Travel

To organize home videos, give each recording a stable ID and keep its source, date and file roles in a readable catalog. Treat the title shown by a media server as a separate display label. Before renaming a whole collection, move three sample items—with their records—to a separate test library and check what survives.

This workflow is for your own recordings and authorized media, including videos stored on self-authored Blu-rays. It starts with files you can already access. For choosing the archive itself, see the ISO guide.

Keep the recording’s identity separate from its filename

A useful title might change from “Summer trip” to “Summer trip, day two.” Its source and relationship to other versions should remain traceable. Use an ID such as HV001 for that recording, then distinguish the files belonging to it.

Here is a proposed layout for a hypothetical recording, not a format required by Plex, Jellyfin or Blu-ray:

HomeVideoArchive/
  README.txt
  catalog.csv
  originals/
    HV001_source.iso
  access/
    HV001_access_v1.mp4

In this example, the ISO is the retained image of a self-authored disc and the MP4 is a viewing version. “Source” does not prove it is the camera original or a lossless master. NARA distinguishes preservation and access copies; record what each file actually contains instead of relying on its suffix.

If a disc contains several recordings, give the recordings separate IDs and map each back to that disc. Keep a disc-level record too. For an existing BDMV folder, keep its internal names and structure intact; use the outer archive folder and catalog to describe it.

Make a catalog you can understand without the media server

Use a spreadsheet exported as UTF-8 CSV, or another documented, readable format. Put one row per file and reuse the recording ID for related versions. These are suggested fields:

The sample values are invented. Explain the columns, ID scheme and folder roles in README.txt. Add editing history or processing settings when you make a new version. Keep detailed names and locations out of shared filenames if the people involved would not want them exposed.

This catalog is a migration record for you; it is not a promised automatic import file for a player. NARA’s organization guidance supports keeping understandable structure and descriptive information with recordings. Keep the catalog and README in your archive’s independent copies too.

Choose filenames without inventing dates

If chronological sorting helps, you could name a file 200907_HV001_access.mp4, with the catalog explaining that only the month is known. If the date is unknown, leave it out and record unknown. Do not insert a fictional January 1 merely to fill a date field, or assume the current file modification time is the recording date.

Use short, consistent names, keep the extension appropriate to the real format, and check for collisions before applying a naming plan. The Smithsonian naming guide hosted by NARA explains why distinctive names and consistent patterns help. The examples here are our own convention, not a universal filename-length limit.

For two clips from the same event, use different IDs or an explicit sequence. Avoid relying only on uppercase versus lowercase to distinguish files. Preserve an old-path → new-path mapping and never overwrite an existing same-name file during a trial rename.

Adapt the viewing library separately

Plex: its personal-media guide describes filename-based display names and embedded metadata for some formats. That page was last modified in 2019. Check your current library setup with samples; do not assume its old agent menus apply unchanged.

Jellyfin: its NFO documentation specifies filenames by media type, gives local NFO metadata priority over remote providers, and documents an optional Nfo saver. Reading and writing support different field sets. Do not assume an export preserves every field or that Plex will consume it.

Keep application-specific sidecars with the files they describe, following that application’s naming rules. If you export metadata, inspect the exported result before treating it as a recovery copy. Your independent catalog should still identify the video when a server’s display title is missing or incorrect.

Try three items before reorganizing everything

Choose one recording with a known date, one with an uncertain date, and one with a title containing non-Latin characters. Work on copies in a separate test directory and library.

1. Copy the selected files, catalog rows, README and relevant sidecars together. Allow for the extra working space.
2. Follow the destination application’s documented import or library procedure. Reapply metadata manually if its format is unsupported.
3. Compare the title, date, description and duplicate entries against your catalog. Check that the source and viewing version have not been confused.
4. Open the intended viewing file and check its audio and subtitles. A successful scan alone does not verify playback.
5. Record missing fields and the mapping used to restore them. Keep the old library and sources until the new result is checked and recoverable.

If the trial fails, correct the naming or metadata mapping on the test copies first. The useful result is a recording you can identify and understand outside one particular application—not just a tidy-looking library screen.

Official documentation was checked on October 21, 2026. This is a documented planning workflow; we did not test a physical disc, rename a reader’s files, or perform a Plex/Jellyfin migration.