DEV Community: Pixotter

Can You Actually Fix a Blurry Photo?

Pixotter — Tue, 07 Apr 2026 16:13:25 +0000

How to Sharpen an Image Online (5 Free Methods)

Blurry photos happen. Soft focus, camera shake, motion blur, low light — they all produce images that look slightly off. Sharpening can recover the crispness your photo should have had, and you do not need Photoshop to do it.

Here are five free methods to sharpen an image, ranging from browser-based editors to command-line precision. Each method uses the same underlying technique, so the concepts transfer across tools. If you want the opposite effect — adding blur for backgrounds, privacy, or creative purposes — see How to Blur an Image instead.

How Image Sharpening Works

Sharpening does not add detail that was never captured. It increases contrast along edges — the boundaries between light and dark areas — making existing detail look more defined.

The most common algorithm is Unsharp Mask (USM), which works in three steps:

Create a blurred copy of the image.
Subtract the blur from the original to isolate edge detail.
Add that edge detail back at a controlled intensity.

Three parameters control the result:

Parameter	What It Does	Too Low	Too High
Amount / Strength	How much edge contrast to add	No visible effect	Halos around edges
Radius	How wide the edge detection zone is	Only sharpens fine texture	Thick, glowing edges
Threshold	How different pixels must be before sharpening applies	Sharpens noise too	Skips subtle edges

Other algorithms exist — High Pass filtering, Richardson-Lucy Deconvolution — but USM is the default in nearly every tool and produces good results for most images.

The hard limit: Sharpening enhances edges, not actual detail. A photo that is severely out of focus or motion-blurred beyond recovery will just look over-processed with halos and artifacts. Mild softness responds well; heavy blur does not.

Method 1: GIMP (Free, Desktop)

GIMP 2.10.36 (GPLv3, free and open source) includes multiple sharpening filters.

Steps

Open your image in GIMP.
Go to Filters → Enhance → Unsharp Mask.
Adjust the three parameters:
- Amount: 50–80% (start at 60% for general photos)
- Radius: 1–3 px (1 for web images, 2–3 for print)
- Threshold: 0–5 (0 sharpens everything, 3–5 protects smooth skin tones)
Toggle the Preview checkbox to see the effect before applying.
Click OK, then File → Export As to save.

When to Use GIMP

GIMP gives you the most control. You can sharpen selectively by painting a layer mask — sharpen the subject while leaving the background soft. For batch work, GIMP supports Script-Fu and Python-Fu plugins, though the command-line tools below are faster for bulk processing.

Method 2: Photopea (Free, Browser)

Photopea is a Photoshop-compatible editor that runs entirely in your browser. No install, no account, works on any OS.

Steps

Open photopea.com and drag your image onto the canvas.
Go to Filter → Sharpen → Unsharp Mask.
Set the parameters (same range as GIMP — Amount 50–80%, Radius 1–3 px, Threshold 0–5).
Click OK.
File → Export As → JPG / PNG to download.

Photopea also offers Smart Sharpen (Filter → Sharpen → Smart Sharpen), which adds a Remove dropdown for targeting specific blur types: Gaussian Blur, Lens Blur, or Motion Blur. If your image has directional motion blur, Smart Sharpen with the Motion Blur option and an angle setting can partially correct it.

Free with ads, no signup required. Photopea supports PSD, XCF, GIMP, Sketch, and RAW formats.

Method 3: ImageMagick (Command Line)

ImageMagick 7.1.1-29+ (Apache 2.0 license) is the standard command-line image processing toolkit.

Unsharp Mask Syntax

# ImageMagick 7.1.1-29+ (Apache 2.0)
# Format: -unsharp radiusxsigma+amount+threshold
# sigma controls the Gaussian blur; amount is the strength multiplier

# Standard sharpening — good for most photos
magick input.jpg -unsharp 0x1+1.0+0.05 sharpened.jpg

# Stronger sharpening — for very soft or slightly out-of-focus images
magick input.jpg -unsharp 0x2+1.5+0.02 sharpened.jpg

# Light sharpening — for images that just need a subtle boost
magick input.jpg -unsharp 0x0.5+0.5+0.05 sharpened.jpg

Batch Sharpening

# Sharpen every JPG in the current directory (overwrites originals)
magick mogrify -unsharp 0x1+1.0+0.05 *.jpg

# Sharpen and save to a separate folder (non-destructive)
mkdir -p sharpened
for f in *.jpg; do
    magick "$f" -unsharp 0x1+1.0+0.05 "sharpened/$f"
done

ImageMagick is ideal when you have dozens or hundreds of images to process. Combine it with -resize to sharpen at the final output size in a single pass.

Method 4: Python with Pillow

Pillow 10.2.0 (HPND license, free) provides ImageFilter.UnsharpMask for programmatic sharpening.

from PIL import Image, ImageFilter  # Pillow 10.2.0 (HPND license)

img = Image.open("input.jpg")

# UnsharpMask(radius, percent, threshold)
# radius: size of the blur kernel (pixels)
# percent: strength of the sharpening effect
# threshold: minimum brightness difference to sharpen
sharpened = img.filter(ImageFilter.UnsharpMask(
    radius=2,
    percent=150,
    threshold=3
))

sharpened.save("sharpened.jpg", quality=90)

Batch Processing With Pillow

from pathlib import Path
from PIL import Image, ImageFilter  # Pillow 10.2.0

source = Path("photos")
output = Path("sharpened")
output.mkdir(exist_ok=True)

for img_path in source.glob("*.jpg"):
    img = Image.open(img_path)
    sharp = img.filter(ImageFilter.UnsharpMask(radius=2, percent=150, threshold=3))
    sharp.save(output / img_path.name, quality=90)
    print(f"Sharpened: {img_path.name}")

Python is the right choice when sharpening is one step in a larger processing pipeline — you can combine it with resizing, watermarking, format conversion, and metadata stripping in a single script.

Method 5: macOS Photos

If you are on a Mac, the built-in Photos app has a sharpness slider.

Steps

Open the image in Photos.
Click Edit (top right).
Click Adjust.
Scroll to Sharpness and drag the slider right.
Click Done to save.

The slider offers no control over radius or threshold — it is a single-parameter adjustment. For casual sharpening of phone photos, this is fast and sufficient. For precise control, use GIMP, Photopea, or the command-line tools above.

Preview (macOS) has no sharpening capability — it supports crop, rotate, and basic annotations but not image enhancement.

After Sharpening: Optimize for the Web

Sharpened images tend to be larger than their soft originals. Increasing edge contrast creates more high-frequency detail, which compressors have to work harder to encode. A photo that was 180 KB before sharpening might weigh 220 KB after.

That extra weight matters if the image is destined for a website, email, or social media post. Three steps to keep file size under control:

Compress — Run the sharpened image through Pixotter's compression tool to reduce file size without undoing the sharpening work. Lossy compression at quality 80–85 preserves sharpened edges while cutting bytes.
Convert to WebP — WebP delivers 25–35% smaller files than JPEG at equivalent visual quality. If your sharpened photo is a JPEG, converting to WebP is free file size savings.
Resize to final dimensions — Sharpening a 4000×3000 photo and then displaying it at 800×600 wastes bandwidth. Resize first, then sharpen at the output size (see tips below).

Pixotter processes everything in your browser — no upload, no server round-trip. Drop the sharpened image, pick your operations, and download the optimized result.

Sharpening Tips

Sharpen at final output size. Resize your image to its display dimensions first, then sharpen. Sharpening a 4000 px image and then downscaling it to 800 px discards most of the sharpening work and can introduce moiré patterns.

Sharpen luminance, not color. Sharpening the color channels directly can create color fringing — bright colored halos along edges. In GIMP: convert to LAB mode (Image → Mode → LAB), sharpen only the Lightness channel, then convert back. In Photopea: use the same LAB technique, or apply the filter to a desaturated copy on a Luminosity blend mode layer.

Less is more. Subtle sharpening looks professional. Over-sharpening screams "processed." If you can see halos or a gritty texture, dial the Amount back. When in doubt, reduce the Amount by 20% from where you think it looks good.

Match settings to subject matter:

Subject	Amount	Radius	Threshold	Why
Portraits	Low (30–50%)	1–2 px	3–5	Protects skin texture from looking harsh
Landscapes	High (80–120%)	1–2 px	0–2	Fine detail in foliage, rocks, and water benefits from aggressive sharpening
Text / screenshots	High (100–150%)	0.5–1 px	0	Crisp edges on letterforms, small radius keeps text clean
Product photos	Medium (50–80%)	1–2 px	1–3	Balanced — sharp enough to show texture, not so much that it looks artificial

Preview at 100% zoom. Sharpening artifacts are invisible at zoomed-out views. Always check the image at actual pixel size before saving.

Comparison: Which Method Should You Use?

Method	Cost	Platform	Batch Support	Control Level	Best For
GIMP 2.10.36	Free (GPLv3)	Windows, macOS, Linux	Script-Fu / Python-Fu	Full (Amount, Radius, Threshold + selective masking)	Precise control, selective sharpening
Photopea	Free (ads)	Browser (any OS)	No	Full (USM + Smart Sharpen)	Quick edits, no install needed
ImageMagick 7.1.1-29+	Free (Apache 2.0)	Windows, macOS, Linux	Yes (shell loops, mogrify)	Full (command-line parameters)	Batch processing, scripted pipelines
Pillow 10.2.0	Free (HPND)	Any (Python)	Yes (programmatic)	Moderate (radius, percent, threshold)	Integration into Python workflows
macOS Photos	Free (bundled)	macOS only	No	Low (single slider)	Quick fix for casual photos

For one image: Photopea is the fastest path — open a browser tab, drag, sharpen, export.

For many images: ImageMagick or Pillow. Both support batch processing and integrate into automated workflows.

For maximum control: GIMP, with its layer masks and LAB mode sharpening, gives you the most precise results.

Frequently Asked Questions

Can sharpening fix a completely blurry photo?

No. Sharpening enhances edge contrast that already exists in the image. If the camera was significantly out of focus or there was heavy motion blur, the edge information is lost at capture time. Sharpening a severely blurry photo just amplifies noise and creates artifacts. Mild softness responds well to sharpening; heavy blur does not.

What is the difference between sharpening and upscaling?

Sharpening increases edge contrast at the image's existing resolution. Upscaling (super-resolution) uses AI models to generate new pixels and increase the image dimensions — tools like Real-ESRGAN or Topaz Gigapixel. If your image is both blurry and low-resolution, upscaling may produce better results than sharpening alone, but the output is an AI approximation, not recovered data.

Should I sharpen before or after resizing?

After. Resizing changes the pixel dimensions, which changes the edge structure. Sharpening before a resize is wasted work — the downscale operation will soften the image again. Resize to your final output dimensions first, then apply sharpening tuned for that size.

Does sharpening increase file size?

Yes, typically by 10–30%. Sharpening adds high-frequency detail (edge contrast), which is harder for compression algorithms to encode. The stronger the sharpening, the larger the file. To offset this, compress the sharpened image or convert to WebP before publishing. For more strategies, see the guide to reducing image size.

What format should I save a sharpened image in?

For photos: JPEG (quality 80–90) or WebP (quality 75–85). Both handle the gradients in photographs well. For screenshots, text-heavy images, or anything with sharp edges and flat colors: PNG preserves exact detail without compression artifacts. For the best combination of quality and file size on the web, WebP is the strongest choice.

Need to Mirror an Image? Here's the Fastest Free Way

Pixotter — Mon, 06 Apr 2026 22:16:16 +0000

How to Flip an Image (Mirror, Horizontal & Vertical)

Flipping an image creates a mirror reflection — horizontally (left-right) or vertically (top-bottom). It's one of the simplest image operations, but the terminology trips people up. Here's how to flip images on any platform, plus when and why you'd want to.

Flip vs Rotate: What's the Difference?

These terms get confused constantly, so let's clear it up:

Operation	What Happens	Example Use Case
Flip Horizontal	Left and right sides swap (mirror image)	Fix a mirrored selfie, reverse text direction
Flip Vertical	Top and bottom swap (upside-down mirror)	Create reflection effects, fix inverted scans
Rotate 90°	Image turns 90 degrees (no mirroring)	Fix a photo taken in wrong orientation
Rotate 180°	Image turns upside-down (no mirroring)	Fix an upside-down scan

Key distinction: Flipping creates a mirror image. Rotating spins the image. A horizontally flipped photo has text reading backwards. A rotated photo has text still reading forwards (just at an angle). If you need rotation instead, see How to Rotate an Image.

Flip an Image in Your Browser (Free, No Upload)

Pixotter's Rotate tool handles flipping and rotation in one interface. Everything processes in your browser — no files are uploaded to any server.

Open Pixotter's Rotate tool.
Drop your image onto the page (or click to browse).
Click the Flip Horizontal or Flip Vertical button.
Download the result.

Batch processing is supported — drop multiple images and flip them all at once. The tool preserves your original image format and quality. Need to compress the result afterward? Do it in the same session — no re-upload needed.

Common Reasons to Flip an Image

Fix Mirrored Selfies

Front-facing phone cameras show a mirrored preview (so it feels like looking in a mirror), but many phones save the photo un-mirrored. This creates confusion: text on your shirt reads correctly in the preview but appears normal in the saved photo — or vice versa.

If your selfie looks "wrong" compared to what you saw on screen, flip it horizontally to match the mirror view.

Create Reflection Effects

Flipping a landscape photo vertically and placing the flipped copy below the original creates a water reflection effect. This is a common design technique for hero images, product photography, and social media graphics.

Fix Design Composition

Sometimes a photo would work better if the subject faced the other direction — facing into the layout instead of away from it. Horizontal flip solves this instantly, as long as there's no readable text in the image (flipped text is immediately noticeable).

Correct Scanned Documents

Flatbed scanners sometimes produce vertically flipped output if the document is placed face-up instead of face-down (or the scanner driver has a bug). A vertical flip corrects the orientation.

Print Transfer Designs

Iron-on transfers, screen printing, and some engraving workflows require a horizontally flipped image so it reads correctly when transferred to the final surface.

How to Flip an Image on Windows

Method 1: Pixotter (Browser)

Open pixotter.com/rotate/ in any browser. Drop the image, click flip, download. Works on Windows 10, 11, and any version with a modern browser.

Method 2: Windows Photos App

Open the image in Photos.
Click Edit image (pencil icon) or press Ctrl+E.
Click Crop & rotate.
Click the Flip icon (horizontal mirror symbol).
Save.

Windows Photos only supports horizontal flip. For vertical flip, rotate 180° then flip horizontally (equivalent result).

Method 3: Paint

Open the image in Paint.
Click Rotate in the toolbar.
Select Flip horizontal or Flip vertical.
File → Save.

Method 4: PowerShell + ImageMagick

# Requires ImageMagick 7.1.1-29+
# Horizontal flip (mirror)
magick input.jpg -flop output.jpg

# Vertical flip
magick input.jpg -flip output.jpg

# Batch flip all JPGs horizontally
Get-ChildItem -Filter *.jpg | ForEach-Object {
    magick $_.FullName -flop "flipped_$($_.Name)"
}

Note: In ImageMagick, -flop is horizontal flip and -flip is vertical flip.

How to Flip an Image on Mac

Method 1: Pixotter (Browser)

Open pixotter.com/rotate/ in Safari, Chrome, or Firefox.

Method 2: Preview

Open the image in Preview.
Tools → Flip Horizontal or Flip Vertical.
File → Save (Cmd+S).

Preview supports both flip directions and preserves metadata.

Method 3: Terminal (sips)

# Horizontal flip
sips -f horizontal input.jpg --out flipped.jpg

# Vertical flip
sips -f vertical input.jpg --out flipped.jpg

# Batch flip all JPGs horizontally
for f in *.jpg; do
    sips -f horizontal "$f" --out "flipped_$f"
done

sips is built into macOS. No installation needed.

How to Flip an Image on Linux

Method 1: Pixotter (Browser)

Open pixotter.com/rotate/ in Firefox or Chrome.

Method 2: ImageMagick

# Install
sudo apt install imagemagick

# Horizontal flip
magick input.jpg -flop output.jpg

# Vertical flip
magick input.jpg -flip output.jpg

# Batch flip
magick mogrify -flop *.jpg

Method 3: GIMP (GUI)

Open the image in GIMP (version 2.10.36, GPLv3 license).
Image → Transform → Flip Horizontally or Flip Vertically.
File → Export As to save.

