Separate capture, storage and delivery
The format your camera captures does not have to be the format you send to every website. HEIF is an efficient image format used by supported Apple devices; JPEG is widely accepted by older applications and upload forms. A sensible workflow can keep the efficient original and create a JPEG for a particular recipient, rather than converting an entire library after one failed upload.
HEVC is the related video-compression topic, not another name for a photo. Some video modes and resolutions have their own compatibility requirements. This guide focuses on ordinary photos and their delivery copies. It does not compare professional raw workflows or claim that one format is always visually superior in every editing application.
Check what the recipient actually accepts
Read the destination's file requirements. If a form accepts only JPG or PNG, send a supported file rather than renaming a .heic extension to .jpg. Renaming changes the label, not the encoded contents. If the form accepts HEIF but rejects your image, inspect file size, dimensions and upload state before assuming the format is responsible.
For an email to a person, ask whether they can open the sample if compatibility is uncertain. A single small trial is more efficient than converting hundreds of images in advance. The receiving app, operating system and sharing path can all affect the representation that arrives.
Choose a camera default based on repeated use
On supported iPhone models, Settings > Camera > Formats offers High Efficiency and Most Compatible. Choosing Most Compatible changes new ordinary captures toward JPEG and H.264; it does not retroactively convert the photos already in your library. Some advanced capture modes require particular formats, so the exact options depend on the device and mode.
If most of your photos stay in a supported Apple workflow, retaining High Efficiency can reduce storage needs. If your daily job repeatedly feeds an older system that only accepts JPEG, a compatible capture default may remove a recurring step. Decide from your routine, not from the inconvenience of a single exceptional upload.
| Situation | Practical choice | What to preserve |
|---|---|---|
| Personal library on supported devices | Efficient original format | Original file and a suitable backup |
| One website requires JPEG | Export a JPEG delivery copy | Original remains unchanged |
| Repeated legacy workflow | Consider Most Compatible for new captures | Verify the resulting file before relying on the change |
| Long-term photo archive | Retain originals and document exports | Do not mistake a compressed delivery copy for the only master |
| Recipient needs editing history | Use a supported original-data sharing method | Confirm what the receiving application actually retains |
Make one compatible copy on Mac
Open an HEIF image in Preview and choose File > Export. Choose JPEG, select a suitable quality and save it under a distinct name or in a Delivery folder. Open the exported file and inspect fine detail, orientation and any text in the photograph. Finder's Get Info can confirm the file type and size; the filename alone is not enough.
For a workshop application, keep the original project photograph in your archive and export Project photo for application.jpg. If the form sets a size limit, adjust the delivery copy until it meets that limit while remaining readable. Avoid repeatedly resaving the same JPEG through several apps when one export from the original can do the job.
Understand automatic conversion during sharing
Apple's sharing and transfer paths can convert media for compatibility. In Photos sharing options, Automatic, Current and Most Compatible can affect what is sent where those choices are available. A cable import can also convert media unless the relevant Photos transfer setting keeps originals. Check the actual received file instead of inferring its format from what the camera originally captured.
Automatic conversion can be convenient for delivery and undesirable for an archive intended to preserve original files. That is why those two tasks should be named separately. A recipient who only needs a readable picture may welcome a JPEG; your own archive may need the unmodified original and its related metadata.
Troubleshoot a failed upload in order
First, open the file locally to confirm it is complete. Next, check the accepted formats and size limit. Then export one compatible copy and retry. If that works, use the same process for the remaining selected images. If it still fails, investigate the upload connection, browser or form rather than repeatedly degrading the image.
If an exported image looks different, compare color, brightness and crop in the apps involved. A format conversion is not a reason to silently alter the content of a documentary photograph. Keep any intentional edits separate from the claim that a file is merely more compatible.
Keep the archive and delivery folder distinct
Once the recipient confirms the file opens, you can clean up unnecessary temporary exports while retaining the original according to your normal storage plan. For motion content, read Live Photos sharing before converting: a still image cannot preserve the whole experience. For long-term copies, the photo archive workflow explains how to export originals and inspect the result.
Sources & further reading
Apple’s documentation supports the feature details. The scenarios and decision sequences above are CJVV’s editorial guidance.