Practical guide · files stay on your device

Inspect a batch. Clean only the files that are supported.

PixelRinse already accepts mixed-file batches. Each file gets its own capability decision: cleaning supported, inspection only, or unsupported. A batch does not turn an unsupported format into a cleanable one.

Publisher and editorial responsibility: Project Hubbs · Updated 31 October 2026

Inspect your files for free

No account required. Prepare resources explicitly before local processing. Inspection is free; cleaning and cleaned downloads require a license.

Can PixelRinse clean my file?

Look up a format or extension. No file selection, upload or engine download.

Real eligibility requires local inspection of the file and selected operation.

Key takeaways

Inspect first for free. File format and structure—not the extension alone—determine eligible cleaning.
Supported metadata for each eligible image, document or media format.
Up to 100 selected references / 1 GiB retained in this tab; active groups of 20 files / 200 MiB. 25 MiB per file. JPEG Preserve validates encoded structure without requiring pixel decode. JPEG/PNG Fresh and HEIC primary photos are bounded to 50,331,648 pixels (50.3 MP), 8192 pixels per side. HEIC separately allows 64M primary coded-tile pixels and 20M discarded auxiliary coded pixels, at most 256 items, and a conservative 1536 MiB allocation guard. AVIF/TIFF retain their 40 MP subsets. These are refusal bounds, not a guarantee of browser memory safety. Full 48 MP exports have generated-fixture desktop evidence only, with substantial memory use even after cancellation/retry improvements. Physical iPhone memory, Photos/Files delivery and saving remain unverified.

Example

A folder of twelve mixed files may include supported images, an inspection-only format and one oversized file. Each gets its own outcome, so only the eligible ones are cleaned and offered for download.

Try the local workflow

The demonstration uses a fictional PNG to show the local inspect, clean and verify workflow. It is not proof of GPS, JPEG or PDF capabilities; check the file-support page for those formats.

Open the fictional PNG demonstration

Then explicitly prepare and inspect when prompted, review the fictional findings, and choose Clean example free. Opening this link does not prepare resources or process files.

How to do it safely

Select up to 100 file references / 1 GiB in this tab, then explicitly prepare local resources if needed. The first group of at most 20 files / 200 MiB is inspected locally; later groups remain unread until you release the active group.
Review each file’s proposed changes and limitations. Each file is limited to 25 MiB, and only the active group can total up to 200 MiB.
With Individual Pro, explicitly clean eligible files. Review errors and Not checked results instead of assuming every item succeeded.
Download verified eligible outputs individually or review the ZIP inclusion summary before saving a batch archive.

What this workflow removes

Supported metadata for each eligible image, document or media format.
Supported archive metadata only where the archive-specific policy and checks apply.

What it does not promise

Up to 100 selected references / 1 GiB retained in this tab; active groups of 20 files / 200 MiB. 25 MiB per file. JPEG Preserve validates encoded structure without requiring pixel decode. JPEG/PNG Fresh and HEIC primary photos are bounded to 50,331,648 pixels (50.3 MP), 8192 pixels per side. HEIC separately allows 64M primary coded-tile pixels and 20M discarded auxiliary coded pixels, at most 256 items, and a conservative 1536 MiB allocation guard. AVIF/TIFF retain their 40 MP subsets. These are refusal bounds, not a guarantee of browser memory safety. Full 48 MP exports have generated-fixture desktop evidence only, with substantial memory use even after cancellation/retry improvements. Physical iPhone memory, Photos/Files delivery and saving remain unverified.
Inspection-only and rejected files are not silently reported as cleaned. Partial archives can retain unresolved entries and require review.
Archive entry names can still disclose information. Nested archives have additional expansion, entry-count and depth limits.

Retained

Visible/audible content and internal archive entry names.
Unresolved source entries in a partial archive; read its inclusion report.

Not checked

Checks not run for an individual file, even when other batch items passed.
Whether filenames or internal entry names identify a person or client.

Understand the evidence

Use per-file Removed, Retained and Not checked results. ZIP packaging checks are separate from each file’s content-preservation evidence.

Processing, comparisons and verification receipts stay local. PixelRinse sends no product-usage events. Payment and legacy license upgrades are separate online actions that never include selected file contents, names, hashes or metadata.

Check exact format support Understand verification Privacy and limits

Common questions

What are the batch limits?: Up to 100 selected references / 1 GiB in this tab, with one active group of up to 20 files / 200 MiB; 25 MiB per file. Later groups are unread until you save/discard and explicitly release the current group.
If one file fails, are the others affected?: No. Each file has its own result; retry or remove only that item without discarding good cleaned outputs.

Free inspection. One-time cleaning unlock.

Individual Pro is EUR 99 total, one-time, including applicable tax. No product tax is added on top. Lifetime (perpetual) use of the version you buy, plus 12 months of updates; update expiry does not revoke that access.

Merchant processing fees are covered. External network or issuer fees outside PixelRinse may be additional. Load purchase options on the pricing page to see currently configured methods.

Review pricing and payment options

All guides Help Support