Is There a Lovable WordPress Plugin?

Why no plugin can import a Lovable project

A WordPress plugin runs on your server, in PHP, after WordPress has booted. It can read files you upload, write posts, register blocks and change templates. That is a lot, but it does not include running a React build.

A Lovable project is a React and TypeScript app styled with Tailwind CSS and shadcn/ui. Its pages are .tsx files. Its layout lives in class names like grid gap-8 md:grid-cols-3. Its colors and fonts live in Tailwind configuration. None of that is block markup, and none of it is a theme.

To turn it into WordPress, something has to read the React source, work out what each section means, and write the equivalent Gutenberg blocks, template parts and theme.json tokens. That is a translation job, not a file import. A plugin sitting in wp-content/plugins has no access to your Lovable account and no sensible way to do the translation on a shared host.

There is a second, simpler reason. Lovable does not publish a WordPress integration. If that changes, it will be announced in Lovable's documentation; check there rather than trusting a plugin in a search result that claims to be official.

What you may find when you search for one

Searches for a Lovable WordPress plugin tend to return three kinds of result, none of which is what the name suggests.

Read the plugin description before installing. If it does not say it reads React source files and writes block templates, it is not doing the job you are after.

Theme and code importers. Plugins that upload a .zip theme or paste HTML. They accept a finished WordPress theme, not a React project.
AI page builders. Plugins that generate layouts from a prompt. They can make something that looks similar, but they never read your Lovable code, so the result is a new design, not your design.
iframe and embed plugins. They put your hosted Lovable app inside a WordPress page. That works, with the trade-offs in the section below.
Headless starters. Plugins that expose WordPress content over the REST API or GraphQL to a React front end. That is the opposite direction: WordPress as the back end, Lovable as the front end.

Route one: convert the export into a block theme

The route that keeps your design and gives you real WordPress is a conversion. You export the code from Lovable, then turn it into a block theme that you install under Appearance → Themes.

GitHub sync works on every Lovable plan. The Download codebase ZIP needs a paid plan. Either output is a normal project: npm install, then npm run build on Node 22. The steps and the screenshots are in our export guide.

Our converter does the translation in your browser. You give it the ZIP or a GitHub repository, and it writes a block theme: templates, header and footer template parts, one pattern per page, a theme.json with your palette and fonts, and your images copied into the theme. A review screen shows the converted site next to the original inside WordPress Playground, so you see the difference before you download anything. Conversion, review and the download are free.

You can also do the same translation by hand. It is slower, but it is the most faithful route if your site is small or unusual. Our comparison of converter, manual rebuild and headless lays out the effort on each path.

Export the code from Lovable with GitHub sync or Download codebase.
Open iqdesk.com/app and upload the ZIP or connect the repository.
Review the converted pages next to the originals in the Playground preview.
Download the theme and install it with Appearance → Themes → Add New → Upload Theme → Activate.
Check the pages that WordPress created on activation, then set the front page under Settings → Reading.

Route two: embed the Lovable app in a page

If your Lovable app is interactive software rather than a marketing site, a conversion is the wrong tool. A dashboard, a login area, a Supabase-backed app or anything built on React state does not become blocks. Keep it running as a Lovable app and point WordPress at it.

Two practical shapes work. Put WordPress on the main domain for the marketing pages and the blog, and the Lovable app on a subdomain such as app.example.com. Or keep both and link between them in the navigation. Custom domains are supported on Lovable hosting; see our hosting guide for the options.

An iframe embed inside a WordPress page is the third shape. It is easy, and it is the weakest for search. Google indexes the WordPress page, not the embedded app, so the app's content does not help the page rank. Forms and scroll behaviour inside an iframe are often awkward on phones. Use an embed for a tool or a calculator, not for your whole site.

Route three: WordPress as a headless back end

The reverse setup is real and supported: keep the Lovable front end, and use WordPress only to store content. WordPress exposes posts and pages over its REST API, and your React app fetches them.

