Supported formats
The image formats SeqLens recognizes as input, and how it decides what counts as a sequence.
| Extension | Use case | Notes |
|---|---|---|
exr |
VFX intermediate material | Recommended. Supports HDR and multilayer files |
dpx |
Film / color management | Recommended |
tif / tiff |
High-quality scans and intermediates | |
png |
Lightweight previews and checks | |
jpg / jpeg |
Lightweight previews and checks | |
webp |
Web delivery | |
tga |
Game / legacy assets | |
bmp |
Legacy assets |
All eight formats above are enabled by default. Toggle them individually under Preferences → Scanning → Extensions. At least one must stay enabled.
Sequence detection rules
Only files whose names match the following regular expression are treated as sequence candidates.
^(.+?)(\d+)\.([^.]+)$ example: shot_0001.exr / render.0042.png / frame.001.dpx
The trailing numeric portion is the frame number. The extension must be one of the eight formats above, and extension matching is case-insensitive (EXR and exr are the same). The base name, however, is case-sensitive, so Shot and shot become separate groups. Files are grouped as a sequence only when they have the same directory, same base name, same extension, and same digit count. For example, 0001.exr and 1.exr have different digit counts, so they become separate groups.
Only groups with two or more frames are shown as sequences. Single image files do not appear in the list. To avoid accidentally treating long timestamp-like numbers as frame numbers, files with a frame range of 1 million or more are not treated as sequences.
EXR layers and metadata
EXR files that contain multiple layers (diffuse / specular / normal, and so on) can be expanded in the table to inspect each layer. Metadata can be checked in Lens, and can also be used for CSV / JSON export and anomaly detection rules.
Unsupported
NOTE
Video containers such as mp4 / mov, psd / ai, and gif are not accepted as input (even when numbered). MP4 is supported only as an export target.