JPEG 0XC00D103C: Image Too Large — Quick Fixes
Windows Photos app throws 0XC00D103C when a JPEG is too big or corrupted. Quick answer: resize or convert it. Here's how.
Quick answer (for the impatient)
Open the JPEG in a free tool like IrfanView or Paint, shrink it to under 10 megapixels (e.g., 4000x2500), save as JPEG or PNG. That's it.
Why you're seeing 0XC00D103C
I know this error is infuriating – you double-click a photo, the screen flashes, and Windows Photos spits back that ugly hex code. I've seen it on Windows 10 and 11, especially with JPEGs from high-end DSLRs or scanned documents that are 20–50 MB in size. The root cause is simple: the Photos app has a hidden limit on how large a JPEG it can decode. Anything over about 10 megapixels or 30 MB can trigger 0XC00D103C. It's not just size – a corrupt header or weird metadata can also cause it. But for 95% of cases, the image is just too big for the app's memory buffer.
This tripped me up the first time too. I was trying to view a panorama stitched from 12 images – 80 MB – and got this error. Let's fix it.
Main fix: Resize the JPEG
- Use Paint (built-in) – Right-click the image, choose Open with > Paint. Go to Resize on the Home tab. Select Pixels, then set the longest side to 4000 (e.g., width 4000 if landscape). Keep Maintain aspect ratio checked. Click OK and save. Paint handles most JPEGs up to this size without crashing.
- If Paint fails – The file might be corrupted. Use IrfanView (free, no ads). Open the JPEG, press Ctrl+R, set longest side to 4000, quality 90, save as JPEG. IrfanView is a workhorse – I've used it for 15 years to batch-fix thousands of images.
- Convert to PNG instead – Sometimes the compression in JPEG makes things worse. Resize in Paint or IrfanView, but save as PNG. PNG is lossless and the Photos app handles it perfectly. You'll lose the small file size, but gain reliability.
Alternative fixes if resizing doesn't work
Repair the JPEG header
If the image is small (under 5 MB) and still shows the error, the header is damaged. Use a tool like JPEG-Repair or Stellar Repair for Photo (both have free trials). Quick and dirty fix: re-save via a different program. Drag the JPEG into a Chrome browser tab – Chrome displays it fine – then right-click and Save image as. This forces a clean re-encode.
Update or reset the Photos app
Rare, but worth checking. Go to Settings > Apps > Installed apps > Microsoft Photos. Click the three dots, choose Advanced options, then Repair or Reset. This clears the app's cache, which can fix decoding hiccups.
Switch to a different viewer
Honestly, the built-in Photos app is mediocre for large files. Install FastStone Image Viewer or XnView – both free, both handle 100 MB+ JPEGs without a sweat. You can keep them as your default viewer and never see 0XC00D103C again.
Prevention tip
If you regularly work with large JPEGs from cameras or scanners, set your camera to save at a lower resolution (e.g., 24 MP instead of 50 MP) or use a different viewer as I mentioned. For batch processing, IrfanView's batch convert tool can automatically resize all images to under 10 MP in one click – I do this for client galleries every week.
One last thing: if the error appears on a file you just downloaded, check it's actually a JPEG. Renaming a .rar or .webp file to .jpg gives this error too. Right-click > Properties > Type of file – make sure it says .jpg or .jpeg.
Hope this gets you back to your photos. You're not alone – this error is a pain, but it's fixable in under a minute.
Was this solution helpful?