Fixes · From design to theme

Your Claude Design or Lovable export looks different as a Shopify theme

The fix

An export from Claude Design, Lovable or v0 is a finished web page: the words, pictures and styles are written into it, and the basket often only exists in the browser. Turned line by line into Liquid, it can give Shopify a theme it accepts, but not one that looks the same or that anyone can edit.

Keep the export’s styles and use its pages as the reference. Rebuild each part of each page as a section with settings, and each list as blocks. Put the real products, basket and checkout behind it, then compare every page with the design at phone and desktop sizes.

01Why the converted theme doesn’t match

AI design tools give you a page that works in a browser: HTML, CSS and JavaScript, with every word and picture written into the code. Clickable prototypes go further and fake the parts of a shop that need a server. Fuzzball’s, made in Claude, kept its basket, its quiz answers and a pretend subscription in the browser’s own storage, and had a “Reset demo” button in the footer.

A Shopify theme is built the other way round. “JSON templates are data files that store a list of sections to be rendered, and their associated settings,” and “Merchants can add, remove, and reorder these sections using the theme editor” (Shopify, JSON templates). Inside a section, “Blocks are reusable modules of content that can be added, removed, and reordered within a section” (Shopify, section schema). The words, pictures and links live in those settings, not in the code.

So the job isn’t a conversion from one format to another. A merchant on Shopify’s developer forum (Aug 2026) had Claude rebuild a Claude Design export as a Liquid theme. Shopify accepted it, “however the resulting website differed significantly from the original Claude Design, with design elements, animations and functionality either changed or missing.” The reply put it plainly: “There isn’t a direct way to import a standalone HTML/CSS/JavaScript project into Shopify and preserve it 1:1.”

Where it goes wrong

  1. 01

    The styles are rewritten

    A conversion that rebuilds the page in a theme’s own markup brings new class names and new CSS, so the export’s spacing, type sizes and phone layout no longer apply. The reply on the forum: “Some of the original CSS, JavaScript, and animations may be reusable, but they still need to be integrated and tested within that structure.”

  2. 02

    The content stays in the code

    If the headings, pictures and links are copied into the Liquid as they were in the export, Shopify shows the page, but the theme editor has nothing to change. Every edit goes back to a developer.

  3. 03

    The fake parts stay fake

    A basket kept in the browser, prices typed into the page and a checkout button that goes nowhere all look right in a demo. On a store they have to be Shopify’s real products, basket and checkout.

  4. 04

    Nobody compares it with the design

    The theme loads, so it looks done. Differences only show when each page is put beside the design at the same size.

02Build it as sections, against the design

For store owners

  1. Keep the export, not just a link

    Download the export or the project’s code from the tool, and keep the version you approved. It is the design: whoever builds the theme works from it and checks against it.

  2. Write down what has to be real

    Go through the prototype and list everything a shopper does: add to basket, pick a size or a plan, sign up, log in. Each one needs Shopify, an app you already run, or something built.

  3. Decide what your team will change

    Headings, pictures, offers, the order of sections on a page. Those become settings and blocks in the theme editor. Anything you’ll never change can stay fixed.

  4. Check it in the theme editor before it goes live

    Open the new theme in the theme editor from Online Store > Themes and try changing a heading, a picture and a link on each page. If you can’t find where something is set, it isn’t finished.

For developers

  1. Start from a clean theme and bring the export’s styles across

    Start from Shopify’s skeleton theme or your own base, and bring the export’s stylesheet in as it is, so the page looks right from the first section. Move each rule into the section that uses it as you build that section, until the shared file is empty.

  2. One section per part of the page

    Each part of the design becomes a section, and its words, pictures and links become settings. Use image_picker for pictures and url for links, whose picker lists the store’s products, collections, pages, blogs and articles (Shopify, input settings). A typed path or file name in a text box is a setting nobody can use.

  3. Lists become blocks

    Steps, cards, questions and quiz screens become blocks, so the team can add, remove and reorder them. A JSON template can hold up to 25 sections, and each section up to 50 blocks (Shopify, JSON templates).

  4. Colours become colour schemes

    Take the design’s brand colours from its CSS variables and set them up as theme colour schemes, so each section can pick one in the editor.

  5. Replace every fake part

    Products, prices and collections come from Shopify objects, never typed. The basket goes through the Cart API (Shopify, Cart API), with whatever line properties and selling plans your apps read. Checkout is Shopify’s own: style it in the checkout settings, not in the theme (Shopify Help, checkout style).

  6. Keep the prototype’s logic where it has some

    If the prototype works something out, like a price or a recommendation, move that code into a theme script as it is and check both give the same answer for the same inputs.

