Tech

iPhone 18 Pro Photos Aren't Actually Bigger: HEIC Upload Limits on 6 Image Hosts, Checked

Published on9/17/202613 min read

Everyone's talking about the camera. I went and read the spec sheet instead

The iPhone 18 Pro and Pro Max landed on September 9, and my feed immediately filled up with "biggest camera upgrade ever" takes. Honestly, I've learned to be skeptical of launch-day hype after testing more than sixty image hosts and file-sharing services over the years — phone camera specs climb every year, but upload limits on the receiving end were often set three or five years ago and rarely get revisited to match.

So instead of waiting for camera review videos, I pulled up Apple's own spec page and cross-checked it against the official FAQs of a handful of mainstream image hosts.

What I found first was the opposite of what I expected.

Myth to bust first: 18 Pro photos aren't bigger than last year's

Before this round of launch coverage, I assumed this article would be about "the new camera shoots way bigger files, and hosting services need to keep up." That's not what the spec sheet says.

Yes, the iPhone 18 Pro's main, ultra-wide, and telephoto lenses are all 48MP Fusion cameras. But the iPhone 17 Pro already had three 48MP lenses last year — the telephoto jump from 12MP to 48MP happened in 2025, not this year. What's new this time is a mechanical variable aperture (four stops: f/1.48, f/1.8, f/2.8, f/4) and a new main sensor — but the sensor size is unchanged from the 17 Pro: 1/1.28-inch, 1.22µm pixels. The physical ceiling on light-gathering hasn't moved.

In other words, resolution and file structure are essentially identical to last year. What actually improved is low-light performance and depth control, not file weight.

So if you're jumping from an iPhone 16 Pro or older, your files will genuinely get bigger — the telephoto lens really did jump from 12MP to 48MP. But if you're already on a 17 Pro, this upgrade changes nothing about whether your photos will suddenly blow past your image host's limit. Same ballpark as last year.

This piece isn't really about which iPhone generation you're on — it's about what shooting 48MP photos, period, means for upload limits. The new phone is just a good excuse to check your assumptions again.

Six image hosts, checked one by one — limits and HEIC support

I didn't want to recycle secondhand numbers floating around forums for this table. Where an official FAQ or product page exists, I read the source directly; where it doesn't, I say so honestly instead of pretending certainty.

