WordPress to Astro converter
Paste a WordPress address and see your site as an Astro project: how many posts and pages come across, one post converted to Markdown, and what will not make the move. Every converted post and page keeps its URL.
Not WordPress, or the REST API is turned off? The static snapshot saves the HTML any public site serves, on a $3/mo pod. Snapshot the site instead
Sample post, converted
→
Found on your site and in the sample post
Get the Astro project
Both buttons open your InstaPods dashboard with this site filled in. Downloading the zip is free with an account; deploying builds it on a $3/mo pod with your redirects applied ($10 credit when you add a card).
What will not come across
What comes across
Showing a result from the last 10 minutes for this site.
How the converter works
It reads the JSON your WordPress site already publishes at /wp-json/ (or ?rest_route= on sites without pretty permalinks) and builds an Astro 5 project from it:
- Posts and pages as Markdown, with title, date, last update, slug, permalink, categories, tags, excerpt and featured image in the frontmatter. Blocks that do not convert cleanly (tables, embeds, galleries, page-builder layouts) stay as HTML inside the Markdown, never dropped.
- Your images from your own domain, saved at the same
/wp-content/uploads/path. - The same URLs. Every converted post, page, category and tag archive is built where it is today. Plain
?p=123links and the old feed and sitemap addresses get a 301. Archive pagination, author and date archives are not rebuilt. - RSS, a sitemap, a plain readable layout and a README that explains how to edit, build and deploy.
The full conversion takes the newest 500 posts by default (up to 1,000), 200 pages and 40 MB of images. The step-by-step guide, including redirects, what breaks and how to keep editing, is WordPress to Astro, step by step.
Is Astro the right exit for your site?
Astro suits a developer who wants posts as files in git. If non-developers edit the site, EmDash gives them an admin and imports from WordPress itself. If a plugin runs your store, memberships or bookings, stay on WordPress. Leaving WordPress compares all four paths.
Frequently asked questions
Is the WordPress to Astro converter free?
The preview on this page is free and needs no account. Downloading the finished Astro project is free with an InstaPods account. Deploying it on InstaPods costs $3/mo, and adding a card gives a one-time $10 credit.
Does it need my WordPress login?
No. It reads only the public WordPress REST API, the same JSON any visitor can fetch from your site. It never sees drafts, private posts, users or settings, and it changes nothing on your WordPress install.
Will my URLs change?
Not for anything it converts: every converted post, page, category and tag archive is built at the path it has today. Plain ?p=123 links and the old /feed/ and sitemap addresses get 301 redirects, listed in redirects.json and public/_redirects. Archive pagination (/page/2/), author and date archives, and feeds other than the main one are not rebuilt, and posts past the conversion limit are not included.
What does not come across?
Comments, forms, search, shops and logins (the result is static), drafts and private posts, shortcodes from inactive plugins (they show as plain text), custom post types such as products, and your theme, menus and widgets. The preview lists what applies to your site.
What if my REST API is turned off?
The converter says so. Some security plugins disable the REST API; turn it back on for the migration, or use the static snapshot instead, which saves the HTML your site serves and works on any public site.
How big a site can it convert?
Up to 1,000 posts (the newest 500 by default), 200 pages and 40 MB of images per conversion. Anything past a limit is noted in the project's MIGRATION-NOTES.md.