framelet. batch image templatesOpen the editor
Reference

How to write a product CSV for image batches

A batch fails for boring reasons: a header with a trailing space, a blank cell, a currency symbol in the wrong encoding. This page is the short version of what is enforced and why.

Header rules

Value rules

A minimal working example

Template fields: title, price, cta

title,price,cta
"A little room to grow",$24,Shop the collection
"Slow mornings",$38,See the set

Two rows, three fields, no empty cell. Each row produces one PNG.

The six mistakes behind most failed uploads

  1. A trailing space in a header. Invisible in a spreadsheet, fatal on upload.
  2. Capitalisation drift. Price does not match a price variable.
  3. An empty cell somewhere in the middle of the sheet.
  4. Excel exported as plain CSV and mangled accented characters — re-export as CSV UTF-8.
  5. Leading zeros stripped from SKUs and IDs — format those columns as text first.
  6. A comma inside an unquoted value, which pushes every later column one place to the right.

What this does not do

  • No .xlsx upload, no Google Sheets sync, and no automatic column mapping — headers must match the template's variables by hand.
  • A batch is limited to 50 rows, and each template has a single page.
  • Values are text only. There is no per-row image URL column, no conditional formatting and no per-row colour overrides.
  • Nothing is uploaded to a server for rendering; the images are produced by your browser.

Test the headers before the data

Upload a two-row file with real headers first. If it validates, the rest of your sheet almost certainly will too.

Open the editor — no sign-up needed

Related guides