ZIP Inspector and EPUB Metadata Basics (What Browser Tools Can See)

ToolComb’s ZIP Inspector lists what is inside an archive in the browser. EPUB Metadata Editor edits title, author, and related fields in an EPUB package - also locally. Neither uploads your file to ToolComb’s application server to complete the job. Neither replaces antivirus, sandboxes, or DRM-aware publishing workflows.

Roundup context: Best free CSV, chart, and file inspector tools. Before sharing any export: Privacy checklist before you share a file.

ZIP Inspector: what you learn from a listing

Open ZIP Inspector with an archive you already have reason to trust - your CI artifact, a theme zip from your repo, an EPUB you wrote.

You typically see:

• Path names (content/chapter1.xhtml, __MACOSX/...)
• Uncompressed sizes (did someone commit a 400 MB asset?)
• Compression method hints

Use cases:

• Accidental secrets - .env, id_rsa, .pem before you send a zip to a client
• Bloat - duplicate node_modules nested twice
• EPUB sanity - mimetype present, no stray Mac resource forks dominating size

What listing does not do:

• Scan for malware signatures
• Prove a .pdf entry is not executable content
• Safe-open nested setup.exe because the name looked fine

For unknown downloads, use organizational policy: quarantine, scan, sandbox. Filename peeks are reconnaissance, not clearance.

EPUB structure in one minute

An EPUB 3 book is a ZIP with:

1. mimetype - plain text application/epub+zip (should be first, uncompressed in spec-faithful files)
2. META-INF/container.xml - points to the OPF
3. OPF package - metadata, manifest, spine (reading order)
4. Content - XHTML, CSS, images, fonts

Readers care about metadata for library shelves: wrong author breaks search. Broken spine breaks chapter order - that is beyond metadata-only edits.

EPUB Metadata Editor: safe, narrow fixes

Open EPUB Metadata Editor when Calibre shows Untitled or a typo in dc:creator. Update title, author, language, and related fields, then download the adjusted EPUB.

Good fits:

• Self-published author fixes a misspelled pen name
• Developer bundles docs as EPUB and needs correct dc:title
• Language code wrong (en vs en-US) for accessibility tooling

Bad fits:

• Merge two books into one volume
• Reflow PDF scan into reflowable text
• Remove publisher DRM
• Replace embedded fonts you are not licensed to ship

This tool is metadata, not layout studio. Sigil and Calibre remain the right hammer for TOC surgery and CSS.

ZIP Inspector on EPUB files

Because EPUB is ZIP, you can inspect the same file in ZIP Inspector before metadata edits:

• Confirm no absolute paths or ../ traversal patterns in names (packaging mistakes)
• See if cover.jpg exists where you expect
• Spot accidental inclusion of .DS_Store or editor swap files

Then open EPUB Metadata Editor for OPF-level fields without manually unzipping on disk - still local processing, still your responsibility for backups.

Privacy and sharing

Archives often contain PII - exported mail, HR zips, customer JSON inside a build. Local inspection avoids a cloud upload, but:

• Shared computers leave downloads in browser folders
• Screenshots of listings leak paths
• Re-zipping after edit still needs Privacy checklist

ToolComb does not need your ZIP on an application server to list or edit metadata in these tools. Your policy still governs whether the file should be opened at all.

What people break

They inspect a phishing ZIP, see Invoice.pdf, and double-click extract on desktop anyway.

They edit EPUB metadata but corrupt OPF XML with hand-edited tags outside the tool.

They assume Kindle Accept because title changed - validators differ by store.

They ship 200 MB EPUBs because high-res cover was never optimized - ZIP listing shows the blob; optimization is a different tool chain.

Honest summary

Use ZIP Inspector to see structure on trusted archives and catch stupid packaging mistakes. Do not treat it as malware-safe for unknown ZIPs. Use EPUB Metadata Editor to fix library fields, not to rewrite the book. Both run locally in the browser; neither replaces security hygiene or a full ebook workflow.