The other route is headless. If the export is a full JavaScript app, as Lovable, v0 and Bolt often make, it can run on Hydrogen, Shopify’s own framework for it. More of the code survives, but as the forum reply put it, “Products, collections, cart, checkout, SEO, analytics, privacy, hosting, and ongoing maintenance still need to be implemented,” and the theme editor no longer applies.

03Put it beside the design

  1. Same page, same size, side by side

    Open each page of the prototype and the theme at a phone width (390px) and a desktop width (1440px). Compare the words, the spacing and what happens on a tap.

  2. Run the shopper’s jobs on the theme

    Add to basket, change the quantity, go to checkout, use any quiz or builder, at both sizes. Then empty the basket.

  3. Change something in the editor

    Change a heading, swap a picture and reorder a block on a few pages, then preview. The page should change and nothing else should move.

  4. Look for settings that do nothing

    Settings for things the design never shows are confusing. Take them out.

From our work

04Fuzzball’s new site, from the founder’s own prototype

The founder of Fuzzball, a UK cat food subscription we look after, designed the new site himself as a clickable prototype in Claude: one HTML file with the quiz, the plan page and the bag all working in the browser.

Fuzzball’s home page in the founder’s Claude prototype, on a phone
The same home page in the Shopify theme built from it, on a phone
The home page at phone size: the prototype, then the new theme on a preview, 19 Nov 2026. The theme isn’t live yet.

The build (from 10 Nov 2026). We started from Shopify’s skeleton theme with the prototype’s stylesheet as it was, and set up the prototype’s brand colours as colour schemes. Before anything was styled, the basket was built to match the live store’s line for line, so the subscription app and the order flow get what they get today. The quiz runs on the prototype’s own feeding maths, moved into a theme script with a check that both give the same answers, apart from agreed changes. Each page was then rebuilt as sections, with lists as blocks: the quiz has one block per step.

The check (11 Nov 2026). Every designed page was put beside the prototype at phone and desktop sizes. The copy matched word for word apart from agreed changes, most pages lined up to the pixel, and for the same quiz answers the plan page showed the prototype’s boxes and prices.

The theme editor (18 Nov 2026). Twenty links that were typed paths became link settings, so the editor shows Shopify’s picker. Pictures that were typed file names are now chosen in the picture picker. Settings for things the design never shows came out, and “Show on” boxes now say what they mean.

We’ve done the same at page level: for a brand we build for through an agency, a long-read landing page its team designed in Claude went in as four sections of its theme, the copy word for word, each point a block the team can reorder.

  • In our live log“Store team can now pick pictures visually instead of typing file names”

The bigger picture

05The look is only the start

An AI tool can get you a design you’re happy with. What turns it into a store is everything behind the look: real products and prices, a basket your apps can read, a checkout, and an editor your team can use without calling a developer. If the converted theme is close but not right, or right but locked, the fix is a rebuild against the design, not more conversion.

That’s the work on our AI design page.

06Sources

Every step and claim above comes from one of these, or from the fix on the store it describes.

  1. Shopify developers: JSON templates (sections, the theme editor, 25 sections and 50 blocks)
  2. Shopify developers: Section schema (settings and blocks)
  3. Shopify developers: Input settings (image_picker, url)
  4. Shopify developers: Cart API reference
  5. Shopify developers: Hydrogen
  6. Shopify Help: Checkout style
  7. Shopify developer forum: Best way to integrate a complete Claude Design website into Shopify 1:1? (Aug 2026)

Sources checked on .

Contact

Got a design that needs a theme?

Send the export or a link to it, tell us which tool made it, and send your store’s address if you have one.