GIMP also has a dedicated Flip tool (Shift+F) that can flip individual layers instead of the entire image — useful for compositing.

How to Flip an Image on Mobile

iPhone / iPad

Open the photo in the Photos app.
Tap Edit (top right).
Tap the Crop icon (bottom toolbar).
Tap the Flip icon (top left — two triangles with arrows).
Tap Done.

iOS only offers horizontal flip. For vertical flip, rotate 180° first, then flip horizontally.

Android

Open the photo in Google Photos.
Tap Edit → Crop.
Tap the Flip icon (mirror symbol).
Tap Save copy.

Alternatively, open pixotter.com/rotate/ in your mobile browser for both horizontal and vertical flip.

Flip vs Mirror: Are They the Same?

Yes. "Flip horizontal" and "mirror" describe the same operation — swapping left and right sides of the image. Different software uses different terminology:

Software	Horizontal Flip Term	Vertical Flip Term
Pixotter	Flip Horizontal	Flip Vertical
Photoshop	Flip Canvas Horizontal	Flip Canvas Vertical
GIMP	Flip Horizontally	Flip Vertically
Preview (macOS)	Flip Horizontal	Flip Vertical
ImageMagick	`-flop`	`-flip`
CSS	`transform: scaleX(-1)`	`transform: scaleY(-1)`

They all do the same thing — the naming is just inconsistent across tools.

Flipping Images in Code

CSS (Display Only, No File Modification)

/* Horizontal flip */
.flipped-h { transform: scaleX(-1); }

/* Vertical flip */
.flipped-v { transform: scaleY(-1); }

/* Both */
.flipped-both { transform: scale(-1, -1); }

CSS transforms flip the visual rendering without modifying the image file. The original image data is unchanged — the flip happens at display time.

Python (Pillow)

# pip install Pillow==10.2.0
from PIL import Image

img = Image.open('input.jpg')

# Horizontal flip
img.transpose(Image.FLIP_LEFT_RIGHT).save('flipped_h.jpg')

# Vertical flip
img.transpose(Image.FLIP_TOP_BOTTOM).save('flipped_v.jpg')

HTML Canvas (JavaScript)

const canvas = document.createElement('canvas');
const ctx = canvas.getContext('2d');
const img = new Image();
img.onload = () => {
    canvas.width = img.width;
    canvas.height = img.height;
    // Horizontal flip
    ctx.scale(-1, 1);
    ctx.drawImage(img, -img.width, 0);
};
img.src = 'input.jpg';

Frequently Asked Questions

Does flipping an image reduce quality?

No. Flipping rearranges pixel positions without recompressing the image data. For lossless formats (PNG, BMP, TIFF), it's a zero-quality-loss operation. For lossy formats (JPG), some tools re-encode after flipping, which introduces a tiny generation loss. Tools that support lossless JPEG transforms (like jpegtran) can flip JPGs without any re-encoding.

How do I flip just part of an image?

You need a layer-based editor. In GIMP (2.10.36): select the area with the Rectangle or Free Select tool, then use the Flip tool (Shift+F) to flip only the selection. In Photoshop: select the area, copy to a new layer (Ctrl+J), then Edit → Transform → Flip. Pixotter's Rotate tool flips the entire image.

Can I flip a video the same way?

Flipping video uses the same concept but different tools. FFmpeg handles it on the command line: ffmpeg -i input.mp4 -vf hflip output.mp4 (horizontal) or -vf vflip (vertical). Most video editors (DaVinci Resolve, Premiere Pro, iMovie) have flip/mirror options in their transform controls.

Why do selfies look weird when flipped?

Human faces are asymmetric. You're used to seeing your face mirrored (from mirrors and phone previews), so an un-mirrored photo looks subtly "off" to you — even though it's how everyone else sees you. Flipping the selfie to match your mirror view makes it look "right" to you but technically less accurate to others.

How do I flip an image for iron-on transfer?

Flip the image horizontally before printing. When you iron the transfer onto fabric, the heat transfer reverses the image again, so text and graphics end up reading correctly on the final surface. Most print dialog boxes have a "Mirror" or "Flip horizontal" checkbox specifically for this purpose.

Does flipping change the EXIF orientation tag?

It depends on the tool. Some editors modify the actual pixel data (physical flip). Others update only the EXIF orientation flag (metadata flip). For reliable results, especially when sharing images across different viewers, use a tool that modifies the pixel data. Pixotter modifies the actual image data, ensuring the flip is visible in every viewer regardless of EXIF support. If you want to strip EXIF data entirely after flipping, see How to Remove EXIF Data.

Why Do Your Photos Keep Appearing Sideways?

Pixotter — Mon, 06 Apr 2026 04:21:05 +0000

How to Rotate an Image Online (Free)

You took a photo sideways. You received a screenshot that's rotated 90 degrees. Or you need to fix an image's orientation before dropping it into a slide deck. Whatever the reason, rotating an image should take seconds — not a software install.

Here's how to rotate images on every platform, starting with the fastest method.

Rotate an Image Online with Pixotter

Pixotter's Rotate tool processes everything in your browser using WebAssembly. Your images never leave your device — no upload, no server, no waiting.

Steps:

Open pixotter.com/rotate.
Drop your image onto the page (or click to browse files).
Select your rotation angle: 90°, 180°, 270° (same as -90°), or enter a custom angle.
Preview the result.
Click Download.

That's it. The rotation happens locally on your machine. Your files stay private, and processing is near-instant even for large images.

Batch rotation: Need to rotate 50 photos from the same event? Drop them all at once. Pixotter applies the same rotation to every image and lets you download them individually or as a batch. More on batch processing below.

After rotating, you can compress the result for sharing — or reduce the file size for email or web — no need to open a second tool.

How to Rotate an Image on Windows

Windows Photos App

Open the image in Photos (double-click any image file).
Click Edit image (pencil icon) or press Ctrl+E.
Click Crop & Rotate.
Click the Rotate button to rotate 90° clockwise. Click again for 180°, again for 270°.
Click Save or Save a copy.

Photos handles quick 90° increments well. For arbitrary angles (like 15° or 45°), you'll need a different tool — Photos only does 90° steps.

Paint

Open in Paint.
Click Rotate in the toolbar.
Select Rotate right 90°, Rotate left 90°, or Rotate 180°.
File → Save.

Paint also only supports 90° increments. For arbitrary rotation, use Pixotter's Rotate tool or a full image editor.

How to Rotate an Image on Mac

Preview

Open the image in Preview.
Go to Tools → Rotate Left (Cmd+L) or Tools → Rotate Right (Cmd+R).
File → Save (Cmd+S).

Each click rotates 90°. Press the shortcut multiple times to reach 180° or 270°.

Photos App

Open the image in Photos.
Click Edit (top right).
Click Crop in the toolbar.
Click the Rotate button (top left) to rotate 90° counterclockwise.
Click Done.

Both Preview and Photos are limited to 90° steps. For precise angles, use pixotter.com/rotate in Safari or any browser.

How to Rotate an Image on iPhone and Android

iPhone / iPad

Open the photo in the Photos app.
Tap Edit (top right).
Tap the Crop icon (bottom toolbar).
Tap the Rotate button (square with arrow, top left) for 90° counterclockwise increments.
For fine-tuning, drag the angle dial below the image to rotate by specific degrees.
Tap Done.

iOS supports both 90° steps and arbitrary angles via the angle dial.

Android (Google Photos)

Open the photo in Google Photos.
Tap Edit → Crop.
Tap the Rotate icon (circular arrow) for 90° counterclockwise increments.
Use the angle dial to rotate by custom degrees.
Tap Save copy.

Both platforms also work with Pixotter's Rotate tool in the mobile browser — useful when you want batch rotation or don't want to modify the original in your camera roll.

How to Rotate Multiple Images at Once

Pixotter (Browser, Any Platform)

Drop all your images onto Pixotter's Rotate tool at once. Select the rotation angle, and Pixotter applies it to every image in the batch. Download individually or grab them all. No upload, no file size cap, no account needed.

This is the same pattern as batch resizing images — drop everything, configure once, download all.

ImageMagick (CLI, Apache 2.0)

For developers who prefer the command line, ImageMagick 7.1.x handles batch rotation with a single command:

# Rotate all JPGs 90° clockwise
magick mogrify -rotate 90 *.jpg

# Rotate all PNGs 180°
magick mogrify -rotate 180 *.png

# Rotate a single file to a new output
magick input.jpg -rotate 90 output.jpg

mogrify edits files in place (overwrites the original). Use magick convert (or simply magick input output) if you want to keep the original.

Custom angles: magick input.jpg -rotate 45 output.jpg rotates 45° and fills the new corners with the background color (white by default). Add -background transparent for PNG files to keep the corners transparent.

# 45° rotation with transparent corners (PNG)
magick input.png -background transparent -rotate 45 output.png

Comparison Table

Method	Platform	Batch Support	Arbitrary Angles	Privacy	Cost
Pixotter	Any (browser)	Yes	Yes	Client-side, no upload	Free
Windows Photos	Windows	No	No (90° only)	Local	Free
Preview (macOS)	macOS	No	No (90° only)	Local	Free
iOS Photos	iPhone/iPad	No	Yes	Local	Free
Google Photos	Android	No	Yes	Cloud-synced	Free
ImageMagick 7.1.x	Any (CLI)	Yes	Yes	Local	Free (Apache 2.0)

Rotate vs Flip: What's the Difference?

These two operations get mixed up, but they do fundamentally different things:

Rotate spins the image around its center point. A 90° rotation turns a landscape photo into portrait orientation. Text stays readable (just at an angle).
Flip mirrors the image along an axis. A horizontal flip swaps left and right — text reads backwards.

If your photo is sideways, you want rotate. If your selfie looks weird because the camera mirrored it, you want flip.

Pixotter handles both: /rotate/ for rotation, and the same tool supports flipping. For a full walkthrough on flipping, see How to Flip an Image (Mirror, Horizontal & Vertical).

Common Rotation Problems and Fixes

"My Photo Looks Rotated in Some Apps but Not Others"

This is almost always an EXIF orientation tag issue. Modern cameras and phones store the image data in one orientation and write a metadata tag that says "display this rotated 90°." Some apps respect that tag. Others ignore it.

The result: the same photo appears correctly oriented in Photos but sideways in a browser, email client, or an older image viewer.

The fix: Re-save the image with the rotation baked into the pixel data (not just the metadata tag). When you rotate an image with Pixotter's Rotate tool, the rotation is applied to the actual image data — no EXIF tag ambiguity.

Alternatively, strip the EXIF data entirely after correcting the orientation. See How to Remove EXIF Data from Photos for step-by-step instructions.

"My Photo Rotated Itself After Uploading"

Some platforms and CMS tools auto-rotate images based on the EXIF orientation tag — sometimes incorrectly. WordPress, for example, auto-rotates uploads based on EXIF data. If the tag is wrong (or the original rotation was already baked in), the platform "corrects" an already-correct image and makes it sideways.

The fix: Strip the EXIF orientation tag before uploading, or rotate + re-save so the pixel data matches the intended orientation. Pixotter does both — the saved file has the correct pixel orientation and clean metadata.

"Rotating Added White Bars or Changed My Image Size"

This happens with non-90° rotations. Rotating an image 45° means the corners of the rectangular image extend beyond the original bounding box. Tools handle this differently:

Expand canvas: The output image is larger, with empty corners filled in (white or transparent). This is what ImageMagick does by default.
Crop to fit: The output is cropped to the largest rectangle that fits inside the rotated image, losing some content near the edges.

If you're rotating by 90°, 180°, or 270°, this issue doesn't apply — the image dimensions simply swap (or stay the same for 180°).

Frequently Asked Questions

Does rotating an image reduce quality?

For 90°, 180°, and 270° rotations — no. These are exact pixel rearrangements with no resampling. For lossless formats (PNG, BMP, TIFF), quality is perfectly preserved. For JPEG, some tools support lossless 90° rotation (jpegtran, for example). Arbitrary angles (like 30° or 45°) require pixel interpolation, which introduces a small amount of quality loss — similar to resizing.

Can I rotate a photo without cropping it?

Yes. Most tools expand the canvas to fit the full rotated image at arbitrary angles. In ImageMagick 7.1.x, the default -rotate behavior expands the canvas. In Pixotter, the rotated image includes the full content. Cropping only happens if you explicitly choose a "rotate and crop" option.

How do I rotate an image exactly 1 degree?

Use a tool that supports arbitrary angle input. On Pixotter's Rotate tool, enter 1 as the custom angle. In ImageMagick: magick input.jpg -rotate 1 output.jpg. Note that non-90° rotations involve resampling, so there will be minimal quality loss at the sub-pixel level.

How do I rotate an image back to its original orientation?

If you rotated 90° clockwise and want to undo it, rotate 90° counterclockwise (or 270° clockwise — same result). For arbitrary angles, rotate by the negative of the original angle. If the original rotation angle is unknown, the EXIF orientation tag might contain the answer — check it with any EXIF viewer before guessing.

Why does my phone take photos sideways?

Your phone doesn't actually take photos sideways. The camera sensor captures the image in one fixed orientation (usually landscape). The phone then writes an EXIF orientation tag to tell viewers "display this rotated." When that tag gets stripped or ignored — by email clients, older browsers, or file transfers — the image appears in its raw sensor orientation, which looks sideways for portrait shots. Rotating and re-saving with Pixotter bakes the correct orientation into the image data permanently.

How to Convert HEIC to JPG (Free, No Software Needed)

Pixotter — Sun, 05 Apr 2026 10:41:46 +0000

How to Convert HEIC to JPG (Free, No Software Needed)

Your iPhone takes photos in HEIC format. Your Windows PC, your email client, your WordPress site, and half the internet don't know what to do with them. The fix is simple: convert HEIC to JPG and move on with your life.

This guide covers the fastest ways to convert HEIC to JPG on any platform — including a browser-based method that processes everything locally, with zero file uploads.

The Fastest Method: Convert HEIC to JPG in Your Browser

Pixotter's HEIC to JPG converter runs entirely in your browser using WebAssembly. Your photos never leave your device — there's no upload, no server processing, and no file size limit imposed by a remote API.

Here's the full process:

Open Pixotter's Convert tool and select JPG as the output format.
Drop your HEIC files onto the page (or click to browse). Batch processing is supported — drop as many as you need.
Adjust quality if needed. The default (85%) works well for most photos. Lower values produce smaller files; higher values preserve more detail.
Click Convert and download your JPG files.

That's it. The conversion happens in milliseconds using the same image processing library (libvips) that powers production image pipelines at scale — compiled to WebAssembly so it runs in your browser instead of on a server.

Why this matters: Most online converters upload your files to a remote server, process them, and send them back. That introduces privacy risk, file size caps, and latency. Pixotter's client-side approach eliminates all three.

How to Convert HEIC to JPG on Windows

Windows doesn't natively display HEIC files without the HEIF Image Extensions from the Microsoft Store. But even with that extension installed, you still can't save as JPG from the Photos app without extra steps.

Method 1: Pixotter (Browser, No Install)

Open pixotter.com/convert-heic-to-jpg/ in any browser. Drop files, convert, done. Works on Windows 10, 11, and any version with a modern browser.

Method 2: Windows Photos App

Install HEIF Image Extensions from the Microsoft Store (free).
Open the HEIC file in Photos.
Click the three-dot menu → Save as → choose JPEG from the format dropdown.
Pick your destination folder and save.

This works for single files but has no batch processing. For 50+ vacation photos, you'll want a batch converter.

Method 3: Paint (Windows 11)

Right-click the HEIC file → Open with → Paint.
File → Save as → JPEG picture.

Paint converts the file but strips EXIF metadata (camera model, GPS coordinates, date taken). If you need metadata preserved, use Pixotter or a dedicated converter.

Method 4: PowerShell Script

For developers and power users who want command-line batch conversion:

# Requires ImageMagick 7.1.1-29+ installed
# Install: winget install ImageMagick.ImageMagick
Get-ChildItem -Filter *.heic | ForEach-Object {
    magick $_.FullName "$($_.BaseName).jpg"
}

This converts every .heic file in the current directory to JPG. ImageMagick 7.1.1-29 uses libheif 1.17.6 for HEIC decoding.

How to Convert HEIC to JPG on Mac

macOS has native HEIC support, so Macs can read HEIC files natively. Converting to JPG is straightforward.

Method 1: Pixotter (Browser)

