Free online WEBARCHIVE to HTML converter

Some editors, web servers, browsers, and document systems accept an ordinary .html file but not Safari’s .webarchive container. Converting the file extracts a usable page for editing, publishing, inspection, or sharing without Safari.

What the WEBARCHIVE format is

.webarchive is Apple’s Safari Web Archive format, commonly created on macOS through File → Save As with Web Archive selected. It is usually a binary or XML property-list container, not a normal HTML document.

The archive can contain a main HTML resource, images, CSS, JavaScript, fonts, URLs, MIME types, and other metadata. Safari and some WebKit-based software use these resources to reopen a saved page for offline viewing. The format is most often found in Safari saves, Mac backups, research archives, and older offline web-page collections.

What the HTML format is

.html is the standard markup format for web pages. Browsers render its elements, links, styles, and scripts, while code editors, publishing systems, web servers, indexing tools, and version-control systems can process the file as text.

HTML usually refers to the document structure only. Images, stylesheets, scripts, and fonts are commonly separate files referenced by URLs or relative paths, so extracting the main HTML resource does not necessarily create a complete offline copy of the archived page.

Convert it on 101convert.com

1. Open the WEBARCHIVE-to-HTML converter on 101convert.com.
2. Select the .webarchive file with the file picker or drag it into the upload area.
3. Choose HTML as the output format if it is not selected automatically.
4. Start the conversion and download the resulting .html file.
5. Open the file in a browser and check its text, encoding, images, styles, links, and scripts before publishing or editing it.

The online method requires no installed software. Do not upload archives containing confidential pages, personal data, private URLs, or authentication-related content unless the service’s handling and retention terms are acceptable.

Export it with Safari on macOS

1. Open the archive in Safari.
2. Choose File → Save As.
3. Select Page Source or an HTML-related option if the Safari version provides one.
4. Save the result with an .html extension.

Safari’s save options vary by version. Some versions expose only Web Archive, and the HTML export may contain only the page source rather than the archived images, stylesheets, fonts, and scripts. Use the online converter or local extraction method when Safari does not offer an HTML option.

Extract the main resource with Python

Python 3’s standard-library plistlib module can read many XML and binary WEBARCHIVE files. This method writes only the archive’s main resource:

import plistlib
import sys
from pathlib import Path

if len(sys.argv) != 3:
    raise SystemExit("Usage: python extract_webarchive.py input.webarchive output.html")

with Path(sys.argv[1]).open("rb") as file:
    archive = plistlib.load(file)

main = archive["WebMainResource"]
data = main["WebResourceData"]
if not isinstance(data, bytes):
    raise TypeError("WebResourceData is not binary data")

Path(sys.argv[2]).write_bytes(data)

Save the code as extract_webarchive.py, then run it from Terminal, Command Prompt, or PowerShell:

python3 extract_webarchive.py "saved-page.webarchive" "saved-page.html"

On Windows, the command may be python instead of python3. The output is normally the main HTML resource. Check the archive’s WebResourceMIMEType if the result is not readable HTML; the main resource can also be an image, PDF, or another content type.

Quality and compatibility limits

• Extracting WebMainResource alone does not extract resources listed under WebSubresources. Images, CSS, fonts, and scripts can therefore be missing.
• The HTML may retain absolute URLs to the original website. Such resources can disappear when the site changes, the computer is offline, or the server blocks cross-origin requests.
• A complete offline reconstruction requires extracting the subresources, assigning them local filenames, and rewriting the HTML references. The required paths and resource metadata are not identical in every WEBARCHIVE.
• The saved main resource may be the original document source rather than the final DOM generated by JavaScript. Content inserted after page load may not appear in the extracted HTML.
• Interactive features that depend on cookies, local storage, authentication, server-side requests, browser APIs, plug-ins, or external services may not work after conversion.
• Character encoding can change during export. Inspect non-Latin text and the document’s declared charset before editing or publishing.
• Conversion changes the container format and does not preserve every Safari-specific metadata field or guarantee pixel-identical rendering.