Converting HTML/CSS Designs

HTML/CSS is available as a source format on every plan, including Free. This guide explains how the conversion works and how to structure your source files for the best Fidelity Score.

How the parser works

Tapeto’s HTML parser walks the DOM and converts it into the IR (intermediate representation) shared by every generator. Along the way it:

• Maps standard attributes (src, alt, href, heading level, etc.) onto IR nodes.
• Reads linked and inline CSS, including @media rules — breakpoints are captured in the IR’s designTokens.breakpoints so responsive behavior survives the conversion.
• Treats headings, paragraphs and images as leaf nodes — they are never turned into containers, even if your markup nests other elements inside them.

Using the URL Cloner

Instead of uploading files, you can point Tapeto at a public URL. The URL Cloner downloads the page’s HTML and its external stylesheets and feeds them into the same pipeline as an uploaded HTML/CSS project. External CSS is fetched with MIME-type checks, a maximum size limit and a timeout, so a slow or unexpected resource won’t stall your conversion.

Tips for a higher Fidelity Score

• Keep styles in CSS, not inline style attributes — the parser reads stylesheets more reliably than scattered inline styles.
• Use semantic HTML (<h1>–<h6>, <p>, <img>, <a>) — semantic tags map directly to IR node types; generic <div> soup loses structure.
• Avoid relying on JavaScript-rendered content — Tapeto parses the HTML as delivered, not after client-side rendering.
• Check image paths — relative paths are resolved against the source; broken paths show up as missing images in the result.

Choosing a builder

Once the IR is built, you pick the target builder for the conversion (gutenberg, elementor, oxygen or divi, depending on your plan). The same IR can be converted to multiple builders without re-uploading the source — see API Reference if you’re scripting this.

Next step

Once you have a completed conversion, see Exporting Results to download it or push it to WordPress.