Batch Creation runs Image Creation against up to 50 input photos in a single request — same prompt, same settings, applied across the batch. Cost scales with the number of variants per output (1–4). Use it for SKU-velocity catalog work where you have many photos and a single styling intent.
Steps
- Open Batch CreationGo to /app/Creative/batch-creation. — open in Apiway
- Upload up to 50 photosEach file ≤ 60 MB; total request ≤ 200 MB. UI staging budget is 15 MB per browser session.
- Write the prompt and pick variant countSame prompt applies to every input. Pick 1–4 variants per output.
- GenerateApiway processes the batch and saves all results to your gallery. Heavy queue: only one heavy job per server process at a time.
Inputs and limits
- Max files: 50 per batch request.
- Per file: ≤ 60 MB. Total request: ≤ 200 MB.
- Browser staging budget: 15 MB total for batch originals (IndexedDB cap), so very large originals should be downsized client-side first.
- Variants per output: 1–4 (cost multiplies).
Heavy queue behavior
Batch jobs count as heavy. Apiway runs one heavy job at a time per server process to keep latency predictable. If the queue is busy, the request returns 503 with a 30-second retry hint. See Heavy queue busy.
Resuming a batch
Batch progress is tracked server-side. The shared /app/Creative/result page polls the generation session and reconstructs partial output if the browser tab closes mid-batch. Open the gallery to see what was finished; re-run the batch with the remaining inputs if some failed.
Cost
cost per output × variantCount × number of inputs. Reference: 50 inputs × 1 variant × 14 credits (nano-banano-2 at 2K) = 700 credits = $7.