Topic
Background Removal Without Cloud Image Processing
Cloudless here means your image is not the input payload to a vendor’s remote segmentation API for the primary editor flow.
Definition
Without cloud processing, the mask is computed on-device in the browser tab. Third-party CDNs may still deliver static files for the app itself.
Threat modeling
Removing the upload step closes a major data-flow path, but you should still review analytics, ads, and crash reporting if your policy requires it.
Tradeoffs
You trade vendor-side scaling for device variability—test on representative hardware.
FAQ
Is every byte local?
No—HTTPS delivery and normal web plumbing still exist. The distinction is image inference location.
Enterprise on-prem?
This is a public web app, not self-hosted enterprise software; adjust expectations accordingly.
Related topics
Why local processing matters
nobg.eu runs background removal in your browser session. The goal is simple: fewer unnecessary image transfers and faster starts than upload-first pipelines—without promising impossible quality on every edge case.
No upload image editing
Core cutout processing is designed as local image processing: you open a file, the model runs client-side, you export. You still load the website and assets over HTTPS like any site.
Browser AI explained
Browser AI here means inference executes in web runtime (WebGPU when available, with fallbacks). It is not a generic “cloud brain”—it is on-device execution after the app loads.