DesignerBox Batch runs one workflow, app or image model over many rows. Each row is one product, and each row makes its own pictures or videos. You pick what to run, add your rows, read the cost of the whole sheet and press Run. Then you judge each result and keep the good ones. One sheet holds up to 200 rows. You find Batch in the app under Automation, then Batch.
Batch is the fourth way to run a workflow in DesignerBox, after a template, your own workflow and an app. It is one part of the app we rebuilt, and the new DesignerBox explains the other parts. This guide covers what a batch can run, how you add rows, how review works, and where the limits are.
Key Takeaways
- A batch runs one workflow, app or image model over a sheet of rows. One sheet holds up to 200 rows.
- You add rows in four ways: one at a time, import a list of instructions, one row per uploaded picture, or “Add in bulk” for every combination.
- You keep or discard each result with the J and K keys.
- Every row reads the same brand rules, so row one and row two hundred have the same look.
- Batch does not send results to a store. You download them, or send them with a webhook or an S3 step.
What a batch is
The Batch page in the app describes it in two sentences: “A batch runs one workflow, app or image model over many rows. Each row makes its own pictures or videos.”
A batch is a table. Each row is one run of the same job, with that row’s product and its own settings. The Batch page on the site says each row holds its own photo and its own line of text. Every result lands in the last column of its row.
A batch is different from a prompt list. A prompt list sends many text prompts to one model. A batch can send many products through one saved job, with your brand attached. Our guide to the bulk image generator compares the two approaches in detail.
Three things a batch can run
The first card on the Batch page is titled “Pick what to run”. It names three choices: an image model, an app, or your own workflow published as an app. The Batch page has one tab for each: Workflows, Apps and Image model. Its first line reads: “Pick a workflow, an app or an image model. Every row runs it with its own words and pictures.”
| What you run | What it is | Pick it when |
|---|---|---|
| A workflow you published | Your own set of steps, built once with your brand and your rules | The job has several steps, and you have already checked the result on one product |
| One of the apps | A workflow with a form, built by DesignerBox or by your team | An app already does the job, and you do not need to change its steps |
| An image model on its own | One model, with no saved steps around it | Each row needs one picture from one line of text, and no step before or after |
The Workflows tab shows which workflows are ready. A published workflow says “Runs the published form, once per row”. An unpublished one says “Not published as an app yet”.
The Image model tab describes itself this way: “Just an image model. No workflow behind it. Write one instruction on every row, pick the model, and run them all.”
You build a workflow on the workflows page. Our guide to DesignerBox apps covers what an app is and how a colleague runs one.
The site gives one piece of advice. Run the job once on one product and check the result. Then fill the sheet.
Four ways to add rows
The second card reads: “Add your rows. Type them, paste a list, or drop a folder of photos. Each photo becomes a row.” The app gives four ways to add rows.
- One at a time. Press “Add row”.
- Import a list of instructions. One instruction becomes one row.
- One row per uploaded picture. Each picture you upload becomes a row.
- Add in bulk. You write several values, and every combination becomes a row.
The site describes one product per row: the photo, the name and the colors. One sheet holds up to 200 rows, and a counter on the sheet shows how many you have used. A catalog with more products than that needs more than one sheet.
The sheet for an image model has five columns. Two of them are required. Each row can have its own model, size and aspect ratio.
| Column | Required | What goes in it |
|---|---|---|
| Instructions | Yes | One instruction for the row |
| Pictures | Optional | The row’s own pictures |
| Model | Yes | The image model the row runs |
| Size | Optional | For example Default, 1K or 2K |
| Aspect ratio | Optional | For example auto, 1:1 or 4:5 |
“Add row” adds one row. Three more controls sit under the columns: “Import instructions”, “Upload pictures” and “Set all”. “Upload pictures” makes one row per picture.
The “Add in bulk” box builds many rows at once. You write one value per line in its boxes: Instructions, Model, Size and Aspect ratio. The box states its rule: “Every combination of what you write becomes its own row: three instructions against two models is six rows.”
So “Add in bulk” lets you try the same instructions on two models. Check the row count before you run, because the number of rows grows quickly. The image model test method uses this grid on three hard products. Pictures are not part of this box. You add them with the upload control under the Pictures column.
The free plan runs on sample products, so a free batch shows you how the sheet works.
A batch run, step by step
- Pick what to run. Choose a workflow you published, one of the apps, or an image model on its own.
- Add your rows. Type them, paste a list, or drop a folder of photos. Each photo becomes a row.
- Check the rows and read the cost. The footer of the sheet says: “Every row needs instructions and a model.” Set “Runs per row”, from 1 to 4. The sheet line shows the rows that are ready, the credits for the run, and the credits you have left after it. Over 20 runs, DesignerBox asks you to confirm first.
- Run them all. Press “Run batch”. Each row shows its state: draft, queued, generating, done or failed.
- Judge each picture. Press J to keep a result and K to discard it. Re-run a row that failed or looks wrong.
- Deliver. Every kept result goes to Assets, beside its source photo. Download it from there, or send it with a webhook or an S3 step.
The batch menu has three choices for a finished sheet: “Download the kept pictures”, “Send the kept pictures for review” and “Download the sheet as CSV”. Assets is also an item in the app’s sidebar.
Review of each row
The third card on the Batch page reads: “Keep the best pictures. Run them all, then judge each picture. Keep the good ones.”
Making the pictures is the short part. Finding the few wrong ones takes longer. Our guide to bulk product images covers where a catalog run breaks at this stage.
The sheet handles review in three ways, as the site describes them:
- Each row shows its state. A failed row is easy to find, because its state says so.
- You keep or discard each result as it lands. Use the J and K keys. You decide every result yourself. Nothing is approved for you.
- You re-run one row on its own. The rest of the sheet does not move.
An agency often needs a second review, by the client. Reviews sends your client a page of pictures. The client opens the link with no account, chooses the pictures they want and sends the choice back to you. In a batch, the menu choice “Send the kept pictures for review” starts this step. Our guide to DesignerBox Reviews covers that step.
Brand rules across rows
Anyone can make an AI picture. Making hundreds that still look like your brand is the hard part.
A batch answers that with one rule: every row runs the same steps and reads the same brand. You set the brand once. It holds your products, your logo, colors and fonts, your voice and rules, and your reference pictures. The Brand page in the app says: “Workflows read the rules before every prompt.”
Row one and row two hundred have the same look, because nothing between them changed except the product.
An agency keeps one brand record per client. You pick the brand for a run, so a sheet for one client reads that client’s brand. Our guide to the Brand page covers what a brand holds and how a run uses it.
Cost before the run
The cost is shown before the run. For a batch, that number covers the whole sheet, and the sheet line also shows what is left after the run. Nothing is spent until you start the run.
This matters most to an agency or a reseller. You can price the job for your client first, then start the run.
Batch runs on every plan, and so do templates, apps and brand rules. Uploading your own photos and the commercial license start on the Pro plan. AI video, virtual try-on and upscaling start on the Premium plan. Plans and credits are on the pricing page.
A worked example with 40 products
This example is illustrative. A homeware brand adds 40 new products this month. Each product needs four shots: a hero, two angles and a lifestyle scene.
| Part of the job | Count |
|---|---|
| Products in the drop | 40 |
| Rows in the sheet | 40 |
| Pictures per row | 4 |
| Pictures to review | 160 |
| Sheets needed | 1 |
The brand lead builds a workflow that makes the four shots, and checks it on one product. Then she drops a folder of 40 source photos onto the sheet. Each photo becomes a row. She presses Run.
Review is 160 pictures in one pass. Say six rows have a wrong picture. She re-runs those six rows only. The other 34 rows do not move. The kept pictures go to Assets, and she downloads them for the store.
A catalog of 500 products follows the same pattern across three sheets: two of 200 rows and one of 100.
Who batch is for
Batch fits a team that repeats one job across many products.
- A brand with 20 to 500 products. Each drop needs the same set of shots. The ecommerce brands page covers this buyer.
- An agency with several clients. One brand record per client and one sheet per drop.
- A reseller who sells finished sets. The next customer’s set uses the same workflow.
Four guides show a batch on a real job: white background photos for a supplier delivery, seasonal versions of your hero pictures, listing pictures for the whole catalog and one client’s workflow over 30 products.
DesignerBox holds the whole job, from the first product photo to the finished ad. Batch is the part of it that handles volume.
Limits of batch
These are the limits as of October 2026.
- One sheet holds up to 200 rows. A larger catalog needs more than one sheet.
- Batch does not publish to a store. You download the results, or send them with a webhook or an S3 step. Nothing lands in a listing on its own.
- Every plan below Ultra is one seat. Team features, shared brand kits and white label are on the Ultra plan.
Start with one workflow and a short sheet, then add rows once the first results look right. Get started free.
FAQ
How many rows can one DesignerBox batch hold?
Up to 200, one product per row. Every row runs the same steps with the same brand rules. A catalog with more than 200 products needs more than one sheet.
What happens when one row goes wrong?
You re-run that row on its own, and the rest of the sheet does not move. Each row shows its state, so a failed row is easy to find. You keep or discard every result yourself.
Does a batch show its cost first?
Yes. The cost of the whole sheet shows in credits before you press Run, and nothing is spent until you start. An agency can use that number to quote a client.
Which plan includes batch?
Batch is on every plan. Uploading your own photos starts on the Pro plan, and the free plan runs on sample products. AI video starts on the Premium plan, so a batch that makes videos needs that plan.
Where do batch results go?
Every kept result goes to Assets, beside its source photo. From there you download it, or send it with a webhook or an S3 step. DesignerBox does not publish to a store.
Sources
- DesignerBox Batch page (designerbox.ai/product/batch), October 2026: the 200-row sheet, row states, keep, discard and re-run, Assets, the cost of the sheet, plan gates
- The DesignerBox app, read October 2026: the Batch, Brand and Reviews pages, the sheet columns, “Add in bulk” and the batch menu
- DesignerBox pricing page (designerbox.ai/pricing), October 2026: plans and plan gates
- DesignerBox app, read 22 October 2026: the four ways to add rows, the sheet line, runs per row, the J and K keys and the batch menu
Batch facts checked against designerbox.ai and the DesignerBox app in October 2026. The cost of a sheet depends on what each row runs. Plans and limits change, so read the cost shown before you run a large sheet. Individual results vary.