FAQ
Questions, answered plainly.
Practical details about the browser pipeline, privacy boundaries, output files, and current limitations.
01What is BGRemoved.pro?
BGRemoved.pro is a browser-based tool that estimates an image subject, removes the surrounding background, and exports a transparent PNG.
02How do I remove a background?
Choose a supported image on the homepage, wait for browser processing to finish, review the result, and download the PNG.
03Is bgremoved.pro free?
Yes. The current browser tool can be used without an account or payment.
04Is registration required?
No. The current tool does not require an account or sign-in.
05Which files are supported?
JPG, JPEG, PNG, and WebP images up to 20 MB are accepted. The browser must also be able to decode the file.
06Can I use it for products or portraits?
Yes. Product photos and portraits are common uses, but results still need review around reflective packaging, contact shadows, hair, glasses, and low-contrast edges.
07Can I use the tool on a phone?
The responsive browser interface can be used on a phone with a supported browser. Processing time and memory availability depend on the device, and the downloaded PNG may appear in the browser's Downloads or Files location.
08Are my images uploaded?
No. Image pixels are processed locally in a web worker and are not sent to bgremoved.pro or a third-party image-processing API.
09Does the site make any network requests?
Yes. Like any website, it requests application code, fonts, images, and model files. Those requests do not contain the pixels or filename of the image you selected.
10What is stored in my browser?
The browser may cache site and model resources. Session storage can hold limited editor metadata such as dimensions and the source filename. Temporary image URLs remain in memory and do not survive a page reload.
11What do I download?
A PNG with an alpha channel at the same pixel dimensions as the source image. File size can change because PNG compression differs from JPG, WebP, or the original PNG.
12Why can the first result take longer?
The browser may need to download, verify, and initialize a model before the first inference. Later runs can reuse cached model data and an active worker session.
13What happens without WebGPU?
The production pipeline can switch to a WebAssembly fallback. It runs on more devices but can be slower, and output quality can differ from the primary path.
14Will every cutout be perfect?
No. Contact shadows, reflections, transparent materials, thin details, fine hair, and low-contrast boundaries are common difficult cases.
15Can I change the background color?
The editor can preview transparent, white, black, or custom colors. Those previews do not alter the downloaded transparent PNG.
16Why did the editor lose my image after a reload?
The image itself is kept in a temporary in-memory URL for privacy. Reloading the page removes that URL even though limited editor metadata may remain for the session.
17Do you use analytics, advertising, or tracking cookies?
Not currently. AdSense support is present in the codebase but remains disabled unless a verified publisher configuration and appropriate consent controls are deliberately enabled.
For more detail on the processing flow, read how it works. Practical preparation and review advice is available in the resource library.