Image Tool
Compress, resize, convert — all in your browser. Images never leave your device.
PNG · JPG · WebP · GIF (first frame) · AVIF/BMP — max 50 MB. Or paste (Ctrl+V).
Compress, resize, convert — all in your browser. Images never leave your device.
PNG · JPG · WebP · GIF (first frame) · AVIF/BMP — max 50 MB. Or paste (Ctrl+V).
Image Tool shrinks image file sizes, resizes pictures and converts between PNG, JPG and WebP. Everything happens in your browser, so your photos never leave your device. It's ideal for preparing images for a website, an email, social media, or forms with strict file size limits.
Beyond compressing and resizing, the Edit panel lets you rotate the picture, crop it to a standard ratio (1:1, 4:3, 16:9, 9:16) and stamp a text watermark. Every result is rebuilt on a canvas, which also means all EXIF metadata is permanently removed — a genuine privacy win.
Lossy formats (JPG, WebP) reduce quality slightly, but you choose the level that works for you.
WebP usually gives the smallest file at good quality. PNG suits graphics and transparency, and JPG suits photos.
No. Processing is local, so your photos stay private.
Results are rebuilt on a canvas, so EXIF fields (GPS, camera model, timestamp) are fully stripped in every download — originals on your disk keep their data.
Type your text under Edit and choose a position; the stamp renders on the live preview and is saved into every exported format.
Yes — load a square-friendly image and hit Download favicon ZIP: you get 16/32/48 px icons, an apple-touch 180 and Android Chrome 192/512, plus a mini README.
Why the right choice depends on the picture's content, not on the file's current extension. · 6 min read
JPEG and WebP (in lossy mode) ask 'how much of this detail can we drop before anyone notices?' — they are designed for photographs, where tiny chroma errors are invisible. PNG and lossless WebP ask 'how do we store every pixel exactly?' — they are designed for screenshots, diagrams, logos with hard edges, and anything with text, where a single wrong pixel is visible.
This is why converting a screenshot to JPEG usually looks bad at small sizes: JPEG's 8×8 block transform smears sharp edges into faint ringing. And it's why converting a photo to PNG bloats it 5–10×: every subtle noise grain in the photo is now stored faithfully and compresses poorly.
The pragmatic rule: photographs → JPEG or WebP (quality 75–85 is the sweet spot; below 70 you usually see blocking, above 90 you pay bytes for detail nobody can see). Screenshots, logos, diagrams → PNG. If everything is WebP-capable (browsers and most apps are now), lossy WebP generally beats JPEG by 20–30% at equal quality.
The biggest wins come from resizing, not from squeezing the encoder. An image displayed at 800 px wide does not need the 4000 px original — every extra pixel is stored, transmitted, decoded and then thrown away. Serving a 4000 px image into an 800 px box costs roughly (4000/800)² ≈ 25× the bytes of the right-sized image at the same quality.
For responsive pages the common approach is two or three widths (for example 480, 960 and 1600) and letting the browser pick; modern formats add srcset and density descriptors on top. Even a single, correctly sized export is usually a 3–5× saving with zero visible difference.
Camera and phone files carry EXIF blocks: timestamps, camera model, exposure settings, and — importantly — GPS coordinates of where the photo was taken. Social networks strip these on upload; direct file sharing does not. Sending a photo as-is to a group chat or an email therefore leaks location history.
This tool rebuilds every result on a canvas: the output is encoded from pixels alone, so the EXIF block is simply not carried over. The original file on your disk is untouched — the privacy win applies to what you download and share. The only trade-off is that colour profile hints (like a wide-gamut ICC profile) are dropped too, which matters only for specialist printing workflows.
A favicon set is not one file but a small family: 16×16 for browser tabs, 32×32 for shortcuts, 48×48 for Windows desktops, a 180×180 'apple-touch' image for iOS home screens, and 192/512 for Android and PWA installs. Sourcing all of those from one high-resolution square image is exactly why the favicon ZIP export exists — every size is downscaled from the same source so the set stays visually consistent.
One tip: design the master image with a solid background and generous margins. Favicons are usually seen at 16–32 CSS pixels, where fine detail turns to mush; simple, high-contrast shapes survive the shrink.