Benchmark · 3 October 2026
Us vs Office's own repair
The same broken files, given to Microsoft Office's "recover the contents" prompt, to LibreOffice's repair, and to us. Modern and pre-2007 formats alike.

Content recovered from 384 damaged files
Words and numbers that came back, against the undamaged original. Files that opened at all: Office 65%, LibreOffice 63%, us 84%.
Files that opened after repair, of 234
Files broken for real, not by us: crash reports, fuzzing finds and security test cases. None crashed the service.
Content recovered
| Format | Files | Content recovered |
|---|---|---|
| .xlsx | 72 | 34% 35% 75% |
| .docx | 60 | 57% 54% 87% |
| .pptx | 72 | 72% 51% 86% |
| .xls | 60 | 71% 68% 82% |
| .doc | 60 | 67% 84% 91% |
| .ppt | 60 | 20% 30% 63% |
How it was run
- Damaged files
- 384 copies of real files from the Apache POI test files, each broken one of 12 ways files really break: cut off, bad sectors, flipped bits, an overwritten header, a lost index, an interrupted save, a text-mode transfer.
- Broken in the wild
- 234 files from LibreOffice's broken-file test suite (the qa/**/pass and qa/**/fail folders).
- Office
- Microsoft 365 for Mac 16.113: the file opened, the "recover the contents" prompt accepted.
- LibreOffice
- LibreOffice 26.8, in its repair mode.
- Opens
- The result opens in Microsoft Office with no prompt.
Us vs OfficeCLI
False alarms on 5,342 workbooks Excel opens
From xlsx-corpus-bench, each verified to open in Excel. OfficeCLI v1.0.152 rejected 4.5% of them.· lower is betterDataset
Faults found, of 133
A 156-case fault corpus plus files written by common libraries. We repaired 104 of 104 fixable files; OfficeCLI reports but doesn't repair.
See it on your own file.
Repair a file