Setting One Price Across Adobe, Vecteezy And Dreamstime: The Metadata Tradeoffs Nobody Mentions
Description and use
Generating platform‑specific CSVs, maintaining an upload ledger, and consistently applying AI disclosure rules prevent CSV rejections and duplicate posts across Adobe Stock, Vecteezy, and Dreamstime.
Problem
Uploading the same vector files to Adobe Stock, Vecteezy, and Dreamstime with a single CSV fails because each platform requires a different header format and metadata limits, causing rejections and duplicate submissions.
Outcome
The workflow eliminates CSV header rejections, prevents duplicate uploads, ensures consistent AI disclosure, and runs efficiently on minimal hardware.
Workflow
- 1. Store assets in a fixed folder structure (assets/, output/, packs/, research/).
- 2. Run make_metadata.py to read assets and optional titles.json, then generate three CSVs with the exact headers required by Adobe (5 columns), Vecteezy (4 columns), and Dreamstime (15 columns).
- 3. Use upload_tracker.py to record each asset marked as uploaded. Before a new batch, run the pending command to list only assets not yet uploaded.
- 4. Upload each platform’s CSV and assets; the ledger prevents double‑posting.
- 5. Include AI‑disclosure flags per asset in the metadata and track generation cost in the ledger.
- 6. Run the packaging script to zip products and render preview images.
- 7. Monitor peak memory with resource.getrusage and run gc.collect() between assets to stay within 2 GB RAM on a 1 vCPU box.
Evidence
Adobe Stock wants a 5-column CSV. Vecteezy wants 4 columns. Dreamstime wants 15.
If the header row does not match exactly, the upload rejects before a human ever sees your file.
The fix is dumb and effective: a ledger. upload_tracker.py keeps a plain text record of every asset marked done.
- Record date: 2026-10-19T11:56:15.314Z