How to Find Missing Files and Duplicate Numbers in a Filename Sequence

When a folder contains numbered files, check the sequence before you rename, upload, archive, or deliver it. Start by separating unrelated filename patterns, sort the relevant names by their numeric part, and look for missing values, repeated numbers, inconsistent zero-padding, extension changes, and spelling differences. Do not rename anything until you have confirmed whether a gap is an error or an intentional part of the workflow.

For a small folder, this can be done manually. For a larger set, Tweaknook's SeqName can compare file names and relative folder paths in the browser and narrow the review to the entries that deserve attention. The checker does not open selected file contents and it does not rename or delete files.

First, Decide What Counts as One Filename Sequence

A sequence is more than a group of files that happen to contain numbers. The files should share a meaningful naming pattern and usually belong to the same export, scan, render, photo set, document batch, or delivery folder.

The first task is therefore to define the family: which folder, prefix, suffix, extension, and numeric position should be compared. Mixing unrelated families creates false gaps and false duplicates.

Preserve the Original Folder Before You Inspect or Rename

Sequence checking is normally non-destructive, but the next action often involves batch renaming or replacing files. Keep the original folder unchanged until the intended order has been confirmed. For an important delivery, create a separate copy or verified backup before applying a rename plan.

Also record which applications or project files refer to the current names. Video editors, 3D projects, scripts, spreadsheets, web pages, and publishing systems may store exact paths. A technically tidy rename can still break a workflow when those references are not updated.

Check a Small Sequence Manually

For a short list, use a simple inspection process:

1. Display the full filename, including its extension.
2. Sort by name using a numeric-aware file manager when possible.
3. Write down the common prefix and suffix.
4. Mark the numeric part that represents the intended sequence.
5. Compare each value with the previous value.
6. Record gaps, repeated values, padding changes, extension changes, and text differences separately.

Keep those issue types separate because they do not mean the same thing. A missing value suggests a possible absent item. A repeated number means two files claim the same position. A padding change such as 0006 versus 006 may only be a naming inconsistency. A different extension may be an alternate deliverable rather than an error.

Use SeqName to Narrow a Larger Folder

When manual comparison becomes difficult, open SeqName and use the smallest set of files that represents the sequence you want to audit.

1. Select files or a folder.
2. Keep Check each folder separately enabled when subfolders contain independent sequences.
3. Use extension filters when unrelated file types should not be compared.
4. Leave common sidecar handling enabled when formats such as XMP, JSON, XML, SRT, or VTT accompany a primary file.
5. Run the check and read the overall verdict before opening technical details.
6. Review each flagged filename against the source project.
7. Download or copy a report only when it will help with the manual correction process.

SeqName uses file names and relative folder paths to build its model. It does not parse the file contents, so it cannot determine whether an image is visually missing, whether two files contain identical data, or whether a skipped number was intentional.

Interpret the Result Types Correctly

Missing number

A missing-number result means the detected pattern suggests an expected value between surrounding values. It is evidence for review, not proof that a file was lost. Render queues, camera exports, scans, and document batches can intentionally skip numbers.

Repeated number

A repeated number means more than one filename uses the same sequence value within the detected family. The files may still have different contents. If you need to know whether two files are content duplicates, compare hashes rather than relying on names. Tweaknook's PowerShell duplicate-file report covers that separate content-based check.

Padding difference

Zero-padding keeps lexical and numerical order aligned. In a sequence that consistently uses four digits, frame_006.png is an outlier next to frame_0005.png and frame_0007.png. Confirm the intended width before changing it, especially when another application expects a fixed pattern.

Extension difference

A different extension can be legitimate. It may represent a preview, sidecar, alternate format, or accidental export. Changing an extension does not convert the underlying file format; Microsoft explicitly notes that renaming an extension does not transform the file itself.

Pattern difference

A spelling change, missing separator, or altered prefix can split one logical series into several apparent groups. Compare the outlier with its neighboring files and the naming rule used by the source application.

Low-confidence or review result

When several numeric positions or irregular intervals are present, an automated checker should not pretend the answer is certain. Treat a low-confidence result as a prompt to identify the correct numeric token and intended step manually.

Handle Filenames with Several Numbers

Dates, versions, resolutions, camera identifiers, and sequence numbers often appear together:

project_2026-08-22_v03_frame_0012.png

Here, the date, version, and frame number are all numeric. Before checking for gaps, decide which number should advance. A useful method is to hold every other part constant and compare neighboring files. If only the final token changes from 0012 to 0013, that is stronger evidence that it is the sequence number.

Do not remove dates or version numbers merely to make a checker produce a simpler result. Those values may carry necessary workflow information.

Account for Sidecars and Alternate Deliverables

Files with the same base number are not always duplicates. A photo may have an XMP sidecar, a video may have an SRT or VTT caption file, and an export may include both a master image and a compressed preview.

Decide whether extensions belong to one family or separate families. If the goal is to confirm that every image has a matching sidecar, a pair is expected. If the goal is to find repeated master images, group the primary extension separately.

Check Cloud and Cross-Platform Naming Limits Before Renaming

A filename that works locally may fail in a synchronized or cross-platform destination. Windows reserves several characters and device names, while OneDrive and SharePoint apply additional filename and path restrictions. Apple Finder supports batch renaming but also has its own filename rules. Review the destination before creating a new naming scheme.

Keep names reasonably short, avoid trailing spaces or periods for Windows-oriented workflows, and do not introduce characters that the destination service rejects. These checks are separate from sequence analysis, but they prevent a clean sequence from becoming an upload or sync problem.

Create a Safe Rename Plan

After confirming the issue, plan the change before applying it:

1. Keep a backup or unchanged source folder.
2. List every old name and proposed new name.
3. Check that no two proposed names are identical.
4. Preserve extensions unless you are performing a real format conversion in the source application.
5. Use a temporary intermediate name when a direct swap would collide.
6. Update applications, links, manifests, or project files that refer to the old paths.
7. Rename a small sample and reopen it in the dependent application.
8. Apply the remaining changes only after the sample works.

For a preview-first Python workflow, see How to Safely Bulk Rename Files with Python. SeqName itself intentionally does not rename files.

What Not to Do

• Do not declare every numerical gap a missing file.
• Do not treat equal sequence numbers as proof of identical contents.
• Do not compare unrelated folders or naming families as one sequence.
• Do not remove or change extensions to make names look consistent.
• Do not batch rename the only copy of an important folder.
• Do not ignore project files or applications that store exact filenames.
• Do not delete an outlier until its role has been confirmed.

Confirm the Folder Is Ready

The audit is complete when the intended sequence family is clear, every reported gap or duplicate has been classified, zero-padding and text patterns are consistent where required, sidecars and alternate formats are accounted for, and the final names work in the destination system.

Keep the report or rename map with the project when the naming rule will be reused. That makes later additions easier to check and reduces the chance that the next export introduces the same inconsistency.

Official References

• Microsoft: Common file name extensions in Windows
• Microsoft Learn: Naming Files, Paths, and Namespaces
• Microsoft: Restrictions and limitations in OneDrive and SharePoint
• Apple: Rename files, folders, and disks on Mac