Image variants

A master image is often too big to ship as it is. A 2400×1350 PNG of key art can be 2 MB, while a web build wants a 900-pixel WebP and a store page wants a 256-pixel thumbnail. Image variants are smaller copies that agh makes from an accepted image, keeps beside it, and publishes like any other asset. Image variants come with the Studio and Enterprise plans.

Make variants

Reviewers (admins and developers) find Make variants… in two places:

• On Review, under a delivered image. The copies are made right away so you can compare them, and they are saved when you accept the image. Rejecting the image drops them.
• In the Library, on any accepted or published image. The copies are saved straight away.

Each variant has:

• a name, such as web or thumb: lowercase letters, digits and underscores, up to 32 characters
• a format: WebP, JPEG or PNG
• a longest edge in pixels, from 16 to 8,192. agh never makes a copy bigger than the master.
• a quality from 1 to 100, for WebP and JPEG
• a background colour for JPEG, which has no transparency. It's white unless you choose another.

You can make up to eight variants at once. The dialog remembers the sets of settings you use as presets, and starts with *web* (WebP, 900 px, quality 82) and *thumb* (WebP, 256 px, quality 75). Compare at 100% shows the master and a variant side by side, or with a swipe, so you can check the quality before you save.

What a variant is

Each variant is an asset of its own, accepted as soon as it is made. Nobody claims it and nobody reviews it, because it is a copy of an image someone already accepted.

• Id and path follow the master: art.hero at art/hero.png makes art.hero.web at art/hero.web.webp.
• Tags start as the master's, with variant=<name> added.
• Provenance is the master's: who made it and how.
• Sets: the master and its variants form a set made from the master, with the master first. If the master is already in a set, its variants join that set after it.
• Your plan: variants count toward storage, but not toward your plan's asset limit. The AI disclosure counts the master only.

You can't make variants of a variant, or ask for a new version of one. Remake it from its master instead.

When the master changes

A new version of the master makes its variants out of date. When you accept the new version, the box Remake out-of-date variants when I accept is ticked by default, and agh remakes each variant from the new file with the same settings.

If you untick it, the variants stay as they were and are marked Out of date. An out-of-date variant is held back from publishing. The copy already published, if there is one, stays where it is. Press Remake on the variant, on the master's page in the Library, or on the Publish page to bring it up to date.

Publishing

Variants publish with everything else. On the Publish page they sit under their master. Settings › Publishing has an Image variants row under *Where files go*, so copies can go somewhere other than their masters, such as masters to GitHub and variants to your bucket. Roblox doesn't take image variants.

Coding agents

Agents use the make_variants MCP tool to make variants (variants) or remake them (remake with optional names). review_delivery takes remakeVariants: false to leave variants out of date. Over HTTP, GET and POST /assets/{id}/variants list and make them, and POST /assets/{id}/variants/remake remakes them.

Plans

Making a variant encodes images on agh's servers and stores the copies, so it is part of the Studio and Enterprise plans. On other plans the Variants panel explains what it does and links here. Variants made before a plan changes stay, but a new master leaves them out of date. To upgrade, ask us.

For agents: this page as Markdown is at /docs/image-variants.md, and the CLI prints it with agh guide image-variants.