Same as Windows — open pixotter.com/convert-heic-to-jpg/, drop files, convert. Works in Safari, Chrome, and Firefox on macOS.

Method 2: Preview

Open the HEIC file in Preview (default double-click behavior).
File → Export.
Change format to JPEG. Adjust the quality slider.
Save.

For batch conversion in Preview: select multiple HEIC files in Finder, right-click → Open With → Preview. Then Edit → Select All, File → Export Selected Images, and choose JPEG format.

Method 3: Automator Quick Action

Create a reusable right-click menu option for batch conversion:

Open Automator → New Document → Quick Action.
Set "Workflow receives" to image files in Finder.
Add a Change Type of Images action → set to JPEG.
Save as "Convert to JPG".

Now you can right-click any HEIC file(s) in Finder → Quick Actions → Convert to JPG.

Method 4: Terminal (sips)

macOS includes sips (scriptable image processing system) out of the box:

# Convert a single file
sips -s format jpeg input.heic --out output.jpg

# Batch convert all HEIC files in current directory
for f in *.heic; do
    sips -s format jpeg "$f" --out "${f%.heic}.jpg"
done

sips preserves EXIF metadata by default. It's been included in macOS since OS X 10.3 (2003) and supports HEIC natively since macOS High Sierra (10.13).

How to Convert HEIC to JPG on Linux

Linux doesn't include HEIC support by default. You need libheif and a conversion tool.

Method 1: Pixotter (Browser)

Works identically on Linux — open pixotter.com/convert-heic-to-jpg/ in Firefox or Chrome. No library installation required.

Method 2: heif-convert (Command Line)

# Ubuntu/Debian
sudo apt install libheif-examples

# Convert a single file
heif-convert photo.heic photo.jpg

# Batch convert
for f in *.heic; do
    heif-convert "$f" "${f%.heic}.jpg"
done

The libheif-examples package (version 1.17.6 on Ubuntu 24.04) includes heif-convert, heif-info, and heif-thumbnailer.

Method 3: ImageMagick

# Ubuntu/Debian (with HEIC support)
sudo apt install imagemagick libheif-dev

# Convert
magick input.heic output.jpg

# Batch convert with quality setting
magick mogrify -format jpg -quality 90 *.heic

ImageMagick 7.1.1-29+ delegates HEIC decoding to libheif. Verify support with magick identify -list format | grep HEIC.

HEIC vs JPG: Key Differences

Feature	HEIC	JPG
Compression	HEVC-based (lossy + lossless)	DCT-based (lossy only)
Typical file size	40-50% smaller than JPG at same quality	Baseline reference
Color depth	10-bit (1 billion colors)	8-bit (16.7 million colors)
Transparency	Supported (alpha channel)	Not supported
Multiple images	Yes (bursts, sequences, depth maps)	No (single image per file)
Browser support	Safari only (as of March 2026)	Universal
Software support	macOS, iOS native; limited elsewhere	Universal
Metadata	Full EXIF, XMP, IPTC	Full EXIF, XMP, IPTC
Editing	Supports non-destructive edits	Destructive only

HEIC is technically superior — better compression, wider color gamut, transparency support. But JPG wins on compatibility. If you need to share photos with anyone outside the Apple ecosystem, email them to a client, upload them to a website, or use them in a design tool, JPG is the safe choice.

If you need lossless quality or transparency support, convert to PNG instead. For a deeper dive into the HEIC format, see What Is HEIC? Apple's Image Format Explained.

