Limitations

docray is honest about what it does not do. Everything here is by design or known, not hidden.

• PPTX is element-only. It has no character/word boxes, faithful rendering, or chart/SmartArt geometry. See PowerPoint extraction.
• DOCX/DOCM is flow-only. It has no resolved y coordinates, line boxes, or trustworthy pages. Optional approximate-page hints come only from Word’s cached break markers. See Word extraction.
• No OCR. Raster-only pages are flagged ("scanned": true) but their text is not recovered — recovering it requires OCR downstream.
• No semantic layer. docray reports physical structure — it does not classify headings or lists and does not infer reading order. PDF text and words appear in content-stream order; PPTX elements appear in z-order.
• Silently recovered corruption. When the underlying parser encounters a corrupt page it sometimes recovers by rendering an empty page without reporting an error; such pages are indistinguishable from genuinely blank ones.
• Shading objects (gradient fills) are skipped, with a warning per skipped object.
• Job state is instance-local — single-instance deployments are the supported topology.
• Rotated-page text grouping: geometry on rotated pages is correct, but text that renders vertically groups one character per line.
• No HTTP response compression — front docray with a reverse proxy and enable gzip/brotli there if you transport large char-level responses.