Skip to content

Import Image Download Tasks From CSV — Bulk Image Downloader Pro

danito

If you manage image downloads from spreadsheets, product feeds, client lists, or recurring research sources, copying URLs by hand gets old quickly. The cleaner workflow is to import image download tasks from CSV, so each row can become a prepared task with its own URLs, folder, filters, naming rules, and output settings.

Bulk Image Downloader Pro supports a schema v4 CSV workflow for task import. The safest way to use it is to start from the template or export an existing task first, then edit the CSV with the same headers.

When CSV import is useful

CSV import is useful when the task setup already exists outside the extension. That might be a product spreadsheet, a list of campaign image URLs, a monthly archive plan, or a set of client folders that need consistent settings.

Instead of creating each task manually, you can prepare rows in a spreadsheet and import them into the options page.

Start from the template

Use the Download CSV Template link or export a task you already configured. This matters because the import expects specific columns, including URLs, file types, folder name, download time, ZIP setting, filename constructor data, Download IF rules, conversion and resize settings, custom filenames, watermark settings, filename cleanup rules, task status, input mode, and CSV schema version.

Do not invent new headers. If a column is not needed, leave the value empty instead of renaming the field.

Put URLs in the correct format

In schema v4, multiple URLs for one task should be placed one per line inside the same CSV cell. Legacy semicolon-separated URLs can still work only when every segment is a complete HTTP or HTTPS URL, but newline-separated URLs are the preferred format.

Other fields, such as file types, Download IF keywords, and custom filenames, use semicolons between values. Mixing these rules is one of the easiest ways to create a broken import.

Import a small test first

Before importing a large CSV, test two or three rows. Confirm that the URLs appear in the right task, folder names are correct, file type filters are applied, filename rules look right, and scheduled times are not in the past.

If the test import looks wrong, fix the spreadsheet before loading hundreds of rows.

Use export as your import builder

The most reliable import workflow is to create one task manually, save it, export it, and then duplicate that row in your spreadsheet. That gives you the current header order and a real example of how complex settings are serialized.

This is especially helpful for filename constructor HTML, watermark JSON, custom filename lists, and filename cleanup rules.

Licensing and mode notes

Bulk CSV import is a PRO workflow. The template also supports URL tasks and file-mode task data, but file-mode imports depend on IndexedDB keys from the same browser context. For most portable imports, URL-based tasks are the safer choice.

Queue Download ignores downloadTime because scheduling is disabled while queue mode is active.

A practical CSV import checklist

  1. Export a working task or download the official template.
  2. Keep the schema v4 headers unchanged.
  3. Use newline-separated URLs inside the URLs cell for multi-URL tasks.
  4. Use semicolons for fields that expect lists, such as file types or Download IF rules.
  5. Test a small CSV before importing the full file.
  6. Review imported tasks before running downloads.

For the reverse workflow, read export image download tasks to CSV. For URL-list basics, see bulk download images from a URL list.