Prompt in, alpha out
Every generator hands back artwork welded to its background. cazper hands back the same artwork with a real alpha channel — the soft edges, the glass and the glow still there, instead of the halo a one-click cutout leaves behind.
iOS · Android · Web · CLI
A cutout tool draws a boundary and calls everything inside it solid. cazper keeps the parts that were never solid — antialiased edges, glass, smoke, a glow that falls off — so the sprite drops onto any background, not just the one it was born on.
Generation returns a grid, not a file per icon. cazper splits the sheet for you, so
what lands is asset-001.png, asset-002.png, and a
manifest.json saying where on the sheet each one came from.
The app and the CLI post an image or a prompt and receive a zip. The API does all of the work, so nothing about what you get back changes because you switched device.
Prompt or sheet
Describe what you want and the model draws it for you, or bring a sheet you already have and cazper works from that. Either way the same endpoint answers, and the assets come back as separate files you can drop straight into a project.
The app runs on iOS, Android and the web from one codebase and keeps a library of what it made. The CLI writes to a directory and prints where it put it, which is the version a build script wants.
$ cazper prompt "fantasy inventory icons: potions, scrolls, keys, gems" cazper-out $ find cazper-out -type f | sort cazper-out/assets/asset-001.png cazper-out/assets/asset-002.png cazper-out/assets/asset-003.png cazper-out/assets/asset-004.png cazper-out/manifest.json $ jq '.assets[0] | {name, file, size}' cazper-out/manifest.json { "name": "asset-001", "file": "assets/asset-001.png", "size": [ 384, 384 ] } ▍
Describe it.
Ship the sprite.