Bulk CSV Uploads for Stock Contributors: Column Schemas, UTF-8 Encoding and Fixing Rejected Spreadsheets

How to prevent semicolon delimiter bugs, Excel BOM corruption, unescaped quotation marks, and case-sensitive filename mismatches across six stock agencies.

Technical Guides · · 10 min read · by Salman Ahmad

A single unescaped comma, UTF-8 BOM byte, regional semicolon setting in Excel, or uppercase `.JPG` mismatch can cause a 300-row stock CSV upload to fail silently. Master RFC 4180 CSV formatting and verified per-agency header rules.

When you move from uploading five files a week to managing batches of 100 or 300 assets—especially video clips and multi-agency catalogs—manual browser copy-pasting becomes unsustainable. Bulk CSV import is the universal bridge supported by Adobe Stock, Shutterstock, Freepik, Vecteezy, Dreamstime, and 123RF.

Yet CSV ("Comma-Separated Values") is deceptively fragile. Because spreadsheet apps like Microsoft Excel silently rewrite delimiters, prepend invisible 3-byte UTF-8 Byte Order Marks (`EF BB BF`), and save regional Windows-1252 encodings behind your back, contributors routinely spend hours wondering why a portal says "0 rows matched" or "Invalid header format."

Here is an engineering-level guide to how stock CSV parsers actually read your file—and how to fix every common failure fast.

1. Every Agency Expects Different Exact Header Names, Delimiters, and BOM Rules

One generic spreadsheet cannot be uploaded unchanged across six portals.

