An older website, content management system, or online form built before HEIC became common can reject the upload outright, or accept it but display it incorrectly. Converting to JPG beforehand avoids discovering this problem partway through whatever task you were actually trying to complete.
Why older platforms struggle with HEIC specifically
HEIC is a relatively newer format compared to JPG or PNG, and software built or last updated before it became common on phones often simply doesn't recognise or support it. This is particularly common with older content management systems, legacy web forms, and platforms that haven't been updated to handle newer file types.
Steps to prepare your photos for an older platform
- Open HEIC to JPG.
- Upload your HEIC photo or photos.
- Convert to JPG, which is supported by essentially any platform, old or new.
- Upload the converted JPG files to the website or system in question.
Checking the platform's specific requirements beforehand
Before uploading, check whether the older platform specifies any particular file size limit or additional format requirement beyond simply not supporting HEIC, since converting to JPG solves the format issue but doesn't automatically guarantee the file also meets any separate size restriction the platform might have.
Converting proactively rather than discovering the problem mid-task
If you know in advance you're working with an older or unfamiliar platform, converting your HEIC photos to JPG as a standard first step, before attempting any upload, saves the frustration of an upload failing partway through a longer process, like filling out a form with multiple required fields.
Testing with a single file before a larger batch upload
If you need to upload several photos to the same older platform, test with a single converted file first to confirm the platform accepts it correctly, before committing to converting and uploading an entire larger batch.
Keeping a converted copy on hand for repeat use
If you expect to interact with the same older platform again in the future, keeping your converted JPG versions on hand, rather than just the original HEIC files, saves repeating the conversion step each time you need to use that specific platform again.
Recognising an older platform by its other behaviours
A platform that struggles with HEIC uploads often shows other signs of being built or last updated some time ago — an outdated visual design, limited format support elsewhere, slower general performance — which can help you anticipate this issue even before attempting your first upload.
Documenting a workaround for recurring use
If you interact with the same older platform regularly, writing a brief note of the exact conversion steps that worked, including which format it accepted, saves you from rediscovering the same solution from scratch each time you need to use that platform again.
Flagging the limitation to whoever maintains the older platform
If you interact with a specific older platform regularly and it's maintained by someone you have a relationship with, mentioning that it doesn't support HEIC uploads is reasonable feedback that might eventually prompt an update, even if converting manually remains your practical solution in the meantime.
Why patience with older systems is sometimes the more practical approach
Not every older platform is worth pushing to be updated, particularly if you only interact with it occasionally; in these cases, simply building the conversion step into your routine each time is often more practical than investing effort trying to change a system you don't control.
Keeping both formats if you're not sure the older platform will be your only destination
If you're not certain the older platform is the only place this photo will ever need to go, keep both the original HEIC and the converted JPG, rather than only keeping the converted version and potentially needing to reconvert later for a different destination with different requirements.
Treating format compatibility as a routine pre-check
Building a habit of checking format compatibility before attempting any upload to an unfamiliar or older platform, rather than discovering issues reactively through a failed attempt, is a small practice that saves recurring frustration across many different situations, not just this one.
Frequently asked questions
Why does an older website reject my HEIC photo upload?
Older platforms built or last updated before HEIC became common often simply don't recognise or support the format.
What's the fix?
Convert the photo to JPG before uploading, since JPG is supported by essentially any platform, old or new.
Should I check for other requirements beyond format?
Yes, check the platform's specific file size or other requirements, since converting the format alone doesn't guarantee it meets a separate size limit.
Should I convert proactively or wait until an upload fails?
Converting proactively, before attempting the upload, avoids the frustration of a failed upload partway through a longer process.
Should I test with one file before uploading a whole batch?
Yes, confirming the platform accepts a single converted file first is a reasonable check before a larger batch upload.
Should I keep converted copies for future use on the same platform?
Yes, if you expect to use the same platform again, keeping converted versions on hand saves repeating the step later.
Is HEIC to JPG free to use?
Yes. No sign-up, no watermark, and files are removed from the server automatically about an hour after processing.