Practical guide · files stay on your device
Make a product photo smaller without guessing the result.
Start with the dimensions your shop actually requests. Resize an oversized photo first, then use the compressor when you also need a smaller file. The result is measured, not a promise that every photo reaches a target size.
Publisher and editorial responsibility: Project Hubbs · Updated
Start the guided webshop taskOpen the image compressorInspect your files for freeNo account required. Prepare resources explicitly before local processing. Inspection is free; cleaning and cleaned downloads require a license.
Supported input
- Supported still JPEG and PNG images; WebP only where the browser verifies its encoder.
- HEIC/HEIF requires the separate supported decode/conversion path and explicit effects review. Keep the original.
Key takeaways
- Inspect first for free. File format and structure—not the extension alone—determine eligible cleaning.
- A checked local image export with the selected dimensions and encoding settings.
- 25 MiB per input and the tool’s displayed dimension/device limits apply; 32 MiB input is not enabled.
How to do it safely
- Keep the original product photo. Check the required pixel dimensions and maximum file size in your shop’s own upload guidance.
- Open Resize image if dimensions need changing. Choose files, review the local inspection, and keep proportions locked unless a deliberate frame is required.
- Open the compressor for a byte-size target. Choose a supported JPEG/WebP output and review the quality floor and optional size reduction.
- Read conversion effects before accepting them. JPEG removes transparency; lossy encoding can change fine text, texture and color. HDR conversion produces SDR, not an equivalent HDR original.
- Use the tool’s explicit processing action with your existing license. Review actual output dimensions, byte size and any target-not-met explanation.
- Download the checked result and view it at the size your shop displays. This does not test or upload to the shop.
What this workflow produces
- A checked local image export with the selected dimensions and encoding settings.
- A measured size result; a requested target is not a guarantee.
What it does not promise
- 25 MiB per input and the tool’s displayed dimension/device limits apply; 32 MiB input is not enabled.
- PNG is lossless by default. Optional 32-level/channel RGB reduction is lossy, limited to 8 MP and leaves alpha unquantized. Output can grow.
- No AVIF or HEIC output, animated-image compression or guaranteed target size.
Retained
- The original photo and earlier completed versions remain separate.
- Visible product details remain identifying content; this is not an anonymity tool.
Not checked
- Acceptance, appearance or conversion by a particular webshop.
- Whether altered color or fine detail meets your product-photography requirements.
Understand the evidence
Compare the reported final bytes and dimensions, then inspect the saved photo. A metadata check and an encoding/quality check are different claims.
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.
Common questions
More answers
Can I compress, resize and convert an image locally?
Yes. Quality, crop, rotation, dimensions and format are combined in one local export; the original stays unchanged.
Technical details and limits
JPEG/WebP offer lossy quality settings and bounded target-size search. PNG defaults to lossless; optional RGB color reduction (32 levels/channel, up to 8 MP) deliberately changes colors without quantizing alpha. Compare actual bytes: output can grow. Crop and enlargement are off by default. Animation is refused; secondary JPEG photos need explicit primary-only consent. HEIC remains conditional on validated decoding and HDR/color/auxiliary effects, with PNG/JPEG output only. Processing and exports of your files still require the existing Individual Pro license; free inspection and fixed synthetic demos remain.
What is the difference between preserving and re-encoding?
Preserve keeps the original image data and removes only supported metadata; Fresh Export re-encodes the image.
Technical details and limits
Re-encoding can change bytes and quality, so it is an explicit opt-in. PixelRinse never switches to it automatically.
What size and count limits apply?
Keep up to 100 selected file references / 1 GiB in this tab. Only one group of up to 20 files / 200 MiB is active at a time.
Technical details and limits
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. Later groups remain unread until you explicitly acknowledge saving or discarding current results and release the group. No file bytes persist or continue processing after closing the tab. Splitting a selection does not override per-file limits.
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