How to use Offline Static-Site Bundle Packager
- Enter the supported text bundle or choose a bounded static-file ZIP.
- Declare any served path prefix and the active-content stop policy.
- Inspect removed/unresolved references and reopen the exported static bundle.
Example: Offline Static-Site Bundle Packager
Package supplied static HTML, CSS and assets into a reviewed ZIP with local references and an omissions report.
Options
- Path prefix
- The prefix maps root-relative references into the supplied archive. References outside it remain reported rather than silently redirected.
- Active content
- The stop setting refuses active findings for review. The other mode removes the documented active subset and lists changes; it is not a general sanitization certificate.
Supported inputs and limits
Where your input is processed
This tool processes your input in this browser. Your text and files are not uploaded to UseFreeTools. Check this tool's limits for anything it may save on your device.
A static archive can omit essential behavior
Removing scripts can change a page that depended on them. Remote addresses are not fetched, and unresolved assets cannot receive an offline guarantee. Review the manifest and each important page before publishing or replacing a source tree.
Questions about Offline Static-Site Bundle Packager
Can it package a dynamic application?
It prepares the supplied static subset and does not preserve server or script behavior.
Are remote assets downloaded?
No. Their references remain reported and unresolved for offline use.
Is the output certified safe HTML?
No. The removal pass is bounded; review the exported files before publishing.