You can ask your AI tool for the new design in minutes. The hard part is getting it onto the live site without wiping out everything that was edited in WordPress.

Why Re-Importing Everything Is Risky

If you simply import the whole new design over the old one, every page goes back to the words and pictures in the ZIP. The client’s edits disappear. Copying sections across by hand avoids that, but it’s slow and easy to get wrong.

How Kerf Updates a Design Section by Section

When Kerf imports a design, it remembers where each top-level section came from. When you upload a newer ZIP (or paste updated HTML) under Kerf → Update design, it lines up the old sections with the new ones and sorts every section:

You tick or untick what you want, choose whether to update stylesheets, scripts and new pictures too, and click Apply selected changes.

A Workflow That Works

1. Keep the files you imported. Ask your AI tool to change the design in those same files, keeping file names and the sections you’re not changing as they are.
2. Ask for one change at a time when you can—“add a testimonials section after services”—so the comparison shows only what you meant to change.
3. Zip the whole site again and upload it under Kerf → Update design.
4. Read the list before applying. Anything marked as edited in WordPress deserves a look: apply it only if the new design should win.

And If You Change Your Mind: Undo

Every import and every design update can be undone. Undo last import / update restores the pages, header and footer, templates and asset settings to how they were just before. Read the Update design documentation →

For Client Sites: Client Mode

Fewer surprises start with fewer accidents. Give your client an Editor account and client mode keeps the layout locked—blocks can’t be moved, added or deleted—while words, pictures and links stay editable.

See it for yourself: try Kerf free in your browser, import a design, edit a section, then upload a changed version under Update design.

Originally published on kerf.site. Try Kerf free in your browser — a private WordPress with Kerf installed, no sign-up: https://kerf.site/demo/

That isn’t the AI’s mistake. A form in plain HTML only describes the fields; something on a server has to receive the message and deliver it. Static HTML has no such server. Here’s how to fix that without giving up the design.

Why the Form Does Nothing

An HTML <form> sends its fields to the address in its action attribute. AI-generated pages usually leave that empty, point it at #, or attach a small script that shows “Thanks!” without sending anything. Either way, the message goes nowhere.

The Usual Fixes

• A third-party form endpoint: point the form’s action at a hosted form service. It works on static hosting, but it’s one more account, often a monthly plan, and your messages live outside your site.
• Rebuild the form with a WordPress form plugin: reliable, but the plugin outputs its own markup and classes, so the form stops looking like the design.
• Write a handler yourself: fine if you’re a developer and want to maintain it—including spam protection.

How Kerf Makes the Same Form Work

When Kerf imports a page with a form—other than a search form or one that already posts to an outside address—it keeps every <input>, <textarea>, <select> and button exactly as styled, and turns on Send this form with Kerf:

• Visitors submit the form on the page and see a clear status message.
• Kerf emails the submission to your site’s recipient address, with any uploaded files attached.
• Every submission is also saved under Kerf → Form entries, so a message isn’t lost if an email goes astray.

Block Editor — Contact form settings

Select the form in the editor to change its confirmation message or turn Kerf’s handling off.

Spam Protection Included

Forms on a public site attract bots. Kerf adds an invisible honeypot field and a timing check, limits how often one address can submit, and keeps suspected spam in its own Spam folder under Form entries instead of your inbox.

A Tip on Email Delivery

Like any email a WordPress site sends, delivery depends on how your host handles mail. If messages land in spam or don’t arrive, a standard SMTP plugin connected to a proper mail service usually fixes it—and in the meantime every message is still waiting under Form entries.

Business Details, Too

The phone number and email next to the form usually appear in the header and footer as well. Kerf links them to Kerf → Site details, so changing them once updates every page—including the tel: and mailto: links. Read the forms documentation →

Want to see it with your own design? Try Kerf free in your browser—drop in your ZIP and open the contact page in the editor.

Originally published on kerf.site. Try Kerf free in your browser — a private WordPress with Kerf installed, no sign-up: https://kerf.site/demo/

The honest answer is: not by importing it—not with Kerf, and not with any tool that works from HTML. Here’s why, and what you can do instead.

Why a React App Is Different from an HTML Website

Tools like ChatGPT, Claude, Gemini and Google Stitch can give you HTML files: open index.html and the whole page is there—every heading, paragraph and picture written out in the file.

