Placeholder Art for Game Prototypes at $0.004 an Image

Prototype art has one job: stop being a blocker. You need two hundred item icons so the inventory screen reads as an inventory screen, and you need them today, and you will throw all of them away when art direction lands. Grey boxes work until the moment you show the build to anyone.alibaba/z-image-turbo-t2i fits this slot because of what it costs and what it exposes, not because the output is good enough to ship.

Key Takeaways

• Two hundred throwaway icons cost about $0.80 at the measured $0.004 per image.
• The prompt string is the asset source. Commit it next to the sprite.
• Record the seed in your asset manifest and a full regeneration becomes a script.
• No transparency field exists, so prompt a flat background and key it out in your pipeline.

Treat the Prompt as Source, Not as a Chat Message

The mistake that makes generated placeholder art expensive is generating it by hand, in a browser, and saving the PNGs. Six weeks later the palette changes and you have two hundred orphan files and no way to make new ones match.

The fix is to stop thinking of the prompt as something you typed and start treating it as a build input that lives in the repo:

{  
"id": "item_healing_draught",  
"prompt": "small glass vial of red liquid, game item icon, flat lighting, plain flat mid-grey background",  
"seed": 84021,  
"size": "1024x1024"
}

That record is the asset. The PNG is a build artifact. When the art director says the palette is going colder, you edit one shared style clause in your generator, re-run the manifest, and two hundred icons come back consistent, because every entry still carries its own seed.

The Seed Is the Difference Between a Script and a Weekend

The request body is four fields: model, prompt, seed, size. Only the first, second, and fourth are required. seed is optional, which makes it easy to skip, and skipping it is the expensive choice.

Without a recorded seed, regenerating an asset is a new roll. With one, the same prompt plus the same seed reproduces the same icon, so a regeneration pass changes only what you intended to change. That is the whole difference between "re-run the generator" and "spend Saturday matching two hundred icons by eye."

Sizes, and the Transparency Problem

size is required and takes exactly three values: 1024x1024, 768x1024, and 1024x768. For prototype work that maps to icons and tiles, portrait cards, and banners or backdrops respectively. All three are about one megapixel, which is well past what a 128px inventory slot needs.

There is no alpha or transparency field in the spec. Every result is an opaque raster. The practical workaround is to say so in the prompt, plain flat mid-grey background or solid white background, and key the background out in your own asset pipeline. Keep that background clause in the shared style string so all two hundred icons key out with the same threshold.

What Two Hundred Icons Actually Cost

The measured console price is $0.004 per image, currently 20% off a struck-through $0.005 list. That discount is a promotion, so check the Pricing block on the model detail page before budgeting a large run.

Two hundred icons is about $0.80. Three full regeneration passes across the project's life is about $2.40. At that level the cost stops being a line item and the only real constraint is how fast you can iterate on the style clause.

If your prototype already has a ComfyUI graph and you would rather keep it than write a new generator, the siray-comfyui node bridges a local ComfyUI install to Siray's 300+ models, so you keep the graph and skip the VRAM and the weight downloads. Search siray-comfyui in ComfyUI Manager, or read the node's setup notes.

Developer Notes

Related reading: what Z-Image Turbo is and where it sits, how per-image and per-second rates compare across the catalog, and the same per-image economics pushed to bulk throughput in Z-Image at scale.

Wire it into your build today: create an account and open the model page.