The browser checks the source.
FlytheBG validates the selected file and confirms that the browser can decode it. PNG, JPEG, and WebP can go straight through; other raster formats can be normalized locally when the browser supports them.
Use portrait, landscape, square, vertical, or panoramic raster images without forcing a preset crop. FlytheBG preserves the source aspect ratio, uses the smaller IMG.LY quantized model, and tries WebGPU first where supported.
Most browser-decodable raster image formats up to 12 MB.
Background removal is foreground segmentation, not a simple color delete. The model estimates an alpha mask describing how visible each foreground pixel should remain, and FlytheBG returns the resulting transparent PNG without changing the source aspect ratio.
FlytheBG validates the selected file and confirms that the browser can decode it. PNG, JPEG, and WebP can go straight through; other raster formats can be normalized locally when the browser supports them.
The current implementation uses IMG.LY’s quantized IS-Net model. Compatible secure browsers try WebGPU first for acceleration. If that backend cannot initialize or finish, FlytheBG retries the same small model using CPU/WASM.
FlytheBG checks that the generated result contains meaningful foreground and transparency, then uses the model cutout directly. The old full-resolution edge-expansion pass is no longer part of the live workflow.
The model can only work with detail that exists in the source image. A few photography choices make difficult boundaries easier to identify.
Motion blur and missed focus blend foreground and background pixels together. If possible, use a photo where hair, shoulders, product edges, and clothing seams remain visibly defined.
A subject wearing dark clothing against an equally dark background is harder to separate than the same subject against a visibly different background. You do not need a studio backdrop, but clear visual separation helps.
Heavily compressed screenshots and repeatedly shared images can contain block artifacts around edges. Starting from the original camera image or a higher-quality copy gives the model more information to work with.
Veils, glass, smoke, reflections, flyaway hair, fur, lace, and motion blur are naturally ambiguous. Zoom in after removal and check those areas before using the result in a final design or document.
Source photos and generated cutouts stay in browser memory while you work. Model/runtime assets can still be downloaded by the browser from their configured provider, but FlytheBG does not intentionally attach your source image to those asset requests.
No automatic remover can guarantee a perfect result for every image. Difficult foregrounds can be clipped, background fragments can remain, and fine translucent details can be simplified. Check important results at full size before publishing or printing them.
Use the Passport Photo Maker to frame the result, set real-world dimensions, choose a photo background, and build a white print sheet. Document authorities can have additional rules beyond image size.
Open Passport Photo Maker ↗These answers describe the current FlytheBG workflow rather than promising results the model cannot guarantee.
Yes. FlytheBG preserves the source aspect ratio instead of forcing the image into a square. Extremely large files are still limited by browser memory and the configured upload-size guard.
Clear photos with a visible subject boundary usually produce the most reliable result. Strong lighting, useful resolution, and some contrast between the foreground and background help the model separate fine details.
Those areas contain partially transparent or ambiguous pixels. A segmentation model must estimate which pixels belong to the foreground, so very fine strands, reflections, transparent objects, smoke, and heavy blur can need manual checking.
The current production remover runs IMG.LY in the browser. The page does not intentionally send source or generated image bytes to a FlytheBG inference server or image database.
The browser may need to download the smaller quantized model and runtime assets before processing the first image. Compatible browsers try WebGPU first, and CPU/WASM is the automatic fallback.
The background-removal workflow exports a PNG so the removed background can remain transparent. Applications that do not display transparency may show the transparent area as white, black, or a checkerboard preview.