Igikoresho cy'Ubuhanga cyo Kongeraho Inyuma

Hitamo mu mibara ikomeye, gradienti, ibishusho, imitako no gushyiramo yihariye.

Yego! Shyiramo ishusho iyo ari yo yose kugira ngo uyikoreshe nk'inyuma yihariye.

AI yacu yemeza guhuzanya kw'imipaka kuzuye ku bisubizo bisa bisanzwe.

Yes, and that's actually the highest-value workflow for brand teams running headshot grids, About-page galleries, or product-launch ad sets. The custom-upload slot caches the backdrop you uploaded for the duration of the editor session, so you can drop subject one, composite against the brand backdrop, export, then drop subject two and composite against the same backdrop without re-uploading. For longer-term reuse across sessions, the brand-kit feature in the editor (saved templates) persists the backdrop in your browser's IndexedDB so it's available next time without a re-upload — useful for an agency processing 30 team headshots over a week, or a brand running a quarterly product-launch shoot. The backdrop never transits the network: it sits in your browser tab and gets composited client-side. For brand-kit deliverables specifically — handing the cutout back to a client agency or web developer — the better workflow is often to export the cutout as a transparent PNG via `/transparent-background/` and let the downstream tool handle the backdrop, since the destination context (web hero, print spec, video frame) often dictates a backdrop choice that's outside this tool's preview.

Three different intents, three different slug pages. `Add a background` (this page) replaces the original backdrop with a new one — flat colour, gradient, scene, or your own upload. The original backdrop is discarded entirely; only the subject cutout carries forward into the composite. `Blur the background` (`/blur-background/`) keeps the original backdrop visible but softens it with a Gaussian or radial blur — useful for portrait photography where the environment provides context (`subject is at a coffee shop` or `subject is outdoors`) but you want the subject to read clearly without competing detail. The original backdrop colour temperature, lighting, and rough composition all carry forward; only the focus is changed. `Remove the background` (`/transparent-background/`) discards the backdrop entirely and ships the cutout against transparency — the asset is then composited onto whatever backdrop the downstream context (Figma frame, Webflow CMS hero, brand-kit deliverable) decides. The decision tree: if you want a different scene, use this page; if you want the same scene but softer, use `/blur-background/`; if you want no scene at all so the destination tool decides, use `/transparent-background/`. The white-only case (`/white-background/`) is a fourth specialised slug for the marketplace-mandated pure-white backdrop; the colour-only case (`/change-background-color/`) is a fifth for when you already know the exact hex you want. All five run on the same segmentation pipeline.