Sample the actual background
Pick one or more key samples from the asset instead of relying on a generic "remove background" button. This is especially useful when generated artwork includes antialiasing, compression noise, or colored glow.
Launch workbench
Private asset cutout studio
Clean up AI-generated icons, stickers, logos, UI elements, and web graphics created on solid helper backgrounds. Sample the color, inspect the matte, repair the edge, and export a transparent PNG locally.
Why this exists
Generic background removers are useful for photos, but AI asset work has a different shape. You can ask the generator for a solid green, magenta, cyan, or alpha-helper backdrop, then remove that known color with more control and less guesswork.
Alpha Chroma Studio focuses on that practical path: sample the helper color, inspect the matte, reduce spill, repair edge mistakes, and export a transparent PNG that still looks clean on light, dark, and checkerboard previews.
Pick one or more key samples from the asset instead of relying on a generic "remove background" button. This is especially useful when generated artwork includes antialiasing, compression noise, or colored glow.
Switch between result, original, compare, mask, edge, spill, and sample views so halos and pinholes are visible before the PNG leaves your browser.
Use tolerance, softness, edge cleanup, despill, hole fill, and manual brush corrections to preserve the subject while removing the helper color.
Visual playbook
The tool works best when the asset is generated, inspected, and exported as one deliberate production workflow instead of a one-click cleanup guess.
A clean chroma backdrop gives the sampler a narrow target. Use the color family that sits farthest away from the subject's edges, highlights, and glow.
Mask, edge, spill, and compare views reveal different failures. Fix the real problem instead of flattening every edge with aggressive tolerance.
A transparent asset should hold up on checkerboard, white, dark, and brand-color backgrounds before it goes into a site, app, deck, or marketplace listing.
Before and after
The generated studio visual below shows the pattern this tool is designed for: source assets on controlled helper backgrounds, then matched transparent versions checked against a neutral alpha grid.
Recommended workflow
Ask your image model for a flat chroma background with no shadows, texture, floor plane, or gradient. Strong helper colors make sampling predictable and help protect fine edges.
Green is reliable for many icons. Magenta is useful when the asset contains foliage or teal. Cyan can work well for warm stickers, orange UI elements, and dark logos. Avoid a helper color that appears inside the subject.
Drop the PNG, JPG, or WebP into the workbench, then click the background with the Key tool. Add more key samples for uneven generated backgrounds, and add Protect samples when subject colors are close to the backdrop.
Toggle result, compare, mask, edge, spill, checkerboard, white, black, and custom backgrounds. A transparent PNG that looks fine on one preview can still reveal halos on another.
Tune tolerance first, then softness, despill, and edge cleanup. Use manual erase or restore strokes for small areas rather than pushing global sliders until the whole subject changes.
Helper color guide
Best for neutral UI assets, dark icons, white stickers, and logos without green edge detail.
Useful when the subject includes green, teal, leaves, game slime, or emerald lighting.
Good for warm stickers, orange badges, yellow products, and dark marks with clean outlines.
Only use when the asset has no beige, white, gold, or skin-tone edges that need to stay opaque.
Export checklist
Transparent files fail quietly. The edge can look clean on checkerboard and still show a colored rim on a dark website, or the subject can lose tiny interior details after aggressive tolerance changes.
Local-first trust
When you choose or drop an image into the tool, the file is decoded and processed locally with browser canvas and worker logic. The current public beta does not require sign-in and does not upload source images, masks, samples, or exported PNGs to an Alpha Chroma Studio server.
Future cloud features, such as saved projects or batch queues, should be opt-in and documented before launch. The local workflow remains the default trust promise.
Read the privacy policyReady when you are
Use a PNG, JPG, or WebP generated on a solid helper background. Start with one key sample, then inspect.