filename.heic
Queued—
You shot the dish on your phone between steps and now the blog will not take the files. Convert the set below and get the post published.
100% Local — Files Never Leave Your Device
Drop your food photos here
or pick them from your device — process shots and hero images at once
Supports .heic and .heif from iPhone, iPad and modern Android cameras
88% is the practical blog setting: appetising on retina screens, fast on mobile.
filename.heic
Queued—
WordPress, Squarespace and most recipe card plugins validate uploads against a fixed list of MIME types that does not include HEIC. Even where an upload is forced through, the resizing that generates your thumbnails and featured images runs on server libraries built without HEVC support.
Recipe plugins add another layer: schema images for Google, Pinterest-ready vertical crops and card thumbnails are all generated from the file you upload. Those pipelines expect JPEG.
Page speed is a ranking factor and food blogs are image-heavy by nature, so 88% is a deliberate default — the dish still looks appetising at retina resolution while the page stays quick on a phone in someone's kitchen.
Resolution is unchanged, so your hero shot is still large enough for a full-width header or a Pinterest crop. Convert the whole shoot at once and upload the batch in one go.
Drag them onto the box above or press Select Files. Conversion starts automatically.
Download the JPGs or take the ZIP, then add them to the post and the recipe card as usual.
Your JPGs carry no EXIF metadata.
Conversion re-encodes pixels only, so capture dates, GPS coordinates and camera details are not carried across. That is usually what you want for anything published, but keep your original .heic files if those timestamps matter to you.
WordPress blocks .heic uploads because the format is not among its permitted MIME types, and the image libraries on most hosts cannot decode HEIC to generate the resized copies it needs. Converting to JPG avoids both problems with no plugin.
Around 85–90% is the practical range. Food photography rewards detail, but recipe posts are image-heavy and page speed matters for both rankings and readers on phones. 88% keeps the dish looking good without the page weight.
No. The decoder is a WebAssembly module that runs inside your browser tab, so the photo is read from your device into memory and converted there. You can check it in your browser's Network tab, or disconnect from the internet once the page has loaded and convert anyway.