Shopify "Liquid error" showing on a product or collection page
By Michael Broadbridge. Last checked 14 November 2026 on Shopify admin, code editor.
Short answer
The message names the file and line, for example Liquid error (sections/main-product line 12). Duplicate the theme, open Edit code on the copy, and find that file and line. If it says Could not find asset, a snippet file has gone, so remove the render tag or put the snippet back. Timeline restores earlier file versions.
Symptoms
You may see one of these messages:
Liquid error
Liquid syntax error
Could not find asset
Liquid error: internal
HTML error found
Theme error
- Text starting Liquid error or Liquid syntax error appears on a product, collection or other page.
- The message names a file and line, such as (snippets/product-card line 40).
- It appeared straight after an app was installed or removed, the theme was updated, or code was edited.
- The theme editor shows HTML error found or Theme error.
Causes, most likely first
A snippet that no longer exists
A render or include tag asks for a snippet file that has been deleted, and the page shows Could not find asset followed by its name. This happens when an app or a person deletes the snippet but leaves the tag.
A syntax mistake in edited code
A tag that is opened but never closed, or one that is mistyped, gives a Liquid syntax error. Liquid’s messages include ones such as 'if' tag was never closed and Unknown tag.
A theme update
Updating a theme creates a new copy. Code edits, including changes an app made, are only carried across when they do not conflict with the update, so a tag in one file can end up pointing at code that did not come across.
A failure Liquid cannot describe
Liquid error: internal is shown when the code fails for a reason that is not a normal Liquid error. If the named file has not been edited, the theme developer needs to see it.
How to fix it
Read the error
- Copy the full message. Liquid error (sections/main-product line 12) means the problem is on line 12 of main-product.liquid in the Sections folder. The text after the colon says what went wrong.
- Note which pages show it. If only some products show it, compare their Theme template setting with a product that works.
- If the message has no file or line, search the theme code for the snippet or tag it mentions.
Work on a copy
- Open your themes, click the three dot button on the live theme and choose Duplicate.Menu:
Online Store > Themes - On the copy, open the same menu and choose Edit code.
- Press Cmd + P on a Mac or Ctrl + P on Windows, type the file name from the error, such as main-product, and open it.
- Go to the line number from the error. The code editor underlines problems in red, and hovering over the line shows the error.
Fix a missing snippet
A render tag is a line such as {% render 'product-badge' %} that pulls a snippet into the page. The tag and the snippet file have to exist together.
- If the message says Could not find asset snippets/ followed by a name, click the search icon in the left sidebar and search all files for that name.
- If the snippet belonged to an app you have removed, delete each render or include tag that loads it, and save.
- If the snippet is part of the theme, copy it from an older duplicate or a fresh copy of the same theme from the Theme Store, and create it again in the Snippets folder with the same name.
- Preview the copy and check the page that showed the error.
Fix a syntax error or roll the file back
- For a Liquid syntax error, check the named line and the lines above it for a tag that is opened but not closed, such as an if with no endif.
- If you cannot see the mistake, open the file’s Timeline view and click an earlier entry to compare it with the current version.
- Copy the current contents somewhere safe. Then right click the version from before the error, choose Restore contents and click Restore.
- Preview the copy, check product and collection pages, then publish it.
Timeline restores one file, not the whole theme. Files in the Assets folder, such as CSS and JavaScript, have no Timeline history, and deleted files cannot be recovered.
If that didn’t work
The code belongs to an app you still use
If the file or snippet name matches an installed app, contact the app developer with the full message and the page address.
The version you need is not in Timeline
Timeline history is finite, so older versions may not be there. A fresh copy of the same theme from the Theme Store shows what the file looked like originally.
Liquid error: internal keeps coming back
This is not a mistake you can see in the code. If the file has not been edited, send the theme developer or Shopify Support the page address and the full message.
When to get help
Stop if the error is in a file nobody has edited and you cannot tell what added it, if restoring an older version breaks other pages, or if the fix means changing how prices, variants or the add to cart form work. Leave the live theme as it is and keep any changes on the copy.
What a developer would check
- The file and line in the message, and which tag or snippet fails there.
- Render and include tags that point at snippets no longer in the theme.
- Code from removed apps, and edits lost in a theme update.
- Theme Check warnings in the files that were changed.
Describe the problem in your own words and WebFixed gives you an instant fixed quote. Nothing is charged until you accept it.
Related questions
- What does Liquid error (sections/main-product line 12) mean?
- Liquid is Shopify’s theme language. The part in brackets names the file, main-product.liquid in the Sections folder, and the line where it failed. The text after the colon says what went wrong.
- Can I create an empty snippet to make the error go away?
- It removes the message but not the cause. If the tag belongs to an app you have removed, deleting the tag is cleaner. If the snippet belongs to the theme, an empty file leaves that part of the page missing.
- Can I get a deleted snippet back?
- Not from Timeline, which only restores earlier versions of files that still exist. Copy it from an older duplicate of the theme or from a fresh copy of the same theme.
Written by Michael Broadbridge, Founder of Webgro. First published 14 November 2026. Last checked 14 November 2026 on Shopify admin, code editor.