Free tool

HTML → Divi Converter

Paste a finished HTML page and get it back as native Divi sections, rows, columns and modules. Download a Divi import file or copy the shortcodes. Free, no plugin.

Divi does not take plain HTML. A Code module will display it, but then nothing is editable with Divi's own settings. This free converter reads your HTML and CSS and rebuilds the page as native Divi content: each top-level block becomes a section, flex and grid layouts become rows with the closest Divi column structure, and headings, paragraphs, lists, images, buttons, dividers and YouTube or Vimeo embeds become their Divi modules. Colors, fonts, sizes, spacing, backgrounds, borders and shadows land in the matching Divi settings, including tablet and phone values from your media queries. Download the .json and import it with Divi's Portability option, or copy the shortcodes. Works with Divi 4, and Divi 5 converts the layout on import. Whatever has no Divi module comes in as a Code module, and the conversion notes list exactly what changed.

  1. 1

    Copy your HTML

    A whole page or one section, with its <style> blocks. Linked stylesheets can go in the optional CSS field.

  2. 2

    Convert here

    Paste it below, hit Convert, read the notes, then download the .json or copy the shortcodes.

  3. 3

    Import in Divi

    Open the page in the Divi Builder, click the Portability icon in the page settings bar, choose Import and pick the file.

🔒 Conversion runs in your browser. To improve conversion quality we keep an anonymized structural copy of the input — all text is scrambled and URLs removed before anything leaves your browser. Details.

HTML Input

Paste any HTML — a full page, a section, an email fragment, or AI-generated markup.

Optional: add your CSS (colors, backgrounds, fonts)

Easiest: download the .json, open the page in the Divi Builder, click the Portability icon (the up and down arrows in the page settings bar), choose Import and pick the file. Or paste the copied shortcodes into the page content (Text view of the classic editor), then open the page in the Divi Builder. Works in Divi 4, and Divi 5 converts it on import.

Images are not uploaded for you. External image URLs keep pointing at the source site until you add them to your Media Library. Anything with no Divi module comes in as a Code module and is listed in the notes.

Divi Shortcodes

Designing in Figma? Export Figma frames as clean HTML, then bring them into Divi →

From the makers of ready→made

Building from a Figma design instead?

ready→made converts your Figma designs into clean HTML with a real layout engine, not AI guesswork. Bring that HTML into Divi with this tool.

Figma to HTML →
FAQ

Good to know.

Is this really free? Do I need a plugin?

The converter is free and runs in your browser. You only need Divi on the WordPress site: the .json uses Divi's own Portability import, and the shortcodes are the ones Divi itself saves.

Does it work with Divi 5?

The output is Divi 4 layout content. Divi 5 imports Divi 4 layouts and converts them to its own format, so the same file works in both. We have not tested every Divi 5 release, so check the result after import.

What maps to native Divi settings?

Sections, rows and columns (flex and grid layouts get the closest Divi column structure), Text modules for headings, paragraphs, lists, quotes and tables, Image, Button, Divider and Video modules, plus colors, fonts, font sizes, line height, letter spacing, alignment, padding, margin, backgrounds and gradients, borders, rounded corners, box shadows and widths. Media queries become Divi's tablet and phone values, and display: none becomes Divi's per-device visibility.

What does not survive?

JavaScript does not carry over at all, so sliders, tabs, accordions, mobile menu toggles and scroll or click animations have to be rebuilt with Divi modules. CSS animations, hover states and @font-face rules are kept as raw CSS in one Code module labelled "Converted CSS", but they are not editable in Divi's design settings. Forms are kept as HTML in a Code module: they display, but they are not Divi Contact Form modules, and any validation or submit script is gone.

What else lands in a Code module?

Anything without a matching Divi module: inline SVG, iframes other than YouTube and Vimeo, canvas, and unknown widgets. Visual CSS without a Divi field, like opacity or transform, goes into the module's Custom CSS. Every fallback is listed in the conversion notes.

Why do some layouts look different?

Divi rows only offer fixed column ratios, so a 70/30 split becomes the nearest Divi structure, here 2/3 and 1/3. Divi 4 regular sections cannot nest rows, so columns inside a column are stacked. Divi also adds its own default spacing wherever your HTML set none.

What about images?

Image URLs are kept as they are. They keep loading from the original site until you upload them to your Media Library. Relative URLs like /img/hero.jpg will not load in WordPress, and the notes count them.

Moving an existing Divi site to Elementor instead?

Use the free Divi → Elementor converter. It reads Divi exports and shortcodes.

More free tools

Other converters in the suite.

Starting from a Figma design? Use the Figma to HTML converter.

Ready?

Build a real site from your Figma file in minutes.

menu