Developer · Info
Can You Export WordPress to HTML? The Short Answer

Short answer
Yes. WordPress has no built-in HTML export, but plugins like Simply Static or mirroring tools like wget can save every page as static HTML with its CSS, scripts and images. Dynamic features such as forms, search, comments and checkout stop working unless you replace them.
Key takeaways
- WordPress core only exports XML content, not HTML.
- Simply Static and similar plugins create a static copy.
- Forms, search, comments and carts need replacements.
- Static files can be hosted cheaply and load fast.
- You must export again after every content change.
Can you export WordPress to HTML?
Yes, you can export a WordPress site to static HTML files with a plugin such as Simply Static or with a site mirroring tool, but dynamic features like forms, search and comments stop working.
WordPress normally builds each page with PHP and a database every time someone visits. A static export runs that process once, saves the finished pages as HTML, and packs them with CSS, JavaScript and images.
The result can be hosted almost anywhere, even on services that do not run PHP.
You keep WordPress as your editor, often on a private or local server, and publish the HTML copy to the public.
Does WordPress have a built-in HTML export?
No, WordPress core has no HTML export; its Tools, Export screen creates an XML file of content for importing into another WordPress site, not a browsable website.
The built-in exporter is designed for moving posts and pages between WordPress installs. The file includes content and metadata but no theme design.
If you open that XML file in a browser, you see raw data, not your website.
For static HTML you need a plugin or an external tool. If the XML export itself fails, see our WordPress export error fix guide.
How do you export WordPress to HTML with a plugin?
Install a static site plugin like Simply Static, run a full export from its menu, then download the zip or deploy it directly to a host.
Simply Static is one of the most used options on WordPress.org. It crawls your site, saves every page and asset, and rewrites links so they work in the static copy.
The general steps are:
- Install and activate the plugin from Plugins > Add New Plugin.
- Open its settings and choose how URLs should be written, such as absolute or relative.
- Pick a delivery method, such as a zip file or a local folder.
- Run the export and wait for the crawl to finish.
- Download the zip and upload the files to your static host.
Another option is Export WP Page to Static HTML, which can export selected pages rather than the whole site.
Plugin features, especially deployment targets and form handling, can differ between free and paid versions. Check the plugin page for what is included.
Can you export WordPress to HTML without a plugin?
Yes, a site mirroring tool such as wget can download every page and asset from the live site, though it needs some command-line comfort and cleanup.
A typical mirror command looks like this:
wget --mirror --convert-links --adjust-extension --page-requisites --no-parent https://example.com/
The GNU Wget manual explains each option. In short, the command follows links, saves pages as .html files and rewrites links to work offline.
This works for small, simple sites. It can miss pages that are not linked from anywhere, files loaded by JavaScript, and assets referenced only in CSS.
What stops working after an HTML export?
Anything that needs PHP or the database at the moment a visitor arrives stops working, including forms, search, comments, logins, carts and most membership features.
| Feature | Works as static HTML? | Common replacement |
|---|---|---|
| Pages and posts | Yes | None needed |
| Images, CSS, scripts | Yes | None needed |
| Contact forms | No | Third-party form service |
| Site search | No | JavaScript search index |
| Comments | No | Hosted comment service |
| WooCommerce cart and checkout | No | Keep WordPress dynamic |
| User logins and members | No | Keep WordPress dynamic |
If your site relies on these, a static export is a poor fit, or you need replacements for each feature.
Why would you export WordPress to HTML?
People export to HTML for speed, security, cheaper hosting and archiving, because static files load fast and give attackers no PHP or database to target.
Common reasons include:
- Archiving an old site that no longer changes, such as an event or campaign.
- Security, because a static site has no login page or plugins to exploit.
- Cost, since static hosting is often free or very cheap.
- Speed, as pages are pre-built and can be served from a CDN.
Our comparison of a static site vs WordPress covers the tradeoffs in detail.
Where can you host the exported HTML?
Any web server can host static files, including static hosting services like Cloudflare Pages and GitHub Pages, object storage, or your existing hosting account.
Cloudflare Pages and GitHub Pages both serve static files and can rebuild when you push new files.
You can also upload the HTML to a normal web host with FTP. It works like any old-style HTML site.
Check that your chosen host handles redirects and custom 404 pages if your old site used them.
How do you keep the static site updated?
Edit content in WordPress as usual, then run the export again and redeploy, because the HTML copy does not update itself.
Most people keep WordPress on a local machine, a staging server or a password-protected subdomain. Only the static copy is public.
Every time you publish or edit a post, run a new export. Some plugins can push changes to a host automatically or export only changed pages.
Our guide on setting up a staging site for WordPress explains how to keep a private editing copy.
Is exporting to HTML the same as going headless?
No, a static export saves finished HTML pages, while headless WordPress keeps the database live and lets a separate front end request content through an API.
Headless setups use the WordPress REST API or GraphQL. The front end can still be static, but it is built by a separate framework rather than by WordPress itself.
A plugin export is simpler and needs no coding. Headless offers more flexibility but needs a developer.
Read headless WordPress vs traditional if you are weighing the two.
What problems should you expect?
The usual problems are broken links from wrong URL settings, missing assets loaded by scripts, pages not linked anywhere being skipped, and large exports timing out.
Fix them like this:
- Broken links: switch between relative and absolute URL settings and export again.
- Missing files: add extra URLs or folders in the plugin's include settings.
- Unlinked pages: add them manually or link them from a sitemap.
- Timeouts: raise PHP time limits or run the export on a local copy.
Test the static copy on a temporary address before switching your domain.
Should you export your WordPress site to HTML?
Export to HTML if your site is mostly content that rarely changes and you can live without built-in forms, search and comments; keep WordPress dynamic for stores, members and busy blogs.
Before you switch, take a full backup of the WordPress site. Our guide on how to back up a WordPress site shows how.
Keep the original WordPress install safe. It is your editor and your recovery copy if the static site ever needs rebuilding.
Frequently asked questions
Can I convert my WordPress site to HTML for free?
Yes. Free plugins on WordPress.org, such as Simply Static, can export a full site to HTML. Command-line tools like wget are also free. Paid versions mainly add automatic deployment and extra integrations.
Will my WordPress theme design be kept in the HTML export?
Yes. A static export saves the pages exactly as visitors see them, including theme styles, fonts and images. Only features that need PHP or the database while a visitor is on the page stop working.
Can I export WooCommerce to static HTML?
You can export product pages, but the cart, checkout, accounts and stock updates need PHP and the database. A real store should stay on dynamic WordPress hosting.
Do I need to keep WordPress after exporting?
It is wise to keep it. WordPress remains your editor, and you export again whenever content changes. Keep it on a private or local server so it is not exposed to the public.
Is a static HTML site better for SEO?
Static pages can load faster, which helps users, but search rankings depend mostly on content and links. Keep the same URLs and redirects when switching so you do not lose existing rankings.
Sources
- Simply Static WordPress.org Plugins
- Export WP Page to Static HTML WordPress.org Plugins
- GNU Wget Manual GNU Project
- Cloudflare Pages Cloudflare Docs
- GitHub Pages documentation GitHub Docs
Is your product missing, or something out of date?
Tell us what to add or correct. We read every note and reply when we need a source. A message does not buy a ranking.
Thanks — we review requests within 3 business days.
Related guides
About the editors
Researched from the primary sources listed above and checked against our editorial rules before publishing.