When to Keep HEIC (Don't Convert Everything)

Not every HEIC file needs conversion. Keep the original HEIC when:

Archiving photos. HEIC's smaller file size means more photos per gigabyte of storage. A 12 MP iPhone photo is roughly 1.5 MB in HEIC vs 3-4 MB in JPG.
Staying in the Apple ecosystem. If your workflow is iPhone → Mac → iCloud, HEIC works everywhere seamlessly.
Preserving quality. HEIC supports 10-bit color and lossless compression. Converting to 8-bit JPG permanently discards color information.

Convert to JPG when:

Sharing with Windows or Android users
Uploading to websites, WordPress, or social media platforms that don't accept HEIC
Sending via email to recipients who may not have HEIC support
Using in design software (Canva, older Photoshop versions, Google Slides)
Submitting documents — if you need your HEIC photos in a PDF for applications or portfolios, see How to Convert HEIC to PDF

Stop Your iPhone From Shooting HEIC

If you'd rather have JPG files from the start:

Open Settings → Camera → Formats.
Select Most Compatible (instead of High Efficiency).

This switches your camera to JPG/H.264 instead of HEIC/HEVC. Files will be roughly 2× larger, but universally compatible.

You can also keep shooting HEIC and have your iPhone auto-convert when sharing: Settings → Photos → scroll to Transfer to Mac or PC → select Automatic. This converts HEIC to JPG during AirDrop, email, and USB transfers.

Batch Conversion: Handling Hundreds of HEIC Files

For large photo libraries (vacations, events, photo shoots), you need a method that handles volume:

Method	Batch Support	Speed (100 files)	Metadata Preserved	Quality Control
Pixotter	Yes	~10 seconds	Yes	Adjustable slider
macOS Preview	Yes (select all)	~30 seconds	Yes	Quality slider
Windows Photos	No (one at a time)	N/A	Partial	No control
sips (macOS)	Yes (shell loop)	~15 seconds	Yes	Flag: `-s formatOptions`
ImageMagick	Yes (mogrify)	~20 seconds	Yes	Flag: `-quality`
heif-convert	Yes (shell loop)	~25 seconds	Yes	Flag: `-q`

For the fastest batch experience without installing anything, Pixotter's converter handles unlimited files in a single session. Drop them all at once and download a ZIP of the converted JPGs.

Frequently Asked Questions

Does converting HEIC to JPG lose quality?

Yes, but the loss is minimal at reasonable quality settings. HEIC uses HEVC compression (lossy). JPG uses DCT compression (lossy). Converting between two lossy formats introduces a generation loss — the image is decoded from HEIC and re-encoded as JPG. At quality 85-90%, the difference is imperceptible for photos. Avoid converting the same file multiple times, as each round-trip compounds the loss.

Are HEIC and HEIF the same thing?

Almost. HEIF (High Efficiency Image File Format) is the container format specification (ISO/IEC 23008-12). HEIC is a specific variant that uses HEVC (H.265) compression inside the HEIF container. When Apple says "HEIC," they mean HEIF with HEVC encoding. In practice, .heic and .heif files are interchangeable for conversion purposes.

Can I convert HEIC to JPG without losing EXIF data?

Yes, most converters preserve EXIF metadata (camera model, date, GPS coordinates, exposure settings). Pixotter, macOS sips, ImageMagick, and heif-convert all preserve metadata by default. Windows Paint does not — it strips all EXIF data during conversion.

Why does my iPhone use HEIC instead of JPG?

Apple adopted HEIC in iOS 11 (2017) because it produces files roughly half the size of equivalent JPGs. On a 256 GB iPhone, that's the difference between storing 50,000 and 100,000 full-resolution photos. HEIC also supports features JPG can't: 10-bit color, transparency, image sequences, and depth maps for Portrait mode.

Is HEIC better than JPG for web use?

No. While HEIC offers better compression, browser support is limited to Safari. Chrome, Firefox, and Edge don't display HEIC files. For web use, convert HEIC to JPG (universal support) or WebP (better compression than JPG, supported by all modern browsers). See Best Image Format for Web for detailed format recommendations.

How do I convert HEIC to JPG on a Chromebook?

Use Pixotter's browser-based converter. Since it runs entirely in the browser via WebAssembly, it works on ChromeOS without any Linux container or Android app. Open the page, drop your files, and download JPGs.

How to Convert WebP to JPG (5 Free Methods)

Pixotter — Sat, 04 Apr 2026 16:41:32 +0000

How to Convert WebP to JPG (Free, No Upload Required)

You downloaded an image from a website and it saved as a .webp file. Now your email client, your presentation software, or your print shop does not accept it. WebP adoption is widespread on the web, but compatibility outside browsers is still inconsistent. Converting WebP to JPG solves this instantly.

This guide covers the fastest methods to convert WebP to JPG — from a zero-install browser tool to command-line batch processing.

Convert WebP to JPG in Your Browser

Pixotter's WebP to JPG converter processes files entirely in your browser. Your images never leave your device.

Open pixotter.com/convert and select JPG as the output format.
Drop your WebP files onto the page — batch conversion is supported.
Adjust quality if needed. The default (85%) balances file size and visual fidelity.
Click Convert and download your JPG files.

The conversion uses libvips compiled to WebAssembly. It runs in milliseconds for typical images, even on modest hardware.

Why client-side matters: Online converters that upload your files introduce latency, impose size limits (typically 5-20 MB), and route your images through third-party servers. Pixotter's approach eliminates all three — no upload, no waiting, no privacy concern.

Why Convert WebP to JPG?

WebP is technically superior to JPG — smaller files at the same quality, with alpha channel support and both lossy and lossless modes. But JPG has something WebP still lacks: universal compatibility outside of web browsers.

Common reasons to convert:

Email attachments. Many email clients display JPG inline but treat WebP as a generic file download.
Print services. Photo printing shops, poster services, and business card printers overwhelmingly accept JPG and PDF — not WebP.
Older software. Microsoft Office versions before 2021, older versions of Adobe products, and some CMS platforms do not display WebP.
Social media uploads. While most platforms accept WebP now, some (particularly less-updated platforms) still reject it or convert it with unpredictable quality.
Sharing with non-technical users. JPG opens everywhere. WebP sometimes does not. When you are sending images to people who should not have to troubleshoot a file format, JPG is the safe choice.

How to Convert WebP to JPG on Windows

Method 1: Pixotter (Browser)

Open pixotter.com/convert-webp-to-jpg/ in any browser. Drop, convert, done. No install required.

Method 2: Paint (Built-in)

Windows 10 and 11 can open WebP files in Paint:

Right-click the WebP file → Open with → Paint.
File → Save as → JPEG picture.
Choose your destination and save.

Paint strips EXIF metadata during conversion. If you need metadata preserved, use Pixotter or ImageMagick.

Method 3: PowerShell + ImageMagick

# Requires ImageMagick 7.1.1-29+
# Install: winget install ImageMagick.ImageMagick

# Single file
magick input.webp output.jpg

# Batch convert all WebP files in current directory
Get-ChildItem -Filter *.webp | ForEach-Object {
    magick $_.FullName "$($_.BaseName).jpg"
}

Method 4: Windows Photos App

Windows 11's Photos app can open WebP files. Click the three-dot menu → Save as → change the file type to JPEG. Limited to one file at a time.

How to Convert WebP to JPG on Mac

Method 1: Pixotter (Browser)

Same process — open pixotter.com/convert-webp-to-jpg/ in Safari, Chrome, or Firefox.

Method 2: Preview

macOS Preview supports WebP natively since macOS Big Sur (11.0):

Double-click the WebP file (opens in Preview by default).
File → Export.
Change format to JPEG and adjust the quality slider.
Save.

For batch conversion: select multiple WebP files in Finder, right-click → Open With → Preview. Then Edit → Select All, File → Export Selected Images, choose JPEG format.

Method 3: Terminal (sips)

# Convert a single file
sips -s format jpeg input.webp --out output.jpg

# Batch convert all WebP files
for f in *.webp; do
    sips -s format jpeg "$f" --out "${f%.webp}.jpg"
done

sips preserves EXIF metadata and supports quality settings via -s formatOptions [1-100].

How to Convert WebP to JPG on Linux

Method 1: Pixotter (Browser)

Works identically on Linux — open pixotter.com/convert-webp-to-jpg/ in any browser.

Method 2: dwebp + ImageMagick

# Install WebP tools
sudo apt install webp  # Ubuntu/Debian

# Convert using dwebp (outputs PNG, then convert to JPG)
dwebp input.webp -o output.png
magick output.png output.jpg

# Or use ImageMagick directly (7.1.1-29+ supports WebP natively)
magick input.webp output.jpg

# Batch convert with quality setting
for f in *.webp; do
    magick "$f" -quality 85 "${f%.webp}.jpg"
done

Method 3: FFmpeg

# FFmpeg 7.0 — single file
ffmpeg -i input.webp -q:v 2 output.jpg

# Batch convert
for f in *.webp; do
    ffmpeg -i "$f" -q:v 2 "${f%.webp}.jpg"
done

The -q:v 2 flag sets JPEG quality (1 = best quality, 31 = worst). Values 2-5 produce high-quality output suitable for most purposes.

WebP vs JPG: When Each Format Wins

Feature	WebP	JPG
File size (photos)	25-35% smaller at same quality	Baseline
File size (graphics)	Much smaller (lossless mode)	Poor (lossy artifacts on flat colors)
Color depth	8-bit (lossy), 8-bit (lossless)	8-bit
Transparency	Yes (alpha channel)	No
Animation	Yes	No
Browser support	All modern browsers since 2020	Universal
Non-browser support	Inconsistent	Universal
Metadata	EXIF, XMP, ICC	EXIF, XMP, IPTC, ICC
Max dimensions	16,383 × 16,383 px	65,535 × 65,535 px

Use WebP for web delivery, app assets, and any context where the viewer is a modern browser. WebP's compression advantage is real and meaningful for page load performance.

Use JPG when sharing files with people or systems that might not support WebP — email, print, legacy software, presentations, document embedding. JPG is the universal fallback.

For a more detailed format comparison, see Best Image Format for Web and What is WebP?.

Quality Settings: How to Get the Best JPG Output

When converting WebP to JPG, you are re-encoding from one lossy format to another. Each re-encoding introduces a small quality loss. Choosing the right JPEG quality level minimizes the damage.

JPEG Quality	File Size (relative)	Use Case
95-100	Very large	Archival, print, source files
85-90	Medium	General purpose — web, email, sharing
75-80	Small	Thumbnails, preview images, mobile
60-70	Very small	Low-bandwidth situations, batch uploads

Recommendation: Use quality 85 for most conversions. This preserves detail while keeping file size reasonable. Go higher (90-95) for images that will be edited further or printed. Go lower (75) for thumbnails or images where file size matters more than detail.

After converting, you can further optimize the JPG with Pixotter's compression tool — it applies smart compression that squeezes additional bytes without visible quality loss.

Frequently Asked Questions

Does converting WebP to JPG lose quality?

Yes, slightly. WebP lossy and JPG both use lossy compression, so converting between them introduces a generation loss — the image is decoded from WebP and re-encoded as JPG. At quality 85+, the difference is typically imperceptible for photos. Avoid converting the same file back and forth multiple times, as each round-trip compounds the loss.

Can I batch convert many WebP files to JPG?

Yes. Pixotter supports batch conversion — drop multiple files at once. For command-line batch processing, ImageMagick and FFmpeg both handle directories of files efficiently. See the batch examples above.

Why do websites save images as WebP?

WebP files are 25-35% smaller than equivalent JPGs at the same visual quality. Smaller files mean faster page loads, lower bandwidth costs, and better Core Web Vitals scores. Most modern websites serve WebP to browsers that support it and fall back to JPG for older browsers. For more on why WebP exists and how it works, read What is WebP?.

Will converting WebP to JPG make the file larger?

Usually yes. Since WebP compresses more efficiently than JPG, the JPG output is typically 25-35% larger than the WebP source at equivalent visual quality. The tradeoff is compatibility — the larger JPG file works everywhere.

Can I convert animated WebP to JPG?

No — JPG does not support animation. Converting an animated WebP to JPG produces a still image of the first frame. If you need the animation preserved, convert to GIF instead. For more on GIF handling, see How to Compress a GIF.

How do I stop Chrome from saving images as WebP?

Chrome saves images as WebP when websites serve them in that format. You cannot change this behavior in Chrome settings. The simplest fix: save the WebP file normally, then convert it to JPG using Pixotter or any method in this guide. Browser extensions exist that intercept WebP images and convert them on download, but they add complexity and may break on some sites.

Is there any reason NOT to convert WebP to JPG?

If the image has transparency (alpha channel), converting to JPG will fill transparent areas with a solid color — JPG does not support transparency. In that case, convert to PNG instead. Also, if the image will only be displayed on the web, keeping it as WebP saves bandwidth. Convert to JPG only when you need the compatibility that JPG provides.

How to Open WebP Files on Any Device

Pixotter — Fri, 03 Apr 2026 22:51:16 +0000

How to Open WebP Files (View and Convert on Any Device)

You right-clicked an image, hit "Save image as," and got a .webp file. Now your image viewer cannot open it, your email client does not recognize it, and your photo editor rejects it. This is one of the most common frustrations on the modern web.

WebP is Google's image format — smaller files, better compression — and it has been the default serving format for most websites since 2020. But while browsers handle WebP perfectly, the rest of the software ecosystem is still catching up.

Here is how to open, view, and convert WebP files on every platform.

Can Your Computer Already Open WebP?

Before installing anything, check what you already have:

Operating System	Native WebP Support	Default Viewer
Windows 11	Yes	Photos app opens WebP
Windows 10 (updated)	Yes	Photos app opens WebP (after update 1809+)
Windows 10 (older)	No	Extension needed
macOS Ventura (13+)	Yes	Preview opens WebP
macOS Monterey (12)	Yes	Preview opens WebP
macOS Big Sur (11)	Partial	Quick Look works, some apps do not
macOS Catalina or older	No	Third-party viewer needed
Ubuntu 22.04+	Yes	Eye of GNOME, Shotwell
Chrome OS	Yes	Built-in viewer
iOS 14+	Yes	Photos app
Android 4.0+	Yes	Gallery/Photos

If your OS supports WebP but the file will not open: The issue is usually the specific application, not the OS. Try opening the file in a different program — your browser always works as a fallback viewer (drag the WebP file into a browser tab).

Method 1: Open WebP in Your Browser

Every modern browser displays WebP files. This is the zero-install solution:

Open Chrome, Firefox, Edge, or Safari.
Drag and drop the WebP file into the browser window (or press Ctrl+O / Cmd+O to browse).
The image displays immediately.

This works on every operating system. If you only need to view the image — not edit or convert it — this is the fastest path.

Method 2: Convert WebP to JPG or PNG

If you need the image in a format that your other software accepts, convert it.

Using Pixotter (Browser, No Install)

Open pixotter.com/convert.
Drop the WebP file and select JPG or PNG as the output format.
Download the converted file.

Everything runs locally in your browser — the file never leaves your device. Batch conversion is supported.

Using Windows Paint

On Windows 10/11:

Right-click the WebP file → Open with → Paint.
File → Save as → choose JPEG picture or PNG picture.

Using macOS Preview

On macOS Monterey or later:

Double-click the WebP file to open in Preview.
File → Export.
Change format to JPEG or PNG → Save.

Using Command Line

# ImageMagick 7.1.1-29+ (any OS)
magick input.webp output.jpg
magick input.webp output.png

# macOS sips
sips -s format jpeg input.webp --out output.jpg

# Linux: dwebp (from libwebp-tools)
sudo apt install webp
dwebp input.webp -o output.png

For a comprehensive conversion guide with batch processing and quality settings, see How to Convert WebP to JPG.

Method 3: Install a WebP Viewer

If you frequently work with WebP files and want them to open natively in your preferred image viewer:

Windows (Older Versions)

Install the WebP Image Extension from the Microsoft Store (free, by Google). This adds WebP support to the Photos app, File Explorer thumbnails, and most UWP applications.

macOS (Catalina or Older)

Install a third-party viewer:

XnView MP (free for personal use) — opens WebP and 500+ other formats
qView (GPLv3, free) — lightweight, opens WebP natively

Or upgrade to macOS Monterey or later for native support.

Linux

Most modern Linux distributions include WebP support. If yours does not:

# Ubuntu/Debian
sudo apt install webp

# This installs dwebp, cwebp, and adds WebP support to many applications

GIMP 2.10+ (GPLv3) opens and saves WebP files on all platforms.

Why Browsers Save Images as WebP

You did not ask for a WebP file. So why did you get one?

When a website serves images, it checks what formats your browser supports (via the Accept HTTP header). Modern browsers advertise WebP support, so the server sends the WebP version — it is smaller and loads faster. When you right-click and "Save image as," you save the WebP version that was delivered, not the original format.

This is called content negotiation — the server picks the best format for your browser. The same image URL might serve JPEG to an old browser and WebP to a modern one.

Can You Force Browsers to Save as JPG?

Not directly. The browser saves whatever format the server sent. Workarounds:

Convert after downloading. Save the WebP, then convert using Pixotter or any method above.
Use a browser extension. Extensions like "Save Image as Type" (available for Chrome and Firefox) let you choose the download format. The extension converts on-the-fly.
View page source. Some websites still host the original JPG/PNG and use a CDN to convert to WebP on delivery. Right-clicking → Inspect Element → checking the <img> tag's src or srcset attributes may reveal the original URL.

WebP File Format Overview

Property	Value
Developer	Google (2010)
Compression	Lossy (VP8) and lossless (VP8L)
Transparency	Yes (alpha channel in both modes)
Animation	Yes
Color depth	8-bit per channel (24-bit RGB + 8-bit alpha)
Max dimensions	16,383 × 16,383 pixels
Browser support	Chrome 17+, Firefox 65+, Safari 14+, Edge 18+
File extension	.webp
MIME type	image/webp

WebP consistently produces files 25-35% smaller than equivalent JPEG (lossy) and 26% smaller than PNG (lossless). It supports both lossy and lossless modes, transparency, and animation — making it a versatile replacement for JPEG, PNG, and GIF in web contexts.

For a deeper technical comparison, see What is WebP? and PNG vs WebP.

Software That Supports WebP (2026)

Software	WebP Support	Notes
Chrome, Firefox, Safari, Edge	Yes	All major browsers since 2020
GIMP 2.10+	Yes	Open, edit, and save WebP
Photoshop 23.2+ (2022)	Yes	Native open/save
Photopea	Yes	Browser-based, free
macOS Preview	Yes (Monterey+)	View and export
Windows Photos	Yes (10/11)	View and basic edit
LibreOffice 7.4+	Yes	Insert WebP images in documents
WordPress 5.8+	Yes	Upload and serve WebP
Microsoft Office 365	Yes	Insert WebP in Word, PowerPoint
Older Office versions	No	Convert to JPG/PNG first
Canva	Yes	Upload WebP assets
Figma	Yes	Import WebP
Most print services	No	Convert to JPG or TIFF

If your software is not listed: Try opening the WebP file. Many applications have added WebP support in recent updates without prominently advertising it. If it does not work, convert to JPG or PNG using Pixotter.

Frequently Asked Questions

What is a WebP file?

WebP is an image format developed by Google that produces smaller files than JPEG and PNG at equivalent quality. It supports both lossy and lossless compression, transparency, and animation. Most websites now serve images in WebP format to reduce page load times. For the full technical breakdown, see What is WebP?.

Why can't I open a WebP file on my computer?

Your operating system or image viewer may not support WebP. Windows 10/11 and macOS Monterey+ support it natively. Older systems need a WebP extension or a third-party viewer. The simplest solution: drag the file into any web browser to view it, or convert it to JPG/PNG using Pixotter.

How do I convert WebP to JPG without installing software?

Open pixotter.com/convert in your browser, drop the WebP file, select JPG as the output, and download. The conversion runs entirely in your browser — nothing is uploaded. For batch processing and more methods, see How to Convert WebP to JPG.

Is WebP better than JPG?

For web delivery, yes — WebP produces 25-35% smaller files at the same visual quality, with features JPG lacks (transparency, animation, lossless mode). For compatibility outside browsers (email, print, legacy software), JPG is still the safer choice. See Best Image Format for Web for the current recommendations.

Can I upload WebP files to social media?

Most major platforms accept WebP: Instagram, Facebook, Twitter/X, LinkedIn, and Pinterest all support WebP uploads. Some smaller or older platforms may not. When in doubt, convert to JPG before uploading.

How do I stop saving images as WebP?

You cannot change browser behavior directly — browsers save whatever format the server sends. Options: (1) convert after saving using Pixotter, (2) install a "Save Image as Type" browser extension, or (3) check the page source for the original image URL in a different format.

Can WebP files contain viruses?

WebP files are image data, not executable code. They cannot contain viruses in the traditional sense. However, like any file format, crafted WebP files could theoretically exploit vulnerabilities in image parsing libraries. Keep your browser and OS updated to protect against known vulnerabilities. This risk is not unique to WebP — the same applies to JPEG, PNG, and every other image format.

How to Open HEIC Files on Windows and Mac

Pixotter — Thu, 02 Apr 2026 06:56:35 +0000

How to Open HEIC Files on Windows and Mac

Someone sent you a photo. Or you plugged in your iPhone, copied files to your PC, and got a folder full of .heic files that nothing will open. Windows says "File type not supported." Your email client shows a blank attachment. Your favorite image editor doesn't recognize it.

The good news: opening HEIC files is a solved problem on every platform. The better news: you might not even need to open them — converting to JPG takes seconds and gives you a file that works everywhere.

What Is a HEIC File?

HEIC (High Efficiency Image Container) is the image format iPhones have used by default since iOS 11 in 2017. It wraps HEVC (H.265) compression inside a HEIF container, producing files roughly half the size of equivalent JPGs with better color depth and quality.

The format is technically excellent. The problem is compatibility — outside Apple's ecosystem, support is inconsistent. That's why you're here.

For the full technical breakdown — compression details, color depth specs, and format comparisons — see What Is HEIC? Apple's Image Format Explained.

How to Open HEIC Files on Windows

Windows 10 and Windows 11 don't display HEIC files out of the box. You need a free extension from Microsoft.

Step 1: Install HEIF Image Extensions

Open the Microsoft Store (search for it in the Start menu).
Search for HEIF Image Extensions (published by Microsoft Corporation).
Click Get or Install. It's free.
Restart any open image applications.

Direct link: HEIF Image Extensions on the Microsoft Store.

Step 2: Open Your HEIC Files

After the extension is installed:

File Explorer shows HEIC thumbnails automatically
Windows Photos opens HEIC files on double-click
Paint (Windows 11) can open and save HEIC files
Snipping Tool recognizes HEIC as a valid input

Limitations on Windows

The HEIF extension gives you viewing capability, but the experience has rough edges:

No batch export. Windows Photos converts one file at a time — no "select all and export as JPG" option.
No editing tools. Basic crops and rotations work. Advanced adjustments are limited compared to what you'd get after converting to JPG and using a proper editor.
Occasional codec confusion. Some HEIC files encoded with specific HEVC profiles trigger a prompt to install the HEVC Video Extensions ($0.99). This happens rarely with standard iPhone photos but can occur with HEIC files from other sources.

If you need to work with HEIC files regularly on Windows — not just view them — converting to JPG is the more practical path.

How to Open HEIC Files on Mac

macOS has native HEIC support since High Sierra (10.13), released in September 2017. If your Mac runs macOS 10.13 or later, HEIC files just work.

Native Viewer Options

Preview — Double-click any .heic file. It opens, displays, and supports basic editing (crop, rotate, color adjust). You can also export to JPG, PNG, or other formats via File → Export.
Photos — Import HEIC files directly. Full editing suite, iCloud sync, and album organization.
Quick Look — Press Space on any HEIC file in Finder for an instant preview without opening an app.
Finder thumbnails — Generated automatically, no configuration needed.

What If HEIC Files Won't Open on Mac?

If double-clicking a HEIC file doesn't work:

Check your macOS version. HEIC support requires macOS High Sierra (10.13) or later. Open Apple menu → About This Mac to verify.
Reset the file association. Right-click the HEIC file → Get Info → under "Open with," select Preview → click "Change All."
Check the file extension. Some files arrive as .HEIC (uppercase) or .heif instead of .heic. macOS handles all three, but third-party apps may not.

How to Open HEIC Files on Linux

Linux doesn't ship with HEIC support by default, but adding it takes one package install.

Method 1: Install libheif

# Ubuntu/Debian (22.04+)
sudo apt install libheif1 libheif-examples

# Fedora 38+
sudo dnf install libheif

# Arch Linux
sudo pacman -S libheif

After installing libheif (version 1.17.6 on Ubuntu 24.04), most GTK-based image viewers pick up HEIC support automatically:

Eye of GNOME (eog) — opens HEIC files directly
Shotwell — imports and displays HEIC photos
GIMP 2.10.32+ — opens HEIC files for editing (requires libheif plugin)
Gwenview (KDE) — displays HEIC with libheif installed

Method 2: ImageMagick

# Install ImageMagick 7.1.1-29+ with HEIC support
sudo apt install imagemagick libheif-dev

# View a HEIC file
magick display photo.heic

# Get file info
magick identify photo.heic

ImageMagick 7.1.x delegates HEIC decoding to libheif. Verify HEIC support is active with:

magick identify -list format | grep HEIC

You should see HEIC* rw+ in the output, confirming read/write support.

Method 3: Convert First, Then Open

If you'd rather not install system libraries, convert your HEIC files to JPG or PNG in the browser using Pixotter's converter — works on any Linux distribution with Firefox or Chrome, no packages needed.

How to Open HEIC Files on Android

Android's HEIC support depends on your OS version.

Android 9 (Pie) and Later

Android 9+ includes native HEIF decoding. The default Gallery app, Google Photos, and most third-party image viewers handle HEIC files out of the box. No action needed — tap the file and it opens.

Android 8 (Oreo) and Earlier

Older Android versions lack native HEIC support. Your options:

Google Photos (if installed) — can display HEIC files regardless of Android version, since it uses its own decoder.
A third-party viewer — apps like Simple Gallery Pro include built-in HEIC decoding.
Convert before transferring — convert HEIC to JPG on your computer or in the browser before sending files to the phone.

Quick Check

Not sure if your phone supports HEIC? Transfer one .heic file to your device and try to open it with the default gallery app. If it works, you're set. If not, Google Photos is the simplest fix — it's free and handles HEIC on any Android version.

How to Open HEIC Files in a Browser

You don't need to install anything on your computer. Pixotter's Convert tool opens and processes HEIC files directly in your browser using WebAssembly.

Here's how it works:

Open pixotter.com/convert/ in any modern browser — Chrome, Firefox, Safari, or Edge.
Drop your HEIC files onto the page.
Pixotter decodes and displays the images instantly — you can see the contents right in the browser.
Choose an output format (JPG, PNG, or WebP) and convert if needed.

Everything runs locally. Pixotter uses wasm-vips (libvips compiled to WebAssembly) to decode HEIC files in your browser. Your photos never leave your device — no upload to a server, no privacy risk, no file size limits.

This works on any platform: Windows, Mac, Linux, Chromebook, or even a tablet. If you have a browser, you can open HEIC files.

The Better Solution: Convert HEIC to JPG or PNG

Opening HEIC files solves today's problem. Converting them solves it permanently.

Here's the reality: you can install viewers and extensions, but you'll still hit HEIC compatibility walls every time you try to upload a photo to a website, attach it to an email, paste it into a Google Doc, or share it with someone on Android. JPG and PNG work everywhere — every browser, every email client, every app, every operating system.

When to Convert to JPG

Sharing photos via email, messaging apps, or social media
Uploading to websites, WordPress, Shopify, or web forms
Sending to clients, coworkers, or anyone outside the Apple ecosystem
Archiving in a universally accessible format

JPG is the safe default for photographs. Read the step-by-step guide: How to Convert HEIC to JPG.

When to Convert to PNG

Images that need transparency (logos, overlays, screenshots)
Graphics with sharp edges and text where JPG compression would blur
When you need lossless quality and file size isn't a concern

See the full walkthrough: How to Convert HEIC to PNG.

Convert with Pixotter (30 Seconds)

Open Pixotter's HEIC to JPG tool (or the general converter for other formats).
Drop your HEIC files. Batch is supported — drop dozens at once.
Adjust quality if needed (default 85% is a good balance of size and detail).
Click Convert and download your files.

No signup, no watermark, no file count limit. The conversion runs in your browser via WebAssembly, so nothing gets uploaded.

Comparison: HEIC Viewing Methods at a Glance

Platform	Native Support	Steps to Open	Limitations
Windows 10/11	No (extension required)	Install HEIF Image Extensions from Microsoft Store → open with Photos	No batch export, limited editing, occasional HEVC codec prompt
macOS 10.13+	Yes	Double-click → opens in Preview	None — full native support
Linux	No (library required)	Install libheif → open with image viewer	Requires terminal, GIMP needs plugin
Android 9+	Yes	Tap to open in Gallery or Google Photos	Older Android (8-) needs third-party viewer
Chromebook	No	Use browser-based converter (Pixotter)	No native viewer; conversion is the best path
Browser (Pixotter)	Yes (via WebAssembly)	Drop files at pixotter.com/convert/	Requires internet to load the page (processing is local)

The browser-based approach is the only method that works across every platform with zero installation. If you're dealing with HEIC files from multiple devices or helping less technical users, sending them a link to Pixotter's converter is simpler than walking them through extension installs.

How to Stop Your iPhone from Taking HEIC Photos

If you'd rather avoid the compatibility issue entirely, switch your iPhone camera to JPG output:

Open Settings → Camera → Formats.
Select Most Compatible.

That's it. Your camera now shoots JPG (and H.264 video instead of HEVC). Photos will be roughly 2x larger and limited to 8-bit color, but every device and service accepts them without conversion.

The Middle Ground

Want HEIC's storage and quality benefits but JPG compatibility when sharing? Keep shooting in HEIC and enable automatic conversion during transfers:

Open Settings → Photos.
Scroll to Transfer to Mac or PC.
Select Automatic.

With this setting, iOS converts HEIC to JPG automatically when you AirDrop, email, or USB-transfer photos. You keep the small HEIC originals on your phone, and recipients get universally compatible JPGs.

For a deeper look at the HEIC format and how it compares to JPEG quality-wise, see HEIC vs JPEG: Which Format Is Better?.

Frequently Asked Questions

Why can't I open HEIC files on my PC?

Windows doesn't include HEIC decoding by default because the HEVC codec is patent-encumbered. Microsoft requires a separate extension — HEIF Image Extensions — from the Microsoft Store (free). Install it and Windows Photos, Paint, and File Explorer will all recognize HEIC files.

Is a HEIC file the same as a JPG?

No. HEIC and JPG are different formats with different compression algorithms. HEIC uses HEVC (H.265) compression, producing files roughly half the size of an equivalent JPG with better color depth (10-bit vs 8-bit). However, JPG has universal compatibility while HEIC is mainly supported in Apple's ecosystem. See HEIC vs JPEG for a detailed comparison.

Can I open HEIC files in Photoshop?

Yes. Adobe Photoshop 22.0+ (released October 2020) opens HEIC files natively on both Windows and macOS. On Windows, you still need the HEIF Image Extensions from the Microsoft Store installed. Lightroom 6.14+ also supports HEIC import.

Are HEIC files safe to open?

Yes. HEIC files are standard image data — they cannot execute code or install software. Like any file format, a maliciously crafted HEIC file could theoretically exploit a bug in an image decoder, but this risk is identical to JPG, PNG, or any other image format. Keep your OS updated and open files only from trusted sources.

How do I open HEIC files in Google Drive?

Google Drive can preview HEIC files in the browser — click the file and it displays in Drive's built-in viewer. However, Google Docs and Slides don't accept HEIC files as image inserts. For those, convert to JPG first and then insert the converted file.

Can I batch-open or batch-convert HEIC files?

Yes. For batch viewing, install the HEIF extension (Windows) or libheif (Linux) and your file manager will show thumbnails for all HEIC files at once. For batch conversion, Pixotter's converter accepts multiple files in a single drop — select all your HEIC files, drop them on the page, and download converted JPGs or PNGs as a batch.

What Is WebP? Google's Modern Image Format Explained

Pixotter — Wed, 01 Apr 2026 13:16:21 +0000

What Is WebP? Google's Modern Image Format Explained

WebP is the image format Google built to make the web faster. It produces smaller files than JPEG, supports transparency like PNG, and handles animation like GIF — all in a single format. Since every major browser now supports it, WebP has become the default recommendation for web images in 2026.

Here's what the format actually does under the hood, how it compares to the alternatives, and when you should (and shouldn't) use it.

