Using the converter

Requirements

• A Lovable project: React + Vite + Tailwind CSS (+ shadcn/ui). Routers supported: React Router routes declared in src/App.tsx, pages in src/pages/*.tsx, and TanStack Router file routes in src/routes/.
• A desktop browser. The preview runs WordPress inside the browser (WordPress Playground) and needs about 300 MB of memory; expect 30–90 seconds for the first boot, longer when WooCommerce is installed.
• For the side-by-side comparison: the published URL of the Lovable site (*.lovable.app or a custom domain).
• On the WordPress side: WordPress 6.5+, plus WooCommerce for products and Contact Form 7 for forms.

Input: ZIP or GitHub

Lovable syncs projects to GitHub. Either download the repository as a ZIP (GitHub → Code → Download ZIP) and drop it into the converter, or paste the repository URL; private repositories need a fine-grained token with read access to contents. The converter finds the project root by locating package.json, so a ZIP with a top-level folder is fine.

Decisions

After analysis the app lists the detected routes with what each contains. You can exclude routes, rename page titles, and choose:

• Commerce: auto (product data becomes WooCommerce products, listings use the shop loop), pages (product pages stay designed pages), off.
• Forms: auto (Contact Form 7) or off.

Decisions are stored as lovable-wp.json in the theme; loading the same project again reads them back.

What the theme contains

your-site/
├── style.css               theme header, helper classes, hover rules
├── theme.json              palette, type scale, content width
├── functions.php           first-visit setup, shortcodes, Woo/CF7 glue
├── templates/              front-page.html, page.html, index.html …
├── parts/                  header.html, footer.html
├── patterns/               page-home.php, page-about.php … (one per page)
├── assets/images/          images copied from the project
├── lovable-wp.json         your decisions
└── INSTALL.md              install guide and rollback notes

Patterns are the page content. They use core blocks only, so they can be opened and edited in the block editor; the theme's CSS adds a few helper classes (vertical centering, pinned card buttons, carousels) that stay valid when you edit the blocks.

Installing the theme

1. Take a backup. If the site sells products, activate WooCommerce first; if it has forms, activate Contact Form 7.
2. WP Admin → Appearance → Themes → Add New → Upload Theme → choose the ZIP → Install → Activate.
3. Open the home page once. The first visit creates the pages (an existing page with the same slug is taken over in place; its previous content stays as a revision), sets the front page and permalinks, builds the menu, side-loads the logo, creates products and categories.
4. Reload a couple of times if product images are still importing.

Rolling back means re-activating the previous theme; converted pages remain as pages. A stubborn pattern cache clears with wp transient delete --all.

The review screen

Left: the original site through a same-origin proxy so it can be measured. Right: the theme running in Playground. Both are rendered at the width you choose (default 1440px). The panel shows, per page: headings on both sides with their positions and the difference, image, form and accordion counts, total height, and the conversion notes for that page. "Edit in WordPress" opens the Playground admin, "Re-measure" repeats the comparison after fonts and animations settle.

AI fixes and credits

The fix box sends your instruction to an agent that can read the theme and the original source, measure elements on both pages, edit theme files and copy assets. Changes apply to the running WordPress immediately and are included in the download; each fix can be undone. Model choice: Sonnet (fast) or Opus (thorough).

• Every account gets two free attempts (they run on Sonnet).
• After that, fixes use credits: 1 credit = 1,000 model tokens of any kind (cached reads count one tenth). A typical fix uses 40–150 credits; a long one with many measurements up to about 300.
• Packages: Starter $20 = 666 credits + 1 saved project; Studio $60 = 2,000 credits + 5 saved projects. Payment by card through Stripe.
• Limit: 40 fix requests per account per day.

Saved projects

With a project slot you can save the uploaded source, the current theme (including AI fixes) and the decisions to your account, and reopen them later from the Projects dialog. Without saving, nothing of your project is stored on our servers.

Limits

• Instructions to the AI agent: 2,000 characters. Agent budget: 20 tool steps per request.
• Projects are converted for the desktop breakpoint; WordPress handles column stacking on mobile.
• Application features (auth, Supabase, dashboards, client-side state) are detected and reported, not converted. See supported features.

Where your files go

Parsing, conversion and the WordPress preview happen in your browser. The published site you enter for comparison is fetched through our proxy. GitHub repositories are downloaded through our server and passed to your browser. Theme files and the relevant source excerpts are sent to the model provider (Anthropic) when you ask for an AI fix. Saved projects are stored on our server until you delete them. Details in the privacy policy.