Stock portals match CSV columns by exact case-sensitive header spelling, specific column order, byte-order-mark handling, and (in Freepik's case) a semicolon column delimiter:

• Adobe Stock (`,` comma, UTF-8 BOM accepted): `Filename,Title,Keywords,Category,Releases` — Category is a numeric ID (`1` to `21`), Title max 200 chars (no commas), Keywords 5–49.

• Shutterstock (`,` comma, UTF-8 BOM accepted): `Filename,Description,Keywords,Categories,Illustration,"Mature Content",Editorial` — uses `Description` instead of `Title`, requires English category labels (such as `Business/Finance` or `Technology`), and expects title-case `Yes` / `No` flags.

• Freepik (`;` semicolon-delimited columns, UTF-8 BOM accepted): `filename;title;tags` (plus `;Prompt;Model` when declaring AI media) — all three standard column headers are lowercase, titles cap strictly at 100 characters, and tags inside the `tags` field remain comma-separated inside quotes.

• Vecteezy (`,` comma, strictly NO UTF-8 BOM): `Filename,Title,Description,Keywords,License,Id` — `License` must be lowercase (`free`, `pro`, or `editorial`) and trailing `Id` stays blank.

• Dreamstime (`,` comma, strictly NO UTF-8 BOM): 15-column schema where `keywords` is lowercase (`Filename,Image Name,Description,Category 1,Category 2,Category 3,keywords,Free,W-EL,P-EL,SR-EL,SR-Price,Editorial,MR doc Ids,Pr Docs`), Title <=130 chars recommended, 10–80 keywords.

• 123RF (`,` comma, UTF-8 BOM accepted): `oldfilename,123rf_filename,description,keywords,country` — all five headers strictly lowercase; see our Marketplace Metadata Limits reference for full details.

Byte-Verified 6-Marketplace CSV Specification Matrix
MarketplaceDelimiterUTF-8 BOMTitle CapKeyword RangeExact Header Schema
Adobe StockComma (,)Allowed200 chars (no ,)5 – 49Filename,Title,Keywords,Category,Releases
ShutterstockComma (,)Allowed200 chars7 – 50Filename,Description,Keywords,Categories,Illustration,"Mature Content",Editorial
FreepikSemicolon (;)Allowed100 chars5 – 50filename;title;tags
VecteezyComma (,)FORBIDDEN200 chars5 – 50Filename,Title,Description,Keywords,License,Id
DreamstimeComma (,)FORBIDDEN130 chars (warn)10 – 80Filename,Image Name,Description,Category 1..3,keywords,Free,W-EL... (15 cols)
123RFComma (,)Allowed255 chars7 – 50oldfilename,123rf_filename,description,keywords,country

Practitioner Tip: Never hand-rename CSV headers from memory. Convert one spreadsheet into all six verified portal formats automatically in our Multi-Agency Stock CSV Converter or audit rows in the Free Metadata & CSV Checker.

2. The RFC 4180 Quoting Rule: Why Unquoted Commas Shift Every Column

Your keyword list contains 48 commas—without outer double quotes, the parser sees 49 extra columns.

In standard RFC 4180 CSV syntax, any cell value that contains a comma `,`, a semicolon `;`, a newline, or a double quote `"` must be wrapped in outer double quotes `"..."`, and any literal double quote inside the text must be doubled `""`.

If you build a CSV with a naive script or text concatenation without quoting:

• A keyword list `solar, rooftop, energy` splits into three separate columns, pushing your category ID off the end of the row.

• Even when properly quoted, Adobe Stock specifically rejects commas inside Titles, so stripping commas out of the Title string altogether prevents both parser edge cases and moderation rejections.

Valid Adobe Stock vs. Freepik CSV Row Comparison:

# Adobe Stock (comma-delimited, comma-free title, quoted keyword list, numeric Category ID)
Filename,Title,Keywords,Category,Releases
solar-01.jpg,"Commercial solar panel array on warehouse roof at golden hour","solar panel, renewable energy, rooftop solar, clean energy, warehouse",19,

# Freepik (semicolon-delimited columns, lowercase headers, <=100 char title, quoted comma tags)
filename;title;tags
solar-01.jpg;"Commercial solar panel array on warehouse roof at golden hour";"solar panel, renewable energy, rooftop solar, clean energy, warehouse"

Worked example

Weak or risky title: solar-01.jpg,Solar rooftop, golden hour,solar, energy, sun,19,

Clear descriptive title: solar-01.jpg,"Commercial solar panel array at golden hour","solar panel, renewable energy, rooftop",19,

Wrapping text fields in standard RFC 4180 double quotes and keeping Adobe Stock titles comma-free keeps all 5 columns aligned.

3. Why Opening a Valid CSV in Excel Can Break It (BOM, Locale & Encoding)

Invisible EF BB BF bytes, European list-separators, and ANSI saves silently corrupt good files.

Three classic spreadsheet traps ruin valid CSVs when contributors double-click them in Excel to make a quick edit:

1. UTF-8 BOM header corruption on Dreamstime & Vecteezy: Choosing CSV UTF-8 (Comma delimited) in Excel writes three invisible bytes (`0xEF 0xBB 0xBF`) before the `F` in `Filename`. Dreamstime and Vecteezy read column 1 as `\uFEFFFilename` instead of `Filename` and reject the entire upload.

2. Regional list-separator swap: On Windows machines configured with a comma as the decimal separator (`1,50`), Excel saves 'CSV' files using semicolons `;` instead of commas! That works by coincidence for Freepik, and breaks Adobe Stock and Shutterstock completely.

3. ANSI / Windows-1252 encoding: Clicking plain Save As → CSV (Comma delimited) in older Excel builds can write Windows-1252 instead of UTF-8, corrupting non-ASCII characters.

If you need to inspect or tweak a CSV manually, open it in VS Code (check the bottom-right status bar for `UTF-8` vs `UTF-8 with BOM`), LibreOffice Calc, or verify it in our CSV Compliance Checker.

Compliance Note: Open any suspect CSV in a plain-text editor like VS Code before uploading: line 1 immediately reveals whether columns are separated by `,` or `;`, whether BOM is active, and whether keyword lists are quoted.

4. Case-Sensitive Filenames and Wait-For-Ingestion Timing

Why valid CSV rows report '0 files matched' on the contributor portal.

Linux-backed ingestion servers compare filenames byte-for-byte:

• `Cafe_Latte_01.JPG` does not match `Cafe_Latte_01.jpg` or `cafe_latte_01.jpg`.

• Include the file extension (`.jpg`, `.eps`, `.mp4`), and never include folder paths (`C:\Exports\photo.jpg` or `batch1/photo.jpg`)—only the bare filename!

• Wait until thumbnails finish processing: If you upload 100 heavy MP4 or EPS files via FTP/SFTP and upload the CSV immediately while half the batch is still transcoding, only the finished files will match. Wait until every asset appears in your 'Unfinished / To Submit' queue, then import the CSV.

Summary

Bulk CSV failures disappear once you verify five invariants: exact portal-specific headers, correct BOM presence/absence (no BOM for Dreamstime and Vecteezy), RFC 4180 double-quoted cells, clean UTF-8 encoding untouched by regional Excel defaults, and exact case-sensitive bare filenames imported only after media ingestion finishes.

Pre-Submission Review Checklist

  • Use the exact column header schema and delimiter (`,` vs `;` for Freepik) required by the target portal
  • Strip UTF-8 BOM (`EF BB BF`) before uploading CSVs to Dreamstime or Vecteezy
  • Verify every keyword cell and multi-word title is wrapped in RFC 4180 double quotes
  • Keep Adobe Stock titles comma-free and trim Freepik titles cleanly at <=100 characters
  • Confirm CSV `Filename` entries match uploaded file extensions with exact uppercase/lowercase casing
  • Wait for all uploaded videos and vectors to appear in your portal queue before importing the CSV

Official Documentation & Standards Referenced

Related contributor guides

Tags: CSV Upload, Bulk Metadata, UTF-8, Spreadsheet Troubleshooting, Workflow Automation. Written and reviewed by Salman Ahmad — see our editorial standards.

More resources: metadata limits by marketplace, free metadata checker, free browser tool, all guides.