Fix it now
- Drop the file
- Repair runs locally
- Download the result
When PowerPoint says "PowerPoint found a problem with content in [name].pptx" and offers to attempt a repair, it has opened the file, started reading its internal parts, and hit one it can't parse — a damaged ZIP index or a malformed piece of XML. It refuses the whole presentation rather than showing you the good slides. But a .pptx is not one opaque blob: it's a standard ZIP package of separate XML and media files (the OOXML / Open Packaging Conventions format). Drop it above and the tool rebuilds that package in your browser, recovering the parts that survived — nothing is uploaded.
What a .pptx actually is
Rename a .pptx to .zip and you can open it: underneath, it is an ordinary ZIP archive following Microsoft's Office Open XML (OOXML) layout. Inside you'll find [Content_Types].xml (which declares the type of every part), a _rels/ folder of relationship files that wire the parts together, and the presentation body under ppt/: ppt/presentation.xml (the deck's backbone and slide order), one ppt/slides/slide1.xml, slide2.xml… per slide, plus slideLayouts/, slideMasters/, theme/, and a ppt/media/ folder holding the embedded images, audio and video as ordinary files.
That structure is why the error is usually survivable. Your text lives as readable XML inside the slide parts; your pictures are whole files in ppt/media/. If the ZIP's central directory (its table of contents at the end of the file) was damaged by a truncated download or a bad transfer, or if one XML part is malformed, PowerPoint stops — but the vast majority of the parts are still intact and extractable.
How the in-browser repair recovers your slides
The tool treats the .pptx as what it is — a ZIP/OOXML package — and works at two levels. First, the container: if the ZIP index is broken or missing, it scans the file for the local headers of each stored part and rebuilds the archive from the entries that survived, so parts that were fully written come back even when the directory at the end was lost. Second, the parts: it checks the key XML pieces ([Content_Types].xml, presentation.xml, the slide parts and their relationships) and reassembles a valid package PowerPoint will open, salvaging every slide whose XML is well-formed and every media file that's intact.
Honest limits apply. If a specific slideN.xml is itself corrupted beyond parsing, that individual slide's editable content may be lost even though the rest of the deck opens — sometimes its images survive in ppt/media/ even when the slide markup doesn't. And bytes that a truncated download never delivered can't be recreated; if the original is still available, re-downloading it is always the cleanest fix. Everything here runs in your browser, so a confidential deck is never copied to a server just to be repaired.
What this can and can't fix
Can fix
- A .pptx whose ZIP central directory was damaged or truncated — parts that were fully written are rebuilt
- Presentations where one malformed part blocks opening but the other slides are intact
- Recovering slide text and layout from slide parts whose XML is still well-formed
- Recovering embedded images and media that survived in ppt/media/
Can't fix
- An individual slide whose own XML is corrupted beyond parsing (its editable content may be unrecoverable)
- Parts of the file that a truncated download never delivered (re-download the original if you can)
- Password-encrypted .pptx files when the password isn't supplied
- Files that read as 0 bytes or mostly zeros
If a repair fails, we tell you why (missing data versus broken structure), and you are never charged for a failed repair.