Page Source Capture: Save Page as ZIP

Save any web page as one verified .zip: rendered DOM, assets, source maps and a site-intel report for extension builders.

Save any web page as one verified .zip: what you see, what the server sent, and the original source behind it. View Source shows the HTML as the server sent it, before any JavaScript ran. Page Source Capture saves what the browser is showing now: the rendered DOM, including open and closed shadow roots, iframe content and CSS-in-JS rules that never appear in the HTML. Stylesheets, scripts, fonts and images are rewritten so the copy opens with no network. The raw server HTML is kept beside it, and original source files are unpacked from source maps. 👥 BUILT FOR ▸ Extension developers testing content scripts and injected UI against real pages ▸ Front-end engineers and QA reproducing a bug or documenting a page state ▸ Researchers, archivists and auditors who want a clean, checksummed copy ▸ Anyone who needs an offline copy of a page they own or may copy 📦 WHAT IS IN EVERY ARCHIVE ▸ index.html: the rendered DOM, with open and closed shadow roots, iframe content, and CSS that exists only in the CSSOM ▸ original-server.html: the raw response, for comparison ▸ assets/: stylesheets, scripts, fonts and images, rewritten to work offline ▸ sources/: original files recovered from source maps ▸ frames/ and runtime/: iframe documents, plus chunks and workers loaded at runtime ▸ intel/REPORT.md: the site-intel report ▸ screenshot.png ▸ SHA256SUMS.txt: every file checksummed ▸ An offline-readiness score and a plain list of anything that could not be saved, with the reason 🔍 SITE-INTEL REPORT A plain-language read-out of how the page is built and what that means for code you inject: Content Security Policy, frame tree, open and closed shadow roots, about:blank and srcdoc frames, z-index and top-layer hazards, CSS-in-JS, detected frameworks, storage and cookie key names (names only, never values) and traces left by other extensions. Findings are heuristics. Treat them as leads, not an audit. 🧪 DEEP MODE (Alt+Shift+D) Attaches Chrome DevTools to the tab for a single capture to keep the exact network responses: a HAR with response bodies, a single-file MHTML snapshot and a full-page screenshot. Optionally reloads the tab to record the whole network. Chrome shows its debugging banner while it runs, and the extension detaches when the capture ends. ◻ CAPTURE SCOPE This tab, selected tabs, a window, or all windows. ✓ WHAT "VERIFIED" MEANS Before the download starts, every file is re-read and matched to its checksum. That proves the archive is intact. It does not prove the page content is authentic, and a capture is not forensic evidence. 🔒 PRIVATE BY DESIGN ✓ Runs entirely on your computer: no servers, accounts, analytics, ads or remote code ✓ Does nothing until you start a capture ✓ Typed values, hidden inputs, CSRF tokens and cookie and authorization headers in the HAR are redacted by default. Password fields are never saved. Redaction is best effort, so review a capture before you share it ✓ "Report a problem" opens a draft in your own email app; nothing is sent until you press send ✓ "Clear saved data" in the popup. Privacy Policy and Terms are linked there ⚠ LIMITS, STATED PLAINLY ▸ Video and audio are not saved, and scripts are saved inert ▸ Pages that detect or block saving can produce incomplete captures; the report lists what failed ▸ Standard mode reads Chrome's resource-timing list, which is capped at about 250 entries, so runtime-loaded resources can be incomplete on very heavy pages. Deep mode has no such limit ▸ Only capture pages you own or are allowed to copy © 2026 Win Htut Hein. All rights reserved. Independent project, not affiliated with or endorsed by Google or Chrome.