This guide covers “wordpress to static html” in plain language. Exporting a WordPress site to static HTML means converting your dynamic pages into plain files that any web host can serve, with no PHP or database needed. People do this for speed, security, cheap hosting or to archive a site. This guide covers four methods and what to expect.
Why go static?
- Speed. Plain files load fast and cache well.
- Security. No PHP or database to attack.
- Cheap hosting. Static files can sit on inexpensive hosts or a CDN.
- Archiving. A snapshot of a finished campaign or retired site.
- Portability. Move to any host, or leave WordPress entirely.
What stops working on a static site
Anything that needs a server to run code at request time won’t work as-is:
- Contact and other form submissions (use a form service instead)
- On-site search
- Comments and user logins
- Dynamic e-commerce carts and checkout
Static sites work best for brochure sites, blogs, documentation and portfolios.
Method 1: A static export plugin
Plugins such as Simply Static and WP2Static crawl your site, save each page as HTML and bundle the assets into a zip or push them to a host.
- Install and activate the plugin on your live or staging site.
- Set your destination URL and which content to include.
- Run the export and download the result.
- Upload the files to your static host and test.
This is the most beginner-friendly route and handles link rewriting for you.
Method 2: Your theme’s built-in export
A few themes and builders include their own export tool. Tuli Builder, for example, has an Export Site tab that crawls the public front end and produces a zip of plain HTML with assets and rewritten links. If your theme offers this, it is the simplest option because it needs no extra plugin.
Method 3: Mirror it with wget
For developers, the command-line tool wget can mirror a site:
wget --mirror --convert-links --adjust-extension
--page-requisites --no-parent https://example.com/
It downloads pages and assets and rewrites links to work locally. Check the result carefully, because JavaScript-loaded content and some assets may need extra attention.
Method 4: A site copier like HTTrack
HTTrack is a free desktop app that does the same job with a graphical interface. Enter your site’s URL, choose a folder and let it download. It is handy for one-off archives.
After exporting: your checklist
- Open the files locally and click through key pages.
- Check images, fonts and scripts load from the right paths.
- Replace forms with a form service or a serverless function.
- Add redirects for any URLs that changed.
- Submit an updated sitemap to search engines if URLs changed.
- Keep your WordPress copy as the editing environment if you plan to re-export later.
Where to host a static site
Any web host works, as do static-friendly platforms such as Netlify, Cloudflare Pages, GitHub Pages and object storage with a CDN. For example, many have generous free tiers for small sites.
WordPress to static HTML FAQ
Will my SEO survive going static?
Yes, if URLs, titles, meta tags and internal links stay the same. As a result, keep URLs identical or add 301 redirects.
Can I keep editing in WordPress?
Yes. A common setup keeps WordPress private for editing and publishes a static copy publicly, re-exporting after changes.
Does exporting delete my WordPress site?
No. Exporting copies the public output. Your WordPress install stays untouched.