How 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.
Soraia
Founder, PocketUI
There is no import button in Elementor for an existing website. The five real options are rebuilding it by hand, pasting the markup into an HTML widget, running it through an HTML or URL to Elementor converter, redrawing it in Figma and using a Figma-to-Elementor plugin, or capturing the section from the live page and pasting it in as native widgets. Only the HTML widget leaves you nothing to edit. Among the rest, what decides the result is whether the section's CSS and its tablet and mobile values come across.
Elementor has no "import this website" button. That is the first thing worth saying plainly, because most guides on this topic bury it.
Elementor imports its own template files and kits. It does not import arbitrary HTML. So when you find a pricing section you like and want it in your WordPress build, you have five real options, and they differ enormously in how much work you do afterwards.
The five ways to convert a website to Elementor
1. Rebuild it by hand
Open the page, open DevTools, read off the colors, fonts, spacing and radii, then drag widgets onto the canvas until it matches.
What it keeps: everything, eventually. The result is native Elementor, so every control works.
What it costs: an hour or two per section, and it is the part of the job that feels like data entry rather than design. You will also miss things. The hover transition on the button, the slightly different padding at the tablet breakpoint, the letter spacing on the heading. Those are the details that make a copy look "close but wrong".
Use it when: the section is simple, or you want to change the design anyway.
2. Paste the markup into an HTML widget
Copy the section's HTML and CSS from DevTools, drop an HTML widget on the page, paste it in.
What it keeps: the appearance, if you also bring the CSS across.
What it breaks: the editing experience, completely. An HTML widget is a sealed box. Elementor's Structure panel shows one item called HTML. You cannot click the heading and change the text, you cannot restyle the button in the Style tab, and the responsive controls do nothing, because the original CSS is deciding the layout. Six months later, when a client asks to change a price, someone has to edit raw markup.
Use it when: you need something on the page today and nobody will ever edit it.
3. Run it through an HTML or URL to Elementor converter
Most of page one for "html to elementor" is this kind of tool. You give it HTML or a URL, and it gives you Elementor data to paste into the editor or a template to import:
- Free web converters such as htmltoelementor.com and WPConverters take pasted HTML (WPConverters also a URL) and return native widgets, with no account.
- Web2Elementor takes a URL, HTML or a screenshot and builds an Elementor template per page, priced per page.
- ClonewebX clones whole pages of live sites, into Elementor and several other WordPress builders.
What it keeps: the structure, usually as native widgets. How much of the styling survives depends on what the tool reads. HTML copied out of DevTools rarely carries every CSS rule that styles the section, or its media queries, so a section converted from pasted HTML often looks right on desktop and loose on a phone. Tools that read the live page do better here.
Use it when: the HTML is your own, or you want whole pages rather than one section.
We compared the main ones with PocketUI: ClonewebX, Web2Elementor and WPConverters.
4. Redraw it in Figma, then use a Figma-to-Elementor plugin
Tools like UiChemy convert a Figma file into Elementor. They work well, and if your design already lives in Figma this is a good path.
The catch for an existing website: the design does not live in Figma. So the flow becomes website, then Figma, then Elementor. You either import the page into Figma with another plugin, or you redraw it. Each hop loses something, and the Figma import step is exactly the one that tends to produce absolutely positioned layers that convert badly.
Use it when: you are designing in Figma first anyway.
5. Capture the section from the live page, paste it as widgets
Skip Figma, and skip digging out the code. Read the section on the page directly, with the CSS rules that style it at each width, convert that into Elementor's own format, paste.
This is the path PocketUI takes, and it is the reason the tool exists: the design already exists as a working website, with real CSS and real breakpoints. That is better source material than a redrawn Figma file, because nothing has been interpreted yet.
What "real widgets" actually means
This is the distinction that decides whether a conversion is useful, so it is worth being concrete.
A sealed result looks like this in the Structure panel:
- HTML
A native result looks like this:
- Container · Pricing
- Heading · Simple pricing
- Text Editor · No hidden fees
- Container · 3 columns
- Icon Box · Pro
- Button · Start free
In the second one, every line is something you can click, restyle and set a different value for on mobile. That is the whole point of using a page builder. A conversion that gives you the first one has saved you the layout work and taken away the editing work.
What survives a good conversion
| What | Rebuild by hand | HTML widget | HTML or URL converter | Figma plugin | Capture from the page |
|---|---|---|---|---|---|
| Native, editable widgets | Yes | No | Usually | Yes | Yes |
| Colors and fonts | You retype them | Yes | If the CSS comes along | Yes | Yes |
| Hover and focus states | Often missed | Yes, via CSS | Depends on the tool | Sometimes | Yes |
| Responsive values in Elementor | You set them | No | Depends on the tool | Sometimes | Yes |
| Needs a Figma file first | No | No | No | Yes | No |
| Time per section | 1–2 hours | 10 minutes | A few minutes | 20–40 minutes | Under a minute |
Doing it with PocketUI
PocketUI is a Chrome extension that saves parts of live websites as real code: the structure, the authored CSS rather than hundreds of computed values, the hover and focus states, and the breakpoints. The same capture can then go to Figma as editable layers, out as HTML, Tailwind, React or Vue, or into a page builder. For Elementor, that is PocketUI's HTML to Elementor converter.
- Open the page you want to convert. Find the section you want: a pricing block, a hero, a testimonial row.
- Select it. Drag over the section in the extension. It captures the real structure, the authored CSS, the hover states and the breakpoints, not a screenshot.
- Check what was captured. The section lands in your library as real code. Open it to see the preview at desktop and phone width.
- Copy it for Elementor. Pick a mode. Editable converts the capture into Elementor's own format: containers with widgets inside, responsive values filled in from the original CSS. Exact copy keeps it as one pixel-perfect HTML block, for when it must look exactly like the original.
- Paste it into the editor. Right-click in the Elementor editor and paste. In Editable mode the section appears in the Structure panel as real widgets, not one HTML block, and its images are downloaded into your Media Library.
- Swap the content for your own. You kept the layout work; the words and images should be yours.
Where it stands: the Elementor export works today, in both Editable and Exact copy mode, and is in early access ahead of PocketUI's public launch. The HTML to Elementor export page shows what lands in the editor, and you can join there to get it on launch day. If you need the conversion this afternoon, use one of options 1 to 4 above.
The part everyone skips: the content
Whichever method you use, the layout is the part you are reusing. The words, the photographs, the logo and the brand colors belong to whoever made the site.
Copying a competitor's pricing layout to understand how they present their tiers is ordinary competitive work. Moving a client's existing site into a new Elementor build is ordinary agency work. Publishing their copy and their images under your own domain is not. Swap the content out as soon as the structure is in place.
Which method should you use?
- One simple section, and you want to change the design anyway: rebuild it by hand.
- A complex section, needed today, never edited again: HTML widget, and accept the trade.
- Clean HTML of your own, or whole pages at once: an HTML or URL to Elementor converter.
- Your design already lives in Figma: UiChemy.
- The design exists as a live website and you want native widgets: capture it from the page.
The thing worth optimising is not the first paste. It is what the section looks like in the Structure panel a month later, when someone needs to change a price on mobile.
Moving a whole site rather than one section? See how to convert HTML to WordPress, or Lovable to WordPress for sites built with Lovable, v0 or Bolt.
Frequently asked questions
Not directly. Elementor imports its own template files (JSON) and kits, not arbitrary HTML. To bring an existing website section into Elementor you either rebuild it with widgets by hand, drop the markup into an HTML widget, or use a tool that converts the section into Elementor's own template format so it arrives as real widgets.
An HTML widget is a sealed box: the markup renders on the page, but the Elementor editor cannot see inside it. You cannot change the heading with the text control, restyle the button in the Style tab, or set different padding on mobile. Real widgets appear in the Structure panel as Heading, Text Editor, Button and containers, each with its own controls.
No. Figma-to-Elementor plugins such as UiChemy need the design to exist as a Figma file first, so for an existing website you would have to import or redraw the page in Figma before converting it. HTML and URL converters, and capturing the section from the live page, skip that step entirely.
They do if the tool reads the site's own media queries and writes them into Elementor's desktop, tablet and mobile values. If you paste markup into an HTML widget, the original CSS controls the layout and Elementor's responsive controls do nothing, which is the usual reason a pasted section looks right on desktop and breaks on a phone.
Treat layout and structure as things you can learn from and rebuild, and treat the content as someone else's property. Copying a competitor's layout to understand it, or moving a client's existing site into a new build, is normal work. Republishing their text, photographs, logos or brand assets is not. Replace the content with your own.
Rebuilding by hand and the HTML widget both work on the free version. For converted output, check what the tool produces: an export built on core widgets and flexbox containers works on Elementor Free, while one that relies on Pro-only widgets such as Loop Grid or Mega Menu will not.
Keep reading
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.
Read ExportLovable 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