Quick answer
Handling Private images needs a supported browser/app, enough disk/memory and a valid input file. Do not upload IDs/contracts/client images to unknown online tools; local compression is safer.
Why it matters
Missing any condition can turn an environment issue into a false file-corruption diagnosis.
Local browser processing still needs protection from malicious extensions.
Step by step
- Back up the original; never overwrite the only copy.
- Confirm the target platform's format, dimensions and size limit.
- Cap the longest side first, then quality; change one variable at a time.
- Compare size and sharpness after compressing, and step back one setting if needed.
- Keep the original until the output is confirmed.
Common mistakes
- Chasing the smallest file and blurring text/edges.
- Converting transparent PNG to JPEG, turning transparency white or black.
- Recompressing the same file and accumulating loss.
- Overwriting the original, so a bad result cannot be undone.
Checklist
- Original backed up.
- Output format/dimensions/size meet the platform.
- Text is readable and transparency is correct.
- Verified in the real page/email/upload field.
- Original kept until confirmed.
Key facts
- Local browser processing still needs protection from malicious extensions.
- Crop unrelated personal information before sharing.
FAQ
What do I need to handle Private images?
Handling Private images needs a supported browser/app, enough disk/memory and a valid input file. Do not upload IDs/contracts/client images to unknown online tools; local compression is safer.
How long does it take?
Usually 1-3 minutes; for intermittent issues, run 30 seconds and retest elsewhere.
Is data uploaded?
Runs locally and does not upload video/audio; extensions may still read the page.
Source: FTC privacy