Upload iPhone Photos to WordPress as WebP
WordPress has accepted WebP since version 5.8. Whether it can handle HEIC depends on your host. Converting first takes the host out of the question.
Open the converterDrag an iPhone photo into the Media Library and what happens depends on the server rather than on you. If the host’s image library can read HEIC, WordPress turns it into a JPEG. If it cannot, the file is kept with a warning asking you to convert it yourself.
Converting to WebP on your own machine first means the file arrives in a format WordPress handles directly, a fraction of the size of the original, and without the GPS position of wherever you took it.
What WordPress does with a HEIC upload
Since 6.7, it converts, sometimes
WordPress 6.7 turns an uploaded HEIC into JPEG on the server, but only when the host’s ImageMagick can read HEIC. You can check under Tools → Site Health → Info → Media Handling.
Otherwise, a warning
Without that support WordPress keeps the HEIC but cannot make the resized copies a theme uses, and asks you to convert it to JPEG yourself.
The result is JPEG, not WebP
Even when the server conversion works, you get JPEG. If you wanted the lighter format, there is still a second step.
Hosts differ, and change
Whether ImageMagick has HEIC support is a build detail most site owners never see. A host migration or a server update can change it without notice.
Why WebP instead
WordPress accepts it natively
WebP uploads have been supported since WordPress 5.8, with no plugin needed, as long as the server’s image library can process WebP.
Smaller for the same look
Google’s WebP documentation puts the saving over JPEG at around 30 percent on average. Your photos will vary; the converter shows each file’s size so you can compare.
No location on the public page
The converted file carries no EXIF block, so the GPS position, shot time and phone model never reach the Media Library, or a visitor who downloads the image.
The server does less work
WordPress still makes its resized copies, but it starts from a smaller file in a format it already understands.
Before you upload
Pick a quality
The slider runs from 50 to 100 and starts at 85. For photos in a post, 75 to 85 is a reasonable range; below about 70, smooth skies start to show banding.
Large photos get scaled anyway
WordPress scales images wider or taller than 2560 pixels down to that size and keeps the original alongside. A 12- or 24-megapixel iPhone photo is well over that.
Name the file first
The converter keeps the original file name, so IMG_4821.HEIC becomes IMG_4821.webp. WordPress puts the file name in the image URL, so renaming it to describe the picture costs nothing.
If the upload is refused
“This image cannot be processed by the web server. Convert it to JPEG or PNG before uploading.” means the host’s image library cannot handle WebP. Ask the host to enable it, or upload JPG instead.
Where WebP is not the answer
Images people download and reuse
If a post offers photos to download, such as a press kit or a print, give them JPG. WebP is for display on your pages.
Email newsletters
Some email clients still do not display WebP. If posts go out by email through a newsletter plugin, check how the images arrive.
Colour-critical photos
iPhones shoot in the wide Display P3 colour space. The converter does not embed a colour profile, so browsers show the WebP as standard sRGB and strongly saturated colours can look a little flatter than on the phone.
It works on iPhone too
Browsers on iPhone and iPad, and Safari on a Mac, cannot write WebP themselves. There the converter uses its own built-in WebP encoder, so you can convert straight from the phone. It takes a little longer.
Frequently asked questions
Does WordPress support WebP images?
Yes, since version 5.8, provided the server’s image library (GD or ImageMagick) can process WebP. If it cannot, the upload is refused with a message asking for JPEG or PNG.
Can I upload HEIC to WordPress directly?
Since WordPress 6.7, yes, if the host’s ImageMagick can read HEIC; the upload is then converted to JPEG. Otherwise WordPress keeps the file with a warning and cannot create the resized copies a theme uses.
Does the WebP keep the photo’s location?
No. The output carries no EXIF block, so there is no GPS position, shot time or phone model in the file you upload.
What quality should I use for a blog?
Start at the default 85 and compare. For photos shown across the full width of a post, 80 to 85; for small images in the text, lower settings are usually not visible.
Are my photos uploaded to a server?
No. Decoding runs in your browser using WebAssembly. The files are read from disk into memory and never sent over the network.
Speed is why you care? Read what image weight does to page load.
Convert iPhone HEIC photos to WebP before uploading to WordPress. WordPress accepts WebP natively since 5.8, while HEIC is only converted, to JPEG, when the host’s ImageMagick supports it.
Since WordPress 6.7, an uploaded HEIC is converted to JPEG on the server if ImageMagick with HEIC support is available; otherwise the file is stored with a warning and resized copies cannot be generated. WebP uploads have been supported since WordPress 5.8 when the server’s GD or ImageMagick can process WebP; if it cannot, WordPress shows “This image cannot be processed by the web server.” Google’s documentation cites roughly 30 percent smaller files than JPEG on average. The converter writes no EXIF, so no GPS position reaches the Media Library, and it does not embed the iPhone’s Display P3 colour profile. WordPress scales images larger than 2560 pixels and keeps the original. Where the browser cannot encode WebP itself, as on iPhone and iPad, the converter uses a built-in WebAssembly WebP encoder.