WebP at a Glance

Property	Details
File extension	`.webp`
MIME type	`image/webp`
Compression	Lossy (VP8) and lossless (VP8L)
Color depth	8-bit per channel (24-bit RGB, 32-bit RGBA)
Transparency	Yes — full alpha channel (lossy and lossless)
Animation	Yes — multi-frame sequences with timing control
Max dimensions	16,383 × 16,383 pixels
Metadata	EXIF, XMP, ICC color profiles
Creator	Google
Year introduced	2010
Browser support	Chrome 17+, Firefox 65+, Safari 14+, Edge 18+
License	BSD — royalty-free

How WebP Compression Works

WebP borrows its compression technology from video codecs. If you understand how video compression squeezes hours of footage into manageable file sizes, WebP's approach will feel familiar — it applies the same techniques to individual still images.

Lossy WebP (VP8)

Lossy WebP uses Google's VP8 video codec, treating each image as a single video frame. The encoder:

Divides the image into macroblocks — 16×16 pixel regions, each processed independently.
Predicts pixel values from neighboring blocks using spatial prediction (intra-prediction). The encoder picks from four prediction modes for luma and the best matching mode for chroma. If a prediction is close to the actual pixels, only the small difference needs to be stored.
Applies a discrete cosine transform (DCT) to the prediction residuals, converting spatial data into frequency coefficients. High-frequency coefficients (fine detail) get quantized more aggressively — this is where the controlled quality loss happens.
Entropy-encodes the result using boolean arithmetic coding, which is more efficient than JPEG's Huffman coding.

The combination of better prediction, finer quantization control, and arithmetic coding is why lossy WebP files are 25-34% smaller than equivalent-quality JPEGs, according to Google's published comparisons.

Lossless WebP (VP8L)

Lossless WebP uses a completely different algorithm from lossy mode. VP8L applies a series of reversible transforms before the final compression:

Subtract green transform — stores red and blue channels as differences from the green channel. Since natural images have high correlation between RGB channels, this reduces entropy significantly.
Predictor transform — for each pixel, VP8L selects from 13 spatial predictors and stores only the prediction error.
Cross-color transform — decorrelates the color channels further by encoding inter-channel relationships.
Color indexing transform — if the image uses few colors (≤256), VP8L automatically switches to a palette-based mode.
LZ77 backward references — finds repeating pixel patterns and replaces them with references to earlier occurrences.
Huffman coding — entropy-encodes the final stream.

The result: lossless WebP files are 26% smaller than equivalent PNG files on average. The advantage is most pronounced on photographic content, where the spatial prediction transforms have more redundancy to exploit.

Lossy vs Lossless WebP

WebP's dual-mode design means you pick the compression type based on your content:

Lossy WebP works best for photographs and complex images with smooth gradients, many colors, and no hard edges that need pixel-perfect preservation. Quality is controlled by a 0-100 parameter — quality 75-80 is the sweet spot for web images, producing files that are visually indistinguishable from the original at typical viewing sizes.

Lossless WebP works best for graphics, screenshots, illustrations, logos, and any image where every pixel matters. No quality parameter — the output is bit-for-bit identical to the input. File sizes are larger than lossy but still smaller than PNG.

A unique WebP feature: lossy compression with alpha channel. JPEG forces you to choose between small files (lossy, no transparency) and transparency (PNG, large files). WebP lets you have both — a lossy-compressed image body with a separately compressed lossless alpha channel. This is particularly useful for product photos on transparent backgrounds.

For a deeper dive into the tradeoffs between lossy and lossless compression across all formats, see Lossy vs Lossless Image Compression.

WebP vs Other Formats

Feature	WebP	JPEG	PNG	AVIF	GIF
Compression	VP8 (lossy) / VP8L (lossless)	DCT (lossy)	DEFLATE (lossless)	AV1 (lossy/lossless)	LZW (lossless, 8-bit)
File size (photo, equivalent quality)	~30% smaller than JPEG	Baseline	3-5× larger than JPEG	~20% smaller than WebP	5-10× larger than JPEG
Transparency	Yes (lossy and lossless)	No	Yes (lossless only)	Yes	1-bit only (on/off)
Animation	Yes	No	APNG (limited support)	Yes	Yes
Color depth	8-bit	8-bit	8/16-bit	10/12-bit	8-bit (256 colors max)
HDR support	No	No	No	Yes	No
Browser support	All modern (Chrome 17+, Firefox 65+, Safari 14+, Edge 18+)	Universal	Universal	Chrome 85+, Firefox 93+, Safari 16.4+	Universal
Encoding speed	Fast	Fast	Fast	Slow (10-100× slower than WebP)	Fast
License	Royalty-free (BSD)	Royalty-free	Royalty-free	Royalty-free (AOM)	Royalty-free (patents expired)
Best for	General web images	Universal photo sharing	Graphics, screenshots	Best-possible compression, HDR	Simple animations, memes

Key takeaways from the comparison:

WebP vs JPEG: WebP wins on file size (25-34% smaller), adds transparency and animation, and is supported everywhere JPEG is supported in modern browsers. The only reason to choose JPEG over WebP is backward compatibility with very old software.
WebP vs PNG: Lossless WebP is 26% smaller than PNG with identical quality. WebP also adds animation support. PNG's advantage is broader software support outside browsers (print tools, legacy editors) and 16-bit color depth. See the full comparison at PNG vs WebP.
WebP vs AVIF: AVIF compresses roughly 20% better than WebP and supports 10/12-bit HDR. But AVIF encoding is dramatically slower (sometimes 100× slower), and browser support is narrower — Safari only added AVIF in version 16.4 (2023). For a detailed breakdown, see WebP vs AVIF.
WebP vs GIF: Animated WebP files are significantly smaller than equivalent GIFs with better color reproduction (24-bit vs 8-bit). For more on GIF's history and limitations, see What Is GIF?.

For help choosing the right format across all use cases, see Best Image Format for Web.

Browser Support

WebP support was a pain point for years. Google shipped support in Chrome 17 (2012), but Safari held out until version 14 (2020). That gap forced developers into fallback gymnastics with <picture> elements and multiple source files.

That era is over. As of 2026, every major browser supports WebP:

Browser	WebP Support Since	Version
Chrome	2012	17+
Firefox	2019	65+
Edge	2018	18+
Safari	2020	14+ (macOS Big Sur, iOS 14)
Opera	2012	12.1+
Samsung Internet	2015	4+

Safari 14+ means every iPhone running iOS 14 or later displays WebP natively. Since Apple drops iOS support aggressively (iOS 14 requires iPhone 6s or later, released in 2015), the percentage of active iPhones that cannot display WebP is negligible.

Global browser support for WebP exceeds 97% of web users according to Can I Use. The remaining ~3% is almost entirely legacy browsers on unmaintained systems. Unless your analytics show meaningful traffic from Internet Explorer or pre-2019 browsers, you can serve WebP without fallbacks.

When to Use WebP

WebP is the right choice when you need:

Smaller photo files for web pages. Replace JPEG with lossy WebP at quality 75-80. Expect 25-34% file size reduction with no visible quality difference. This directly improves page load times and Core Web Vitals scores — particularly Largest Contentful Paint (LCP), which Google uses as a ranking signal.

Transparency without the PNG tax. Product photos, logos, and UI elements on transparent backgrounds compress dramatically better as lossy WebP with alpha than as lossless PNG. A product photo that's 800 KB as PNG might be 120 KB as lossy WebP with alpha — same transparency, 85% smaller.

Replacing animated GIFs. Animated WebP files are typically 50-80% smaller than equivalent GIFs with full 24-bit color instead of GIF's 256-color limit. The visual improvement is dramatic, especially for animations with gradients or photographic content.

A single format that does everything. If you want one format for photos, graphics, and animations, WebP handles all three. JPEG can't do transparency. PNG can't do lossy compression or animation. GIF can't do more than 256 colors. WebP does it all.

When NOT to Use WebP

WebP is not the right choice in every situation:

Print workflows. Print pipelines expect TIFF or high-quality JPEG/PNG. WebP's 8-bit color depth and web-oriented compression are not designed for print reproduction. If your images go to a printer, use TIFF (16-bit, lossless) or PNG.

Archival storage. For long-term image archives, lossless formats with broad software support are safer bets. PNG and TIFF have decades of software support and standardization behind them. WebP is well-supported now, but PNG is a W3C standard with a 30-year track record.

When you need the absolute best compression. AVIF outperforms WebP by roughly 20% in file size at equivalent quality, with the bonus of 10/12-bit HDR support. If encoding speed is not a constraint and your audience's browsers support AVIF (97%+ in 2026), AVIF is the better choice for maximum compression. See What Is AVIF? for the details.

When you need 16-bit color depth. WebP maxes out at 8-bit per channel. Scientific imaging, medical imaging, and high-end photography workflows that require 16-bit precision should use PNG or TIFF.

Legacy system integration. Some older CMS platforms, email clients, and desktop applications still don't handle WebP. If your images will be opened in software from 2018 or earlier, JPEG or PNG is safer.

How to Convert Images to WebP

Using Pixotter (Browser-Based)

The fastest way to convert images to WebP without installing anything:

Open Pixotter's Convert tool.
Drop your images — JPG, PNG, HEIC, BMP, TIFF, GIF, or any other supported format.
Select WebP as the output format.
Adjust quality if needed (default 80 is a good starting point for photos).
Download your converted files.

Everything processes in your browser using WebAssembly. Your files never leave your device — no upload, no server, no waiting for a round-trip. Batch conversion works too: drop multiple files and convert them all at once.

Already have WebP files that are too large? Run them through Pixotter's Compress tool to reduce file size while keeping the WebP format. For a detailed walkthrough of WebP compression settings and strategies, see How to Compress WebP Images.

Need to go the other direction? Pixotter also converts FROM WebP to JPG, PNG, GIF, and other formats — useful when you receive WebP files but need a different format for print, email, or legacy software. See How to Convert WebP to JPG for the full walkthrough, or How to Convert WebP to GIF if you need animated GIF output.

Using the Command Line (cwebp)

Google provides cwebp (version 1.4.x) as part of the libwebp package for command-line conversion:

# Convert JPEG to lossy WebP at quality 80
cwebp -q 80 input.jpg -o output.webp

# Convert PNG to lossless WebP
cwebp -lossless input.png -o output.webp

# Convert with near-lossless mode (quality 90-100 range, slight lossy)
cwebp -near_lossless 60 input.png -o output.webp

Install on Ubuntu/Debian:

sudo apt install webp

Install on macOS:

brew install webp

The cwebp encoder is fast — a 12 MP image converts in under a second on modern hardware. For batch conversion, combine with find and shell scripting, or use Pixotter's batch conversion for a visual interface.

Frequently Asked Questions

What does WebP stand for?

WebP doesn't have an official expansion — Google named it as a play on "web" and the idea of a web picture format. It's pronounced "weppy" according to Google's documentation, though many people say "web-P."

Is WebP better than JPEG?

For web use, yes. WebP produces files 25-34% smaller than JPEG at equivalent visual quality, and adds transparency and animation support that JPEG lacks. The only scenarios where JPEG is preferable are legacy software compatibility and print workflows.

Can I open WebP files on my computer?

Yes. Windows 10+ (with the WebP Image Extension from Microsoft Store), macOS (Preview in macOS Big Sur 11+), and Linux (via libwebp and most modern image viewers) all support WebP natively. Chrome, Firefox, Safari, and Edge display WebP in web pages. For older systems, convert to JPEG or PNG using Pixotter's Convert tool.

Does WebP support transparency?

Yes — both lossy and lossless WebP support full 8-bit alpha channels. This is a significant advantage over JPEG (no transparency at all) and GIF (1-bit transparency only — each pixel is fully transparent or fully opaque). WebP's lossy-with-alpha mode is especially powerful: you get the small file sizes of lossy compression with the transparency of PNG.

Should I convert all my PNGs to WebP?

For web delivery, usually yes. Lossless WebP is 26% smaller than PNG with identical quality. If the images will only be served on the web and you don't need 16-bit color depth, WebP is the better format. For source files in design workflows, keep the PNGs as originals and export WebP for the web. Read the detailed comparison at PNG vs WebP.

Will WebP replace JPEG and PNG?

WebP is already the recommended format for web images, but "replace" is too strong. JPEG and PNG have decades of universal software support, established workflows, and use cases (print, archival) where WebP doesn't fit. What's more likely: WebP (and eventually AVIF) become the default for web delivery, while JPEG and PNG remain the standard for everything else. For help deciding which format fits your use case, see Best Image Format for Web.

What Is AVIF? The Next-Gen Image Format Explained

Pixotter — Tue, 31 Mar 2026 19:05:35 +0000

What Is AVIF? The Next-Gen Image Format Explained

AVIF is showing up everywhere. Browsers support it, image tools list it as an output option, and developers keep recommending it for web performance. The format promises dramatically smaller files than JPEG and WebP without visible quality loss — and unlike HEIC, it is completely royalty-free.

Here is what AVIF actually is, how it works under the hood, and when you should (and should not) use it.

AVIF at a Glance

