Photo File Too Large to Upload? Why Free Tools Reject Camera Files

The Short Answer

A "file too large" error means your photo exceeds a hard cap set by either the tool you are compressing with or the site you are uploading to - and with current 40-61 megapixel cameras, exceeding those caps is normal, not a mistake. The fix is a compressor whose input limit actually fits camera files: check the tool's max file size against your camera's real output (13-52MB for high-resolution JPEG and HEIF stills) before you waste time re-exporting. And if the file is a RAW, no web compressor is the right tool - convert it to JPEG in your raw software first.

We sell one of the tools in this comparison, so we will show our own limits alongside everyone else's, including the case our paid tier does not solve.

How Big Camera Files Actually Are in 2026

Straight-out-of-camera stills from current high-resolution bodies routinely run 13MB to 52MB, and RAW files run far beyond that. The resolution race made this normal: Fujifilm's X-T5 and X-H2 shoot 40MP, Canon's EOS R5 45MP, Sony's A7R V 61MP - pixel counts that were medium-format territory a few years ago are now the enthusiast default.

Real numbers, from two sources. Canon's official EOS R5 specifications list approximate file sizes of 13.5MB for a Fine Large JPEG, 13.4MB for a Fine Large HEIF (.HIF), 21.9MB for C-RAW, and 45.4MB for RAW. Those are Canon's averages; detailed scenes run higher.

At 61MP the numbers jump. AlphaShooters' measured Sony A7R V file sizes across four test scenes:

Read that JPEG row again: a maximum-quality JPEG from a current 61MP body is 35-52MB. Not RAW - JPEG. Every one of those files sails past a 5MB cap, most pass 20MB, and the detailed-scene ones pass anything short of 75MB.

Two format notes. First, HEIF is doing real work in that table - the same scenes that produce 35-52MB JPEGs produce 12-27MB HEIFs, which is why pro bodies push the format; our guide on shooting HEIF vs JPEG on mirrorless cameras covers that trade-off. Second, a demarcation we insist on: .HIF files come from professional cameras (Canon, Sony, Fujifilm); .HEIC files come from iPhones. Same format family underneath, completely different workflows. This guide is in the pro-camera lane; if your too-large file is a .HEIC from an iPhone, the HEIC to JPEG converter is your faster path.

The Free-Tool Wall: Where the Size Limits Sit

Most free compression tiers cap input files at 5MB to 20MB, which means they reject typical pro-camera output before compression even starts. The caps as of July 2026:

• TinyPNG (free web tool): 5MB per image. A respected tool, but its free cap is smaller than nearly every file in the A7R V table above, and smaller than plenty of phone photos. Tinify's paid Web Pro raises it to 75MB.
• Compressor.io (free): commonly reported at 10MB.
• Mochify (Free tier): 20MB. Covers a Canon R5 Fine Large JPEG or .HIF (about 13.5MB), most HEIFs, and effectively all phone photos - but not a 61MP Extra Fine JPEG.
• Mochify (Seller and Pro): 75MB. Covers everything in the stills table above except uncompressed RAW.

Stated plainly, because this is the article's honest core: our free cap is 4x TinyPNG's, and there is still a class of file it rejects. A Sony A7R V or similar 61MP body producing 35-52MB Extra Fine JPEGs needs the 75MB ceiling of a paid tier - ours ($7.99/month Seller) or someone else's. And no tier of any web compressor is the right home for a 125MB uncompressed RAW - more on that below.

Competitor numbers are dated for a reason: caps change. These were verified in July 2026; check the tool's own pricing page if you are reading this much later.

Why Free Tools Reject Big Files

File-size caps exist because every megabyte you upload costs the tool real bandwidth and compute, and free tiers have to bound that cost somewhere. A 50MB upload consumes 10x the bandwidth of a 5MB one, occupies an encoder worker for longer, and produces a larger result to send back. Free tiers are marketing expenses; a size cap is the simplest lever that keeps the marketing expense proportional to the value of a free user. That is not a scandal - we do it too, at 20MB - but it explains the pattern: the cap is set where the typical free user's files top out, and pro-camera files are not typical. The 5MB caps were calibrated for an era of 12-24MP compressed JPEGs. Sensors moved; many caps did not.

The practical consequence: "file too large" from a free tool is usually a pricing boundary, not a technical one. The same service will often happily take the identical file on a paid tier. Knowing that changes the question from "what is wrong with my photo" to "which tier or tool actually fits my camera" - a five-second spec check instead of an evening of frustrated re-exporting.

The Other Wall: Upload Limits at the Destination

Even after you find a compressor that accepts your file, the destination has its own cap - and those caps are much lower than camera output. The ones sellers and photographers hit most, as of July 2026:

• eBay: 12MB per photo (eBay's picture guidelines), up to 24 photos per listing.
• Vinted: 10MB per photo, up to 20 photos.
• Gmail: 25MB per message including all attachments (Google's attachment limits) - two full-quality R5 JPEGs and you are done.
• Client galleries, portals, forms: commonly 10-25MB, often unstated until the error.

So the real target is not "under my compressor's cap" - it is "under the destination's cap, at the destination's ideal resolution." A 45MP, 8192px-wide image is wasted on a marketplace that displays 1600px; resizing to the display size is where the giant savings come from, with compression doing the rest. A 40MB Extra Fine JPEG resized to 2000px and re-encoded lands around 1-2MB with no visible loss at display size - a 95%+ reduction, most of it from resolution nobody would ever see.

The Right Fix for Each File Type

Match the fix to what the file actually is - the answer differs by extension:

• Oversized JPEG (10-52MB): resize to the destination's display resolution and re-encode with a modern encoder. This is the everyday case and any capable compressor handles it, size cap permitting. Mochify re-encodes JPEGs with Google's jpegli encoder, which delivers roughly 35% better compression than legacy encoders at the same visual quality - our Jpegli guide has the numbers.
• HIF/HEIF from a pro body (10-27MB): convert to JPEG for compatibility (the HIF to JPG converter handles Canon, Sony, and Fujifilm files), or go to AVIF to keep the 10-bit quality in a smaller file. The full decision tree is in our complete HEIF to JPG conversion guide.
• RAW (45-134MB): stop - a web compressor is the wrong tool, including ours. RAW is unprocessed sensor data; it needs demosaicing in your raw converter (Lightroom, Capture One, the maker's own software), which then exports a JPEG or HEIF. Compress that export. Any web service claiming to "compress RAW" is quietly converting it first, with a generic rendering of your carefully shot file.
• Scans and TIFF exports (often 50-500MB): flatten and export to JPEG or PNG at the needed resolution first; then compress.

Cheat Sheet: File Sizes vs Tool Limits

Destination caps to hit: eBay 12MB, Vinted 10MB, Gmail 25MB. Caps verified July 2026: TinyPNG free 5MB, Compressor.io ~10MB (reported), Mochify Free 20MB, Mochify Seller/Pro 75MB.

FAQ