Uvlio

Command Palette

Search for a command to run...

Back to articles
Technical Article

Image Formats Explained: JPEG, PNG, WebP, AVIF, HEIC, and Resizing Order

Image preparation becomes easier when you separate three decisions: geometry, format, and compression. Geometry decides dimensions and crop. Format decides capabilities such as transparency, animation, compatibility, and compression style. Compression decides final file size and visible quality. Changing everything at once makes problems hard to diagnose. A reliable workflow handles them in order.
Uvlio editorial team by limitcool2026-05-177 min read
Topic coverUtilityImage Resize & CropImage Rotate & Flip

Image Formats Explained: JPEG, PNG, WebP, AVIF, HEIC, and Resizing Order

A practical technical article on choosing image formats, resizing before compression, preserving transparency, and preparing batches for upload.

Guide subject preview
Resize first
Choose format
Compress copy
Tool stack
Image Resize & CropImage Rotate & FlipImage Format ConverterBatch Image Converter
Reading focus
1Resize first
2Choose format
3Compress copy

Original workflow visual

Image Formats Explained: JPEG, PNG, WebP, AVIF, HEIC, and Resizing Order

This original Uvlio visual summarizes the practical path from input inspection to output review for this workflow.
1

Resize first

Review before moving forward

2

Choose format

Review before moving forward

3

Compress copy

Review before moving forward

Maintainer and review note
Maintained by limitcool. Use it to understand the technical model, processing boundaries, privacy risks, and verifiable behavior.
JPEG is good for photos, not transparency

JPEG is a lossy format designed for photographic content. It usually produces small files for photos with gradients and many colors. It does not support transparency and can create artifacts around sharp edges, text, and screenshots. Re-saving a JPEG repeatedly can degrade quality. Use it for ordinary photos when compatibility matters, but avoid it for logos, UI screenshots, line art, and images that need alpha transparency.

PNG preserves sharp edges and alpha

PNG is lossless and supports transparency, making it useful for logos, diagrams, screenshots, and graphics with hard edges. The tradeoff is file size, especially for large photos. A PNG product screenshot may be perfect, while a PNG camera photo may be unnecessarily huge. If the image has text or needs transparent background, PNG is often safer than JPEG. If it is a large photo, consider modern lossy formats instead.

WebP and AVIF improve web delivery

WebP and AVIF can produce smaller web images than older formats in many cases. They support modern compression features, and WebP also supports transparency. AVIF can be excellent for compression but may be slower to encode and less predictable in older workflows. Format choice should follow the destination. A website can often serve modern formats with fallbacks, while a government upload form or older CMS may still require JPEG or PNG.

HEIC is common from phones but not universal

Many phones can capture HEIC or HEIF images because they offer efficient storage. The problem is compatibility. Some browsers, upload forms, and desktop workflows still expect JPEG or PNG. Converting HEIC to JPEG can make sharing easier, but it may remove metadata or change color handling depending on the tool. Keep originals when image quality or provenance matters, and export compatible copies for the destination.

Resize before tuning compression

If an image is 4000 pixels wide but will display at 1200 pixels, resizing first usually saves more than aggressive compression. Compression should be tuned on the final dimensions. Otherwise you may waste effort compressing pixels that will be thrown away later. The same rule applies to batches: establish target dimensions, test one image, then apply settings to the rest.

Metadata and orientation need final checks

Image conversion can strip or preserve metadata depending on settings. It can also change how orientation tags are handled. A phone photo may look correct before conversion and rotate unexpectedly afterward if the metadata was removed without rotating pixels. Inspect the exported file, not only the source preview. If privacy matters, review EXIF after the final export.

A batch workflow that avoids surprises

Choose one representative image from the batch. Crop and resize it to the target dimensions. Export to the intended format. Compare quality, file size, transparency, orientation, and metadata. Only then process the full batch. After batch export, sample a few edge cases: the smallest image, largest image, transparent image, text-heavy image, and phone photo. Batch work is fast only when the settings were proven on realistic examples first.

Common Questions

Should I convert every image to WebP?

Not always. WebP is useful for many web images, but destination compatibility and transparency requirements still matter.

Why did my transparent image get a white background?

It was likely exported to a format or setting that does not preserve alpha transparency, such as ordinary JPEG.

Should I compress before resizing?

Usually resize first, then compress the final dimensions so quality and file size are tuned on the actual output.

What should one sample image include before batch processing?

Choose a sample that represents the hard cases in the batch: transparency if any image has alpha, text if screenshots are included, skin tones if portraits matter, and one large phone photo with orientation metadata. A clean sample can hide problems that appear across the real set.

Why do screenshots often look bad as JPEG?

Screenshots contain sharp text, flat colors, and UI edges. Lossy JPEG compression can create visible artifacts around those edges. PNG or a carefully tuned WebP export is often better for screenshots, while JPEG remains stronger for ordinary photographic content.

Should originals be overwritten during conversion?

No. Keep originals and export derivatives for upload or delivery. If compression, resizing, color handling, or metadata cleanup goes wrong, the original gives you a reliable source for a corrected export instead of forcing quality loss on top of quality loss.