Image Not Uploading? Fix 'File Size Exceeded' Errors
Short answer: an upload almost always fails for one of three reasons: the file has more bytes than the portal allows, the extension isn't on its accepted list, or the filename broke something. Read the error message literally: "file size exceeded" means you need fewer bytes, "invalid file type" means you need a different format, and a bare "upload failed" usually means the filename or your connection. Fixing it takes about two minutes: check the real size, drop the photo into the free BeeToolify Image Compressor, set it under the cap (aim for 80% of the limit), rename the file to something simple, and upload again. Nothing is sent to a server while you do it.
What does each upload error actually mean?
Portals are built by different teams with different vocabularies, but the messages map onto a small set of real causes:
| Error message you see | What's really wrong | Fix |
|---|---|---|
| "File size exceeds…", "Max 2 MB", "File too large" | Bytes over the cap. The file is stored heavier than it looks. | Compress below the number: target 80% of it |
| "Invalid file type", "Only JPG/PNG accepted" | Extension or actual encoding not supported (HEIC is the usual offender) | Convert to JPEG (photos) or PNG (graphics) |
| "Upload failed" with no detail | Filename characters, expired session, or a dropped connection | Rename simply, refresh, retry on a stable connection |
| "Invalid file name" | Special characters, spaces at the end, or no extension at all | jane-doe-photo.jpg style names only |
| "Image dimensions must be…" | Pixel size, not file size: many photo rules specify exact pixels | Resize first with the Image Resizer, then compress if needed |
| "The file is corrupt" / nothing happens | Truncated download, zero-byte file, or an interrupted camera save | Re-export the original; test it opens before uploading |
| "Only one file allowed" | You selected a folder or multi-select | Merge into one PDF (documents) or send files one at a time (photos) |
What size limit does my portal probably have?
When the error names a number, that's the rule. When it doesn't, these are the caps that come up most often (by portal type, as of late 2026). Treat them as targets to aim under, then confirm from the message itself:
| Portal type | Common image cap | Typical format list |
|---|---|---|
| Government & immigration forms | 30 KB – 2 MB (varies wildly by form) | JPEG usually; some demand PDF for documents |
| Exam & job application photos | 20 KB – 500 KB | JPEG, sometimes PNG |
| Insurance & medical portals | 1 – 5 MB per attachment | JPEG, PNG, PDF |
| Employer career pages (ATS) | 2 – 10 MB | PDF for resumes, JPEG/PNG for portfolio |
| College & school portals | 1 – 5 MB | PDF documents, JPEG photos |
| Email attachments (Gmail, Outlook) | 20 – 25 MB total | anything with an extension |
| Social & marketplace listings | usually generous (5 – 25 MB) | JPEG, PNG, WebP, HEIC (platform-dependent) |
The safe rule: if the message doesn't say, aim for 80% of the smallest plausible cap. A photo that's 150 KB passes a 200 KB exam rule, a 2 MB government rule and a 1 MB legacy portal, all in one attempt, with no second round of guessing.
How do I reduce a photo below the limit (the 90% case)?
This is the fix you'll use most, and it's a three-step job in the browser:
- Check the real size. Windows: right-click → Properties. Mac: ⌘-I / Get Info. On a phone: open the photo → Details/Info. Note the KB/MB number: "it looks small" isn't a measurement.
- Open the Image Compressor, drop the file in. It processes locally: no upload, no account, no watermark, works offline once loaded.
- Set the target. Type the KB limit the portal gave (or drag the quality slider), watch the before/after numbers, and download when the output sits at about 80% of the cap.
- Upload the downloaded copy: the original stays untouched on your device in case another portal wants something different.
Why 80%? Two reasons. Some systems count in a slightly different unit or add a few bytes of metadata after your export, and a file sitting exactly on the line has nowhere to go. The other: you'll be doing this again for the next application. A margin means you only do it once.
Quality expectations: dropping a 4 MB phone photo to 200 KB sounds drastic, but photographs compress extremely well because JPEG throws away data your eye doesn't use. At normal viewing size the difference is invisible; only a pixel-peeping crop at 400% shows it. Text in photos (signs, forms, receipts) survives moderate compression: if the text matters, reduce dimensions less aggressively and lower quality only a little.
What if the problem is pixels, not bytes?
Plenty of forms specify dimensions instead: "600×600 px", "max 200×230", "width between 400 and 800". Compression won't change a single dimension, so the order matters:
- Resize first with the Image Resizer: enter the exact pixels, pick fit mode (aspect-ratio preserved by default), download.
- Compress second if the resized file is still over the byte cap: resize often fixes both problems at once, since smaller dimensions mean fewer bytes automatically.
- Re-check both numbers before uploading: dimensions and size are separate rules and a portal can enforce either or both.
Common US-specific numbers, for reference: passport and visa photos are 2×2 inches at 600×600 px minimum; many immigration forms want square photos at 600×600; LinkedIn's minimum profile image is 400×400; eBay and most listing platforms prefer at least 1600 px on the long edge. The form's own instructions win over any table, including this one.
Format matters: JPEG, PNG, or WebP?
| What you're uploading | Right format | Why |
|---|---|---|
| Photo (person, scene, document photo) | JPEG | Smallest size for a given quality; accepted by every portal on earth |
| Screenshot, text, logo, line art | PNG | Lossless: JPEG turns sharp text edges into mush at small sizes |
| Anything a modern portal accepts WebP on | WebP | Same quality at roughly 25–35% fewer bytes than JPEG |
| iPhone photo showing as .heic | Convert to JPEG | Many portals and Windows workflows don't handle HEIC |
| Document that must contain selectable text | PDF (not an image) | ATS and search systems parse PDF text; an image of text is invisible to them |
One trap worth naming: converting JPEG → PNG doesn't make it smaller: it re-wraps lossless data around the same pixels and usually grows the file. Convert in the direction of your need (to meet a format list), not as a size fix. The Image Converter handles JPEG, PNG and WebP in either direction when a portal is strict about extensions.
Five lesser-known reasons an upload fails
- The filename.
photo (2).jpg,final—draft.jpgwith an em-dash, accents, or # and % symbols trip older upload systems. Rename tojane-doe-photo.jpg. - Files with no extension. Downloads from some email systems land as extension-less files; type filters can't identify them, so they fail silently.
- Zero-byte or corrupt files. A failed camera save or interrupted download produces a file that looks fine but contains nothing. Open it before uploading.
- Session timeout. Long forms expire. You fill in ten fields, attach the file, submit, and get a generic failure. Save your work, refresh, attach first if the form allows.
- Mobile data on the edge of coverage. A 4 MB upload on one bar of signal often dies mid-transfer and reports as a size or server error. Stable Wi-Fi removes a whole category of mystery.
Why fix it locally instead of using a random converter site?
Because of what those files are. An upload failure most often happens on exactly the documents you'd least want floating around: passport photos, license scans, insurance evidence, medical images, application forms with your address and ID numbers. A server-based converter has to receive that file before it can shrink it: you're trading one upload for another, and you have no way to see what happens after the download link expires.
The BeeToolify tools never take that step: your browser reads the file, re-encodes it in memory, and hands the result back for download. Open DevTools → Network while it runs and the log stays empty. That's the proof, not a promise. It's also why the tools keep working with no signal: once the page has loaded, the processing needs nothing but your device.
Quick FAQ
Why does my photo keep failing to upload?
Because one of three rules is being broken: the file is heavier than the portal's size cap, the format isn't in its accepted list, or the filename/connection caused a generic failure. The error message tells you which: 'file size exceeded' is bytes, 'invalid format' is the extension, and a bare 'upload failed' is usually the filename or your network. Fix in that order: reduce the size, convert the format, rename and retry.
What does 'file size exceeded' mean?
The file has more bytes than the portal accepts. It counts the file as stored, not how it looks: a 4000×3000 phone photo can be 4 MB even though it displays as a thumbnail. The error usually names the cap. When it doesn't, aim well under the common ones: 2 MB for government and insurance forms, 1 MB for older portals, 200 KB for exam or job form photos.
How do I reduce a photo below 2 MB or 1 MB?
Open the BeeToolify Image Compressor in your browser, drop the photo in, set the target size or lower the quality slider until the estimated output is comfortably under the cap, and download the result. Compression takes seconds and happens on your device, so the file is never uploaded. As a rule, aim for about 80% of the limit so a slightly different re-export doesn't push you over again.
Which image format should I upload?
JPEG for photographs: smallest size for a given quality, accepted everywhere. PNG for screenshots, text, logos or anything needing transparency, because JPEG fringes around sharp edges. WebP when a modern portal accepts it, since it beats both on size. If the form only accepts .jpg and you have a .png, convert it in a second rather than fighting the form.
Why does the portal say 'invalid file name' or fail silently?
Some upload systems reject names with special characters (#, %, &, accented letters), double extensions, spaces at the ends, or names that are extremely long. Rename to plain ASCII with hyphens (for example 'passport-photo.jpg' or 'jane-doe-resume.pdf') and upload again. Also check the file actually has an extension: a file saved without one is invisible to type filters.
Can I upload HEIC iPhone photos directly?
Only if the portal lists HEIC among accepted types. Many don't, and browsers can't decode HEIC for in-browser conversion either. Convert on the phone instead: in the Photos app open the image, Share → Options → Image Format → JPEG, or turn on Settings → Camera → Formats → Most Compatible so future captures are JPEG. Then compress and upload.
Is it safe to compress ID or medical photos on a website?
Only if the processing never leaves your device. The Image Compressor runs entirely in the browser: the image is read, re-encoded and downloaded locally, and the network tab in DevTools stays empty while it works. That matters for passports, licenses, insurance cards and medical documents: a server-based converter sees those files whether or not it promises to forget them.