Filename Tokens and Sequences for Perfectly Ordered Downloads

Server-generated names like a8f3c2.jpg tell you nothing and sort into nonsense. The cure is to take naming into your own hands with filename tokens and sequences, building each filename from meaningful parts as the image downloads instead of accepting whatever the server hands back.

The Filename Constructor, drag and drop

Naming happens in the Filename Constructor, where you assemble a filename from segments by dragging and dropping them into the order you want. Think of it as building a pattern: a fixed label, a token, a number, in whatever arrangement makes sense for the job. Because it is drag-and-drop, rearranging the structure is a matter of moving blocks around rather than typing out syntax.

Tokens and sequences, the two key ingredients

Two ingredients do most of the work, and together they give the feature its name.

• Tokens are dynamic placeholders the tool fills in. A special token like [timestamp] stamps each file with its capture time, which is great for keeping versions distinct or recording when a batch was pulled.
• Sequences are auto-incrementing numbers. Turn one on and your files become 001, 002, 003 and so on, in order, so a gallery or product set downloads in a predictable, sortable line.

Combine them and a name like shoot-[timestamp]-001 becomes self-describing and self-ordering at the same time.

Extensions handled, order preserved

You do not need to worry about file extensions in your pattern; they are appended automatically based on the actual file, so a JPEG stays .jpg and a PNG stays .png without you typing it. Pair filename tokens and sequences with the “respect order” download setting and the numbering lines up with the source order, which keeps multi-page scrapes from scrambling. Bulk Image Downloader From URL List applies the whole pattern as files come down, so the names are right on arrival.

Why ordered names matter

Clean, sequential names pay off downstream. Operating systems sort them correctly, version control and backups stay readable, and anyone you hand the folder to can follow the set without guessing. A timestamp prevents collisions when you rescrape, and a sequence keeps a series intact. Both beat cryptic server hashes that scatter your files into random order.

Mixing custom names with filename tokens and sequences

Tokens and auto-numbering are not your only option. When you need exact, human-chosen names, you can load a list of custom names from a .csv or .txt file, and the tool maps them to your downloads in order. You can lean on whichever approach fits the job: a fully generated pattern for a large anonymous batch, or explicit names for a curated set where each file has a meaning. Those custom names are stored with the task, so they persist through export and re-import rather than evaporating between sessions. In practice many people combine ideas, an explicit base name plus a sequence number, to get both meaning and order in one filename.

Build the pattern once, reuse it

The point of filename tokens and sequences is repeatability. Construct the pattern that fits a project, fixed label plus timestamp plus running number, and every image in the task follows it. For recurring jobs you keep the same structure, so this month’s batch matches last month’s. Set the naming logic deliberately and your downloads stop being a bag of random strings and start being an ordered, readable archive from the first file to the last.