WordPress → Next.js · Astro · any stack
Every other exporter hands back your words and loses the layout. Wordprex opens each page in a real browser, measures it, and rebuilds the design around your content — with comments, search, forms and your shop still working.
Read-only, and nothing is installed. In a few seconds you will see what is on your site and what would come across — before deciding anything.
Exports to
Every page is opened in a real browser, photographed, and measured — where each band starts and stops, its background, the image behind it, the grid the theme laid out on. That is what makes rebuilding the layout possible instead of guessing at it from a screenshot.
Comments arrive with their threads intact and anything WordPress was holding for review is still held. Full-text search, working forms with a submissions queue, and for shops: products, cart, checkout and your order history. A static HTML copy loses all of it.
Plain Markdown for content, React or Astro for the site, SQLite for the runtime. No account required to keep it running, no service to keep paying, nothing phoning home. Delete us and the site carries on.
Paste the URL. It reads through the WordPress REST API, which is on by default — nothing is installed, and only what the public can already see is read. An Application Password unlocks drafts, private pages and orders if you want them.
A browser opens each page, waits for it to settle, photographs it, and records its layout and real theme colours — read from what actually rendered, not parsed out of stylesheets.
The result is a project that runs: npm install, npm run dev, your site. Media, redirects for every old URL, and your content as Markdown you can edit by hand or through the admin.
Most tools in this category flatten your site to HTML. That is a fine answer for a brochure nobody will touch again, and a poor one for a site people still comment on, search, buy from, or edit.
| Static HTML exporters | Wordprex | |
|---|---|---|
| What you get | A folder of flat HTML | A project you can edit and deploy |
| Your design | Whatever the HTML happened to carry | Pages measured in a browser and rebuilt |
| Comments | Gone, or frozen as text | Migrated with threads, plus a moderation queue |
| Search | Gone | Full-text index over your content |
| Forms | Submit to nothing | Working, with submissions in the admin |
| Shop | Gone | Products, cart, checkout, and past orders |
| Editing later | Edit the HTML by hand | Markdown files, or a familiar admin |
| Best fit | A brochure that never changes again | A site that keeps being a site |
No. Everything is read through the WordPress REST API, which ships enabled. Nothing is added to your site, nothing is changed, and your WordPress keeps running exactly as it is until you decide to switch off.
That is the part we work hardest on, and the honest answer is "close, and getting closer". Your theme's own CSS is not carried over — it styles markup we no longer emit. Instead every page is measured and photographed, and the layout is rebuilt from those measurements. Pages we cannot rebuild are named in the report rather than quietly shipped half-finished.
Public content needs nothing. Drafts, private pages, settings and WooCommerce orders need a WordPress Application Password, which you can create and revoke in your own profile. It is used for that one export and never stored.
The catalogue does, with no credentials at all. Orders and customers need the Application Password, and arrive in the new site's own order history with their original status and id — not as an archive you cannot use.
Every old WordPress path is written into a redirect map, so links people have already shared and anything search engines have indexed keep working. Losing those is the expensive part of a migration.
A WordPress WXR file works too. You lose the parts that need a browser — the screenshots and the layout measurements — so the design has to be rebuilt by hand or by your own coding agent, and the export says so.