“Cannot convert document: Internal Error”

When right-clicking a Microsoft Office file (.docx, .xlsx, .pptx) or a PDF in Google Drive and selecting Open with > Google Docs / Sheets / Slides—or when using File > Save as Google Docs—the system may abort with the message: “Cannot convert document: Internal Error.” This message indicates that Google’s backend document conversion pipeline encountered an unhandled exception while attempting to parse the document’s structure into Google’s native cloud schema.

Quick Answer

The “Cannot convert document: Internal Error” message occurs when a file contains corrupted OpenXML markup, hidden password protection, or structural elements that exceed Google’s parsing limits. To resolve it, open the document in its native desktop app, remove tracked changes and embedded objects, and re-save it as a clean .docx, .xlsx, or .pptx file.

---

Primary Causes of Conversion Failures

Because Google’s error modal provides no specific error code, you must diagnose the issue based on what the document contains:

1. Disguised File Formats: Many third-party platforms (like CRM systems or billing tools) export reports labeled .xlsx or .doc that are actually raw HTML tables, Comma-Separated Values, or Rich Text Format (.rtf) files with the wrong extension slapped on them. When Google attempts to read them as modern OpenXML, the parser crashes.
2. Damaged Internal XML Relationships: Modern Office documents are zipped collections of XML files. If an internal relationship link (like word/_rels/document.xml.rels) points to a missing image, font, or binary target, Google aborts the conversion.
3. Hidden Document Protection or DRM: Documents encrypted with Azure Information Protection, IRM, or password protection cannot be converted by automated web parsers. See Troubleshooting Google Drive “Save as Google Doc” (Encrypted).
4. Volume and Layout Thresholds: Files that push technical boundaries, such as spreadsheets with hundreds of thousands of formulas or documents with deep revision trees, frequently hit backend execution timeouts. For spreadsheets, check Troubleshooting “Too many cells” (Excel to Sheets) and Why Google Sheets says “Workbook too large to open”.

---

Step-by-Step Diagnostic and Resolution Steps

Step 1: Detect Disguised File Formats

Verify whether the file is truly a modern Office document or a disguised text file:

1. Open the file in a basic text editor (such as Notepad or TextEdit).
2. Inspect the very first characters on line 1:
   • Real Modern Office (.docx, .xlsx, .pptx): Must begin with the letters PK (identifying it as a zipped package).
   • Disguised HTML: Begins with <!DOCTYPE html>, <html>, or <table.
   • Disguised Rich Text: Begins with {\rtf1.
3. If the file starts with HTML or RTF tags, rename the file extension to .html or .rtf. You can then open the file directly or copy the text manually into a native Google Doc.

If the file payload appears as an unformatted stream, see Fix: “Heads up: This file is in a binary format”.

Step 2: Clean the Document Structure in Desktop Software

If you have access to Microsoft Office or LibreOffice, use their native repair engines to strip malformed tags:

1. Open the problem file in Microsoft Word, Excel, or PowerPoint.
2. Accept or reject all Tracked Changes and delete all unresolved Comments (deep comment trees frequently crash Google’s conversion engine).
3. Remove legacy embedded objects (like embedded PDF objects or outdated equations).
4. Go to File > Save As.
5. Select a clean destination, set the format dropdown to Word Document (.docx) or Excel Workbook (.xlsx), and save.
6. Upload the clean copy to Google Drive and attempt conversion again.

Step 3: Clear the Conversion Queue and Browser Cache

Occasionally, a transient Google backend communication timeout leaves a “stuck” state in your browser session:

1. Open an Incognito / Private Window.
2. Sign into Google Drive.
3. Right-click the file and select Open with > Google Docs.
4. If the conversion completes successfully in Incognito, clear your browser’s application cache and local storage for drive.google.com.

If conversions consistently hang without completing, consult Troubleshooting “Conversion taking longer than expected”.

---

For PDF Conversions: Address OCR and Layering Faults

If the internal error occurs while converting a PDF into a Google Doc:

• Google Docs applies an Optical Character Recognition (OCR) engine during PDF conversion.
• If the PDF contains high-resolution scan layers mixed with vector paths, or exceeds 50 MB in size, the OCR engine will throw an internal error.
• Fix: Use an external PDF tool to flatten the document (print to PDF), downsample images to 300 DPI, or split the document into smaller page sections (under 50 pages each) before converting.

For deep troubleshooting on PDF scanning and translation failures, review How to Fix OCR Failures in Scanned PDF-to-Google Doc and Fix: “Page limit exceeded” for document conversion.