Lovable, Bolt and v0 typically build React apps. Their source is components and a package.json; a build step bundles it into JavaScript, and the page is assembled in the visitor’s browser when that JavaScript runs. Open the built index.html and you’ll mostly find an empty container like <div id="root"></div>.

An HTML importer turns the elements in the HTML into editable blocks. When the elements only exist after a script builds them, there is nothing in the file to turn into blocks. That’s why Kerf doesn’t import these apps yet—and why its pre-import check tells you so before anything changes on your site.

Your Real Options

1. Keep the App Where It Is, and Add WordPress Next to It

If the site is mostly an app—logins, dashboards, live data—keep hosting it where it runs well today (for example Netlify or Vercel). If you also want a blog or editable marketing pages, run WordPress alongside it, for example on a subdomain, and link between the two.

2. Use WordPress as the Content Source (Headless)

A developer can keep the React front end and have it fetch posts and pages from WordPress’s REST API. Editors write in WordPress; the app shows the content. It’s flexible, but it is a development project, not a one-click move, and the WordPress block editor won’t show your app’s design while you edit.

3. Rebuild the Pages in WordPress

For a simple marketing site, rebuilding by hand in a page builder or block theme works. It takes time, and the result is a look-alike rather than the same design.

4. Recreate the Design as Plain HTML, Then Import It

If what you love is the look, not the app logic, you can ask an AI tool to recreate the pages as plain HTML, CSS and JavaScript—no React, no build step. That version is a normal website, and an HTML website can be imported into WordPress as editable blocks. Our prompt brief for WordPress-ready AI HTML lists what to ask for.

How to Tell Which Kind You Have

If your project has a package.json and you need to run something like npm run build to see it, it’s an app. If you can double-click index.html and see the full page with its words in the file, it’s HTML—and that’s the kind Kerf imports.

What Kerf Is For

Kerf is built for HTML websites: the ZIP you get from ChatGPT, Claude, Gemini or Google Stitch, or from a designer. It keeps the same tags, classes, stylesheets and scripts, and makes every word, picture and menu editable in WordPress. If that’s what you have, you can try it free in your browser—a private WordPress with Kerf installed, no sign-up.

Originally published on kerf.site. Try Kerf free in your browser — a private WordPress with Kerf installed, no sign-up: https://kerf.site/demo/

Then the practical question arrives: where does it live? If you or your client want to change words, swap photos, publish posts and read form messages without touching code, the answer is usually WordPress. This guide shows how to get a Stitch design there with the design intact.

What Stitch Actually Gives You

Stitch can export a screen’s code: an HTML page styled with Tailwind CSS utility classes. That matters, because HTML is exactly what a browser—and WordPress—can show without a build step. Unlike a React app, there is nothing to compile: the page you see is the page in the file.

Before you export, check three things:

1. Export every screen you want as a page—home, about, services, contact—not just the first one.
2. Name the files after the pages (index.html for the home page, then about.html, contact.html and so on) and put them in one folder.
3. Keep any pictures you downloaded next to the HTML (an images/ folder is fine), then zip the folder.

The Usual Ways to Put It on WordPress

Importing a Stitch Export with Kerf

Kerf is a WordPress theme with an importer built in. It doesn’t translate your design into its own widgets: almost every element becomes one block that renders exactly that element, with its own tag, classes and attributes.

Step 1: Drop in the ZIP and Read the Check

Open Kerf → Import design and drop in your ZIP. Before anything is written to your site, Kerf counts the pages, stylesheets, scripts and pictures it found and flags any file the HTML refers to that isn’t in the ZIP—so a missing picture shows up here, not after launch.

Kerf → Import design — the check before importing

The check runs before anything changes on your site. (Shown with our Copperline Studio sample.)

Step 2: Import the Whole Site

With the default scope, Whole site, the header and footer of index.html become your site’s shared header and footer, index.html becomes the front page, and each other HTML file becomes a WordPress page (or a template, if it is a blog or post layout). Stylesheets and scripts—including a Tailwind script tag, if your export uses one—load in the same order the HTML gave them.

Step 3: Point the Menu at the Right Pages

Screens designed one at a time often have menu links that go nowhere (href="#"). Kerf leaves # links alone, so after the import select the header, open the Menu panel in the editor sidebar and point each item at its page. Links written as file names (about.html) are matched to pages automatically, and Kerf → Links lists any that still need a destination—with a Create page button for each.

Step 4: Edit It Like Any WordPress Site

