Quick answer
This Quality processing runs locally and does not upload; browser extensions can still read the page. Cropping itself does not blur; enlarging/low-quality JPEG does.
Why it matters
Local processing reduces upload risk but is not absolute security.
Selected pixels keep original detail.
Step by step
- Confirm where and how large the image will be displayed.
- Drag a box at the target ratio; center the subject and leave safe margins.
- Keep selection pixels at or above the display size.
- Export PNG/WebP for text/UI, JPEG 85-90% for photos.
- Keep the original; use the crop only for publishing.
Common mistakes
- Cropping too tight and cutting avatars/products.
- Ignoring safe areas so cover text gets cropped.
- Cropping low-resolution images then enlarging, causing blur.
- Overwriting the original and losing re-crop ability.
Checklist
- Target ratio/size confirmed.
- Subject intact with safe margins.
- Selection pixels >= display size.
- Format/quality meets the platform.
- Original kept.
Key facts
- Selected pixels keep original detail.
- JPEG export adds one compression pass.
FAQ
Does Quality processing upload my files?
This Quality processing runs locally and does not upload; browser extensions can still read the page. Cropping itself does not blur; enlarging/low-quality JPEG does.
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: Web.dev images