Camera manufacturers give your photos names like DSC_4872.NEF or IMG_0342.CR3. These filenames tell you nothing about what is in the image, when or where it was shot, or which project it belongs to. As your photo library grows into the thousands, meaningless filenames become a real organizational problem. Renaming files in Lightroom Classic replaces those cryptic camera names with descriptive, consistent filenames that make your library searchable and organized for years to come.
Lightroom Classic is the ideal place to rename because it tracks all name changes in its catalog database. When you rename a file through Lightroom, the catalog updates automatically, so all your collections, keywords, edit history, and metadata stay perfectly linked to the renamed file. Renaming files outside of Lightroom (in your operating system’s file browser, for example) breaks this connection and creates “missing file” errors that you will have to fix manually.
Why File Naming Matters
Good file naming is one of those unglamorous skills that separates organized photographers from chaotic ones. Consider the practical benefits.
Searchability. A file named “Johnson_Wedding_0042.NEF” is immediately findable using your operating system’s search or Lightroom’s filter bar. A file named “DSC_0042.NEF” could be from any shoot you have ever done.
Avoiding duplicates. Cameras reset their counters periodically, which means you will eventually have multiple files named DSC_0001. If these end up in the same folder, your operating system will either overwrite one or append a suffix, creating confusion. Unique, descriptive names eliminate this risk entirely.
Client deliveries. When you deliver images to a portrait or wedding client, professional file names make a better impression than camera defaults. They also make it easier for clients to reference specific images when requesting prints or edits.
Archival integrity. Years from now, when you are searching through tens of thousands of files, descriptive names save enormous amounts of time. Good naming is an investment in your future self.
Renaming During Import
The most efficient time to rename files is during import, before they even enter your catalog. Lightroom’s Import dialog includes a File Renaming panel on the right side that lets you apply a naming template to every file as it is imported.
To access it, connect your memory card or select the folder of images you want to import. In the Import dialog, look for the File Renaming panel on the right side. Check the “Rename Files” checkbox to enable it.
You will see a Template dropdown with several built-in options. The most commonly useful built-in templates are “Custom Name – Sequence” (which lets you type a name and adds incrementing numbers) and “Date – Filename” (which prepends the capture date to the original camera filename). But the real power comes from creating your own templates.
Click the Template dropdown and select “Edit” to open the Filename Template Editor. This is where you build custom naming structures using a combination of typed text and dynamic tokens.
The Filename Template Editor
The Filename Template Editor is more powerful than it first appears. It lets you combine fixed text (like a client name or project description) with dynamic tokens that pull information from each photo’s metadata.
The template field at the top shows your current naming structure. Below it, you will find categories of tokens you can insert: Image Name, Numbering, Date, Metadata, and Custom. Click the “Insert” button next to any token to add it to your template.
Useful tokens include:
Date tokens. {Date (YYYY)} gives you the four-digit year, {Date (MM)} gives the two-digit month, and {Date (DD)} gives the day. Combining these as {Date (YYYY)}-{Date (MM)}-{Date (DD)} produces dates like 2026-03-15, which sort chronologically in any file browser.
Sequence numbers. The Sequence token adds incrementing numbers to each file. You can control the starting number and the number of digits. Using four digits (0001, 0002, 0003) accommodates shoots of up to 9,999 images and keeps files sorting correctly.
Original filename. The {Original filename} or {Original number suffix} tokens let you preserve the camera’s sequence number as part of your new name. This is useful if you want to cross-reference renamed files with the original filename shown on your camera’s LCD.
Custom text. The Custom Text token inserts whatever you type into the “Custom Text” field in the File Renaming panel. This is how you add client names, project names, or location descriptions. For a wedding, you might type “Smith-Johnson” as the custom text, producing filenames like “Smith-Johnson_0001.NEF.”
Once you have built a template you like, click the Preset dropdown at the top of the editor and choose “Save Current Settings as New Preset.” Name it something descriptive like “Client_Date_Sequence” so you can quickly select it on future imports.
Renaming After Import
If you did not rename during import, or if you need to rename files that are already in your catalog, Lightroom makes this easy. You can rename one image, a selection, or your entire catalog.
Renaming a single file. In the Library module, select the photo you want to rename. Press F2 (or go to Library > Rename Photo). A dialog appears with the same template system used during import. Select a template or type a custom name, and click OK.
Renaming multiple files. Select all the files you want to rename. You can use Ctrl+Click (Cmd+Click on Mac) to select specific images, or Ctrl+A (Cmd+A) to select all images in the current view. Then press F2 to open the Rename dialog. The template you choose will be applied to all selected images, with sequence numbers incrementing automatically across the selection.
When renaming a batch of files, pay attention to the sort order of your selection. Lightroom applies sequence numbers based on the current sort order in the Library module. If you want the numbers to follow the chronological capture order, make sure your images are sorted by Capture Time before starting the rename. If they are sorted by filename or some other criterion, the sequence numbers will follow that order instead.
Practical Naming Conventions
There is no single “correct” naming convention, but some approaches work better than others. The best conventions are consistent, descriptive, and sort well in file browsers.
Date-first naming. Starting filenames with the date (in YYYY-MM-DD format) ensures that files sort chronologically in any file browser or application. Example: 2026-03-15_Portrait_Smith_0001.NEF. This convention works exceptionally well for photographers who shoot multiple projects and need to find images by date.
Client-first naming. For client-focused workflows, leading with the client name makes files easy to find by project. Example: Smith_Wedding_2026-03-15_0001.NEF. This works well if you organize your archive primarily by client rather than by date.
Genre-based naming. Landscape and street photographers who do not work with named clients often use location or subject descriptions. Example: Yosemite_HalfDome_Sunset_0001.NEF. This is less systematic but can work if your library is not enormous.
Regardless of the convention you choose, follow these universal rules. Use underscores or hyphens instead of spaces (some systems handle spaces poorly). Avoid special characters like &, #, or %. Keep names reasonably short, as extremely long filenames can cause problems on some operating systems. And be consistent. A naming convention only works if you follow it every time.
Undoing a Rename
If you rename files and immediately realize you made a mistake, press Ctrl+Z (Cmd+Z on Mac) to undo. Lightroom supports multi-step undo, so you can revert a batch rename even if it affected hundreds of files.
If you discover the mistake later, the situation is more complex but not hopeless. Lightroom stores the original filename in the photo’s metadata. You can see it in the Metadata panel in the Library module under the “Original Filename” field. You could use a naming template with the {Original filename} token to revert to the original camera names. Or you could simply rename the files again using your corrected template.
Renaming and External References
When you rename a file in Lightroom, the actual file on disk gets renamed. This means any external references to that file, such as bookmarks, shortcuts, links in documents, or references in other applications, will break. If you have already shared a file path with someone or linked to it from another program, renaming it will sever that connection.
For this reason, it is best to establish your naming convention early and rename files during import, before they are referenced anywhere else. Renaming after the fact works fine within Lightroom’s ecosystem, but it can cause problems if other systems depend on the old filenames.
This also applies to files you have already exported. Renaming the source file in Lightroom does not automatically rename any exported copies. Those are separate files that retain whatever name they had when exported.
Renaming for Specific Delivery Scenarios
Different delivery contexts sometimes require different naming approaches.
Stock photography. Stock agencies often have specific naming requirements. Some require descriptive keywords in the filename. Others want simple alphanumeric identifiers. Check your agency’s submission guidelines before renaming files for stock submission.
Print labs. Most print labs are flexible about filenames, but avoid special characters and spaces. Some labs use filenames to organize orders, so clear, descriptive names help prevent mix-ups when you submit large orders.
Collaborative projects. When multiple photographers contribute to the same project, include a photographer identifier in the filename to avoid naming collisions. Example: DJ_Smith_Wedding_0001.NEF versus KL_Smith_Wedding_0001.NEF distinguishes files from two photographers at the same event.
Renaming and File Extensions
Lightroom renames the base filename but never changes the file extension. A file originally named DSC_4872.NEF remains a .NEF file after renaming. This is important because the extension tells your operating system and editing software what type of file it is. If you need to convert file formats (for example, from RAW to JPEG), that happens through the Export dialog, not through renaming.
When creating naming templates, you do not need to include the extension. Lightroom appends it automatically. If your template produces “Smith_Wedding_0001,” the final filename will be “Smith_Wedding_0001.NEF” (or whatever the original format is). Do not add “.NEF” or “.CR3” to your template manually, as this will result in doubled extensions like “Smith_Wedding_0001.NEF.NEF.”
Handling Sidecar Files and XMP Data
If you have configured Lightroom to write changes to XMP sidecar files (a common setting for photographers who want their edits portable between applications), renaming a RAW file also renames the associated .xmp sidecar file. Lightroom handles this automatically, keeping the RAW file and its sidecar in sync.
This is another reason to always rename through Lightroom rather than through your operating system. If you rename a RAW file in Finder or Windows Explorer but forget to rename the matching .xmp file, Lightroom will lose the connection between the two. Your edits, keywords, and ratings stored in the sidecar file will be orphaned, and you will need to manually reconnect them or redo the work.
Renaming Across Multiple Cameras
Professional photographers often shoot with two camera bodies at the same event. Each camera produces its own sequence of filenames (DSC_0001 from Body 1 and DSC_0001 from Body 2, for example). This creates an immediate naming collision if both sets of files end up in the same folder.
There are two strategies for handling this. The first is to import from each card separately and use different custom text for each body. Body 1 might get “Smith_Wedding_B1_0001” and Body 2 might get “Smith_Wedding_B2_0001.” The second approach is to import all images from both cards at once, sort them by capture time, and rename them as a single continuous sequence. This interleaves images from both cameras in chronological order, which some photographers prefer because it tells the story of the event in the order things happened.
Whichever approach you choose, having a plan before you start importing prevents the confusion that comes from two cameras producing identically named files.
Common Mistakes to Avoid
Renaming outside of Lightroom. This is the most common and most damaging mistake. When you rename files in Finder, Windows Explorer, or any application other than Lightroom, the catalog does not know about the change. The next time you open Lightroom, it will show those files as missing. You will then have to manually reconnect each file. Always rename through Lightroom to keep the catalog in sync.
Using inconsistent conventions. Switching between naming styles, sometimes using dates first, sometimes using client names first, sometimes using underscores, sometimes using hyphens, defeats the purpose of having a system. Pick one convention and stick with it.
Forgetting to save templates. If you build a custom naming template during import but do not save it as a preset, you will have to rebuild it every time. Always save useful templates as presets in the Filename Template Editor.
Not checking sort order before batch renaming. If your images are sorted by filename instead of capture time, the new sequence numbers will not match the chronological shooting order. This is confusing when reviewing images later. Always verify the sort order before renaming a batch.
Advanced Template Techniques
Once you are comfortable with basic templates, you can build more sophisticated naming structures using Lightroom’s template tokens in combination.
Shooting-specific metadata. The Filename Template Editor includes tokens for EXIF metadata like ISO, focal length, and camera model. While most photographers will not want this data in every filename, it can be useful for specific workflows. A lens reviewer, for example, might include focal length in the filename to instantly identify which lens was used for each shot. A photographer testing multiple camera bodies might include the camera model token.
Combining multiple tokens. You can chain tokens together with separating characters to build complex names. A template like {Date (YYYY)}{Date (MM)}{Date (DD)}_{Custom Text}_{Sequence# (0001)} produces filenames like “20260315_Smith_Wedding_0042.” The key is balancing information density with readability. Too many tokens create filenames that are hard to parse at a glance.
Using different templates for different purposes. You might have one template for imports (date-based, for archival organization) and another for exports (client-based, for delivery). Lightroom’s export dialog also includes a file naming section with its own templates, independent of the import templates. This lets you maintain different naming conventions for your archive and your deliverables without any conflict.
Building File Naming Into Your Workflow
The best file naming approach is one you apply consistently from the start of every project. Build it into your import workflow so it happens automatically. Set up your naming template once, save it as a preset, and select it every time you import. After a few sessions, it becomes second nature.
Combine file renaming with a consistent folder structure for maximum organization. Many photographers use a Year > Month > Project Name folder hierarchy with renamed files inside. When both your folders and your files are named descriptively, finding any image from any shoot becomes trivial, even years later.
File renaming is not exciting. It will never be the reason you create a great photograph. But it is the kind of behind-the-scenes discipline that prevents headaches, saves time, and keeps your growing photo library manageable for decades. The few minutes you spend setting up a naming convention now will save you hours of searching and organizing later.