For most WordPress images, start with WebP. It normally delivers a useful reduction over JPEG or PNG while retaining transparency and animation support. Keep PNG for graphics that require lossless detail or transparency, JPEG for photographic originals and compatibility, and evaluate AVIF when your host’s image-processing library and delivery path support it reliably. The correct choice depends on the image’s purpose, your WordPress version and configuration, and the format your visitors actually receive.
Which image format should you use?
There is no single winner for every image. Choose by the job the asset performs, then verify the delivered file rather than trusting its filename.
| Format | Best fit | Important WordPress checks |
|---|---|---|
| WebP | General photos, illustrations and interface images when broad modern-browser support and smaller files are priorities. Supports lossy and lossless compression, transparency and animation. | WordPress has documented support since 5.8. Confirm whether your installation creates WebP sub-sizes or serves converted files. |
| JPEG | Photographic originals, existing media libraries and a compatibility fallback. | WordPress can create WebP versions from JPEG uploads while retaining the JPEG original under the documented default behavior. |
| PNG | Logos, interface art, screenshots and any image requiring transparency or lossless output. | Compare the resulting size. Ensure conversion does not remove alpha transparency or introduce unacceptable artifacts. |
| AVIF | Sites that need to test a newer, highly compressed format and have a fully compatible processing and delivery stack. | WordPress 6.5 support depends on Imagick or LibGD support on the server. Test uploads, thumbnails, caching and fallback delivery. |
| GIF | Existing animated assets or workflows that specifically require GIF compatibility. | Compare playback and file size with animated WebP; WordPress client-side processing lists GIF as a supported input. |
WordPress’s Theme Handbook describes WebP files as around 30% smaller on average than equivalent JPEG or PNG files. That is an average, not a guarantee for your image. WordPress Core separately describes approximately 30% reduction versus JPEG at the same visual quality for its WebP comparisons. Encoder settings, image content and quality targets can produce very different results.
WebP: the practical default for most sites
Why WebP works well
WebP combines lossy and lossless compression, transparency and animation in one format. That makes it suitable for photographs, illustrations, logos with transparent backgrounds and many simple animations. Modern browsers generally support it, and WordPress has documented WebP support since version 5.8.
The Tool Desk
Outbyte PC Repair FREERepair Windows errors before they cause bigger problemsFix Now →Outbyte Driver Updater FREEFix the driver behind crashes, sound loss and screen glitchesFind Drivers →#1 Best Overall
- HTML CSS Design and Build Web Sites
- Comes with secure packaging
- It can be a gift option
What WordPress actually does
Uploading a WebP file does not automatically mean every generated size or page response will be WebP. WordPress normally creates sub-sizes in the original image format unless the site’s configuration changes the output format. Conversely, WordPress’s documented JPEG workflow can create WebP versions of an uploaded JPEG and its sub-sizes while keeping the original JPEG. These are different behaviors controlled by version and configuration.
After uploading, inspect the generated files and the HTML on a representative page. A theme, optimization plugin, CDN or custom image_editor_output_format filter may alter what is generated or served.
When JPEG is still the right choice
JPEG remains a sensible source and fallback for photographs, especially when an existing library, editor or downstream system expects it. It does not provide alpha transparency, and repeated re-saving can accumulate lossy artifacts, so keep a high-quality original outside the browser-delivery pipeline.
Using JPEG as the upload format does not prevent WordPress from producing WebP derivatives. Under the documented default behavior, WordPress keeps the original JPEG and creates WebP versions and WebP sub-sizes. Verify that your site has this behavior enabled rather than assuming every host uses the same settings.
When PNG beats WebP or JPEG
Choose PNG when exact, lossless edges or transparency matter more than the smallest possible file. Typical examples include logos, UI screenshots, diagrams with text and graphics with a transparent background. A photographic PNG can be unnecessarily large, so compare it with a high-quality WebP or AVIF at the same visual size.
- Check that transparent pixels remain transparent after any conversion.
- Inspect small text and one-pixel lines at 100% zoom.
- Compare the delivered file size, not just the upload size.
WordPress lists PNG and WebP among its supported media types, but a MIME entry does not guarantee that a particular host can decode, resize, convert, cache or deliver every format.
Is AVIF worth using in WordPress?
What WordPress supports
WordPress 6.5 added AVIF support, conditional on support in the server’s image-processing library. The Core announcement specifically identifies Imagick and LibGD. Therefore, “WordPress supports AVIF” is not enough to establish that your host does.
Test the entire path before switching
- Confirm the production WordPress version and whether its image library reports AVIF support.
- Upload a small test AVIF and verify that the original is accepted.
- Generate every required thumbnail size and inspect each file.
- Load a page through the production cache or CDN and check the response’s content type.
- Test browsers and devices that matter to your audience, with a fallback configured where necessary.
- Check image quality, transparency, animation, lazy loading and responsive sizes on real pages.
Current WordPress client-side media-processing documentation describes browser-based conversion for JPEG, PNG, GIF, WebP and AVIF, with a server-side fallback where browser processing is unavailable. The full client pipeline is limited to supported Chromium-based browsers, so the release and configuration deployed on your site matter. Do not enable an AVIF-only workflow until both processing and delivery have passed these checks.
Quick wins for a faster PC:
Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →Clear out junk files and repair common Windows errorsFree Scan →Scan for outdated or missing drivers - takes under a minuteDriver Scan →Animated images: GIF, WebP or AVIF?
Keep GIF when an existing integration requires GIF or when compatibility with a specific consumer is more important than size. WebP also supports animation, so an animated WebP can be a practical replacement when your publishing and delivery chain handles it correctly. Compare actual playback, dimensions, frame timing and file size; an extension alone does not tell you whether the result is better.
A repeatable WordPress format workflow
1. Classify the asset
- Photo: start with WebP; retain a high-quality JPEG source and test AVIF if supported.
- Logo or interface graphic: use WebP or PNG depending on transparency and edge quality.
- Screenshot or diagram: compare lossless PNG with WebP at readable quality.
- Animation: compare existing GIF with animated WebP and verify playback requirements.
2. Compare equal visual results
Export the same dimensions at visually acceptable quality in two or more formats. Record byte size, transparency, animation behavior and visible artifacts. A smaller file that damages text or gradients is not a successful optimization.
Rank #3
3. Check WordPress generation
Open the Media Library attachment and inspect the files created for each registered size. Your site may preserve the original format, create alternate WebP files, or apply a developer filter such as image_editor_output_format. Document the behavior before changing plugins or theme code.
4. Check what visitors receive
In browser developer tools, open Network, reload the page and select an image request. Check the response content type, transferred bytes, cache status and requested dimensions. Repeat on a page using responsive images and lazy loading; the browser may receive a different sub-size than the one you inspected in the Media Library.
5. Review representative pages
- Confirm no thumbnails are missing after regeneration.
- Look for halos, banding, blurred text and broken transparency.
- Test cache and CDN behavior after replacing files.
- Check mobile and desktop responsive sizes.
- Verify that any fallback is reachable when a browser or proxy cannot use the preferred format.
Common problems and fixes
“I uploaded WebP, but the page serves JPEG.”
WordPress normally generates sub-sizes in the original format unless configured otherwise, and a theme, plugin or CDN may select JPEG. Inspect the generated files and the network response. Configure the site’s output-format workflow deliberately rather than renaming extensions.
“AVIF upload fails or thumbnails are missing.”
The server image library may lack AVIF support, or a particular size may fail during conversion. Verify Imagick or LibGD capabilities on production, test a small file, and retain a WebP or JPEG fallback until every required size succeeds.
“The new format is smaller but looks worse.”
Lower the compression aggressiveness or use a lossless format for text, line art and transparency. Compare identical dimensions and visual quality; do not compare a heavily compressed derivative with an untouched original.
Rank #4
- Brand: Wiley
- Set of 2 Volumes
- A handy two-book set that uniquely combines related technologies Highly visual format and accessible language makes these books highly effective learning tools Perfect for beginning web designers and front-end developers
“Images work in one browser but not another.”
Check the browser support expected by your audience and the response content type. Serve an alternate format through your delivery layer when necessary, and test through the real CDN or cache rather than only from the origin.
Windows Errors? Fix Them Before They Spread
Repair common Windows errors and clear accumulated junk for a smoother, more stable PC - no reinstall needed.Free scan · no reinstallCrashes, No Sound, or Screen Glitches?
Random freezes, missing sound and display glitches usually trace back to one bad driver. Find and replace yours safely.Free scan · under a minute“The conversion increased storage.”
Creating WebP or AVIF derivatives while retaining JPEG originals and multiple sub-sizes can increase disk usage. Include originals, derivatives, backups and CDN storage in capacity planning before enabling bulk conversion.
Performance, reliability and cost considerations
Format choice affects more than bytes. Conversion consumes CPU and can slow uploads or thumbnail regeneration; AVIF support may vary by host library; and caches must be purged when a URL’s content changes. Measure representative delivered files and monitor failed image requests after rollout. The WordPress average of around 30% smaller WebP files is useful for planning, not a guaranteed saving or a substitute for measurement.
Keep an original source, change one part of the pipeline at a time, and retain a rollback path. If a plugin performs browser-aware conversion, confirm which browsers use client-side processing and when the server fallback runs.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Or skip the browser setup
If you need repeatable screenshots of pages to inspect delivered image formats, ScreenshotNeo can capture the page through one API request. It accepts the cookie or consent banner before capture and removes more than 60 known consent platforms, newsletter popups and chat widgets. Bot checks, blank pages, timeouts, failed loads and cache hits are not billed, and each response identifies the page verdict and billing status in headers. Its MCP server provides take_screenshot, get_page_info and capture_pdf tools for Claude, Cursor and other MCP clients.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
Use the API documentation at https://screenshotneo.com/docs/ for authentication and options.
cURL
curl -G "https://api.screenshotneo.com/v1/shot" -d access_key=YOUR_API_KEY --data-urlencode url=https://stripe.com -o shot.webpPython
import requests
r = requests.get("https://api.screenshotneo.com/v1/shot", params={"access_key": "YOUR_API_KEY", "url": "https://stripe.com"}, timeout=90)
open("shot.webp", "wb").write(r.content)Node.js
const q = new URLSearchParams({ access_key: 'YOUR_API_KEY', url: 'https://stripe.com' });
const res = await fetch(`https://api.screenshotneo.com/v1/shot?${q}`);ScreenshotNeo also supports full-page captures with lazy images loaded, CSS-selector element capture, custom CSS and JavaScript, waits for a selector, delay or network idle, request and resource blocking, cookies and headers, device presets, retina scale, caching with a chosen TTL, signed links and bulk capture of up to 100 URLs per call. The Free plan includes 1,000 screenshots per month with no card; paid plans start at $5 for 3,000. Create a free ScreenshotNeo account to try it.
A decision checklist
- Identify whether the image is a photo, interface graphic, transparent asset or animation.
- Compare WebP, JPEG, PNG and—where supported—AVIF at acceptable visual quality.
- Confirm your WordPress version and image-processing library.
- Inspect generated sub-sizes and the format actually returned to browsers.
- Test cache, CDN, responsive-image and fallback behavior.
- Keep originals and a rollback path before bulk conversion.
Frequently Asked Questions
Does uploading AVIF guarantee that WordPress will serve AVIF?
No. WordPress 6.5 support depends on AVIF capability in the server’s Imagick or LibGD image-processing library, and your theme, plugins, cache or CDN may still serve another format.
Should every JPEG in an existing media library be converted?
Not automatically. Compare representative delivered files, account for derivative storage, and convert only after checking visual quality, responsive sizes, cache behavior and rollback options.
Do these 3 things before closing this tab:
1Fix the driver behind crashes, sound loss and screen glitches2Clear out junk files and repair common Windows errors3Scan for outdated or missing drivers - takes under a minuteCan a transparent PNG always be replaced by JPEG?
No. JPEG has no alpha transparency. Use PNG or a format such as WebP that preserves the required transparency, then verify the rendered result.
Why can two sites report different WebP results?
WordPress version, image-editor capabilities, output-format filters, optimization plugins, themes and CDNs can all change which files are generated and served.
The Bottom Line
Use WebP as the starting point for most WordPress images, retain PNG for lossless transparency, keep JPEG as a photographic source or fallback, and adopt AVIF only after your production processing and delivery path pass real tests.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
Recommended Free Tools