Open a page in the block editor and you see your Stitch design, with its stylesheets loaded in the editor canvas. Click a heading to retype it, click a picture to swap it from the Media Library, and a contact form already sends email and saves each message under Kerf → Form entries.

Tip: One Header for Every Screen

Because the home page’s header and footer become the shared ones, the import is cleanest when every Stitch screen uses the same header and footer. If Stitch varied them, ask it to make them identical before you export.

Try Your Own Stitch Export, Free

You can test this with your own design before deciding anything: Try it free in your browser opens a private WordPress with Kerf installed—no sign-up, nothing to install. Drop in your Stitch ZIP, then close the tab and it’s gone.

Originally published on kerf.site. Try Kerf free in your browser — a private WordPress with Kerf installed, no sign-up: https://kerf.site/demo/

And then comes the moment every founder, freelancer, and agency hits the wall: “How do I put this on WordPress so my team or client can actually edit it?”

Until now, every answer to that question was painful. In this guide, we’ll compare the traditional ways people bring HTML into WordPress—and walk through how Kerf imports an AI tool's or a designer's HTML ZIP into a real, editable WordPress site in one click. (Not yet: React apps that need a build step, such as Lovable, Bolt or v0 — Kerf's check tells you before anything changes.)

Why the 3 Traditional Ways Break Your AI Design

When you download a .zip folder of HTML, CSS, and JavaScript from an AI tool, you have a finished front-end design. Look at what happens when you try to move it into WordPress the old-fashioned way:

The Root Cause

The usual HTML-to-WordPress routes convert your design into their own widget or block vocabulary. Every wrapper element or renamed class is a markup decision your designer didn’t make—and the cost shows up as CSS that quietly breaks.

How Kerf Imports HTML into WordPress Without Rewriting Your Markup

We built Kerf around a simple rule: the mockup is the design, and the theme’s job is to get out of its way. Instead of forcing your HTML into opinionated widgets, Kerf is a WordPress full-site-editing theme with a deterministic DOM converter and asset pipeline built inside.

Here is the entire workflow from AI ZIP to live WordPress site:

Step 1: Drop Your ZIP into Kerf → Import Design

In your WordPress admin, open Kerf → Import design and drag in your ZIP archive (or paste a single page’s HTML). Kerf runs a pre-flight check before touching your site—counting your pages, stylesheets, scripts, and images, and flagging any missing files up front.

copperline-studio.zip — Pre-import check

Kerf inspects every page, stylesheet, script, and image in your ZIP before importing.

Step 2: Click Import and Check the Match

In a single pass (a few seconds for a design like our sample), Kerf:

1. Stages your asset folders (css/, js/, fonts/, images/) keeping the folder hierarchy intact so relative url(../images/...) paths in CSS resolve without rewriting.
2. Imports content images into the WordPress Media Library so you can swap any photo in the editor while keeping responsive srcset support.
3. Registers stylesheets and scripts in exact source order through WordPress’s dependency graph.
4. Splits <header>, <main>, and <footer> into shared FSE template parts and editable pages.
5. Audits every CSS selector in your stylesheets against the rendered WordPress DOM and prints your fidelity report.

Fidelity Report — 134 of 134 CSS selectors matched (100%)

On our Copperline Studio design, 134 out of 134 CSS selectors match on the first pass.

Step 3: Edit Words, Pictures, Menus, and Forms in Place

Open the imported page in the WordPress Block Editor and you’ll see your actual design—with your stylesheets loaded inside the canvas, scroll-hidden sections automatically revealed for editing, and every HTML tag and class named clearly in List View.

• Click any text or image to edit it in place.
• Open the Menu panel to rename, reorder, or re-link navigation items without losing your <nav> markup.
• Select any <form>—it already sends emails and saves entries under Kerf → Form entries automatically.

Test It Right Now in Your Browser (No Sign-Up)

You don’t have to take our word for it—or even spin up a WordPress server to test your own ZIP. Click Try it free in your browser to launch a private WordPress Playground with Kerf pre-installed, and drop in either our sample Copperline Studio ZIP or your own AI-made website.

Originally published on kerf.site. Try Kerf free in your browser — a private WordPress with Kerf installed, no sign-up: https://kerf.site/demo/

However, how you prompt the model determines whether you get a disconnected code demo or a clean, multi-page HTML package that drops straight into WordPress via Kerf. Here is the exact structural brief we use—and why each instruction matters.

The 5 Rules of WordPress-Ready AI HTML

Although Kerf’s converter handles everything from messy inline styles to third-party carousels, asking your AI tool for five specific habits turns a good import into an effortless one:

1. Use semantic top-level landmarks (<header>, <main>, <footer>): Kerf splits your home page at these boundaries so your navigation header and footer automatically become shared WordPress Template Parts across the whole site.
2. Use real file links in navigation (href="about.html", not href="#"): When links name their target page, Kerf automatically binds them to the matching WordPress pages on import and lists any uncreated pages under Kerf → Links so you can create drafts in one click.
3. Keep shared styles in an external stylesheet (css/style.css): That way every inner page and blog template shares one clean stylesheet in WordPress.
4. Output standard HTML, CSS, and vanilla JS (not an unbuilt React/Vite repo): Browsers—and WordPress—run HTML, CSS, and JS directly. If you use Tailwind, ask for a compiled CSS file or the Tailwind Play CDN script rather than a package.json build step.
5. Optional—add data-kerf-* attributes for live blog & site details: A single attribute on a blog card (data-kerf-loop="latest") or phone number (data-kerf-site="phone") makes it dynamic on import (or you can let Kerf AI mark it automatically!).

The Copy-Paste Prompt Brief for Claude, ChatGPT & Gemini

Every copy of Kerf includes a ready-made brief on Kerf → Import design, under No design yet? → Copy the brief. You can also copy this universal template directly into your next AI session:

Build a complete, responsive website as plain HTML, CSS, and JavaScript files packaged for a ZIP folder (no React, Vite, or build step required).

Pages to include:
- index.html (Home page)
- about.html (About page)
- services.html (Services page)
- contact.html (Contact page with a standard <form>)
- blog.html (Blog listing page)
- post.html (Single blog post template)

Structure & conventions:
1. Wrap the top navigation bar in <header>, the page body in <main> with semantic <section> blocks, and the site footer in <footer>.
2. Inside <header>, use a <nav> with real relative links (index.html, about.html, services.html, blog.html, contact.html).
3. Put shared styles in css/style.css and shared scripts in js/main.js. Keep relative asset paths clean (e.g. images/...).
4. On contact.html, use a semantic <form> with named <input> and <textarea> fields and a <button type="submit">.
5. For dynamic WordPress binding (Kerf markup contract):
   - Mark business details with data-kerf-site="name|phone|email|address|hours".
   - On blog.html, mark the first post card with data-kerf-loop="main" and its inner elements with data-kerf-field="image", data-kerf-field="date", data-kerf-field="title permalink", and data-kerf-field="excerpt".
   - On post.html, mark the post title with data-kerf-field="title", date with data-kerf-field="date", featured image with data-kerf-field="image", and body container with data-kerf-field="content".

What Happens When You Drop That ZIP into Kerf

When you upload the resulting ZIP into Kerf → Import design:

• index.html, about.html, services.html, and contact.html become editable WordPress pages with every link bound.
• blog.html and post.html become your live WordPress Blog and Single Post templates—rendering your real WordPress articles inside your AI design’s cards.
• The contact form on contact.html immediately starts sending emails and saving leads under Kerf → Form entries.
• Your phone number, email, address, and opening hours are wired to Kerf → Site details so you can update them in one place.

Already Generated a Site Without the Brief?

Don’t worry—you don’t need to re-prompt from scratch. Kerf imports unmarked HTML designs cleanly, and Mark it with AI on the import screen can add the blog and post markers for you automatically.

Originally published on kerf.site. Try Kerf free in your browser — a private WordPress with Kerf installed, no sign-up: https://kerf.site/demo/

Why does that happen—even when you copy the exact same CSS file into WordPress? The answer lies in DOM wrapper pollution and cascade order.

1. How Extra Wrappers Break Modern CSS

Modern CSS relies heavily on parent-child relationships: Flexbox, CSS Grid, direct child combinators (>), and adjacent sibling combinators (+). Consider a simple rule from a designer’s stylesheet:

body > header + main > .pricing-grid > article {
  display: flex;
  flex-direction: column;
  justify-content: space-between;
}

Look at what happens in a typical WordPress theme or page builder:

• Full Site Editing wraps the page in <div class="wp-site-blocks">, wraps the header in <header class="wp-block-template-part"><header>..., and wraps the body in <div class="entry-content wp-block-post-content">. Now body > header + main never matches.
• A page builder wraps every widget in 3 to 5 layers of .elementor-widget-container or .et_pb_module divs. Direct CSS Grid and Flex items cease to be children of the grid container.
• WordPress’s own core/table block wraps every <table> in a <figure class="wp-block-table">, breaking .pricing > table.

2. How Kerf Keeps the Same DOM

When we engineered Kerf, we set a strict benchmark: success is not “does it look close,” but “is the rendered DOM the same DOM?”

• Unwrapped document chrome: Kerf unwraps core/template-part and core/post-content at render time and copies your mockup’s <html> and <body> classes and data-* attributes onto the real document tags.
• kerf/div renders one element with one set of attributes: A <section class="hero"> becomes a block that renders <section class="hero">. A <td> renders a <td>. Nothing is normalized or wrapped.
• Additive-only core blocks: Headings (core/heading) and paragraphs (core/paragraph) use native WordPress blocks so you get rich text editing and Yoast/Rank Math compatibility without inserting wrapper elements.
• Case-accurate inline SVG: PHP’s DOMDocument::loadHTML() normally lowercases viewBox to viewbox and linearGradient to lineargradient, breaking SVG scaling. Kerf restores canonical SVG camelCase and sanitizes against a strict DOM allowlist.

3. Proving It: Pixel-by-Pixel Image Subtraction

On the Kerf home page, we show the Copperline Studio template opened as a static HTML file on the left and rendered by WordPress after a one-click Kerf import on the right. When you blend the two 1440×900 screenshots with CSS mix-blend-mode: difference, identical pixels subtract to pure black (#000000).

Copperline Studio on WordPress — 134/134 selectors matched

The rendered WordPress page keeps every tag, class, stylesheet, and script in source order.

Want to test how your most complex stylesheet holds up? Launch the live WordPress Playground demo and drop in your ZIP to see your selector match score in seconds.

Originally published on kerf.site. Try Kerf free in your browser — a private WordPress with Kerf installed, no sign-up: https://kerf.site/demo/

In 2026, the fastest-moving studios use a completely different pipeline: prototype real HTML/CSS designs with AI in the morning, import them into WordPress with Kerf after lunch, and hand off a locked, client-proof CMS before dinner.

1. Prototype in Real HTML Instead of Static Pictures

Instead of showing a client flat images that still have to be rebuilt from scratch once approved, agencies use Claude, ChatGPT, Gemini, or their own front-end library to generate a real multi-page HTML folder. The client previews real responsive typography, hover states, and scroll animations in their browser on Day 1.

2. Import the Entire Multi-Page Site in One Pass

Once the client approves the direction, you upload the ZIP under Kerf → Import design:

• Each page of the design becomes a WordPress page, and its marked blog, post and 404 files become templates (Kerf AI can mark them for you).
• Internal links across the header, footer, and call-to-action buttons bind automatically to the created WordPress pages.
• Contact forms that posted nowhere start emailing notifications and storing leads in Kerf → Form entries.

3. Handle Client Revisions with Section-by-Section Sync

What happens when the client emails two days later asking for a new testimonial carousel on the home page—after your copywriter has already edited the hero and services text inside WordPress?

With Kerf → Update design, you upload the updated ZIP and Kerf diffs the design section by section:

• New and updated sections from the mockup are checked and ready to apply.
• Sections your team already edited inside WordPress are automatically detected and left unchecked so live copy is never overwritten.
• Every update is backed by one-click Undo.

4. Wire Up Site Details & Lock the Layout with Client Mode

Before handing over the WordPress login, two built-in agency features save hours of future support tickets:

1. Kerf → Site details: Centralizes the client’s business name, phone number, email, physical address, and opening hours. When the client changes their phone number or seasonal hours on that one screen, the header, footer, and contact page update everywhere.
2. Client mode: Give your client an Editor account and client mode is on for them (Kerf → Settings can turn it off). Your client can freely edit headlines, paragraphs, images, background pictures, and links in the Block Editor—while block movement, deletion, insertion, and HTML class settings are completely locked.

One-Time Lifetime Agency Licensing

Unlike a page-builder subscription renewed every year, Kerf is a one-time payment with lifetime updates: $99 for 5 sites (Freelancer) or $199 for unlimited sites (Agency) at launch pricing. Compare plans →

Originally published on kerf.site. Try Kerf free in your browser — a private WordPress with Kerf installed, no sign-up: https://kerf.site/demo/

For a real business or client website, the cracks appear on Day 2.

What Happens on Day 2 of a Static HTML Site

As soon as a business site goes live, non-technical owners and marketing teams need to do five everyday tasks that raw HTML files make surprisingly painful:

1. Fixing a typo or swapping a team photo: Without a CMS, changing one sentence or replacing a headshot means opening a code editor, editing raw HTML tags, resizing images manually, and re-deploying files.
2. Publishing articles for SEO: A static blog.html file is just a façade. Without a database, categories, RSS feeds, pagination, and dynamic templates, every new blog post requires duplicating HTML files and manually updating index cards across the site.
3. Receiving contact form leads reliably: Static HTML <form> tags don’t send email or store submissions without wiring up external third-party form endpoints and paying monthly SaaS fees.
4. Using standard WordPress SEO & marketing plugins: Businesses rely on Yoast SEO, Rank Math, redirection managers, analytics integrations, and caching tools that work out of the box on WordPress.
5. Changing a phone number or address across 15 pages: In static HTML, that means search-and-replace across every file.

Why People Hesitated to Use WordPress—Until Now

The main reason designers hesitated to put AI-made HTML sites on WordPress was the conversion tax: nobody wanted to spend two days rebuilding a finished HTML design inside Elementor or watching a theme overwrite their CSS.

How Kerf Gives You Static-HTML Fidelity with a Full WordPress CMS

Kerf eliminates the trade-off between design fidelity and CMS power:

With Kerf, you keep the front-end work your AI tool or designer produced, as written—and gain the publishing power, SEO ecosystem, and client editability of WordPress in a single click.

Originally published on kerf.site. Try Kerf free in your browser — a private WordPress with Kerf installed, no sign-up: https://kerf.site/demo/

When we built Kerf AI into Kerf, we took the opposite path: every Kerf plan includes the full Kerf AI suite, and it talks directly to Google using your own Gemini API key. Even a free key from Google AI Studio works, and nothing is ever sent to Google until you click an AI button.

5 Ways Kerf AI Speeds Up Your WordPress Workflow

Once you paste your Gemini API key under Kerf → Settings, five specialized tools unlock across your dashboard and Block Editor:

1. Build a Complete Multi-Page Site from a Brief (Kerf → Build with AI)

Don’t have an HTML ZIP yet? Describe your business and select up to twelve photos from your WordPress Media Library. Kerf AI designs a cohesive multi-page HTML/CSS site—including marked Blog, Single Post, and 404 templates—and opens it directly in the Kerf importer check screen.

2. Turn Rough Notes or a Word Doc into a Page That Matches Your Site (Kerf → Make a Page)

What happens a month after importing your site when you need a new Services, Pricing, or About page? Open Kerf → Make a page (or click the Kerf AI icon inside the Block Editor on a new page):

• Paste rough notes or upload a .docx Word document, Markdown file, or HTML snippet.
• Kerf AI reads your existing site’s rendered HTML structure and CSS stylesheets, then builds the new page using your design’s actual banners, cards, grids, and buttons—keeping your words verbatim.

3. Rework Any Section Inside the Block Editor

Select any section on an existing page and ask Kerf AI to transform it—for example, “Turn this bulleted list into a 3-column feature card grid using this page’s card styles” or “Add an hours-and-rates table below this heading.” Because the change runs inside the Block Editor, standard Ctrl+Z / Undo works immediately.

4. Automatically Wire Up Static Blog & Post Templates

If your HTML ZIP includes a blog.html or post.html file that wasn’t pre-marked with data-kerf-* attributes, click Mark it with AI during the import check. Kerf AI identifies the post card loops, titles, dates, featured images, comments, and pagination and binds them to live WordPress data automatically.

5. Plain-English Import Diagnostics

If an AI-generated ZIP has missing image references or unmatched selectors on the fidelity report, click Explain it under In plain words on the import's Done step to get a plain-English summary and an exact fix-it prompt you can paste back into the tool that generated the design.

Included in Every Lifetime Plan

Kerf AI is included in Personal ($49), Freelancer ($99), and Agency ($199)—pay once, own it for life, and bring your own Gemini key. Read the Kerf AI documentation →

Originally published on kerf.site. Try Kerf free in your browser — a private WordPress with Kerf installed, no sign-up: https://kerf.site/demo/