Local first
File bytes, names, metadata, previews, reports, and outputs stay in browser memory. The network is used for application delivery and, when chosen, the separate entitlement flow—not file processing.
About PixelRinse
Know what a cleaner can prove.
PixelRinse is a personal file-privacy utility built to make metadata cleaning understandable: inspect the source locally, explain the supported action, rebuild carefully, and verify the result.
PixelRinse is published by Project Hubbs.
Made in Rotterdam with ❤️
Published by Project Hubbs · Updated
Project Hubbs is responsible for the product information and editorial guides on this site. For product, license or billing support, contact hello@pixelrinse.app.
This is PixelRinse.app, at pixelrinse.app. Similar names on other domains do not establish a relationship. For product, billing or license questions, use our existing contact and support routes. Read the privacy methodology and verification scope before relying on a result.
Purpose
Careful sharing starts before upload
Many files carry descriptive or structural data beyond what is immediately visible. PixelRinse helps you examine that risk before a file reaches a messaging, storage, publishing, or conversion service.
It favors explicit support over broad promises. Recognized files may be cleaning supported, inspection only, or unsupported. If the structure cannot be handled within documented limits, PixelRinse reports or rejects it instead of presenting an unverified cleaned file.
Product principles
Inspect before cleaning
PixelRinse identifies a file from its structure and shows whether cleaning, inspection only, or neither is supported before offering an output.
Verify before download
A cleaning attempt is not enough. Generated files are reopened and checked against format-specific removal and preservation rules before download is enabled.
Honest boundaries
PixelRinse does not claim to redact visible or audible content, remove every possible kind of hidden data, erase external copies or operating-system traces, detect steganography, or provide cryptographic erasure of browser memory. Support and verification are limited to the documented checks for each format.