Editing your Shopify theme with ChatGPT or Claude? Check these 9 things before you publish

The short answer: yes. ChatGPT, Claude and Shopify's own AI tools can all write working Liquid, CSS and JavaScript for a Shopify theme. The code is rarely the problem. The problems come from where it gets pasted, what it quietly breaks and what nobody checks. Work on a copy of your theme, keep content editable, test speed and mobile, and get a second pair of eyes on it before you publish.

We build with AI tools every day, and this is the checklist we use ourselves, written for founders and ecommerce managers who are copying theme code into a chat window and pasting the answer back into Shopify.

Can you use ChatGPT or Claude to edit your Shopify theme?

Yes. A general AI assistant knows Liquid (Shopify's template language) well enough to build a new section, restyle a product page or add a small feature. Shopify's own assistant, Sidekick, can now edit themes and generate new theme blocks from a description in the theme editor. For a contained change, such as a new banner section or a tweak to how prices display, the first draft is usually close.

What an assistant can't do is see your whole store. It doesn't know which apps inject code into your product page, how your subscription widget hooks into the add-to-cart button, or that your review count comes from an app rather than the theme. It writes what you ask for, in isolation, and it sounds equally confident whether the answer is right or wrong. Code that runs isn't the same as code that's right: Veracode's 2026 research found AI-generated code almost always compiles, but passes its security checks only 56% of the time (Veracode, July 2026).

Shopify is clear about who owns the result. Its help page on AI-generated blocks says: "You're responsible for reviewing, testing, and ensuring the generated block meets your standards". That's where the checks come in.

Before you paste anything: work on a copy

Never edit your live theme. In your Shopify admin, go to Online Store → Themes, open the menu next to your current theme and choose Duplicate. Make every change on the copy, preview it, and only publish when you're happy. If something goes wrong after you publish, the previous theme is still in your library and you can switch back in a couple of clicks. Most Shopify plans hold up to 20 themes (Plus holds 100), so there's room for a working copy.

Don't rely on the code editor's history as your backup. It restores one file at a time, can't bring back a deleted file, and Shopify says older versions might not be available. A duplicate theme is a complete, known-good copy.

Two more habits save a lot of pain:

• Change one thing at a time. Ask for one section, test it, then move on. A whole page generated in one go is hard to check and harder to fix.
• Name your copies. "Homepage hero test, 8 Oct" tells you what you were doing three weeks later. "Copy of Copy of Dawn" doesn't.

The 9 checks we run on AI-written theme code

1. Can your team still edit the content without touching code?

This is the most common problem we see. Ask an assistant for a "reviews banner" and you may get 4.8 stars from 2,143 reviews typed straight into the code. It looks right on the day and is wrong a week later. Text, images, prices, dates, review counts and claims belong in section settings, metafields or metaobjects, where your team can change them in the theme editor or the admin. Ask the assistant to "add settings to the section schema for every piece of text and every image", then check that they show up in the theme editor.

2. Is the code in the right place?

Assistants often hand back one long block with HTML, CSS and JavaScript together, and the easiest place to paste it is theme.liquid. That file loads on every page of your store, so a script meant for one product page now runs everywhere. It also holds code Shopify and your apps depend on, which Shopify says you shouldn't modify. New features should live in their own section or snippet, with styles and scripts in the theme's asset files, loaded only where they're used. And if the answer starts with <html>, <head> or <body> tags, it's a whole web page, not a Shopify section, and pasting it in will break the layout.

3. Did it leave anything behind?

Every round of "that's not quite right, try again" can leave old code in place. Look for unused CSS classes, functions nothing calls, console.log lines, commented-out attempts and second copies of libraries your theme already loads. One common one: an assistant adds jQuery to make its snippet work, on a theme that doesn't otherwise need it. Each leftover adds weight to every page view.

4. Is the page still fast?

Measure before and after, on mobile. Run the page through PageSpeed Insights on your live theme, then on your preview, and compare. Google's Core Web Vitals targets are a useful bar: the main content should appear within 2.5 seconds (Largest Contentful Paint), the page should respond to a tap within 200 milliseconds (Interaction to Next Paint), and the layout shouldn't jump around (Cumulative Layout Shift under 0.1). Shopify's web performance report in your admin tracks the same three measures from real visitors, but it uses the last 30 days of data, so it won't show the effect of a change straight away. Big images without set dimensions, scripts that block the page from drawing and fonts loaded twice are the usual culprits. We cover the wider causes in how to speed up your Shopify store.

5. Does it work on a phone, with a keyboard and with a screen reader?

Most of your customers will see the change on a phone, so test it on a real one, not just a narrow browser window. Then put the mouse away and try to use the new section with the Tab and Enter keys. AI-written components often use plain boxes where they should use buttons and links, which means keyboard and screen-reader users can't reach them. Check images have alt text, text has enough contrast (Shopify's guidance is a ratio of at least 4.5:1 for body text), and nothing important is only shown on hover. For a benchmark, Shopify asks themes in its Theme Store to average at least 90 for accessibility and 60 for performance in Lighthouse, the audit built into Chrome.

6. Do your apps still work?

