iloveepubLokaal verwerkt — bestanden verlaten je apparaat nooit
EPUB repareren
Eén tool voor de hele reddingsklus: sleep een boek aan dat niet opent, dat met een kapotte inhoudsopgave opent, of dat naamloos in je boekenkast verschijnt. De healthcheck draait eerst, structurele schade wordt automatisch gerepareerd, ontbrekende omslag en metadata vul je zelf in — en het gerepareerde boek wordt opnieuw gecontroleerd voordat je het downloadt. Dat alles gebeurt in je browser; het bestand verlaat nooit je apparaat.
01Selecteer je EPUB
The books that reach this page
A download that Apple Books and Calibre both refuse, often because a zip tool compressed the mimetype entry or moved it off the first position. A merge or a hand edit whose table of contents still points at files that were removed. A shelf that shows the filename because dc:title was never written. You do not yet know which of those it is. The health check is the point of the page.
Come here before the editor. An editor needs a package it can parse. This tool tells you whether the package can be parsed, repairs the structural layer, and runs the same check on the result before the download appears.
The files a repair is allowed to rewrite
META-INF/container.xml is rebuilt when it is missing or malformed. The archive is repacked so mimetype is the first record, stored rather than deflated, containing exactly application/epub+zip. Manifest items and spine entries that point at missing files are removed. A missing EPUB 3 nav, or a missing EPUB 2 NCX, is rebuilt from the chapters that exist. Dead links in a TOC that is already there are stripped.
Chapter HTML, images, and CSS are copied byte for byte. They are not re-encoded and not tidied. Title, author, and cover change only when you type or upload them. Those writes are dc:title, dc:creator, meta name=cover, and the cover-image property. The same checklist then runs on the bytes you are about to download. The cap is 120 MB, with a warning past 100 MB because the repair holds the archive in memory.
Damage this page will name and not pretend to fix
A file that is not a valid ZIP, a book with no readable chapters, and a DRM-protected file are reported as beyond repair. A truncated download has to be fetched again. DRM is not removed. Broken prose inside an otherwise valid chapter — unclosed tags in one story, a stylesheet that hides the text — is not rewritten. The health check does not tidy HTML.
Fonts are not subsetted and images are not recompressed. If the report says the structure is healthy and a reader still misbehaves, the problem is in the chapter markup, which is an editor's job.
Calibre Polish fixes more, and changes more
Calibre's Polish books and Modify EPUB can subset fonts, recompress images, and flatten CSS while they repair a book. That extra cleanup is useful. It is also how an innocent repair changes the typography. The editor's check is closer to EpubCheck, and it leaves you to try the file yourself.
This page stays in the package layer: container, mimetype, manifest, spine, nav, cover markers, Dublin Core. It then repeats its own checklist before download. Use Polish when you want the font and image cleanup. Use this when the chapters should stay byte for byte. If the report says the archive is not a ZIP, Calibre cannot resurrect it either.
Hoe je een kapotte EPUB repareert
Sleep het kapotte boek aan
Kies een willekeurig .epub-bestand — eentje dat niet opent, een kapotte inhoudsopgave toont of naamloos in je boekenkast verschijnt. Er wordt niets geüpload.
Lees het gezondheidsrapport
De diagnose somt elke check op — container, mimetype, verwijzingen, inhoudsopgave, omslag, metadata — gemarkeerd als gezond, repareerbaar of niet te redden.
Pas de reparaties toe
Structurele reparaties draaien automatisch. Ontbreken de omslag of de titel-/auteur-metadata, dan vul je ze in dezelfde stap aan — allebei optioneel.
Download het geverifieerde boek
De gerepareerde EPUB wordt vóór de download opnieuw gecontroleerd. Je krijgt een reparatierapport en een 'alles oké' — niet zomaar een blinde succesmelding.
Veelgestelde vragen
A zip tool re-saved my EPUB and now nothing opens it. What broke?
Often the mimetype entry. Readers expect it first in the archive, stored rather than deflated, containing exactly application/epub+zip. A general zip app breaks that. The repair writes the entry back and runs the health check again on the result.
Which files does a repair rewrite?
container.xml when it is missing or malformed, the mimetype entry, the OPF when dead manifest or spine references are removed, and nav or NCX when they are missing or contain dead links. Chapter HTML, images, and CSS are copied through. Title, author, and cover change only if you supply them.
Calibre's Polish books also claims to fix EPUBs. Why use this?
Polish can subset fonts, recompress images, and flatten CSS while it fixes the package. That changes more than the structure. This page does not do those transforms. It repairs the package and shows the same checklist again before download.
The report says the book cannot be fixed. Should I try Calibre?
If the file is not a valid ZIP, Calibre cannot read it either. Download it again. If it is DRM, neither tool should strip it. If the package is fine and one chapter is broken HTML, Calibre's editor or Sigil can edit that chapter. This check does not rewrite prose markup.
Does the second check send the book anywhere?
No. The re-check is the same in-browser inspection as the first, on the bytes about to be downloaded. A cover you chose to skip stays listed. It is not described as a failure of the structural repair.