Do these 3 things before closing this tab:
1Repair Windows errors before they cause bigger problems2Fix the driver behind crashes, sound loss and screen glitches3Clear out junk files and repair common Windows errorsYes—WordPress supports AVIF from version 6.5 onward, but only when your hosting stack can process AVIF. Confirm that prerequisite first in Tools → Site Health → Info → Media Handling. If AVIF is listed as a supported format, you can upload an .avif file through Media → Add New and insert it like a JPEG or PNG.
Antihost offers managed WordPress hosting with free migration, one-click staging and a 14-day free trial.
AVIF can substantially reduce image transfer size. WordPress Core’s Performance Team says AVIF images can be “up to 50% smaller than JPEGs while maintaining the same image quality,” but that is an upper-bound-style claim, not a guaranteed saving for every image. Keep a WebP or JPEG/PNG fallback when browser coverage, social sharing, or plugin compatibility makes an AVIF-only delivery path risky.
As an Amazon Associate I earn from qualifying purchases.
Free tools Windows power users keep installed
One-click scans. No signup required.
What AVIF changes on a WordPress site
AVIF is a modern image format designed to deliver high visual quality with fewer bytes than many JPEG, PNG, or WebP files. Smaller files can reduce page transfer and improve loading, especially for image-heavy pages. The result depends on the source image, encoder, dimensions, quality setting, transparency, and the device decoding the file.
WordPress Core says that, beginning with WordPress 6.5, supported AVIF files can be uploaded and used “just like a JPEG or PNG image today” when the hosting environment supports AVIF. Core also retains responsive-image behavior, fetch priority, and lazy loading for AVIF images. Changing the extension alone does not make an image efficient: an oversized source, unsuitable quality setting, or missing responsive sizes can still hurt performance.
#1 Best Overall
What the 50% claim means
The WordPress Core Performance Team’s 2024 statement—“AVIF images can be up to 50% smaller than JPEGs while maintaining the same image quality”—describes a possible maximum-style result at equivalent quality. It is not a promise that every photograph, screenshot, logo, or transparent graphic will be half the size. Measure representative files using the settings you intend to deploy.
Where compatibility matters
AVIF support is conditional at two levels: the WordPress server must be able to decode or encode the format, and a visitor’s browser must be able to display it. Social platforms, feeds, image-processing plugins, cache layers, and offload systems may also expect JPEG, PNG, or WebP. A deliberate fallback is therefore an implementation choice, not an admission that AVIF failed.
Check WordPress and hosting prerequisites
Use WordPress 6.5 or newer. Core support also depends on the image-processing library installed by the host—commonly GD or Imagick—being built with AVIF capability. Hosts can run different library versions and compile them with different codecs, so do not infer support from another site or from the host’s product name.
Verify support in the dashboard
- Sign in to WordPress with an account that can view Site Health.
- Open Tools → Site Health → Info.
- Expand Media Handling.
- Look through the supported formats list for AVIF.
If AVIF appears, the server reports support for the relevant media operation. If it does not, ask the host which GD or Imagick version is active and whether its AVIF codec is enabled. A host may be able to enable a compatible library. Alternatively, use a plugin or external service that performs conversion away from the server’s limited codec.
What a missing format tells you
- AVIF absent: WordPress cannot rely on the current server stack for normal AVIF processing. Do not assume uploads, thumbnails, or editor operations will work.
- AVIF present but editing fails: the server may decode an uploaded file but lack complete AVIF encoding support for generated sizes or edits.
- Support varies after a migration: recheck Media Handling after changing hosts, PHP builds, GD/Imagick packages, or container images.
Upload a ready-made AVIF image
This method is simplest when an editor or conversion tool has already exported the file as AVIF and your Site Health report lists AVIF support.
- Export or convert the source image to
.avif. Preserve the original file until you have checked the result. - In WordPress, open Media → Add New.
- Select the AVIF file or drag it into the uploader.
- Wait for the upload to finish, then open the attachment details and confirm that WordPress accepted the file.
- Insert the image into a post or page using the normal image block or editor control.
- Preview the page at the intended display sizes. Inspect the generated image URLs and the browser’s network panel to confirm which file is actually delivered.
Core’s responsive-image features continue to apply to supported AVIF images. Check that the attachment has the expected intermediate sizes and that your theme is not replacing the image URL with a cached or offloaded original.
Prepare files before uploading
- Resize a source to the largest display dimension you actually need; AVIF does not compensate for an unnecessarily large pixel grid.
- Choose quality separately for photographs, screenshots, illustrations, and transparency-heavy assets.
- Compare the AVIF visually with the source at 100% and at the size visitors see.
- Use descriptive filenames and attachment text that fit your existing accessibility and media workflow.
Convert an existing Media Library
For a few images, convert copies outside WordPress and upload the AVIF files manually. For a large library, a conversion and delivery plugin can generate files in bulk, automate future conversions, negotiate formats by browser, and retain a fallback. Evaluate the plugin’s requirements, storage behavior, cache integration, and rollback path before changing production media.
Manual conversion for a small library
- Back up the original image files and the database references that point to them.
- Convert a representative set of JPEG, PNG, GIF, or WebP files with a trusted editor or conversion utility.
- Upload the AVIF copies and insert them where you need them.
- Check responsive sizes, image captions, feeds, templates, and social-image workflows.
- Keep the originals until every use has been verified.
This approach gives you the clearest rollback: remove the AVIF attachment or change the reference back to the original. It does not automatically rewrite every existing image URL, so it is labor-intensive for a large site.
Bulk conversion with a plugin
The Images to AVIF listing says it converts PNG, JPG, GIF, and WebP images. Its documented requirements include PHP 5.6 or newer and GD or Imagick with AVIF support. It also documents a ?no_avif=1 URL option that retrieves the original file, which can provide a direct fallback or troubleshooting path.
Converter for Media can check whether a browser supports AVIF, serve WebP when AVIF is unavailable, and use WP-CLI for faster conversion. Its listing states that WordPress files and Media Library images must be on the same server. That constraint matters when originals live on a separate object-storage or CDN layer.
Crashes, 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 minuteWindows 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 reinstallPlugin behavior changes over time. Before enabling a bulk job, read the current requirements, confirm the plugin’s supported WordPress and PHP versions, and test on a staging copy or a small batch.
Protect the rollback path
- Take a tested backup of originals, the database, and any generated media directories.
- Confirm whether conversion creates additional files or replaces existing files; either choice affects storage and rollback.
- Record the quality settings and naming rules used for the batch.
- Check a sample in post content, theme templates, widgets, feeds, responsive
srcsetoutput, and backups. - Keep originals until cache invalidation and real-page checks are complete.
Choose AVIF-only or a fallback delivery strategy
Use AVIF-only delivery only when you have established that your meaningful audience, sharing workflow, and plugins can handle it. WordPress Core advises avoiding AVIF for a significant audience using unsupported browsers or adding a browser polyfill. In practice, retaining WebP or JPEG/PNG is usually the safer operational choice.
| Approach | How it works | When it fits | Main trade-off |
|---|---|---|---|
| AVIF only | Pages reference AVIF files directly. | A controlled audience and toolchain with verified AVIF browser support. | Unsupported browsers, social tools, or plugins may show a broken image or reject the asset. |
| AVIF plus WebP | Capable browsers receive AVIF; other supported browsers receive WebP. | Sites seeking modern compression while preserving broad web delivery. | Additional generated files and storage, plus cache rules to maintain. |
| AVIF plus JPEG/PNG original | AVIF is selected where possible and the original format remains the fallback. | Mixed browser, feed, social-sharing, or editing requirements. | Fallback files can be larger, especially for photographic JPEG alternatives. |
How negotiation should be verified
- Open a page in an AVIF-capable browser and record the image response in the network panel.
- Repeat in a browser or test path that does not advertise AVIF support.
- Confirm that the fallback response has an appropriate image MIME type and displays correctly.
- Repeat after enabling the production CDN, page cache, image optimization layer, or offload system.
Do not rely on the filename alone. A URL can still serve the original if a theme, CDN, cache, or offload layer bypasses the plugin’s rewrite or negotiation rules.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Measure quality and performance before changing the whole site
Build a small test set containing representative photographs, screenshots, hero images, illustrations, and transparency-heavy graphics. Convert each using the quality settings planned for production, then compare bytes and appearance. The “up to 50% smaller” Core statement is useful context, but your own files determine the result.
Recommended Free Tools
Review these measurements
- Transfer size: compare the delivered response, not just the file on disk.
- Visual artifacts: inspect faces, text in screenshots, fine foliage, gradients, transparency edges, and dark scenes.
- Decode behavior: check lower-powered phones and computers, where decoding can affect perceived responsiveness.
- Largest Contentful Paint: measure pages with large hero images after applying the same cache and responsive rules used in production.
- Responsive selection: verify that
srcsetandsizeschoose an appropriate width rather than downloading a desktop-sized source to a phone. - Cache correctness: clear or version cached responses after changing format rules.
Changing format cannot repair an image whose dimensions are excessive, whose quality is set far above its visual need, or whose page loads many below-the-fold images eagerly. Keep WordPress’s responsive images, fetch-priority behavior, and lazy loading working as intended.
Troubleshoot common AVIF failures
WordPress rejects the upload
- Confirm that the site runs WordPress 6.5 or newer.
- Reopen Tools → Site Health → Info → Media Handling and check for AVIF.
- Verify that the file really is AVIF and has not merely been renamed from another format.
- Ask the host whether GD or Imagick was built with AVIF support.
- Check MIME handling and any security or upload plugins that restrict image types.
- If server support is unavailable, convert with a plugin or service that performs processing elsewhere, then upload a compatible result.
The upload succeeds but thumbnails or edits fail
This usually indicates incomplete server-side encoding support: the stack can decode the original but cannot generate every derivative or edited version. Ask the host which image library and AVIF codec are enabled. If the host cannot provide complete support, use a conversion workflow that generates derivatives outside the limited stack or retain JPEG/PNG originals for operations that require them.
Visitors see a broken image
Inspect the network response, MIME type, and selected URL in both an AVIF-capable and fallback browser. If the unsupported path receives AVIF, configure WebP or JPEG/PNG fallback delivery, or use a plugin’s browser negotiation. Also check that a CDN, cache, theme, or image offload layer is not stripping the fallback rule.
Bulk conversion stops or never starts
- Check PHP execution and memory limits, background-task limits, and available disk space.
- Process a smaller batch to identify a file or timeout boundary.
- Use WP-CLI where the selected plugin supports it and your host permits command-line execution.
- Confirm the plugin’s same-server requirement if files are split between WordPress storage and another service.
- Review logs for permissions, filesystem, or codec errors before restarting a large job.
The site still serves JPEG or PNG
Conversion and delivery are separate steps. A plugin may have generated AVIF files without rewriting page output. Confirm that its delivery feature is enabled, purge relevant caches, inspect the final HTML and network response, and check whether the theme or CDN bypasses the generated rules. Keeping the original response can be intentional when the request comes from a browser without AVIF support.
Quick Recap
Operational checklist for a safe rollout
- Upgrade to WordPress 6.5 or later and verify the upgrade in a staging environment.
- Check Tools → Site Health → Info → Media Handling for AVIF support.
- Back up originals, the database, and generated media before conversion.
- Test a small set of varied images at planned quality settings.
- Decide whether your site needs AVIF-only, AVIF plus WebP, or AVIF plus the original format.
- Verify browser negotiation, MIME types, responsive sizes, cache behavior, and CDN delivery.
- Measure transfer size, visual quality, decoding, and Largest Contentful Paint on representative pages.
- Convert the remaining library in controlled batches, watching disk space and execution limits.
- Keep originals until templates, feeds, social workflows, backups, and rollback have been checked.
- Recheck support and delivery after host, PHP, image-library, plugin, CDN, or cache changes.
AVIF implementation choices at a glance
| Question | Practical answer |
|---|---|
| Can WordPress upload AVIF? | Yes from WordPress 6.5 onward when the hosting image-processing stack supports AVIF. |
| Where is support checked? | Tools → Site Health → Info → Media Handling. |
| Can existing images be converted? | Yes. Convert copies manually for a small set or use a conversion plugin for bulk processing. |
| Should originals be deleted? | Not until generated sizes, templates, feeds, social workflows, caches, and backups have been verified. |
| Is AVIF always smaller? | No. Savings vary by image and encoder; Core publishes an “up to 50%” comparison with JPEG at equivalent quality. |
| Is a fallback required? | Not for every audience, but WebP or JPEG/PNG is prudent when unsupported browsers, social tools, or plugins are significant concerns. |
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.
