STG_E_DOCFILETOOLARGE: Compound file too large fix

Yeah, that error's a pain. You're trying to open a file — maybe a Word doc or an Excel sheet — and instead you get 0x80030111. Here's the deal: the file is a compound file (OLE structured storage) and it's blown past the 2 GB hard limit. You can't just 'fix' the file — you need to shrink or split it.

The fix: shrink or split the file

First, find the file that's causing the error. Right-click it, check Properties. If it's over 2 GB (or close), that's your problem. Here's what to do:

1. Open in a compatible app — If it's an older .doc or .xls file (not the newer .docx or .xlsx), try opening it in the corresponding Office app (Word 2016 or earlier). Newer Office versions sometimes handle compound files differently. But don't count on this alone.
2. Remove embedded objects — Open the file, go to the Object browser (Insert > Object for Word, or in Excel use the 'Object' dialog). Delete any large embedded files — images, PDFs, videos. Those bloat the compound file fast. Had a client last month with a 3.5 GB .doc file because someone embedded a 2-hour video. Popped it out, file dropped to 200 MB.
3. Save as a newer format — If it's a .doc or .xls, save it as .docx or .xlsx. The newer formats use ZIP-based storage, not compound files. This bypasses the 2 GB limit entirely. File > Save As > choose .docx.
4. Split the file — If removing embedded objects doesn't bring it under 2 GB, split the content. For Word docs, copy sections into new files. For Excel, move sheets to separate workbooks. For databases (like .mdb), export tables into separate .accdb files.

Why this works

The 0x80030111 error is hard-coded into the Windows compound file storage system. Microsoft designed it in the 1990s with a 2 GB theoretical limit — and it's been stuck there ever since. The compound file format (used by older Office docs, some installer packages, and even some legacy apps) can't handle anything larger. It's not a bug — it's a design limitation. Shrinking the file under 2 GB removes the trigger.

The fix works because you're either converting to a format that doesn't use compound files (like .docx) or you're reducing the size of the compound file itself.

Less common variations

Sometimes this error shows up in unexpected places:

• Windows Installer (.msi) files — Some .msi packages are stored as compound files. If one exceeds 2 GB, you'll get this error during install. Solution: rebuild the installer with newer tools.
• OLE objects in AutoCAD or Visio — Embedded compound files in those apps can hit the limit. Delete large OLE objects inside those files.
• Outlook .msg files — Rare, but a .msg with massive attachments or many embedded items can trigger it. Export attachments to separate files.
• PDF files with embedded OLE objects — Some older PDF creators embed compound files. The error appears when you try to extract them. Remove embedded content with a PDF editor.

In all these cases, the root cause is the same: a compound file exceeding 2 GB. The fix is always shrink or convert.

Prevention

You don't want to hit this again. Here's how to avoid it:

• Use newer file formats — Save all Office files as .docx, .xlsx, .pptx. They don't use compound files.
• Don't embed large files — Link to files instead of embedding them. In Word, use Insert > Object > Create from File, then check 'Link to file'.
• Set file size warnings — In Excel, go to File > Options > Advanced, look for 'Show paste options buttons'. Not directly a size warning, but you can use macros to alert when a workbook hits 1.5 GB.
• Split large content — If you're working with datasets over 1 million rows in Excel, use Power Query or split to multiple files. The 2 GB limit sneaks up fast with embedded charts and formatting.

That's it. No magic bullet — just practical steps. If you're still stuck after trying these, the file might be corrupted. Try opening it on an older machine with Office 2007 or 2010 — sometimes they handle compound files more gracefully. But usually, shrinking or converting does the job.