How to combine a saved web page into one HTML file for offline use

Understand HTML-only and complete-page saves

Browsers may save just the HTML document or save related images and stylesheets in a companion folder. In Firefox, the “Web Page, complete” option saves the page with additional files, whereas “Web Page, HTML only” does not include its images.

If you plan to make a single file later, keep the HTML and its companion resources together. Save options vary by browser. If you already have an HTML file and a similarly named folder, keep both.

Prepare the HTML and its related files

If the HTML references local images or CSS, those files must be present. Moving a resource folder separately or renaming it can break the paths used by the HTML.

Offline Web Packager accepts HTML files, ZIP archives and folders. For a page with several files or subfolders, keep its directory structure intact and add the folder, or package that structure as a ZIP first.

Load the files and choose the entry HTML

Open Offline Web Packager and add the saved HTML, ZIP or folder. You can also drag and drop files on a computer. The app analyzes input files in your browser without running the imported HTML or JavaScript during inspection.

If several HTML files are present, check the detected entry HTML. For example, if your starting page is `index.html`, make sure that file is selected. Change the selection if you need a different page.

Read the compatibility result

The check returns one of three results: “Can be combined,” “Review needed,” or “Cannot be made into one file as-is.” Continue to packaging only when the result says the page can be combined.

“Review needed” identifies items such as filename case mismatches that deserve attention. “Cannot be made into one file as-is” means files are missing or unsupported features were detected. You can choose “Save check report” to keep the result and its explanations as a text file, including when packaging is blocked.

Know which resources can be included

For supported static pages, the tool can embed local CSS, classic JavaScript, images, fonts, favicons and size-limited audio or video. It also examines references such as CSS `@import`, `url(...)` and image `srcset`.

It does not automatically rewrite runtime `fetch()` calls, ES Modules, Web Workers, Service Workers, WASM loaders or local iframes. It cannot merge a multi-page website into one app or download missing resources from external URLs.

Create and save the single HTML file

If the result is “Can be combined,” choose “Create one HTML file.” The app checks the generated file again for unresolved local paths and resources that were not included. Normal saving is blocked if those checks fail. When generation succeeds, choose “Save HTML.”

Open the saved file and inspect its images, text and layout. Opening it without an internet connection helps reveal any remaining online dependencies. A script in the original page may still attempt network access when the generated HTML runs.

Check input limits and security considerations

The input limits are 50 MB per file, 100 MB total and 2,000 files. Browser support for choosing folders and decompressing ZIP files varies. If the input is too large or folder selection is unavailable, check the input method and file sizes.

The app processes the added files locally and does not upload them for conversion. However, it cannot certify that generated HTML is safe to execute. Treat HTML from unknown sources carefully; this is not a malware scanner.

Tips and limitations

• The tool does not fetch missing images from the web. If the original saved HTML lacks the related resources, save the page and its files again.
• When several HTML files are present, confirm the entry HTML so the correct page is packaged.
• If the result is “Review needed” or “Cannot be made into one file as-is,” read the reported reasons before trying again.
• Before sharing generated HTML, review what it contains and how its scripts behave. Successful packaging is not a safety certification.