You convert an iPhone photo from HEIC to JPG so a website will accept the format, only to get hit with a file size error instead. Here is why your file grew and how to get it under the cap.
Converting HEIC to JPG almost always makes the file larger. Apple uses HEVC compression inside HEIC files, which is far more efficient than the older compression inside a standard 8-bit JPG. When you convert the format to satisfy an upload form, the megabyte count goes up.
Web forms enforce strict 2MB, 5MB, or 10MB ceilings because of default server rules. It is rarely a deliberate choice by the company running the site. Standard web servers and content management systems ship with built-in byte limits that block high-resolution JPGs before the upload even finishes.
Portrait Mode and newer 24MP or 48MP sensors push files past these limits instantly. Stripping the auxiliary depth maps during a browser conversion helps, and knowing how JPEG quality sliders work lets you hit strict portals without ruining the image.
Most administrative portals, visa application sites, and job boards fail on two separate fronts. First, their file input fields check the file extension or MIME type and reject .heic outright. Second, once you convert that photo to a standard .jpg, the server checks the byte size and rejects it for being too heavy.
You can see a full breakdown of how bytes change in our guide to HEIC vs JPG file sizes. The short version is simple: to keep the same visual sharpness at the same pixel dimensions, a JPG needs significantly more storage space than a HEIC file. A photo that sits comfortably under a limit on your iPhone will often cross the line the moment it becomes a JPEG.
Those specific numbers are not random. They come from default configuration files that web developers forget to change, or security ceilings set by cloud infrastructure.
| Upload Limit | Typical Source | Where You See It |
|---|---|---|
| 2 MB | Default PHP configuration (upload_max_filesize) | Government portals, older university systems, basic WordPress forms |
| 5 MB | Identity verification SDKs and HR software | Job applications, insurance claim forms, banking onboarding |
| 10 MB | Cloudflare free tier and AWS API Gateway limits | Customer support tickets, modern web apps, property listings |
Two iPhone features quietly inflate your file sizes before you even touch a converter. Starting with the iPhone 15 lineup, Apple changed the default main camera output from 12 megapixels to 24 megapixels. Double the pixels means a much heavier JPG after conversion. You can step this back down to 12MP by opening Settings > Camera > Formats > Photo Mode on your iPhone.
Portrait Mode causes a different problem. A Portrait HEIC is not a single flat picture. Inside the container, iOS stores the primary image alongside an auxiliary disparity map (depth data), a semantic skin matte, a hair matte, and sometimes a teeth matte. When you share or convert a Portrait photo poorly, those hidden layers get baked in or mishandled. A clean browser converter strips all auxiliary containers and writes only the primary image grid into an 8-bit JPG with 4:2:0 chroma subsampling.
When a converted JPG is still too big for a 2MB portal, you have two levers to pull: the JPEG quality setting and the pixel dimensions.
If you are preparing files for a physical lab rather than a strict government form, read our notes on HEIC to JPG print quality before shrinking anything.
Many online converters reject your original iPhone photo too, because they have to upload your heavy 48MP ProRAW or Portrait HEIC to their own cloud servers first. Because the HEIC to JPG converter runs entirely inside your browser tab, there is no server upload limit to trip over. Drop your files in, let your own device decode the primary image and strip the extra Apple container bloat, and save a clean JPG ready for whatever form you are fighting with.
Your photos are decoded in your own browser — open the converter and see.
First published: 25 October 2026