Your images never leave your device.
Reshrimp is built around local processing, minimal network use, and no image uploads.
How it works technically
When you select an image, it stays entirely in your browser's memory. Reshrimp uses browser APIs to read, manipulate, and re-encode your image inside a single browser tab. No image data is sent to any server during processing.
The processed image is generated as a Blob URL, which exists only in your browser's memory. After the first online visit, the app shell and core tools can also load offline. Background removal downloads its model assets the first time you use it, then can run offline too.
What we don't do
- We don't upload your images anywhere
- We don't use cookies or local storage for tracking
- We don't run analytics scripts (no Google Analytics, no Plausible, nothing)
- We don't require accounts or collect personal information
- We don't upload your image data for processing
- We don't fingerprint your browser or device
Open source verification
Don't take our word for it — read the source code. Reshrimp is fully open source under the MIT license. Every line of code is available for inspection.
The image-processing logic lives in TypeScript services that you can inspect directly. Check the GitHub repository to verify our claims.
Third-party services
Reshrimp is deployed as a static site. The first visit needs a network connection to load the app shell.
After that, the app shell and core tools work offline. Background removal may download model files once before it can work offline. Those requests are for app or model assets, not for uploading your images.