Use a CSV or TXT List for Custom Download Filenames

danito

When the names are already decided

Sometimes you do not want a generated pattern at all. You already know exactly what each image should be called — the names live in a spreadsheet, a product feed, or a list a client sent over. In that case, building a token pattern is the wrong tool. What you want is to hand the extension your list of names and have it apply them in order.

Bulk Image Downloader From URL List supports this directly inside the Filename Constructor. Instead of assembling segments, you upload a file of pre-built filenames and the extension uses your names one-to-one as each image downloads.

How the upload works

The constructor accepts a CSV or TXT file with one filename per row. The key rule is alignment: the names are matched to your URLs by position. The first row names the first URL in your list, the second row names the second URL, and so on down the list. As long as your two lists are in the same order, every file comes out with the name you intended.

This makes the workflow predictable. If you maintain your URLs and your target names in the same spreadsheet, you keep both columns sorted the same way, then export the names column to CSV or TXT. Drop that into the constructor and the mapping just works.

Grab the template from the UI

You do not have to guess at the format. The constructor gives you a CSV or TXT template you can download straight from its interface. Grabbing the template first is the safest way to start, because it shows you the exact layout the importer expects — one filename per row, nothing extra to trip over.

A practical sequence looks like this:

  • Open the task and enable the Filename Constructor.
  • Download the CSV or TXT template from the constructor UI.
  • Fill in your filenames, one per row, in the same order as your URL list.
  • Upload the completed file back into the constructor.
  • Run the task — each image saves with its matching name.

Why this beats renaming afterward

The obvious alternative is to download everything with default names and rename later. On more than a handful of files that falls apart fast: you lose track of which download maps to which intended name, and one out-of-order file shifts everything below it. Uploading the names up front removes that risk entirely, because the extension applies them during the download itself.

It is the right approach whenever the naming is dictated by something outside the extension — a SKU list, an asset catalog, a delivery manifest. You keep the authoritative names where they already live, and the download simply honors them. As with every constructor option, your URL list stays untouched; only the output filenames reflect your uploaded list.