Load
Bring in products, photos, prompts or a list from your asset library.
Bulk AI production. One setup, a thousand assets.
Bulk Editing turns AI generation into a table. Put your products, prompts, models and formats in rows, apply one approved setup down the whole column, and run it — images and video together, without queueing anything by hand.
✓Images and video in one run
✓One control setup down every row
✓No cap on batch size
How bulk production works
Rows in. Finished assets out.
The whole idea is that the creative decision happens once. You approve a setup on a single row, then apply it to the rest and let the run do the repetitive part.
A run is a table: one row per asset, one column per variable, one setup applied across all of them.
Set up one row
Pick the model, controls and format, and get that one right.
Apply to the rest
Push the approved setup down the whole column.
Run
Everything generates together instead of one at a time.
Review and export
Check the grid, reroll what missed, export the rest.
One variable at a time
Change any variable. Hold everything else.
Each column in the board is one decision. A run can vary the product and hold the lighting, or vary the market and hold the product — and you always know which control moved, because it is a column rather than a sentence you rewrote.
Columns are variables. Whatever you do not change stays exactly as approved.
People
Swap who appears in the frame while the shot, the light and the product stay exactly where they were.
Products
Run a whole range through one approved setup. The subject changes; the shoot does not.
Markets
One master adapted per region — language, casting and local formats — without rebuilding the campaign.
Colours
Palette and treatment as a column, so a seasonal repaint does not mean a reshoot.
Formats
Every ratio a placement needs, produced from the same row rather than cropped afterwards.
Controls
A saved Control Bar applied down the column — camera, lighting, style and your own custom controls.
Every column is a control. Every row is an asset.
Image, Control Preset, References, Prompt, Model, Ratio, Quality — and alongside them Team Member, Status and Count, so a run is also a record of who produced what.
An interactive table, not a queue
You can see the whole run while it is running.
Most batch tools hand you a progress bar and a folder at the end. Here the run is a grid you work in: results appear per row, and you can fix, reroll or override a single cell without restarting anything.
Row-level controlChange one cell and rerun only that row.
Results in placeOutput lands next to the input that made it.
Nothing to reassembleNo exporting, renaming and matching files back up afterwards.
The same table produces stills and motion. Generate a product range as images, then send the approved frames on as video inputs — inside one run, on the image and video models Mujo connects.
Image modelsGPT Image 2.5, Nano Banana 2 and Pro, Midjourney, Seedream 5.0 and Grok Imagine.
Video modelsVeo 3.0, Kling 3.0, Seedance 2.5 and 2.0, and Grok.
Image to video in the same runAn approved still becomes the starting frame for the clip beside it.
When a campaign needs a range of people rather than one, casting is the slow part. Generate the range as rows — age, look, setting — under identical lighting and framing, then keep the ones that fit as reusable characters.
A casting sheet produced in one run: every face shot at the same distance, in the same light, so a side-by-side choice actually means something.
Generate the range
Age, look, wardrobe and setting as columns, so a casting sheet arrives as one run instead of a week of prompting.
Compare like for like
Identical framing and lighting across every face — the only way a side-by-side choice means anything.
Keep what fits
Save the ones you picked as reusable AI avatars and bring the same person back in later work.
Localization
One campaign. Every market.
A rollout across regions is a batch problem wearing a marketing hat: same idea, different language, different faces, different formats. Put the markets in rows and the campaign adapts once instead of twelve times.
Copy per marketAdapt the wording alongside the visual rather than in a separate document.
Regional castingChange who appears in the frame without changing the campaign.
Local formatsEach market's placements produced from the same approved master.
The most common reason teams end up here: a catalogue that needs visuals, and a list that is too long to shoot. Rows in, on-brand assets out, in the formats the storefront and the ad accounts expect.
A product list becomes a production plan, and the plan produces the assets.
A bulk run does not have to be a single generation step. Build the process in Node Editor — generation, editing, background work, video, export — then point the whole thing at a table of inputs.
The workflow becomes the setup, and the table becomes the input.
The Iterator node is the whole trick.
One node takes a list of files and sends every one of them through the same step. That is what turns a workflow you built once into a run over a hundred inputs.
Connected to the rest of Mujo
Everything it produces lands in one library.
A batch that ends in a zip file creates a second problem. Output stays in the workspace, attached to the project and the settings that made it, and available to every other tool.
Inputs, outputs and the setup between them stay together after the run finishes.
Creative Controls
The saved setup that shaped the run is the same one you reuse next time.
Video Generator
Approved stills become inputs for motion without leaving the workspace.
Content Studio
Cut the output into publish-ready short form.
Node Editor
Wire the run into a longer process when one step stops being enough.
Bulk work is where informal process breaks first. Shared setups, roles and limits keep a large run from becoming someone's private folder. Shared controls are available from the first paid plan.
Shared setupsAn approved configuration everyone runs from, not a screenshot in chat.
Roles and permissionsDecide who can launch a large run and which models they can use.
Usage limitsCaps per person and per team, set before the run rather than discovered after.
Visibility and cost
Know where a run is, and what it costs.
Two things decide whether a team trusts bulk generation: being able to see the run while it happens, and not being surprised by the bill afterwards.
Production visibility
Status per row, owner per row, output per row. A stalled batch is visible as a stalled row, not as silence.
Credits, before and after
Cost is counted in credits and shown against the run, so the size of a batch is a decision rather than a discovery. There is no cap on how many rows you process — how far a run goes is a question of credits.
What people actually run
The jobs that are always a list.
If you have said the words "and the same for the other two hundred", this is the page for that.
Product photography at catalogue scale
One lighting and camera setup held across an entire range.
Marketplace listing images
Every SKU produced to the same spec, in the formats each platform wants.
Ad creative variations
Dozens of cuts of one idea for testing, instead of three and a guess.
Social content calendars
A month of posts that read as one account.
Campaign localization
One master adapted across languages and regions.
Casting and avatars
A range of faces generated and compared under identical conditions.
Video variations
Many clips of one concept for channels, lengths and markets.
Seasonal refreshes
The same catalogue re-shot for a new season without a new shoot.
Frequently asked questions
Bulk generation, answered plainly.
What is bulk AI generation?
Producing many assets from one approved setup instead of one prompt at a time. In Mujo it works as a table: rows are assets, columns are variables, and a saved control setup is applied across the whole run.
How many assets can I process at once?
There is no cap on batch size. How far a run goes is a question of credits rather than a platform limit.
Can I generate video in bulk too?
Yes. The same table handles video, and an approved still from one row can be used as the starting frame for a clip.
Can I fix a single row without rerunning everything?
Yes. Rows are independent — change a cell, rerun that row, leave the rest of the batch alone.
Do my brand settings apply to the whole run?
Yes. A saved Control Bar — camera, lighting, style and your own custom controls — applies down the entire column.
Can a whole workflow run in bulk?
Yes. Build the process in Node Editor and point it at a table of inputs, so every row goes through the same multi-step pipeline.
Do I need a paid plan?
A free account covers image generation with 20 credits. Video generation and shared team setups require a paid plan.
Where do the finished assets go?
Into your workspace asset library, attached to the project and the settings that produced them, and available to Content Studio, Node Editor and the rest of Mujo.
Stop producing one at a time. Build the system instead.
Put the next repetitive job in a table and see how much of it stops being work.