Apps hook into your theme through app blocks, app embeds and, on older setups, code added to theme files. A rewritten product form can quietly disconnect the subscription selector, the reviews widget, a Klaviyo sign-up form or your tracking. A new section also needs to accept app blocks, or the theme editor will tell you apps aren't supported there. On a subscription store this is the check that matters most. Before you publish, run through the journeys that make money: choose a one-off and a subscription option, add to cart, open the cart, change a quantity and reach checkout.

7. Is it using current Shopify features?

Assistants learn from years of public code, including code written for older Shopify themes. That shows up as deprecated Liquid, such as the old img_url filter instead of image_url, or features rebuilt by hand that Shopify now handles natively. Shopify's code editor flags some problems as you type. The full version, Theme Check, is Shopify's own linter and catches deprecated filters, scripts that block the page, images without dimensions and broken section settings. If a developer connects an AI coding tool to your theme through Shopify's AI Toolkit, it can run these checks as it goes.

8. Does it look like your brand, or like AI?

Ask an assistant to design a whole page and you'll often get the same page everyone else gets: a small label above every heading, three identical cards, soft gradients, rounded everything and copy that says a lot without saying anything. Customers notice, even if they can't name it. Give the assistant references from your own site and brand, build one section at a time, and cut anything that's there because it's "what a website looks like" rather than because your customer needs it.

9. Has someone else checked it, and can you undo it?

The person who wrote the prompt is the worst person to review the result. They know what it's meant to do, so they test the path they had in mind. Ask someone else to try to break it. Then make sure you know how to undo it: which theme copy to switch back to, or which file versions to restore. If you can't answer that before you publish, you're not ready to publish.

When to stop and call a developer

AI is good for contained, visible changes. Bring in a developer when the change touches:

• Checkout, payments or subscriptions. Subscription logic, bundle pricing and anything that changes what a customer is charged needs testing against real scenarios, not a happy path.
• Customer data or API keys. Never paste customer details, app secrets or Admin API tokens into a chat tool.
• Integrations. Anything that sends data to your 3PL, ERP, email platform or subscription app.
• Performance you can't explain. If the page got slower and you don't know why, guessing with more AI prompts usually makes it worse.
• Anything you can't verify. If you can't tell whether the code is correct, you can't tell whether it's safe to publish.

How we use AI on client stores

We use AI tools on client work every day, and they've made us faster. What hasn't changed is the process around the code. Every change starts from a written ticket, goes on its own branch or theme copy, keeps content in settings and metafields, and gets reviewed by someone who didn't write it. It's checked on mobile and desktop, with before and after speed evidence where it matters, and a person approves every release. AI writes the first draft quickly. The checks are what make it safe to publish.

If you've got AI-written changes you're not sure about, or a theme that's grown messy from a few too many quick fixes, our Shopify development team can review it, or take on the work through a growth retainer. Let's talk.

A checklist you can copy

1. Duplicate the live theme and work on the copy.
2. Ask for one section or change at a time.
3. Put text, images, prices, dates and review counts in settings or metafields.
4. Keep new code in its own section, snippet and asset files, not in theme.liquid.
5. Remove leftovers: unused code, logs, duplicate libraries.
6. Compare PageSpeed Insights before and after, on mobile.
7. Test on a real phone, with a keyboard and for contrast and alt text.
8. Run the money journeys: product, subscription option, cart, checkout.
9. Get someone else to test it, and write down how to undo it.

Frequently asked questions

Can ChatGPT edit my Shopify theme directly?

Not on its own. ChatGPT and Claude write code that you copy into Shopify's code editor. Shopify's own Sidekick can edit themes and generate blocks inside the theme editor, and developers can connect tools such as Claude Code to a development theme through Shopify CLI, GitHub or Shopify's AI Toolkit. Whichever route you use, a person should review and publish the change.

Is it safe to paste my Shopify theme code into ChatGPT?

Theme code itself is usually fine to share. Don't paste customer data, Admin API tokens, app secrets or private keys into any chat tool, and check your AI plan's data settings if you're sharing anything commercially sensitive.

How do I undo a change I made in the Shopify code editor?

The simplest way is to publish the theme copy you made before you started. Shopify's code editor can also restore an earlier version of a single file, but its history is limited and it can't recover deleted files, so a duplicate theme is the safer backup.

Will editing my theme's code stop it from updating?

Not usually, but you can lose edits. When a Theme Store theme updates, Shopify creates an updated copy that keeps your theme editor settings and carries over code edits unless they clash with the new version. Clashing edits are left out and have to be redone by hand. Blocks generated by Sidekick don't stop updates, but themes edited in Shopify's new Canvas workspace don't receive updates at all. Keep a note of every code change so it can be reapplied.

How do I check my store's speed after a change?

Run the page through PageSpeed Insights on mobile, before and after the change, and compare the results. Shopify's web performance report shows Core Web Vitals from real visitors over the last 30 days, so it takes a few weeks to fully reflect a change. Use both.

Do I still need a Shopify developer if I use AI?

For small, visible changes you can test yourself, often not. For checkout, subscriptions, integrations, customer data and anything you can't confidently test, yes. The value of a developer now is less about typing the code and more about knowing whether it's right.