Offline Web Package Builder
Paste a web page you own and select its CSS and image files. The builder rewrites matching relative paths, strips scripts and network references, and creates an offline ZIP with index.html, an assets folder and a SHA-256 file manifest. A sandboxed preview and missing-resource report help you inspect it before download. It packages only files you supply; it does not crawl a URL or download remote assets.
Key features
- Repackage supplied HTML plus local PNG, JPEG, GIF, WebP and CSS assets into a usable ZIP
- Rewrite relative image and stylesheet references while reporting missing and blocked paths
- Remove scripts, forms, embeds, external resources and active HTML attributes
- Preview the result in a sandboxed frame with restrictive Content Security Policy
- Include SHA-256 hashes and byte counts for index.html and every bundled asset
How to use
- Paste your HTML or load the example, then select the CSS and image files it references.
- Edit each selected file's relative path so it matches the path used by the HTML or CSS.
- Build the package and review the preview, missing resources, blocked references and file hashes.
- Download the ZIP, extract it and open index.html locally to use the packaged page offline.
Use cases
- Carry a static field guide or lesson page without connectivity
- Package a local HTML prototype with its styles and images for review
- Find missing relative resources before archiving a small static page
- Share an inert, self-contained reference page as a ZIP
Frequently asked questions
Can this tool download a whole website from a URL?
No. It uses only HTML, CSS and image files you select. It does not crawl sites or fetch external resources.
Will JavaScript, forms or embedded media work in the ZIP?
No. The builder removes scripts, forms, frames and other active elements, and adds a restrictive Content Security Policy. It is intended for static reference pages.
How are missing images and styles handled?
Unmatched local references are listed in the report. The generated page omits those broken references; add the file with a matching relative path and build again.
What does the SHA-256 manifest prove?
It lists each packaged file's hash and byte count so changes can be detected later. It is not a digital signature or proof of authorship.
Can I use nested folders?
Yes. Select files and edit their package paths, such as styles/site.css or images/photo.png. Absolute, traversal and unsafe paths are rejected.
Privacy
HTML and files are processed in this browser tab; this tool does not upload or fetch them. The ZIP contains the content you supplied, after sanitization, so review it before sharing. Its hashes detect later file changes but do not prove who created the ZIP.
Comments & questions