HEIC is a good camera format and a bad assumption for a public website. It can keep a photo small while preserving quality, but browsers, CMS tools, email clients, and image pipelines do not all handle it consistently.
The useful question is not "Is HEIC better than JPEG?" It is "Which format will this website, browser, and image pipeline actually accept?" A good workflow keeps the original HEIC, makes a web delivery copy, and checks the result at the size people will see.
Choose the output format first
Use the destination to decide the format:
- JPEG is the safest choice for photographic images and older web systems.
- WebP is a strong general-purpose web format when the CMS and browsers support it.
- AVIF can be very compact, but the surrounding pipeline must handle it correctly.
- PNG is useful for transparency, flat graphics, and screenshots with sharp text, but it is often wasteful for photographs.
- HEIC can stay as an archive or download format when you control the viewing environment, but it should not be the only public web asset without testing.
For background on the trade-offs, see [WebP vs AVIF vs JPEG on Mac](/blog/webp-vs-avif-vs-jpeg-mac). The right answer depends on image content, browser support, and how your publishing system serves the file.
A practical five-step workflow
1. Keep the original
Make a working copy before converting. Do not overwrite the camera original with a web-sized export. You may later need a larger version, a different color profile, or a new format.
2. Resize to the actual display size
An image that appears 800 pixels wide on a page rarely needs to be uploaded as a 6048-pixel iPhone original. Resize based on the largest rendered or high-density display size your design requires.
For a two-column image displayed at 600 CSS pixels on a Retina screen, an export around 1200 pixels wide may be enough. Measure the layout instead of using the original camera dimensions by default.
3. Convert to a compatible delivery format
If the website accepts WebP or AVIF and produces the correct Content-Type, use one of those for delivery. If the CMS, email workflow, or customer support system is inconsistent, JPEG remains the dependable fallback.
Do not convert a screenshot with small text to JPEG at an aggressive quality setting. Text edges and UI lines can become visibly soft. A photo and a screenshot need different export settings.
4. Compress while checking the image
File size is only half the result. Open the compressed image at 100% and inspect faces, text, gradients, and fine texture. A file that is 20% smaller is not a win if it creates obvious artifacts on the page.
For photos, start with a moderate quality setting and compare. For graphics with transparency, choose a format that preserves the alpha channel. For screenshots, prioritize clean edges over the smallest possible byte count.
5. Remove metadata when the image is public
Camera files can contain EXIF data, including capture time, camera model, and sometimes GPS coordinates. Decide whether public files need that metadata. For most website uploads, stripping GPS is the safer default.
Keep the original archive with metadata if you need it for your own records. The public delivery copy does not need to carry every private field.
Native Mac options
For a single image, Preview can export a JPEG or another supported format. The sips command is useful for scripts and batch jobs. A simple example is:
``bash sips -s format jpeg -s formatOptions 82 photo.heic --out photo-web.jpg ``
To resize a copy while preserving the original:
``bash sips --resampleWidth 1600 photo.heic --out photo-1600.heic ``
Check the output rather than trusting the command. A web pipeline may still need a second conversion to WebP or AVIF, and the right maximum width depends on the design.
For a complete command-line workflow, see [the macOS sips image-processing guide](/blog/macos-sips-command-line-guide). It is a good choice when you want a repeatable script and do not need a visual comparison screen.
When QuickPix is faster
[QuickPix](/quickpix-image-compressor) is useful when the job is not one file but a folder of assets. It runs locally on macOS, supports HEIC, JPEG, PNG, WebP, AVIF, TIFF, and other formats, and includes a before/after comparison so you can inspect quality before shipping.
The app is especially useful for a mixed folder from an iPhone or a design handoff: choose a delivery preset, batch the files, and keep the original folder intact. Its folder-watching workflow can automatically process new assets, while color profiles can be preserved and EXIF/GPS can be stripped by default.
QuickPix is not a reason to skip testing. Upload one representative photo and one difficult image first. Check the output in the real CMS and the real page before converting thousands of files.
Common mistakes
- Converting every image to JPEG, including transparent graphics.
- Uploading full-resolution camera files when the page displays a small image.
- Compressing screenshots with the same settings used for photographs.
- Removing all metadata from the only copy of an image.
- Choosing AVIF or WebP without checking the CMS and cache headers.
- Measuring success only by file size instead of visual quality and page performance.
FAQ
Should I convert HEIC to JPEG for a website?
Usually, if compatibility is more important than maximum compression. JPEG is widely supported and works with most CMS and image tools. If your pipeline supports WebP or AVIF reliably, those may be better delivery formats for many photos.
Is WebP smaller than HEIC?
There is no universal winner. The result depends on the image, encoder, quality target, and whether the comparison is visually equivalent. Test the actual files rather than assuming one format always wins.
Can I compress HEIC files in batch on a Mac?
Yes. sips can be scripted for repeatable conversion and resizing, and QuickPix provides a drag-and-drop batch workflow for larger folders with visual comparison.
Does converting HEIC to JPEG reduce quality?
It can, because JPEG is usually a lossy export. Keep the HEIC original and choose a JPEG quality setting that preserves the details your website needs. Repeatedly converting the same image causes more damage than exporting once from the original.
Should I remove GPS metadata before uploading an image?
For a public website, removing GPS metadata is usually a sensible privacy default. Keep a private original with its metadata if you need the location or capture information later.