This keeps your React components exactly as they are. It also keeps all the work. Someone has to write the fetching, the routing, the rendering and the deployment, and keep them working when the content model changes. There is no plugin that does it for you either, although plugins exist to shape the API output.

Search is the part people underestimate. Lovable apps created from 13 May 2026 use TanStack Start and are server-rendered, so crawlers get full HTML. Older apps are React plus Vite and render in the browser; Lovable prerenders them on request for verified search engines, link-preview bots and AI crawlers, which is part of Lovable hosting. Host an older app somewhere else and it is client-rendered unless you add prerendering yourself. Our SEO guide goes through what crawlers actually see.

Picking the route for your site

Match the route to what the site is, not to what is quickest today.

Most Lovable sites that people want in WordPress are marketing sites: a homepage, features, pricing, about, contact, maybe a blog. Those convert well. Sections, grids, cards, headings, the Tailwind type scale and colors, Google Fonts, buttons, navigation, accordions, images, contact forms through Contact Form 7 and product pages through WooCommerce all have block equivalents. Blog-like data arrays become real posts and categories with a query loop.

Some things are approximated, and some are left out. Carousels, tabs, modals and animations arrive in their default or final state. Absolutely positioned decorations, canvas, Lottie, iframes, custom React state, Supabase and authentication do not convert at all. The full list is on our supported features page, and it is worth reading before you pick.

Marketing site, blog, small shop: convert to a block theme and run WordPress.
Interactive app, dashboard, anything behind a login: keep it on Lovable and link to it.
Mixed site: convert the public pages, keep the app on a subdomain.
You want React and editors want WordPress: headless, with a developer to build and maintain it.

Before you launch either way

Whichever route you take, do the same handful of checks. They catch the problems that look like conversion bugs but are really settings.

If you are still building, keep the staging site out of Google with Settings → Reading and the checkbox Discourage search engines from indexing this site. Uncheck it before launch, or the new site will never be indexed.

Then set the front page under Settings → Reading → Your homepage displays, check the URL structure under Settings → Permalinks, and compare each slug with the old one. Per-page titles and descriptions from TanStack Start head() are written to Yoast, Rank Math or SEOPress during conversion; older React plus Vite apps have no per-page meta to carry over, so write it yourself. Redirects in public/_redirects are carried across.

FAQ

Is there an official Lovable plugin for WordPress?

No. Lovable does not publish a WordPress plugin, and no plugin can import a Lovable project into WordPress. Lovable builds React and TypeScript apps, while WordPress renders PHP templates and block markup, so there is no shared file format to import. Check Lovable's documentation at docs.lovable.dev if you want to confirm the current state.

How do I get a Lovable site into WordPress without a plugin?

Export the code from Lovable, then convert it into a WordPress block theme. GitHub sync works on every Lovable plan, and the Download codebase ZIP needs a paid plan. The IQDesk converter at iqdesk.com/app turns that export into a theme you install under Appearance, Themes, Add New, Upload Theme. Conversion, review and the theme download are free.

Can I just embed my Lovable app in a WordPress page?

Yes, with an iframe or an embed plugin, and it is the right choice for an interactive tool or a dashboard. The trade-off is search: Google indexes the WordPress page, not the content inside the iframe. Embeds also behave poorly on small screens. For a whole marketing site, a converted block theme is the better option.

Can WordPress be the back end for a Lovable front end?

Yes. WordPress exposes posts and pages over its REST API, and a React app can fetch and render them. This keeps your Lovable components intact but needs a developer to build the fetching, routing and deployment, and to maintain it afterwards. No plugin does the whole job for you.

Which parts of a Lovable site will not survive a conversion?

Custom React state and event handlers, Supabase, authentication, dashboards, API calls, third-party widgets, canvas, Lottie, iframes and absolutely positioned decorations are not converted. Carousels, tabs, modals and animations come across in their default or final state only. Screens behind a login are reported rather than converted. The full list is on the supported features page.

Convert a Lovable site to WordPress All guides