Select multiple files at once, then let PixelRinse inspect, clean, and verify each eligible result locally so you can see what is safe to download—and what is not.
Built for careful sharing
What PixelRinse does
Focused tools, one private workflow
Open the searchable tools directory for image crop, rotate, resize, compression and conversion; visible-watermark review and local LaMa retouching; BiRefNet-lite background cutouts; local text watermarks; field-level XMP/PDF property editing; PDF asset inventory and bounded exports; comparisons; and tested media/document subsets. Each workspace states its scope before processing. These tools share the existing Individual Pro entitlement.
Prepare smaller, appropriately sized images
Resize is a standalone operation. Crop, rotate, flip, generic ratio presets and quality/format settings combine in one encode, then clean and verify supported metadata in the final bytes. Measured results show growth as honestly as savings. Originals stay unchanged; default cleaning remains conservative.
Inspect before cleaning
Every accepted file is identified from its structure, then labeled as cleaning supported, inspection only, or unsupported before an output is offered.
Process on this device
File bytes, names, metadata, previews, and cleaned outputs remain in browser memory instead of being sent to a conversion server.
Verify every output
Cleaned files are reopened and checked against format-specific metadata and preservation rules before they become downloadable.
Show what changed
Inspection findings, proposed changes, removed data categories, retained structures, and review warnings stay visible in the queue.
Clean multiple files at once
Select or drag in up to 100 files / 1 GiB as unread references in one action. Active groups are limited to 20 files, 25 MiB each and 200 MiB total. Review and save each group, then release it before inspecting the next. Only eligible files can be cleaned.
Preserve or re-export
Lossless JPEG Container Clean and structural Preserve Quality keep encoded image data unchanged where supported. Fresh Export decodes and re-encodes the image: it can retain visual content, but does not promise pixel-identical data.
Keep working offline
After explicitly preparing this build’s application resources while online, supported inspection and cleaning can run offline. Neural editing additionally needs its selected pinned model and local runtime prepared; models are not downloaded on the homepage. Payment and legacy license upgrades require a connection; current signed recovery files restore offline.
Unlock once
Inspection is free. €99 total, tax included: one user, purchased major version, 12 months of updates, no subscription, credits or usage caps.
Comparison
How it compares
Upload-based tools
These services can be convenient and may support different files, but remote processing requires sending the file to another system. PixelRinse keeps file bytes on this device, identifies structure before cleaning, displays proposed changes, and checks eligible outputs before download.
Desktop and mobile apps
Local apps can offer comparable privacy, larger-file handling, or formats PixelRinse does not support. PixelRinse’s browser workflow adds a mixed-file queue, visible inspection states, conservative fail-closed decisions, and optional browser-app installation; the exact inspection and verification available in other apps varies.
DIY scripts
A well-chosen script can run locally and provide comparable privacy or broader format support. PixelRinse packages signature-based routing, visible proposed changes, mixed-file handling, and format-aware verification into a browser interface; with scripts, you select, configure, update, and validate that toolchain yourself.
Inspect, then decide
The detected structure—not just the extension or browser MIME label—controls whether a file is cleanable, inspection-only, or unsupported.
Reject uncertainty
Malformed, ambiguous, active, encrypted, or unsupported structures fail closed instead of receiving a cleaned label.
Check what the output proves
Verification is format-aware: it may reparse metadata, compare encoded streams, or validate archive policy rather than relying on a successful save.
PixelRinse does not cover every format. Cleaning is not content redaction, secure deletion, steganography detection, or removal of copies and traces outside the cleaned container.
One app, two ways to use it
Install PixelRinse for offline use
Use it in a browser, or add it to your home screen or desktop. This installs the same browser-based app, not a separate Windows or Mac program.
On desktop or Android
Open PixelRinse in a supported browser. Choose Install app here when available, or use your browser’s Install / Add to home screen option. Some browsers only offer a shortcut.
On iPhone or iPad
Open PixelRinse in Safari. Tap Share, then Add to Home Screen. If the option is hidden, scroll the Share menu or use your browser’s home-screen instructions.
You can use PixelRinse in your browser; install availability depends on your browser and device.
Not ready for local processing. Checking local cache readiness…
While connected, explicitly prepare the local resources. Preparation downloads this build’s app code, styles, fonts, and other generated dependencies; it does not cache selected files or outputs.
Install it using the browser prompt or browser menu if desired. Installation and first preparation need internet access.
Use the readiness result above—not the connection icon—to confirm the active service worker has every resource for this exact build.
Connection indicator: the browser reports online (this is not a zero-request test). Local file operations run without an application network fallback once the current resource cache is ready; missing cached resources fail rather than being fetched silently. Browser storage can be cleared. Explicit updates, purchase, payment checks and legacy license upgrades are separate online actions; importing a current signed recovery file works offline. Selected files and cleaned outputs are never written to the service-worker cache.
Features describe the workflow. The file-support page gives the exact cleaning, inspection, limits, and verification contract for every recognized format.