iPhone Photos Won't Upload to Websites? Here's the Fix

You've been here: filling out a rental application, a government service, an insurance claim, a school enrollment form — any site that asks for "upload a photo of your ID" or "upload a clear photo of the damage." You tap the upload button, pick the photo from your iPhone's library, and the form throws back something like "invalid file type" or "only JPG/PNG allowed," or it accepts the file and immediately says "upload failed, please try again." You retake the photo. Same result. It is not your fault, and it is not the network. It is a format war between Apple and the website's backend.

The exact symptom you're seeing

There are three flavors of the same underlying problem, and recognizing which one you have saves diagnosis time:

• "File type not allowed" — the form validates extensions before upload. It knows it doesn't accept HEIC and says so outright.
• "Upload failed" right after selecting — the form accepts the upload dialog but the server rejects the HEIC blob it receives. Sometimes it hangs instead, which is the same failure slowly.
• Uploads, but arrives broken / 0 bytes — the backend takes the file but its image pipeline can't decode HEIC, so the stored attachment is corrupt.

In every case the root cause is identical: your iPhone saved the photo as HEIC (the modern, smaller format), and the website only knows how to deal with JPEG (the 1992 format).

Why websites still only accept JPG

Since iOS 11 (2017), iPhones have shot photos as HEIC by default — roughly 40–50% smaller files, same visible quality (the numbers are in our HEIC vs JPG breakdown). Apple made the right call for storage. But the websites people upload to were built earlier, and many are still built to the assumption that "an image = a JPEG."

Why haven't they caught up?

• Backend validation whitelists — most upload systems check the file extension or MIME type against a list. Adding HEIC means recompiling, testing, and redeploying. Enterprise portals move on that timescale.
• Server-side image processing — resizing, thumbnails, watermarks run through ImageMagick or similar, and HEIC support on servers requires extra libraries (and historically, HEVC license work). Many admins just… haven't installed them.
• Scanners and cameras also output JPEG — the backend's whole pipeline was designed around documents scanned as JPG. Adding HEIC is an edge case to them, a daily frustration to you.

Expecting the website to change is a multi-year bet. The practical fix happens on your device, before the upload.

The 60-second convert-before-upload workflow

You do not need an app, a subscription, or a desktop Photoshop license. The whole job is: get the photo out of the HEIC container and into a JPG container, without uploading the photo to some random conversion site. Here is the flow I use:

1. Get the photo onto your computer — AirDrop it to your Mac, or plug the iPhone in and copy it to Windows. This avoids doing conversion on the phone's cramped screen. (On Windows, if the HEIC won't even open, install the free HEIF extension from the Microsoft Store first.)
2. Open the local converter — our HEIC to JPG tool runs entirely in the browser. Drag the photo (or the whole batch of photos) onto the page. No upload — the conversion happens on your machine, which matters for photos like ID cards and insurance claims that contain personal data.
3. Convert and download — one click, and you get a JPG back per file, or a ZIP if you batch. The file sits in your Downloads folder.
4. Upload the JPG to the form — the website has no idea it wasn't always JPG.

On a phone without a laptop, the same tool works in the mobile browser: open the site in Safari, use the file picker, convert, save back to Photos. It's a few more taps than ideal, but it beats fighting the form.

If the website complains about another modern format — say you saved a WebP screenshot from a design tool — the same drag-and-drop trick applies with the WebP to JPG converter. The principle is one sentence: before any upload form, your files should be JPG.

The permanent setting, and when not to use it

You can make your iPhone always shoot JPG instead of HEIC: Settings → Camera → Formats → choose "Most Compatible." I do not recommend this as your default. It wastes roughly 40% of your storage and kills Live Photos, to solve a problem that affects a few uploads a month.

Better policy: keep HEIC on (it's the better default for 95% of use), and spend the 60 seconds converting the handful of photos you actually need to submit. Local conversion is free, fast, and private — there's no reason to downgrade your whole photo library for it.

One more tip while you're in settings: enable "Transfer to Mac or PC → Automatic" in the Photos settings. That makes AirDrop and cable copies land as JPG on Windows automatically for many workflows, which shortens the whole loop.

Frequently asked questions

Why does my iPhone take HEIC photos when websites want JPG?

HEIC is Apple's storage-saving default since iOS 11: about 40–50% smaller than JPG at the same quality. Websites built before (or poorly updated since) that still only accept JPG, so the two sides don't agree.

Will converting HEIC to JPG reduce the photo quality?

By a tiny, usually invisible amount — one lossy generation. At quality 90 it's indistinguishable on screens and in normal prints. Far better than a failed upload.

Can I just take screenshots instead of converting?

It works, but screenshots are lower resolution, include phone UI unless cropped, and lose detail. Converting the original HEIC to JPG gives you a proper full-resolution file.

Is it safe to convert my ID photos on a website converter?

Only if the conversion runs locally in your browser — then the file never leaves your device. Avoid upload-based converters for ID cards, pay stubs and anything personal; you don't want copies of your documents sitting on someone's server.

Why does the form say the file is too big even after I convert?

JPGs straight from a phone are often 3–5 MB; many forms cap attachments at 1–2 MB. Re-export at a slightly lower quality or smaller size, or compress the image — our format converter re-encodes in one pass.

Related reading