Property	Details
Full name	AV1 Image File Format
File extension	`.avif`
MIME type	`image/avif`
Compression	AV1 (lossy and lossless)
Color depth	8-bit, 10-bit, 12-bit
Transparency	Full alpha channel
Animation	Yes (via AVIF sequences)
HDR support	Yes (PQ, HLG, Rec. 2020, DCI-P3)
Browser support	Chrome 85+, Firefox 93+, Safari 16.1+, Edge 85+
Year introduced	2019 (AVIF 1.0 specification)
License	Royalty-free (Alliance for Open Media)

AVIF is the still-image counterpart to AV1 video, packaged in a HEIF-based container. If you know what HEIC is — Apple's image format using HEVC compression inside a HEIF container — AVIF is the same container idea, but with AV1 compression instead.

How AVIF Compression Works

AVIF uses the AV1 video codec to compress individual image frames. AV1 was developed by the Alliance for Open Media (AOMedia), a consortium that includes Google, Apple, Microsoft, Netflix, Amazon, Meta, and Mozilla. The consortium's goal was to create a next-generation video codec that anyone could use without paying patent royalties — a direct response to the licensing complexity around HEVC/H.265.

The Technical Mechanics

AV1 achieves its compression through intra-frame coding — the same technique video codecs use to compress keyframes (frames that don't reference other frames). For still images, every image is a keyframe. Here is what happens when an AVIF encoder processes your image:

Block partitioning. The image is divided into coding units up to 128x128 pixels. AV1's superblock structure is far more flexible than older codecs — it can recursively split blocks into smaller rectangles to match image complexity. Simple regions (blue sky) get large blocks; detailed regions (tree branches) get small ones.
Intra prediction. For each block, the encoder predicts pixel values from already-encoded neighboring blocks. AV1 offers over 50 directional prediction modes (compared to VP8's 4), plus smooth and Paeth predictors. The encoder picks whichever mode minimizes the residual — the difference between prediction and reality.
Transform and quantization. The residual signal is transformed (DCT or ADST variants) and quantized — this is where lossy compression happens. Higher quality settings preserve more of the residual; lower settings discard more.
Entropy coding. The quantized coefficients are compressed using an arithmetic coder that adapts to the statistical patterns in the data.
Loop filtering. AV1 applies deblocking filters, CDEF (Constrained Directional Enhancement Filter), and loop restoration to reduce blocking artifacts at the decoder side. This is why AVIF images look cleaner than JPEG at equivalent file sizes — the filtering happens after decoding, not during encoding.

The result: AVIF files are typically 30-50% smaller than JPEG and 20-50% smaller than WebP at the same perceptual quality. The compression gains come from AV1's larger block sizes, richer prediction modes, and more sophisticated filtering — all of which require more computation to encode.

The Royalty-Free Advantage

This matters more than most developers realize. HEVC (the codec behind HEIC) is patent-encumbered, which is why Chrome, Firefox, and Edge never added native HEIC support. Browser vendors would owe royalties to multiple patent pools for every HEVC decoder they shipped.

AV1 was designed to avoid this entirely. AOMedia's patent license grants royalty-free rights to anyone implementing the standard. This is why AVIF has broad browser support and HEIC does not — the codec politics are as important as the codec technology.

AVIF vs Other Formats

Feature	AVIF	JPEG	WebP	PNG	HEIC
Compression type	Lossy + lossless	Lossy only	Lossy + lossless	Lossless only	Lossy + lossless
File size (1920x1080 photo)	~185 KB	~450 KB	~290 KB	~5.9 MB	~220 KB
Color depth	10/12-bit	8-bit	8-bit	8/16-bit	10/12-bit
Transparency	Yes	No	Yes	Yes	Yes
Animation	Yes	No	Yes	APNG only	Yes
HDR support	Yes	No	No	No	Yes
Browser support	~93% global	~100%	~97%	~100%	Safari only
Encoding speed	Slow	Fast	Fast	Fast	Fast
Patent licensing	Royalty-free	Royalty-free	Royalty-free	Royalty-free	HEVC patents
Best for	Web images, HDR, photography	Universal sharing	General web images	Graphics, screenshots	Apple ecosystem

Key takeaways from this comparison:

AVIF vs JPEG: AVIF produces files roughly 50-60% smaller at equivalent quality. JPEG's only advantage is universal compatibility — every device, browser, and application on earth reads JPEG. For web delivery where you can use <picture> fallbacks, AVIF is strictly better.
AVIF vs WebP: AVIF compresses 20-50% more efficiently than WebP. WebP encodes dramatically faster (milliseconds vs seconds) and has 4% more browser coverage. For a detailed comparison with benchmarks, see WebP vs AVIF: Which Next-Gen Format Wins?.
AVIF vs PNG: Different jobs entirely. PNG is lossless and excels at graphics with sharp edges, text, and transparency. AVIF can do lossless too, but its real advantage is lossy compression of photographs. Use PNG for screenshots and logos; AVIF for photos.
AVIF vs HEIC: Nearly identical compression performance (both are modern codecs with similar capabilities). AVIF wins on licensing — royalty-free vs HEVC's patent pools — which is why AVIF has cross-browser support and HEIC does not. Read more in What Is HEIC?.

For a complete format decision framework, see Best Image Format for Web.

Browser and Platform Support

AVIF support reached a tipping point in late 2022 when Safari 16.1 added support, completing coverage across all major browsers. Here is the current state:

Browser	AVIF Support Since	Version
Chrome (desktop + Android)	August 2020	85+
Firefox	October 2021	93+
Safari (macOS + iOS)	October 2022	16.1+
Edge	August 2020	85+
Opera	September 2020	71+
Samsung Internet	2023	20+

As of March 2026, AVIF has approximately 93% global browser coverage. The remaining 7% is mostly older iOS devices stuck on iOS 15 (Safari 15.x), legacy Android phones, and enterprise environments locked to older browser versions.

That 93% is production-ready for most websites — especially when paired with a <picture> fallback:

<picture>
  <source srcset="photo.avif" type="image/avif">
  <source srcset="photo.webp" type="image/webp">
  <img src="photo.jpg" alt="Description of your image" width="800" height="600">
</picture>

The browser picks the first format it supports. Chrome and Firefox grab AVIF. Older Safari grabs WebP. Ancient browsers fall back to JPEG. Everyone sees the image; most users get the smallest version.

Beyond Browsers

macOS: Native support since macOS Ventura (13.0). Preview, Finder thumbnails, and Photos all handle AVIF.
iOS: Supported since iOS 16. AVIF images render in Safari, Messages, and third-party apps that use system image decoders.
Windows: Windows 11 displays AVIF natively. Windows 10 requires the AV1 Video Extension from the Microsoft Store (free).
Linux: libavif and loaders (gdk-pixbuf, Qt) provide support in most desktop environments.
Adobe tools: Photoshop 23.2+ and Lightroom Classic 11.3+ read AVIF. Export support varies.

When to Use AVIF

AVIF is the right choice when compression efficiency is the priority and encoding time is a one-time cost.

Web images on high-traffic pages. A 30-50% reduction over WebP translates directly to faster load times, better Core Web Vitals, and lower CDN costs. On a page with 20 product images, switching from WebP to AVIF can save 1-2 MB per page load.

Photography and complex imagery. AVIF excels at photographs — smooth gradients, skin tones, and complex textures compress significantly better than with JPEG or WebP. The difference is most visible at aggressive compression levels where JPEG shows blocking artifacts and AVIF stays clean.

HDR content. AVIF is the only web-compatible format that supports 10-bit and 12-bit HDR with PQ or HLG transfer functions. If you are producing content for HDR displays, AVIF preserves the luminance range that WebP (8-bit only) cannot represent.

Images that need transparency and small file sizes. PNG gives you transparency but with large lossless files. WebP gives you lossy transparency but at larger sizes than AVIF. AVIF gives you both: lossy compression with full alpha channel support, producing the smallest transparent images of any web format.

Static sites and pre-built assets. Blog posts, marketing pages, and e-commerce product listings where images are encoded once at build time and served millions of times. The slow encoding is amortized across all those page views.

When NOT to Use AVIF

AVIF is not the right tool for every situation. Know its weaknesses.

When encoding speed matters. AVIF encoding is dramatically slower than WebP or JPEG — roughly 47x slower at default settings (see WebP vs AVIF for benchmarks). User-generated content platforms, real-time image processing pipelines, and dynamic resizing services cannot afford multi-second encoding times per image.

When you need universal compatibility without fallbacks. At 93% browser support, roughly 7% of users see nothing if you serve AVIF without a fallback. For email images, social media embeds, and any context where you cannot control the <picture> element, stick with JPEG or WebP.

When tooling compatibility is critical. AVIF support in design tools, CMS platforms, and image editing software is still catching up. WordPress added AVIF upload support in version 6.5, but many plugins and themes have not updated their image processing pipelines. If your workflow relies on tools that do not handle AVIF, you will spend more time fighting the toolchain than saving bytes.

Animated content. Animated AVIF is technically supported in Chrome and Firefox, but tooling is immature compared to animated WebP or MP4 video. For animated web content, WebP or short video loops are more reliable.

Lossless graphics. For screenshots, logos, and text-heavy graphics, PNG remains the safer choice. AVIF lossless mode exists but is less commonly used, and PNG's universal support and mature tooling make it the path of least resistance. WebP lossless is the better modern alternative for these use cases — see PNG vs WebP.

How to Convert Images to AVIF

In the Browser with Pixotter

The fastest way to convert any image to AVIF — no install, no upload to a remote server:

Go to Pixotter's Convert tool
Drop your image (JPEG, PNG, WebP, HEIC, BMP, TIFF, or GIF)
Select AVIF as the output format
Download the converted file

Everything runs in your browser via WebAssembly. Your images never leave your device — there is no server upload, no waiting in a queue, no privacy concern. Batch conversion works the same way: drop multiple files and convert them all at once.

Need to go the other direction? Pixotter also converts FROM AVIF to JPEG, PNG, or WebP. Same tool, same process — just select a different output format. For step-by-step guides, see How to Convert AVIF to JPG and How to Convert AVIF to PNG. Once converted, you can compress your images further to hit specific file size targets.

Command Line

For build pipelines and batch processing, avifenc from libavif v1.0.x (BSD 2-Clause license) is the standard tool:

# Standard lossy AVIF — good balance of quality and size
avifenc --speed 6 -q 60 input.jpg output.avif

# Best compression (slow — use for pre-built static assets only)
avifenc --speed 0 -q 60 input.jpg output.avif

# Faster encoding (speed 8 — less compression, much faster)
avifenc --speed 8 -q 60 input.jpg output.avif

# Batch encode all JPEGs in a directory
for f in *.jpg; do avifenc --speed 6 -q 60 "$f" "${f%.jpg}.avif"; done

The --speed flag ranges from 0 (best compression, slowest) to 10 (fastest, least compression). Speed 6 is a solid default for most use cases. Speed 0 produces the smallest files but can take 30-60 seconds per image.

The -q flag controls quality (0-100). Quality 60 produces results comparable to JPEG quality 80-85. For photographs where quality matters, try -q 70. For aggressive compression on thumbnails, -q 40 works well.

In Build Pipelines

Sharp (MIT license, v0.33.x) handles AVIF in Node.js:

const sharp = require('sharp'); // v0.33.x

await sharp('input.jpg')
  .avif({ quality: 60, speed: 6 })
  .toFile('output.avif');

For understanding how lossy and lossless modes differ across formats, see Lossy vs Lossless Compression.

Frequently Asked Questions

Is AVIF better than JPEG?

For web delivery, yes. AVIF produces files 50-60% smaller than JPEG at equivalent visual quality, supports transparency, HDR, and animation — none of which JPEG can do. JPEG's advantage is universal compatibility: every device on earth reads it. Use AVIF with a JPEG fallback via the <picture> element to get both.

Is AVIF the same as AV1?

Not exactly. AV1 is a video codec — it compresses moving video frames. AVIF is a still-image format that uses AV1 to compress individual frames, packaged in a HEIF-based container. The relationship is similar to how WebP uses the VP8 video codec for still images.

Can I use AVIF files on my website right now?

Yes. With ~93% global browser support (Chrome, Firefox, Safari 16.1+, Edge), AVIF is production-ready. Use the <picture> element with WebP and JPEG fallbacks to cover the remaining 7%. The browser automatically selects the best format it supports.

Why is AVIF encoding so slow?

AV1 was designed for video encoding on powerful hardware. Its large block sizes (up to 128x128), 50+ prediction modes, and sophisticated filtering produce excellent results but require significant computation. At default speed settings, AVIF encodes roughly 47x slower than WebP. Hardware AV1 encoders (Intel Arc, AMD RDNA 3+, NVIDIA Ada) are narrowing this gap.

Does AVIF support transparency?

Yes. AVIF supports a full alpha channel with both lossy and lossless compression of the alpha plane. This makes AVIF the smallest option for transparent images on the web — smaller than PNG (lossless only) and smaller than WebP with alpha.

Is AVIF free to use?

Completely. AV1 was developed by the Alliance for Open Media specifically to be royalty-free. Any person or organization can encode, decode, and serve AVIF images without paying licensing fees. This is a deliberate contrast to HEVC/H.265 (used in HEIC), which requires patent licensing.

How to Convert AVIF to JPG (5 Free Methods)

Pixotter — Tue, 31 Mar 2026 00:47:21 +0000

How to Convert AVIF to JPG (5 Free Methods)

You received an image in AVIF format and your software cannot open it. Or you downloaded a photo from a modern website and realized it saved as .avif instead of the JPEG you expected. AVIF is the newest image format on the web — better compression than both JPEG and WebP — but tool support outside browsers is still catching up.

Converting AVIF to JPG takes seconds. Here are five free methods, from browser-based instant conversion to command-line batch processing.

Method 1: Convert AVIF to JPG in Your Browser

Pixotter's format converter handles AVIF natively. The conversion runs entirely in your browser — nothing is uploaded to any server.

Open pixotter.com/convert and select JPG as the output format.
Drop your AVIF file(s) onto the page. Batch conversion is supported.
Adjust the quality slider if needed (85% is a good default for photos).
Click Convert and download.

The conversion uses libvips compiled to WebAssembly. It decodes the AVIF using the AV1 codec and re-encodes as JPEG — all locally on your device, in milliseconds for typical images.

Why this is the easiest method: No software to install, no account to create, works on any operating system with a modern browser (Windows, Mac, Linux, Chromebook).

Method 2: ImageMagick (Command Line)

ImageMagick 7.1.1-29+ (Apache 2.0 license) supports AVIF when compiled with libheif and libaom.

# Single file
magick input.avif output.jpg

# With quality control
magick input.avif -quality 90 output.jpg

# Batch convert all AVIF files in current directory
for f in *.avif; do
    magick "$f" -quality 85 "${f%.avif}.jpg"
done

Check AVIF support: Run magick identify -list format | grep AVIF. If AVIF appears in the output, your ImageMagick build supports it. If not, you need to rebuild or install a package with AVIF support enabled.

Install with AVIF support:

# Ubuntu 24.04+ (AVIF support included)
sudo apt install imagemagick

# macOS (Homebrew — AVIF support included by default)
brew install imagemagick

# Windows
winget install ImageMagick.ImageMagick

Method 3: FFmpeg (Video and Image Swiss Knife)

FFmpeg 7.0 (LGPL/GPL) decodes AVIF via its AV1 decoder:

# Single file
ffmpeg -i input.avif output.jpg

# With quality control (-q:v 2 = high quality, range 1-31)
ffmpeg -i input.avif -q:v 2 output.jpg

# Batch convert
for f in *.avif; do
    ffmpeg -i "$f" -q:v 2 "${f%.avif}.jpg"
done

FFmpeg is a good choice if you already have it installed for video work. For image-only tasks, ImageMagick has a simpler syntax.

Method 4: libavif Tools (Dedicated AVIF Toolkit)

libavif 1.0.4 (BSD-2-Clause) is the reference AVIF library. It includes avifdec, a dedicated AVIF decoder.

# Install (Ubuntu/Debian)
sudo apt install libavif-bin

# macOS
brew install libavif

# Decode AVIF to PNG (avifdec outputs PNG by default)
avifdec input.avif output.png

# Then convert PNG to JPG with ImageMagick or sips
magick output.png -quality 85 output.jpg

avifdec does not output JPG directly — it decodes to PNG or Y4M. For a direct AVIF-to-JPG pipeline, ImageMagick or Pixotter is simpler.

Method 5: macOS Preview

macOS Ventura (13.0) and later support AVIF natively:

Double-click the AVIF file to open it in Preview.
File → Export.
Change format to JPEG and adjust quality.
Save.

For batch conversion: select multiple AVIF files in Finder → right-click → Open With → Preview → Edit → Select All → File → Export Selected Images → choose JPEG.

Note: macOS versions before Ventura do not support AVIF. If Preview cannot open your AVIF file, use Pixotter's browser-based converter instead.

AVIF vs JPG Comparison

Feature	AVIF	JPG
Compression efficiency	30-50% smaller than JPG at same quality	Baseline
Compression type	Lossy and lossless	Lossy only
Color depth	8-bit, 10-bit, 12-bit	8-bit
HDR support	Yes	No
Transparency	Yes (alpha channel)	No
Animation	Yes (AVIF sequences)	No
Encoding speed	Slow (seconds for high quality)	Fast (milliseconds)
Browser support	Chrome 85+, Firefox 93+, Safari 16.4+	Universal
Non-browser support	Growing but incomplete	Universal

AVIF is the technically superior format — smaller files, wider color gamut, HDR support. But JPG remains the universal compatibility choice. If you need to share an image and cannot guarantee the recipient has AVIF support, JPG is the safe option.

For a detailed look at how AVIF compares to other modern formats, see What is AVIF? and WebP vs AVIF.

Why AVIF Files Exist (and Why You Are Seeing More of Them)

AVIF (AV1 Image File Format) uses the AV1 video codec for still image compression. It was standardized in 2019 by the Alliance for Open Media — the same consortium behind the AV1 video codec, which includes Google, Apple, Microsoft, Netflix, Mozilla, and Amazon.

AVIF adoption is accelerating because:

Browser support is now universal. Chrome, Firefox, Safari, and Edge all support AVIF as of 2024.
CDNs auto-convert to AVIF. Services like Cloudflare, Fastly, and Akamai can automatically serve AVIF to supported browsers. Users download AVIF without knowing it.
CMS platforms support it. WordPress 6.5+, Shopify, and most modern platforms accept AVIF uploads.

The result: more websites serve AVIF images, more browsers download AVIF files, and more users encounter .avif files they need to convert for non-browser contexts. See Best Image Format for Web for where AVIF fits in the broader format landscape.

Frequently Asked Questions

Does converting AVIF to JPG reduce quality?

Yes, marginally. AVIF and JPG both use lossy compression. Converting between them introduces a small generation loss — the image is decoded from AVIF and re-encoded as JPG. At JPEG quality 85-90, the loss is typically imperceptible for photos. The bigger impact is the format difference: JPG cannot represent AVIF's 10-bit color depth or HDR — these are reduced to 8-bit sRGB during conversion.

Can I batch convert AVIF files to JPG?

Yes. Pixotter supports batch conversion in the browser. ImageMagick and FFmpeg both handle batch processing via shell loops. See the code examples above.

Why is AVIF better than JPG?

AVIF compresses 30-50% more efficiently — the same photo at the same perceptual quality is significantly smaller as AVIF. AVIF also supports transparency, animation, HDR, and color depths up to 12-bit. The tradeoff is slower encoding and less universal tool support. For web delivery, AVIF is increasingly the best choice. For sharing and compatibility, JPG remains the standard.

Can I convert AVIF to PNG instead of JPG?

Yes. If you need lossless output or transparency preservation, convert to PNG instead of JPG. Use the same tools — Pixotter, ImageMagick, or FFmpeg — and specify PNG as the output format. PNG files will be larger than JPG but preserve every pixel exactly. For a complete walkthrough, see How to Convert AVIF to PNG. For more on when PNG makes sense, see What is PNG?.

My software cannot open AVIF files. What should I do?

Convert the AVIF to JPG or PNG using any method in this guide. The fastest option is Pixotter's browser converter — no install required. For a broader look at opening modern image formats, see How to Open WebP Files (the same principles apply to AVIF).

Is AVIF the same as HEIC?

No. Both use modern video codecs for image compression, but they use different codecs: AVIF uses AV1, HEIC uses HEVC (H.265). AVIF is open and royalty-free; HEIC has licensing fees. Both are stored in the HEIF container format, but they are not interchangeable. See What is HEIC? for more on the HEIC format.

How to Compress a GIF Without Losing Quality

Pixotter — Mon, 30 Mar 2026 06:57:07 +0000

How to Compress a GIF (Reduce File Size Without Ruining It)

Animated GIFs eat storage and bandwidth like nothing else. A 5-second screen recording can weigh 15 MB. A reaction GIF pulled from Giphy might be 8 MB. Try emailing that, uploading it to Slack, or embedding it in a blog post — file size limits hit fast.

The fix: compress the GIF. You can cut 40-80% of the file size while keeping the animation smooth and the colors intact. Here is how.

The Fastest Method: Compress GIF in Your Browser

Pixotter's GIF compressor processes GIF files entirely in your browser using WebAssembly. No file upload, no server-side processing, no file size caps.

Open pixotter.com/compress-gif.
Drop your GIF file onto the page (animated GIFs are fully supported).
Adjust the quality slider if needed — the default works well for most GIFs.
Click Compress and download the result.

The compression runs locally on your device using libvips compiled to WebAssembly. Your GIF never leaves your computer.

Why this matters: Most online GIF compressors upload your file to a remote server, process it, and send it back. That adds latency, imposes file size limits (often 5-20 MB), and means your images pass through someone else's infrastructure. Pixotter processes everything client-side — there is nothing to upload.

Batch processing is supported. Drop multiple GIFs at once and download all the compressed versions when they are ready.

How GIF Compression Works

GIF uses the LZW (Lempel-Ziv-Welch) compression algorithm — a form of lossless compression that looks for repeating byte patterns and replaces them with shorter codes. Every GIF is already compressed at the encoding level. So when we say "compress a GIF," we mean one of four things:

1. Reduce the Color Palette

GIF supports a maximum of 256 colors per frame. Many GIFs use all 256 even when the image only needs 64 or 128. Reducing the palette from 256 to 128 colors can cut file size by 20-40% with minimal visible change. Drop to 64 colors and the savings increase — but color banding becomes noticeable on gradients and photographic content.

2. Reduce Frame Rate

An animated GIF at 30 fps contains twice as many frames as one at 15 fps. Cutting the frame rate in half roughly halves the file size. Most GIF animations look fine at 10-15 fps — the format was never designed for smooth video playback, and viewers expect slightly choppy GIF motion.

3. Reduce Dimensions

A 1200×800 GIF carries 4× the pixel data of a 600×400 GIF. If the GIF will be displayed at a smaller size (in a chat message, a blog sidebar, an email), resizing before or during compression produces dramatic savings. A 400px-wide GIF covers most use cases.

4. Optimize LZW Encoding

Tools like Gifsicle optimize the LZW compression itself — reordering color tables, stripping unnecessary metadata, and improving inter-frame delta encoding (storing only the pixels that change between frames instead of re-encoding full frames). This is true lossless optimization: the output looks identical to the input, just stored more efficiently.

Five Ways to Compress a GIF

Method	Type	Batch Support	Animated GIF	Platform	Cost
Pixotter	Lossy + lossless	Yes	Yes	Browser (any OS)	Free
Gifsicle 1.95	Lossless + lossy	Yes (CLI)	Yes	Windows, macOS, Linux	Free (GPLv2)
FFmpeg 7.0	Lossy (re-encode)	Yes (CLI)	Yes	Windows, macOS, Linux	Free (LGPL/GPL)
GIMP 2.10.36	Manual optimization	No	Yes (frame-by-frame)	Windows, macOS, Linux	Free (GPLv3)
ezgif.com	Lossy + lossless	No	Yes	Browser	Free (with ads)

Method 1: Pixotter (Browser, No Install)

Open pixotter.com/compress-gif, drop your GIF, adjust quality, download. Works on any device with a modern browser — Windows, Mac, Linux, Chromebook, iPad.

Best for: quick compression without installing software. Handles animated GIFs natively.

Method 2: Gifsicle (Command Line)

Gifsicle 1.95 (GPLv2) is the gold standard for GIF optimization. It operates directly on the GIF structure without full re-encoding.

# Install
# macOS: brew install gifsicle
# Ubuntu/Debian: sudo apt install gifsicle
# Windows: download from lcdf.org/gifsicle

# Lossless optimization (reorder colors, strip metadata, optimize frames)
gifsicle -O3 input.gif -o optimized.gif

# Lossy compression (--lossy=80 is a good starting point)
gifsicle -O3 --lossy=80 input.gif -o compressed.gif

# Reduce colors to 128
gifsicle --colors 128 -O3 input.gif -o reduced.gif

# Resize to 400px wide (maintains aspect ratio)
gifsicle --resize-width 400 -O3 input.gif -o smaller.gif

# Combine: resize + lossy + color reduction
gifsicle --resize-width 400 --lossy=80 --colors 128 -O3 input.gif -o final.gif

The -O3 flag enables maximum optimization effort. The --lossy flag introduces controlled quality loss — values from 30 (subtle) to 200 (aggressive) control how much inter-frame noise is tolerated. Start at 80 and adjust.

Batch processing:

# Compress every GIF in the current directory
for f in *.gif; do
    gifsicle -O3 --lossy=80 "$f" -o "compressed_$f"
done

Method 3: FFmpeg (Re-encode with Better Settings)

FFmpeg 7.0 (LGPL/GPL) can re-encode GIF animations with an optimized color palette. This approach often produces the best compression ratios for photographic or video-derived GIFs.

# Step 1: Generate an optimized palette from the GIF
ffmpeg -i input.gif -vf "palettegen=max_colors=128:stats_mode=diff" palette.png

# Step 2: Re-encode the GIF using that palette
ffmpeg -i input.gif -i palette.png -lavfi "paletteuse=dither=bayer:bayer_scale=5" compressed.gif

# One-liner (generates palette and re-encodes in one pass)
ffmpeg -i input.gif -vf "fps=15,scale=400:-1:flags=lanczos,split[s0][s1];[s0]palettegen=max_colors=128[p];[s1][p]paletteuse=dither=bayer:bayer_scale=3" output.gif

The one-liner combines three optimizations: reduce to 15 fps, resize to 400px wide, and use a 128-color optimized palette with Bayer dithering. This is the nuclear option — maximum size reduction.

When FFmpeg beats Gifsicle: When the GIF was originally created from video with a suboptimal palette. FFmpeg can re-analyze the entire animation and generate a better global palette, while Gifsicle works within the existing color table.

Method 4: GIMP (Manual Frame Editing)

GIMP 2.10.36 (GPLv3) opens animated GIFs as layers (one layer per frame). You can delete unnecessary frames, crop the canvas, reduce colors, and re-export.

Open the GIF in GIMP — each frame becomes a layer.
Delete every other layer to cut frame rate in half.
Image → Canvas Size to crop if there are unused borders.
Image → Mode → Indexed → set maximum colors (try 128).
File → Export As → .gif → check As animation → set frame delay.

This is the most labor-intensive method but gives you frame-level control. Useful when you need to remove specific frames or crop a specific region of the animation.

Method 5: ezgif.com (Browser, Simple UI)

Upload your GIF to ezgif.com/optimize. Choose a compression level and download. Maximum upload size is 50 MB. Processing happens server-side — your file is uploaded to their infrastructure.

ezgif is convenient for one-off compressions when you cannot install software. For regular use or batch work, Pixotter (client-side, no upload) or Gifsicle (CLI, scriptable) are better choices.

GIF Compression Benchmarks

Real compression results on three common GIF types:

Test 1: Screen Recording (720×480, 8 seconds, 3.2 MB)

Method	Output Size	Reduction	Visual Quality
Gifsicle -O3 (lossless)	2.8 MB	12%	Identical
Gifsicle --lossy=80	1.9 MB	41%	Very good
Gifsicle --lossy=80 --colors=128	1.4 MB	56%	Good — slight banding in gradients
FFmpeg (128 colors, 15fps)	1.1 MB	66%	Good — slightly choppier animation
FFmpeg (64 colors, 10fps, 400px)	420 KB	87%	Acceptable for thumbnails

Test 2: Reaction GIF (480×270, 3 seconds, 4.8 MB)

Method	Output Size	Reduction	Visual Quality
Gifsicle -O3 (lossless)	4.5 MB	6%	Identical
Gifsicle --lossy=80	2.9 MB	40%	Very good
FFmpeg (128 colors, 15fps)	1.8 MB	63%	Good
Resize to 320px + lossy	980 KB	80%	Acceptable for chat

Test 3: UI Animation (600×400, 5 seconds, 1.1 MB)

Method	Output Size	Reduction	Visual Quality
Gifsicle -O3 (lossless)	890 KB	19%	Identical
Gifsicle --lossy=80	620 KB	44%	Very good
Gifsicle --colors=64	480 KB	56%	Good — flat colors compress well

Pattern: Lossless optimization saves 5-20%. Lossy compression saves 35-55%. Combining lossy + color reduction + resize can save 60-90%.

When to Convert GIF to WebP Instead

Sometimes the best way to "compress" a GIF is to stop using GIF entirely. Animated WebP produces files 25-50% smaller than an equivalent optimized GIF, with better color support (24-bit vs 8-bit) and smoother gradients.

Feature	GIF	Animated WebP
Max colors	256 per frame	16.7 million (24-bit)
Compression	LZW (lossless only)	VP8 lossy or VP8L lossless
Transparency	1-bit (on/off)	Full 8-bit alpha
File size	Baseline	25-50% smaller
Browser support	Universal	All modern browsers (since 2020)
Lossy mode	No	Yes

When to convert GIF to WebP:

The GIF will be displayed on a website and you control the markup
File size is the primary constraint
The animation has photographic content or gradients (WebP handles these far better)

When to keep GIF:

The GIF is shared on platforms that do not support WebP (some chat apps, older email clients)
You need universal compatibility above all else
The GIF is a simple animation with few colors where the format difference is negligible

To convert: drop your GIF into Pixotter's GIF to WebP converter and select WebP as the output format. The animated frames are preserved automatically. For a deeper format comparison, see What is GIF? and Best Image Format for Web.

GIF File Size Limits by Platform

Knowing the target platform helps you decide how aggressively to compress:

Platform	Max GIF Size	Notes
Discord	25 MB (free), 50 MB (Nitro)	Most GIFs are fine; compress for mobile data
Slack	20 MB	Workspace admins may set lower limits
Twitter/X	15 MB	Auto-converted to MP4 on upload
Tumblr	10 MB per image	Dashboard displays up to 3 MB smoothly
Reddit	20 MB	Subreddits may enforce smaller limits
Email	5-10 MB (practical)	Many providers block or clip large attachments
GitHub Issues	10 MB	Compressed GIFs or convert to MP4 for demos
WordPress	Server-dependent	Default upload limit often 2-8 MB

If your GIF exceeds the platform limit, compress to fit. If it is already under the limit, compress anyway — smaller GIFs load faster, use less bandwidth on mobile connections, and create a better experience for viewers.

Tips for Smaller GIFs

Record at the smallest dimensions you need. Capturing a 1920×1080 screen recording and then resizing to 600px throws away 90% of the pixel data after encoding the full resolution. Capture at 600px from the start.

Limit animation length. A 2-second loop is more shareable than a 10-second clip. Each additional second adds proportional file size.

Minimize movement. GIF inter-frame compression stores only the pixels that change between frames. If the entire frame changes (camera movement, full-screen transitions), every frame is stored in full. Static backgrounds with localized motion compress dramatically better.

Use a dark or solid background. Gradients and photographic backgrounds require more colors and resist GIF's 256-color palette. A solid dark background compresses efficiently and keeps the focus on the subject.

Remove the first and last frames. Many screen recording tools capture a blank or static frame at the beginning and end. These frames add file size without adding content.

Try lossy before reducing colors. Gifsicle's --lossy flag produces better results than aggressive color reduction for most content. A GIF with 256 colors and lossy=80 typically looks better than a GIF with 64 colors and no lossy compression.

Need to edit before compressing? Pixotter also handles GIF resizing, speed adjustment, reversing, and cropping — all in-browser. Crop or resize first, then compress for maximum savings.

Frequently Asked Questions

Does compressing a GIF remove the animation?

No. All methods described here preserve animation. Frame timing, loop count, and playback behavior remain intact. The compression reduces file size by optimizing how the frames are stored, not by removing them (unless you explicitly reduce the frame rate).

How much can I compress a GIF?

Lossless optimization typically saves 5-20%. Lossy compression saves 35-55%. Combining lossy compression with color reduction and resizing can save 60-90%. The exact savings depend on the GIF content — screen recordings with large static areas compress better than photographic GIFs.

What is the difference between lossy and lossless GIF compression?

Lossless compression (Gifsicle -O3) reorganizes the internal data structure without changing any pixels. The output is visually identical to the input. Lossy compression (Gifsicle --lossy, FFmpeg re-encoding) introduces small changes to pixels that allow more efficient storage. The differences are usually imperceptible at moderate settings but become visible at aggressive compression levels. See Lossy vs Lossless Compression for the full technical breakdown.

Should I convert my GIF to MP4 instead?

If the GIF will only be displayed on a website, yes — MP4 (H.264) produces files 80-95% smaller than equivalent GIFs. Replace the <img> tag with a muted, looping <video> element. The tradeoff: MP4 does not autoplay in all contexts (email, some chat apps, forums), and creating an MP4 requires FFmpeg or a similar tool. GIF works everywhere without any viewer configuration.

Can I compress a GIF without losing quality?

Yes. Lossless optimization tools (like Gifsicle with -O3 and no --lossy flag) reorder the color table, strip unnecessary metadata, and improve inter-frame delta encoding without changing any visible pixels. Savings are modest (5-20%) but guaranteed to be zero-quality-loss.

Why are GIF files so large compared to other formats?

Three reasons: (1) GIF animation stores each frame independently or as a delta from the previous frame, with no inter-frame prediction like video codecs use. (2) LZW compression is less efficient than modern algorithms like VP8 (WebP) or AV1 (AVIF). (3) GIF has no lossy mode — you get lossless or nothing, whereas lossy formats trade controlled quality loss for dramatic size savings. For a comparison with more modern alternatives, see What is GIF? and WebP vs AVIF.

What is the best GIF compressor?

For command-line batch work: Gifsicle 1.95 with --lossy=80 -O3. For browser-based compression without installing anything: Pixotter's GIF compressor. For maximum compression when you can re-encode: FFmpeg with an optimized palette. Each tool has strengths — Gifsicle is fast and simple, Pixotter requires no install, FFmpeg offers the most control over palette and frame rate.

Best WordPress Image Optimization Plugins (2026)

Pixotter — Sun, 29 Mar 2026 12:31:53 +0000

Best WordPress Image Optimization Plugins in 2026

Unoptimized images are the single biggest reason WordPress sites load slowly. A typical blog post with five photos can weigh 10-15 MB before optimization — enough to push your Largest Contentful Paint past 4 seconds and tank your Core Web Vitals score.

A WordPress image optimization plugin fixes this automatically. It compresses images on upload, resizes oversized files, converts to modern formats like WebP, and in some cases serves images through a CDN. The right plugin cuts page weight by 50-80% without visible quality loss.

Here is how the top plugins compare as of March 2026, with honest recommendations for different budgets and use cases.

What Image Optimization Plugins Actually Do

Before comparing specific plugins, here is what you are evaluating:

Compression — reducing file size through lossy (some quality loss, much smaller files) or lossless (no quality loss, moderate savings) algorithms. Most plugins offer both. Some add a "glossy" or "smart" mode that is lossy but nearly imperceptible.
Resizing — scaling down images that exceed a maximum width or height. A 4000 x 3000 photo uploaded from a phone gets resized to, say, 2048 x 1536 before compression even starts.
Format conversion — converting JPEG and PNG uploads to WebP or AVIF for modern browsers. WebP alone saves 25-50% over JPEG at equivalent quality. AVIF pushes that further. See our format comparison guide for the full breakdown.
Lazy loading — deferring off-screen images until the user scrolls to them. WordPress 5.5+ includes native lazy loading via the loading="lazy" attribute, so this is less of a differentiator than it was in 2020.
CDN delivery — some plugins serve optimized images from edge servers instead of your host. This matters most for sites with global audiences or cheap hosting with slow I/O.

Not every plugin does all five. Some specialize. The comparison table below maps exactly which features each plugin covers.

WordPress Image Optimization Plugin Comparison

This is the table you came here for. Every column matters for different use cases, so read horizontally for the plugin that matches your priorities.

Plugin	Free Tier	Compression Modes	WebP	AVIF	CDN	Processing	License	Actively Maintained
Imagify	20 MB/month (~40-60 images)	Lossy, lossless, ultra	Yes	Yes	Yes (via WP Rocket)	Cloud	Proprietary	Yes
ShortPixel	100 images/month (~150-500 MB)	Lossy, lossless, glossy	Yes	Yes	Yes (addon)	Cloud	Proprietary	Yes
Smush	50 images/batch, 5 MB/image cap	Lossy, lossless	Pro only	No	Pro only	Cloud	GPLv2 (free), Proprietary (Pro)	Yes
EWWW Image Optimizer	Unlimited (local mode)	Lossy, lossless	Yes	No	Paid addon	Local or cloud	GPLv3	Yes
Converter for Media	Unlimited	N/A (conversion only)	Yes	Yes	No	Local	GPLv2	Yes

Key takeaway: ShortPixel offers the most generous free tier. EWWW is the only plugin with truly unlimited free compression (using local CPU). Imagify has the best UI but the smallest free tier. Smush locks too many features behind its Pro paywall to recommend on the free tier. Converter for Media is not a compressor — it pairs with any of the above.

Imagify

Made by: WP Media (the team behind WP Rocket)
License: Proprietary
Pricing: Free (20 MB/month), Growth ($5.99/month for 500 MB), Infinite ($9.99/month for unlimited)

Imagify is the most polished option in this list. The interface is clean, the WordPress integration is seamless, and if you already use WP Rocket, the two plugins work together — WP Rocket handles caching and CDN delivery while Imagify handles compression and WebP/AVIF conversion.

Imagify offers three compression modes: Normal (lossless), Aggressive (lossy, good balance), and Ultra (maximum compression, some visible quality loss on detailed images). Aggressive mode is the sweet spot for most sites — it typically saves 60-70% with no perceptible quality difference on web-sized images.

The catch is the free tier. Twenty megabytes per month is roughly 40-60 compressed images depending on originals. For a personal blog that publishes once a week with 2-3 images per post, that might work. For anything busier, you are hitting the paywall within a week. If you commit to paying, Imagify is excellent. If you want to stay free, look elsewhere.

Best for: WP Rocket users, sites that prioritize UI quality, teams willing to pay for a polished experience.

ShortPixel

Made by: ShortPixel
License: Proprietary
Pricing: Free (100 images/month), Short ($3.99/month for 5,000 images), or one-time credit packs starting at $9.99 for 10,000 images

ShortPixel is the plugin I recommend to most people. The free tier is the most generous in the category — 100 images per month covers small blogs entirely. The paid tiers are cheaper than Imagify, and the one-time credit option is ideal for sites that do occasional bulk optimization rather than steady uploads.

ShortPixel's glossy compression mode deserves specific mention. It sits between lossy and lossless — applying stronger compression than lossless while preserving more detail than standard lossy. For photography-heavy sites where subtle quality differences matter, glossy mode produces noticeably better results than Imagify's Aggressive or Smush's lossy at comparable file sizes.

ShortPixel also offers a standalone desktop tool and a web optimizer that work without WordPress. If you run multiple sites across different platforms, ShortPixel's ecosystem makes more sense than a WordPress-only plugin.

WebP and AVIF conversion are included in all tiers. CDN delivery is available through the ShortPixel Adaptive Images companion plugin.

Best for: Most WordPress sites. Best balance of free tier generosity, compression quality, and pricing.

Smush (WPMU DEV)

Made by: WPMU DEV
License: GPLv2 (free version), Proprietary (Pro)
Pricing: Free (limited), Pro ($3/month standalone or included in WPMU DEV membership at $3/month for the first year)

Smush is the most installed image optimization plugin in the WordPress directory, with over 1 million active installations. The brand recognition is deserved — Smush was one of the first plugins in this category and WPMU DEV maintains it actively.

That said, the free version has meaningful limitations. The 5 MB per-image cap means any high-resolution photo from a modern phone (which regularly produces 8-15 MB files) needs to be resized before Smush can process it. WebP conversion, CDN delivery, and the most effective compression modes all require Pro. On the free tier, Smush does less than ShortPixel or EWWW.

Smush Pro is a different story. At $3/month it is competitive with ShortPixel and Imagify, and WPMU DEV members get it included alongside a full suite of WordPress management tools (Hummingbird for caching, Defender for security, SmartCrawl for SEO). If you are already in the WPMU DEV ecosystem, Smush Pro is the obvious choice. If you are evaluating plugins independently, ShortPixel or Imagify offer better standalone value.

AVIF is not supported as of March 2026. For sites that want to serve AVIF, this is a dealbreaker.

Best for: Existing WPMU DEV subscribers. Not recommended on the free tier when better free options exist.

EWWW Image Optimizer

Made by: Exactly WWW
License: GPLv3 (open source)
Pricing: Free (unlimited local compression), Premium ($7/month for cloud compression and CDN)

EWWW is the odd one out. Every other plugin on this list sends your images to a cloud server for processing. EWWW can do that too (on the paid tier), but its core feature is local compression — it runs jpegtran, optipng, pngquant, and cwebp directly on your server using your host's CPU.

This has two major implications:

The upside: Unlimited free compression. No monthly quota, no per-image limit, no credit packs. Your images never leave your server, which matters for privacy-sensitive sites handling medical images, legal documents, or any content where cloud processing raises compliance questions.

The downside: Local compression produces smaller savings than cloud-based optimization. EWWW's local mode typically achieves 10-30% file size reduction on JPEGs — solid but below the 50-70% that cloud services achieve with more advanced algorithms. WebP conversion works well locally, but lossy compression quality depends on the tools installed on your server.

If your hosting plan has decent CPU (dedicated or VPS), local mode works well. On cheap shared hosting, local compression can slow down uploads and occasionally time out on large files.

EWWW supports WebP conversion in both local and cloud modes. AVIF is not supported as of March 2026.

Best for: Privacy-conscious sites, developers who prefer open-source tools, sites with generous hosting resources but zero budget for plugins.

Converter for Media

Made by: Mateusz Gbiorczyk
License: GPLv2 (open source)
Pricing: Free (unlimited)

Converter for Media is not a compression plugin. It does one thing: convert your existing JPEG and PNG images to WebP and AVIF, then serve the converted versions to browsers that support them while falling back to originals for older browsers.

Why include it here? Because format conversion alone can save 25-50% in file size — sometimes more than compression. And it pairs with any compressor. Run ShortPixel for compression and Converter for Media for AVIF conversion, for example. The two do not conflict.

Processing happens locally on your server, so there is no monthly limit and no cloud dependency. The plugin uses the GD or Imagick library already installed on most WordPress hosts.

The limitation is clear: no compression, no resizing, no CDN. It supplements the other plugins on this list rather than replacing them.

Best for: Adding WebP/AVIF delivery to any existing setup. Pairs well with EWWW (which lacks AVIF) or with manual pre-upload optimization.

Manual Optimization with Pixotter

Plugins are not the only approach. For sites where plugin overhead matters — or where you want full control over compression settings — optimizing images before uploading to WordPress is a legitimate alternative.

Pixotter processes images entirely in your browser. Drop your images, pick your operations (compress, resize, convert to WebP), and download the optimized files. No upload to any server, no monthly limits, no account required. Your images stay on your machine.

This approach makes sense in specific situations:

Small sites or blogs with occasional uploads. If you publish 2-4 images per week, spending 30 seconds in Pixotter before uploading is faster than configuring and maintaining a plugin.
Sites where plugin count matters. Every active plugin adds PHP execution time to every page load. If you are already running 20+ plugins and trying to reduce overhead, eliminating one is worth considering.
One-time bulk optimization. Migrating a site and want to optimize 500 images once? Pixotter handles that without a monthly subscription.
Privacy-sensitive workflows. Like EWWW's local mode, Pixotter processes everything client-side. Unlike EWWW, it does not require server resources — your browser does the work.

You can also convert images to WebP or AVIF before uploading, which eliminates the need for a server-side conversion plugin entirely. Pair this with WordPress's native lazy loading and you have a lightweight optimization stack with zero plugin dependencies.

For high-volume sites with multiple authors uploading daily, an automated plugin is the better choice — manual optimization does not scale past a handful of uploads per day.

How to Choose the Right Plugin

Skip the feature-by-feature analysis. Here is the decision framework:

Zero budget, small site (under 100 images/month):
Use ShortPixel's free tier. The 100 images/month allowance covers most small blogs, and the compression quality is top-tier. If you want WebP/AVIF conversion on top, add Converter for Media.

Zero budget, larger site or privacy requirements:
Use EWWW Image Optimizer in local mode. Unlimited compression, no cloud dependency, GPLv3 licensed. Add Converter for Media for AVIF support. Accept that compression ratios will be lower than cloud-based alternatives.

Willing to pay, best compression quality:
ShortPixel or Imagify. ShortPixel wins on pricing (especially the one-time credit packs) and glossy mode quality. Imagify wins on UI and WP Rocket integration. Both support WebP and AVIF.

Already using WP Rocket:
Imagify. Same developer, tighter integration, shared CDN infrastructure.

Already using WPMU DEV:
Smush Pro. It is included in your membership and integrates with the rest of the WPMU DEV stack.

Privacy-sensitive or compliance-constrained:
EWWW local mode or pre-upload optimization with Pixotter. Images never leave the device.

Want the simplest possible setup:
Install ShortPixel, set it to glossy mode, enable WebP conversion, and forget about it. Three minutes of configuration, then it handles everything automatically.

Frequently Asked Questions

Do I need an image optimization plugin if my theme already compresses images?

Most WordPress themes do not compress images — they resize them to fit predefined dimensions (thumbnail, medium, large) but save them at default quality settings. That is not the same as optimization. A proper plugin applies compression algorithms that reduce file size by 50-70% beyond what resizing alone achieves. Check your page weight in Chrome DevTools (Network tab, filter by "Img") to see whether your images need further optimization.

Does WordPress automatically create WebP images?

No. WordPress 5.8+ added WebP upload support (you can upload .webp files), and WordPress 6.1+ added server-side WebP generation when the hosting environment supports it. But this only works if your server has libwebp installed, and the default quality settings are conservative. A dedicated plugin gives you control over quality, also handles AVIF, and processes your existing media library — not just new uploads.

Will image optimization plugins slow down my site?

Not during page loads — plugins compress images at upload time, not on each request. There is a brief processing delay when you upload an image (typically 1-5 seconds for cloud processing, longer for local). Some plugins queue bulk optimization as a background process. The only performance consideration is PHP memory usage during bulk operations on shared hosting.

Can I use multiple image optimization plugins together?

Not for the same operation. Running two compression plugins creates conflicts — double compression degrades quality and sometimes increases file size. However, you can combine a compression plugin (ShortPixel, Imagify, EWWW) with a conversion-only plugin (Converter for Media) safely. Just make sure only one plugin handles each operation.

How much space does WebP conversion save compared to JPEG?

WebP typically produces files 25-35% smaller than JPEG at equivalent visual quality. On a site with 1,000 JPEG images averaging 200 KB each (200 MB total), WebP conversion saves roughly 50-70 MB of storage and — more importantly — that bandwidth reduction compounds across every page view. For a deeper comparison, see our PNG vs WebP analysis.

Should I optimize images before uploading even if I use a plugin?

For most sites, no — let the plugin handle it. The exception is images from professional cameras or design tools that produce 20-50 MB originals. Uploading files that large strains your server's upload limits and PHP memory allocation. In that case, resize and compress with Pixotter to bring files under 5 MB before uploading, then let the plugin handle final optimization and format conversion.

Bottom Line

ShortPixel is the best WordPress image optimization plugin for most sites in 2026. It has the most generous free tier, competitive paid plans, excellent glossy compression, and full WebP/AVIF support. Install it, set glossy mode, enable WebP, and your images are handled.

EWWW earns the pick for privacy-first and open-source-first users. Imagify earns it for WP Rocket users. Smush earns it only if you are already paying for WPMU DEV.

For smaller sites or one-off projects, skip the plugin entirely and optimize images with Pixotter before uploading. Zero overhead, zero monthly cost, and you keep full control over the output. For more on reducing image file sizes and optimizing images for search rankings, we have dedicated guides that go deeper.