Service	Free / anonymous limit	HEIC support	What happens after upload
lpic.cc	8MB per image	Accepted; always converted to JPEG server-side	Converted to JPEG, kept for 30 days on the free tier
Imgur	20MB (non-animated; recompressed if larger)	Not listed as a supported format in the official docs — convert to JPEG/PNG first	Lossy recompression kicks in above 1MB for anonymous uploads, 5MB for logged-in accounts; PNGs over 5MB get converted to JPEG
ImgBB	32MB free / 64MB Pro	Mentioned by third-party sources, but the official site doesn't publish a full format list — test one file first	No official statement on whether it re-compresses
Postimages	32MB (same for anonymous and free accounts), max 10,000×10,000px	Not mentioned in the official FAQ; no published format list	No published conversion policy
Catbox	No explicit numeric limit in the official FAQ (it's a blocklist — only .exe/.scr/.cpl/.doc*/.jar are blocked); third-party sources commonly cite 200MB	Not on the blocklist, so uploading it should work	Officially states files are stored 1:1 — no compression, no conversion
Flickr	200MB per image on the free tier	Official docs list JPEG, PNG, and non-animated GIF as supported — HEIC isn't explicitly mentioned	No published conversion policy

Catbox is the outlier here — it's the only one that flatly states it doesn't touch your file. The tradeoff is that it works off a blocklist rather than a guaranteed whitelist of supported formats, and its long-term availability policy isn't quite like the others.

And lpic.cc's 8MB looks the most conservative in this table on purpose: it's a free, no-login-required host, and keeping the ceiling low is how it controls abuse and storage costs. More on that tradeoff below.

The official numbers behind the table: ProRAW and HEIC file sizes

Let's put the actual numbers on record so the comparison above doesn't look like a guess.

Apple's own support page states it plainly: ProRAW is roughly 25MB at 12MP, and roughly 75MB at 48MP — triple. That's Apple's published figure, not something I measured myself.

HEIC is messier, because it's lossy compression and file size swings hard depending on what's actually in the frame — there's no single fixed number. Two independent write-ups land in similar territory: Cleanor's format comparison lists 48MP HEIC at roughly 5–12MB and 12MP HEIC at roughly 2–3MB; MiniPx separately puts 48MP HEIC at roughly 5–10MB. Both agree that busier scenes (foliage, carpet, anything with fine high-frequency detail) push toward the top of the range, while simpler scenes (sky, negative space) sit near the bottom.

Format	Resolution	Typical size	Source
ProRAW	12MP	~25MB	Apple Support
ProRAW	48MP	~75MB	Apple Support
HEIC (standard photo)	48MP	~5–12MB (estimated range, content-dependent)	Cleanor, MiniPx
HEIC (standard photo, default)	12MP	~2–3MB (estimated range)	Cleanor

See that 75MB figure? That's the real punchline of this article, because — as you just saw in the table above — none of the six hosts comfortably swallow a 48MP ProRAW file.

The 8MB-vs-75MB gap nobody escapes

Stack both tables together and the picture is obvious.

A single 48MP ProRAW file (~75MB) doesn't fit into any of the six hosts — even Flickr's 200MB ceiling is a raw transfer limit, not a promise that the platform will actually keep a RAW file usable. Most community platforms and forums can't preview RAW files at all; upload one and it just sits there as dead weight.

Switch to 48MP HEIC (~5–15MB) and things improve, but lpic.cc's 8MB limit sits right in the middle of that range — a light scene like sky or a simple background usually clears it, while complex texture or a long-exposure night shot often won't. Imgur's 20MB, ImgBB's 32MB, and Postimages' 32MB all have comfortable headroom for HEIC at this resolution.

Concretely: a 12MB-and-change night-sky HEIC gets rejected outright by lpic.cc's 8MB pre-upload check, while the same file sails through on a 32MB host like ImgBB or Postimages. That's not one service being worse — "free, no login required" and "generous upload ceiling" are two variables pulling against each other. Loosen the limit, and abuse plus storage cost get harder to control.

What happens after upload: convert, recompress, or leave it alone

That comparison table hides another thread worth pulling: "supports upload" means very different things depending on the host. Three basic approaches show up:

Force-convert to a universal format — lpic.cc converts every HEIC to JPEG server-side on receipt, so it opens on any device or browser without friction. The cost: wide-gamut color and HDR gain-map data that only HEIC carries gets discarded. I put SSIM numbers on that loss in a separate post on three phone-switching pitfalls, so I won't repeat them here.
Recompress past a threshold — Imgur is the clearest example: anonymous uploads over 1MB and logged-in uploads over 5MB get hit with lossy recompression automatically, meaning your photo gets squeezed a second time with a small but real quality hit.
Keep the original, 1:1 — Catbox is the most explicit about this: no conversion, no compression, whoever downloads it gets the exact same bytes you uploaded.

None of these three is objectively "correct" — it depends on what you need. Want compatibility and a link anyone can open? Pick a host that converts. Want to preserve original image data? Find one that doesn't touch the file (and accept that it may be more bare-bones). Want smaller files for slower connections? Recompression is already the default on most free hosts anyway.

The part rarely mentioned: your messaging app already compressed it before you got here

Here's something that gets skipped in most "which image host has the best limit" comparisons: for a huge share of everyday sharing, the image host is the second thing that touches your file — not the first. If you AirDrop a photo or send it through Messages/iMessage, it may already be resized or recompressed before it ever reaches an upload form, and the same is true of most messaging apps generally. So a file that "should" be 12MB HEIC by camera output might already be a few megabytes smaller by the time you're picking a host — worth checking the actual byte size on your device before assuming a host's limit will reject it.

There's also a privacy angle worth a mention that doesn't come up on r/iphone camera threads: once a photo leaves your device, GDPR (in the EU) and CCPA (in California) govern very different things about how long a host can retain it and what it can do with embedded metadata like GPS location. It's not something most people check before uploading, but if you're sharing photos that include location data, it's worth a glance at a host's retention policy — not just its size limit.

Three things to actually do after you upgrade

Pulling this back together into steps you can act on today:

Check your camera format setting first — HEIC + High Efficiency is the iPhone default and the right balance for everyday sharing. Only switch to ProRAW if you're actually editing afterward, because 75MB per shot eats storage faster than you'd think.
Check the file extension and size before you upload — long-press the photo, check Info; if it's bigger than your usual host's limit, decide upfront whether to compress it or pick a different service.
Separate "quick share" from "keep the original" — for a forum post or group chat, letting it get converted or compressed doesn't matter. For anything going to a client or an editor, use a host that doesn't touch the file, or keep the original on-device or in cloud storage.

That third point is the one people skip. A lot of folks get in the habit of dropping every photo into the same place right after shooting, and only discover it's already been compressed once when they actually need the original — by which point there's no getting it back.

Where lpic.cc actually fits in this picture

Back to lpic.cc specifically. It's built for the "quick share" case above: no login required, upload and get a share link immediately (a link to the post page, not a direct image link), with password protection and self-destructing one-time links for anything sensitive — handy for a screenshot or a private photo you don't want sitting around forever.

But the limits need to be said plainly before you hit them mid-upload: the 8MB per-image ceiling isn't enough for the heavier end of 48MP HEIC files, let alone ProRAW; HEIC gets converted to JPEG on upload, which costs you some color and detail fidelity; and the free tier keeps files for 30 days, funded by ads. Uploading a large 48MP night-sky HEIC? Check the file size first — anything over 8MB needs pre-compression or a different host.

Bottom line: for everyday quick sharing, it's fast enough and good enough. For large files, original quality, or long-term storage, none of those are its strong suit.

Frequently Asked Questions

Q1: Are iPhone 18 Pro photos really bigger than the 17 Pro's?

No. Both generations use three 48MP lenses with the same main sensor size; the 18 Pro's additions are variable aperture and improved low-light performance, not resolution. File sizes sit in the same range as last year. If you're upgrading from a 16 Pro or older, the telephoto jump from 12MP to 48MP will make files feel noticeably bigger — but that change happened with the 17 Pro, not this year.

Q2: Will a 48MP HEIC always blow past an image host's limit?

Not necessarily — it depends on the scene. A simple sky or plain background might land at only 4–5MB, while a complex texture or a long-exposure night shot can push past 15MB. Hosts with an 8MB ceiling (like lpic.cc) will reject the heavier files; hosts at 20MB or above (Imgur, ImgBB, Postimages) generally handle both.

Q3: Can I just upload a ProRAW file directly to an image host?

Most hosts don't recommend it and it isn't practical. A 48MP ProRAW is around 75MB, which exceeds most free upload ceilings outright, and most image hosts can't even preview a RAW file in-browser — it just sits there unused. ProRAW is meant for editing on a computer first, then exporting to JPEG or HEIC for sharing.

Q4: How much does converting HEIC to JPEG actually hurt quality?

Usually not noticeable to the naked eye, but wide-gamut color and HDR gain-map data unique to HEIC get dropped in the process. Fine for casual sharing; if you need to preserve original color for later editing, look for a host that doesn't convert, or keep a backup of the original file yourself.

Q5: Should I change my new phone's photo format setting?

Keep the default HEIC + High Efficiency for everyday use — it's a solid balance of compatibility and quality. Only switch to ProRAW for commercial work or large-format output, and go in knowing each shot runs about 75MB, so double-check whether your upload destination can actually take it.

References

#iPhone 18 Pro#HEIC format#ProRAW#image hosting upload limits#phone upgrade#photo file formats#48MP camera

Written by

Alex Chen

Product Tester

Hands-on testing of every tool, sharing first-person real-world experience.