Troubleshooting “Conversion taking longer than expected”

When converting a document, spreadsheet, or PDF in Google Drive, the process may stall with the warning: “Conversion taking longer than expected.” In some cases, the progress spinner runs indefinitely without producing a converted file. This occurs when Google’s server-side conversion workers encounter excessive structural complexity, oversized images undergoing optical character recognition (OCR), or dense formatting that exceeds real-time processing quotas.

Quick Answer

Refresh your Google Drive tab first; the conversion often finishes in the background and saves the file to your drive even while the popup continues spinning. If the converted file has not appeared, downsample high-resolution images in the source file, reduce the page count below 10 pages for scanned PDFs, and split large files before re-attempting conversion.

---

What Causes the Conversion Engine to Stall?

When you initiate a conversion—such as right-clicking a PDF or Word document and selecting Open with > Google Docs—Google Drive offloads the file to an asynchronous conversion queue.

The process stalls when an asset in the queue hits performance bottlenecks:

1. High-DPI Optical Character Recognition (OCR): Scanned documents saved at 600 DPI or higher require substantial processing power to map text coordinates. When Google’s OCR worker exceeds its execution window, it triggers the delay alert.
2. Dense Embedded Media: Word documents (.docx) containing dozens of high-resolution camera photos, uncompressed screenshots, or complex vector paths (EMF/WMF) force the parser to decompress gigabytes of temporary data in memory.
3. Deeply Nested Tables and Shapes: Documents that use tables inside tables, or hundreds of floating text boxes, require recursive layout calculations that delay rendering.
4. Browser Session Timeouts: The server may successfully create the converted document, but the client-side browser interface drops the status signal, leaving the progress wheel spinning.

---

Step-by-Step Diagnostic & Recovery Path

Step 1: Check Drive Root for Background Completion

The modal dialog frequently loses connection with Google’s backend even after the conversion successfully finishes.

1. Do not close the stalled tab immediately. Open a new browser tab and navigate to drive.google.com.
2. Look at the top of your Suggested files or sort your file list by Last modified.
3. Check whether a new Google Docs, Sheets, or Slides file with the same name has already appeared.
4. If the converted file is present, open it and verify its contents. You can safely close the spinning conversion tab.

Step 2: Downsample Embedded Images

If the file failed to convert, the most common culprit is raw image weight inside the document container.

1. Open the original document in its desktop program (such as Microsoft Word or LibreOffice).
2. Click on any picture in the document.
3. In Word, navigate to the Picture Format ribbon and click Compress Pictures.
4. Set the resolution to Print (220 ppi) or Web (150 ppi).
5. Uncheck “Apply only to this picture” to compress all images across the entire file.
6. Check Delete cropped areas of pictures to purge hidden image data.
7. Save the file and upload the smaller version to Google Drive to re-run conversion.

If the file exceeds total upload boundaries, review Fix: “File too large to convert” (The 50MB Limit).

Step 3: Segment Large Scans and PDFs

If you are converting a scanned PDF through Google’s OCR engine, large page counts will cause the system to hang before throwing a timeout.

1. Check the page count of your PDF. Google’s OCR pipeline is optimized for short files and enforces an extraction limit on long documents.
2. Use a PDF utility or your browser’s Print menu to split the document into segments of 10 pages or fewer.
3. Upload each segment individually and select Open with > Google Docs.
4. Combine the resulting Google Docs once converted.

If your document converts only partially or cuts off abruptly, consult Fix: “Page limit exceeded” for document conversion and How to Fix OCR Failures in Scanned PDF-to-Google Doc.

Step 4: Isolate Corrupt Vector Graphics

If a text-only document with a small file size triggers conversion delays, it typically contains a corrupted drawing element or an unreadable font definition.

• Save the file as plain .rtf (Rich Text Format) or clean .txt to strip corrupt vector instructions.
• For unexpected server drops on non-PDF documents, see Fix: “Cannot convert document: Internal Error”.