Smart Renaming (Rename Tab)

Live preview shows exactly what your filenames will become before you stage the change.

• Custom tokens: build patterns using {index}, {date}, {original}, {city}, and {country}. Tokens are lowercase; {INDEX} or {Index} are left in the filename verbatim.
• Index padding and start number: click the small ▾ next to the + Index token button to open its options popover. Inside you can set the Start number and the zero-pad Digits (3, 4, 5, or 6). The default is 3 digits (001, 002, ..., 042); bump to 5 digits (00001, 00042, ..., 12345) for large archives so filenames keep sorting correctly past 999 photos. Jade GT auto-selects a safe width the first time you open a batch. A gold star (★) marks the recommendation inside the popover, and the + Index button shows your current digit count as a subscript (e.g. + Index₃). If your saved choice would break sort order for the current selection, the button picks up a subtle amber ring and dot as a heads-up. Your manual pick is remembered across sessions on the same device.
• Live preview: see exactly how your files will look before you apply the change.
• Missing location data: if you use {city} or {country} on a photo with no GPS, the token falls back to Unknown. If the photo has GPS coordinates but no reverse-geocoded city, {city} falls back to the decimal coordinate pair (e.g. 45.52,-122.67). Pair location tokens with {index} so batches with missing data still produce unique filenames.
• Staging: clicking Stage Names prepares the files for the final commit. Disk renames happen at commit time, not when you click Stage.

Collisions overwrite silently

If two photos resolve to the same final name, the later one overwrites the earlier one on commit. Always include a unique token ({index} or {original}) when renaming a batch. For batches over 999 photos, raise the Digits setting to 4 or 5 so the sequence keeps sorting in the right order on disk. With 3-digit padding, 1000 ends up lexically before 999.