How to use Offline Static-Site Bundle Packager
- Choose a pasted text bundle/editable text-file rows or one ZIP of supplied static files. Text rows use @@ relative/path file separators; ZIP mode can retain binary assets.
- Set a served subfolder prefix when needed, then choose whether active-content findings should stop packaging or have the documented subset removed.
- Inspect the intake checklist and create the bundle. Review the reference CSV, text report and manifest alongside the ZIP.
- Extract a copy and test its important pages offline before using it. Missing/remote references and removed scripts can leave features incomplete.
Example: Offline Static-Site Bundle Packager
Package the supplied small two-page static example while removing its script and reporting the external reference.
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.
- Bundle source
- A pasted bundle carries text files only. A ZIP can include binary assets, and it is read locally.
- Pasted text bundle
- Start each file with a line that begins with "@@ " and the relative path. Everything until the next "@@ " line is that file. Text files only.
- ZIP of static files
- One ZIP up to 6 MiB with 60 entries or fewer. Unsafe paths (absolute, parent-relative, reserved device names or reserved keys) are refused.
- Root-relative prefix
- A path prefix such as docs/ when the site is served from a subfolder. A reference like /docs/a.css then maps to the entry a.css. A root-relative reference outside the prefix is reported, not rewritten.
- Stop when active content is found
- When on, packaging stops so you can review the active content yourself. When off, scripts, event attributes, javascript:/data:text/html URLs, @import rules and CSS expressions are removed and listed in the report.
Supported inputs and limits
- Up to 60 entries, 300 KiB per expanded entry and 6 MiB total expanded data;
- ZIP intake is also limited to 6 MiB.
- Text input is UTF-8;
- ZIP can contain supported binary assets.
- Unsafe paths are refused.
More details
The removal mode covers the documented HTML/SVG/CSS constructs only, not a general safety certificate.
Remote HTTP(S) references stay remote and are not downloaded.
No live mirroring, dynamic-application conversion or assurance that removed-script behavior survives.
The table shows the first 300 findings; inspect the exported reports.
Where your input is processed
This tool does not upload your inputs. See the limits for anything saved 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.