How to Convert HTML to WordPress (2026): 5 Ways, Compared
Five ways to turn an HTML site or section into WordPress: a custom theme, an import plugin, a page builder rebuild, an HTML to Elementor or Bricks converter, or capturing it from the live page. What each keeps, what it costs you, and which to use.
Soraia
Founder, PocketUI
WordPress cannot open an HTML site and make it editable. You either turn the HTML into a theme (developer work, and the content stays in code), import the content with a plugin (the design does not come along), rebuild it in a page builder, run it through an HTML to Elementor or Bricks converter, or capture each section from the live site into Elementor or Bricks. If someone will edit the site without touching code, pick one of the last three.
WordPress has no "import my HTML site" button. Hand it an index.html and it has nowhere to put it: WordPress pages are blocks or page builder elements stored in a database, styled by a theme. Your HTML is a file.
So converting HTML to WordPress always means rebuilding the page in one of WordPress's own formats. There are five ways to do that, and the right one depends mostly on one question: who edits the site afterwards, and do they write code?
First: what are you converting?
- A folder of HTML files, from a template, an old hand-built site or an export. You have the code.
- A live website, whatever it was built with. You may not have clean source files at all.
- One page or one section you want inside an existing WordPress site.
Routes 1 to 4 start from code you have. Route 5 starts from the page in your browser.
The five ways to convert HTML to WordPress
1. Turn the HTML into a WordPress theme
The developer route. Split the HTML into template files (header.php, footer.php, index.php and page templates), add the theme header to style.css, load your CSS and scripts from functions.php, and replace the hard-coded menu and text with WordPress functions.
What it keeps: your exact markup and CSS.
What it costs: PHP knowledge, and a few days for a real site. Unless you wire every piece of text to WordPress fields, changing a headline still means editing a template file.
Use it when: a developer will maintain the site and wants full control of the code.
2. Import the content with an HTML import plugin
Import plugins read your HTML files and create a WordPress page or post from each one, text and images included.
What it keeps: the content.
What it loses: the design. The pages take on whatever theme you install, so you still have to rebuild the look.
Use it when: you have many pages of content, such as documentation or an old blog, and the design is being redone anyway.
3. Rebuild it in a page builder
Install a light theme (Hello Elementor, or Bricks), then recreate each section by dragging containers, headings, buttons and images until it matches the original. This is what Google's own summary recommends for most people.
What it keeps: everything you rebuild, as editable elements.
What it costs: an hour or two per section, reading colors, fonts and spacing out of DevTools. The hover transitions and the tablet padding are the details that usually get missed.
Use it when: the site is small, or you want to change the design while you are at it.
4. Run the HTML through an HTML to Elementor or Bricks converter
Converters take HTML and CSS and turn them into page builder elements you paste or import:
- WPConverters: free HTML to Elementor and HTML to Bricks converters, no account.
- htmltoelementor.com: free, paste HTML, get Elementor widgets.
- Web2Elementor: a URL, HTML or a screenshot to an Elementor template, priced per page.
- Code2Bricks: a Bricks plugin that converts pasted HTML, CSS and JavaScript inside the builder.
- Bricks' own HTML & CSS to Bricks: built in since Bricks 2.3. Paste code, get native elements and global classes.
What it keeps: the structure, usually as native widgets or elements.
What depends on you: the CSS. A converter can only convert the rules you give it, and HTML copied out of a browser rarely carries every rule that styles it. Breakpoints are the other weak spot: Bricks' import, for example, only maps a media query to its controls when it exactly matches one of your Bricks breakpoints.
Use it when: you have clean HTML and CSS files of your own.
We compared the main ones with PocketUI: WPConverters, Web2Elementor and Code2Bricks.
5. Capture each section from the live page into Elementor or Bricks
Instead of starting from files, start from the page as it renders. You select a section in the browser, and the tool reads its markup together with the CSS rules that actually apply to it, then writes Elementor widgets or Bricks elements.
The advantage is responsiveness. Because the section is measured at tablet and mobile widths, the builder's tablet and mobile fields get real values, whatever breakpoints the original site used.
What it keeps: the structure as native elements, the styling, hover states and the tablet and mobile values.
What it costs: it works section by section, so a long site takes a while. Header, menu and footer are better set up once in your theme or builder.
Use it when: the site is live, or you can run it on a local server, and you want pages someone can edit without code.
What each way keeps
| What | Theme | Import plugin | Page builder rebuild | HTML converter | Capture from the page |
|---|---|---|---|---|---|
| Editable without code | No | Content only | Yes | Yes | Yes |
| Original design | Yes | No | As far as you rebuild it | If the CSS comes along | Yes |
| Tablet and mobile values in the builder | Not a builder | No | You set them | Depends on the tool | Yes |
| Hover states | Yes | No | Often missed | Depends on the tool | Yes |
| Needs PHP | Yes | No | No | No | No |
| Time per page | Days for a site | Minutes | Hours | Minutes | Minutes |
Doing it with PocketUI
PocketUI is a Chrome extension that saves sections of live websites as real code and exports them to Elementor, Bricks, Webflow, Shopify, Figma or code. For WordPress, use the HTML to Elementor converter or the HTML to Bricks converter.
- Open the page in Chrome. If the site only exists as files, serve it from a local server first.
- Select a section. Drag over it in the extension. It saves the markup, the CSS rules that style it, and how it renders at tablet and mobile width.
- Choose Elementor or Bricks. In Elementor, Editable mode gives you containers and core widgets (Heading, Text Editor, Button, Image), which work on Elementor Free. Exact copy keeps the section as one pixel-exact HTML block instead.
- Paste it into the editor, or download it as an Elementor template to import on any site. In Editable mode, Elementor copies the images into your Media Library when you paste.
- Repeat for each section, then set up the header, menu and footer once.
The Free plan includes 10 exports a month, page builders included. For more, Studio covers every builder, or you can add the WordPress pack to Pro. It is in early access ahead of PocketUI's public launch: the Elementor export page shows what lands in the editor, and you can join there.
Keep your rankings when you switch
Moving to WordPress should not cost you search traffic. Before you switch the domain over:
- Keep every URL. Set WordPress's permalinks and each page's slug so
/pricingstays/pricing. - Redirect what changes. Any page that gets a new address needs a 301 redirect from the old one.
- Carry over titles and descriptions, with an SEO plugin if your theme has no fields for them.
- Submit the new sitemap in Google Search Console and watch the Pages report for a few weeks.
The part that is not yours to convert
If the HTML is your own site, or a client's, convert all of it. If it is someone else's site you are using as a starting point, the layout is fair to learn from, but the text, photographs, logos and brand assets belong to them. Replace them before you publish.
Which way to choose
- A developer will maintain it, in code: turn it into a theme.
- Lots of content, new design anyway: import the content, then design.
- A small site, or you want to redesign it: rebuild in a page builder.
- Clean HTML and CSS files of your own: an HTML to Elementor or Bricks converter.
- A live site, editable by someone who does not code: capture each section into Elementor or Bricks.
For the Elementor side in more depth, see how to convert a website to Elementor. For Bricks, see HTML to Bricks Builder.
Frequently asked questions
You can upload it to your server, where it is served as a separate static file, or paste its markup into a Custom HTML block. Neither makes it part of WordPress: the editor cannot see inside it, and your theme's header, menus and styles do not apply to it. To make the page editable, it has to become blocks, page builder elements or a theme template.
For page builders, yes. WPConverters' HTML to Elementor and HTML to Bricks converters are free with no account, and Bricks has had its own HTML & CSS import since version 2.3. All of them convert HTML and CSS you paste in, so the result depends on how complete that code is.
Convert to whatever you, or your client, will edit in. Elementor is the most widely used, and its free version is enough for sections built on core widgets and containers. Bricks is a paid theme with clean output and global classes, popular with developers. The block editor is built into WordPress and needs no plugin, but fewer converters target it.
Not if you keep your addresses. Give each WordPress page the same URL as the old page (Settings → Permalinks, then each page's slug), add a 301 redirect for any URL that has to change, copy over titles and meta descriptions, and submit the new sitemap in Google Search Console.
They do not convert into working WordPress features. A contact form needs a form plugin, and sliders, tabs or other scripted widgets need the page builder's own version or a plugin. Every route in this guide moves layout and content, not behaviour.
Routes 1 to 4 work from the files. To capture sections from the page (route 5), open the site in Chrome from a local server, such as VS Code's Live Server, or from any static host. A page opened straight from a file on your computer is not enough.
Keep reading
Lovable to WordPress: Move a Lovable, v0 or Bolt Site into Elementor or Bricks (2026)
Lovable builds React apps and WordPress runs on PHP, so there is no export button between them. The five real ways to get a Lovable, v0 or Bolt site into WordPress, what each one keeps, and which to use when a client needs to edit it.
Read ExportFigma to Elementor vs Website to Elementor: Skip the Figma Step
If the design you want already exists as a live website, going through Figma adds a lossy conversion for no reason. When the Figma route is right, when it is not, and what each one costs you.
Read ExportHow to Convert a Website to Elementor (HTML to Elementor, 2026)
Five ways to turn an existing website section into Elementor, from rebuilding it by hand to HTML converters and pasting real widgets. What each method keeps, what it breaks, and when to use it.
Read