Pixelry

Image tools, instantly — compress, resize, convert

12 essential image tools. Everything runs in your browser — no data leaves your device.

12 Free Tools No Signup Required 100% Private

All Tools

Why Pixelry?

Instant Processing

All image processing happens in your browser using Canvas API. No uploads, no waiting, no server round-trips.

100% Private

Your images never leave your device. No accounts, no tracking, no data collection. Process sensitive images with confidence.

Works Everywhere

Responsive design that works on desktop, tablet, and phone. Use any tool, any time, on any device.

PNG vs JPEG vs WebP: The Complete Image Format Comparison

Choosing the right image format is one of the most impactful web performance decisions you can make. The wrong choice means either bloated file sizes that slow your page load, or visible quality degradation that undermines your design. Here's how the three dominant web formats differ:

JPEG (.jpg/.jpeg) — Lossy compression optimized for photographs. JPEG analyzes image blocks and discards subtle color variations the human eye struggles to distinguish. A photographic JPEG at quality 80 is visually indistinguishable from the original to most people, at roughly 10-20% of the original file size. Fatal weakness: JPEG does not support transparency (alpha channel), and re-saving a JPEG degrades it further — it's a destructive format. Never edit and re-save the same JPEG file multiple times.

PNG (.png) — Lossless compression designed for graphics with flat colors, sharp edges, text, and transparency. PNG uses DEFLATE compression (same as ZIP) — it reduces file size without discarding any data. For photographs, PNG produces files 3-10× larger than JPEG with no visual benefit. For logos, icons, screenshots with text, and any image requiring transparency, PNG is the correct choice.

WebP (.webp) — Google's 2010 format that supports both lossy and lossless compression plus transparency. Lossy WebP is typically 25-34% smaller than JPEG at equivalent quality. Lossless WebP is 26% smaller than PNG. WebP is supported by all modern browsers (Chrome, Firefox, Safari 14+, Edge). For new web projects started after 2021, WebP is the recommended default for both photos and graphics.

Our Image Format Converter converts between PNG, JPEG, WebP, and other formats instantly in your browser. Our Image Compressor reduces file sizes while letting you compare before/after quality.

Image Compression Explained: Lossy vs. Lossless

Compression algorithms fall into two categories. Lossless compression reorganizes data to take less space without discarding any information — like finding a shorter way to describe the same thing. PNG's DEFLATE compression identifies repeating patterns in the image data and encodes them as references. A solid blue rectangle compresses enormously because it's just "this color, 10,000 times." A photograph compresses poorly because each pixel is unique.

Lossy compression discards information the algorithm predicts you won't notice. JPEG uses the Discrete Cosine Transform (DCT) — it represents each 8×8 pixel block as combinations of wave patterns, then discards the high-frequency components (fine details) that human vision is least sensitive to. At quality 80+, these discarded details are genuinely imperceptible. Below quality 60, you start to see "JPEG artifacts" — blocky patches around high-contrast edges.

The right choice depends on your use case: choose lossless (PNG/lossless WebP) when images must survive multiple editing passes or when pixel-perfect accuracy matters (medical imaging, document scans). Choose lossy (JPEG/lossy WebP) for photographs intended for display, where a 90% size reduction with imperceptible quality loss is the right tradeoff.

Image Dimensions, DPI, and Resolution: What Actually Matters

A common confusion: DPI (dots per inch) is a print concept, not a screen concept. On a screen, only pixel dimensions matter — 1920×1080 pixels is 1920×1080 pixels regardless of whether the image is tagged as 72 DPI or 300 DPI. The DPI metadata only matters when a printer needs to know how large to print the image. A 2400×3000 pixel image at 300 DPI prints at 8×10 inches. The same image at 72 DPI prints at approximately 33×41 inches.

For web use: images should match their display dimensions. Serving a 4000×3000 pixel image that displays at 400×300 pixels wastes 100× the bandwidth for zero visual benefit. Modern responsive design uses <picture> and srcset attributes to serve appropriately sized images to each device. Our Image Resizer lets you set exact pixel dimensions or scale by percentage.

For Retina/HiDPI displays: these screens have 2× or 3× pixel density. A 200×200 CSS pixel image on a Retina display actually renders 400×400 physical pixels. To look sharp, the image source needs to be 400×400 pixels — served at CSS size 200×200. This is why many web images are served at 2× resolution.