What does "Invalid JSON in tag 'schema'" mean in Shopify?

It means the JSON between {% schema %} and {% endschema %} in one section file has a syntax mistake, so Shopify refuses to save that file. The usual culprits are a missing comma, single quotes instead of double quotes, curly quotes pasted from a document or chat window, or an unescaped " inside a text value.

We reproduced the error on a Shopify development store on 17 October 2026 by uploading nine section files, each with a different JSON mistake. The messages and results below are copied from that store.

What does the full error look like?

Shopify names the file and nothing else:

sections/missing-comma.liquid
Invalid JSON in tag 'schema'

There is no line number and no hint about which character is wrong. Every one of the six files Shopify refused in our test got exactly this message, whether the problem was a missing comma or a missing bracket. That is why this error feels harder than it is: the fix is usually one character, but Shopify does not tell you which one. The section below on finding the mistake covers two ways to get the exact spot.

Which mistakes cause it?

We uploaded nine versions of the same small section with Shopify CLI 3.93.1, each broken in one way. Six were refused. Three were accepted, which surprised us:

So Shopify's schema reader is more forgiving than strict JSON about trailing commas and comments, but not about quotes, commas between entries or brackets. We would still remove trailing commas and comments: Shopify does not document that it allows them, and any ordinary JSON checker you paste the schema into will flag them, which hides the real mistake in a list of false alarms.

How do I find the exact mistake?

Two ways, both free.

If you edit in the Shopify admin: copy everything between {% schema %} and {% endschema %} (not the tags themselves) and paste it into a JSON validator such as jsonlint.com, or into any code editor that understands JSON, like VS Code. It will point at the line and character where parsing stopped. The real mistake is usually on that line or the line just above it, because a missing comma is only noticed when the next entry starts.

If you use Shopify CLI: run shopify theme check in the theme folder. Unlike the upload message, it explains each problem under the ValidSchema check. These are the messages it gave for our broken files:

theme check reported each of these as an error with the line it applies to, and it raised nothing for the trailing comma or comment files, which matches what the upload accepted.

Why does one bad schema break my homepage?

Because the refused file is not saved, and whatever points at it then fails too. In our test, a homepage template that used the refused section was itself rejected with a second, unrelated looking message:

templates/index.json
Section type 'missing-comma' does not refer to an existing section file

If you see both messages in one upload, fix the Invalid JSON one. The template error disappears with it. The same chain happens with other schema errors, which we list in why a Shopify theme ZIP will not upload.

Did my live store break when the save failed?

No, and this is the reassuring part. We uploaded a working version of a section, confirmed it on the storefront, then uploaded a broken version of the same file. Shopify refused the broken one and the storefront kept showing the working version. A failed save changes nothing; your store keeps running the last version Shopify accepted.

The risk is the opposite one: a brand new section that is refused simply does not exist, so if you were adding it to a page, it is missing rather than broken. And nothing about this touches your products, orders or customers, which live outside the theme (see will I lose my products if I change my Shopify theme).

How do I avoid it next time?

• Never write schema in a word processor or notes app. They turn straight quotes into curly ones as you type. Use the Shopify code editor or a code editor.
• Check code from a chat assistant or a forum before pasting. Copying from some chat windows and web pages brings curly quotes along. Search the pasted block for “ and ”.
• Avoid double quotes inside text. If a default needs one, write it as \". An apostrophe needs no escaping in JSON.
• Add new settings one at a time and save between them. When the error appears, you know which entry caused it.
• Run shopify theme check before uploading if you use the CLI. It catches every refused case above with a readable message.

Valid JSON is only the first check. A schema can parse perfectly and still be refused for what it says, such as a setting with an empty default; that is a different message, covered in what "default can't be blank" means. If you are new to how settings and blocks fit inside a schema, the difference between a section and a block explains the structure.

Where these results come from

On 17 October 2026 we built a minimal theme with one working section and nine copies of it, each with one JSON mistake from the table above. We pushed it to a Shopify development store as an unpublished theme with Shopify CLI 3.93.1, read the errors Shopify returned, fetched the storefront to see which sections rendered, ran shopify theme check on the same folder, then tested the template chain and a broken save over a working file. We did not test the admin code editor itself. The test theme was deleted afterwards. If you would rather start from schemas that already pass, every theme in our free theme gallery has been uploaded to Shopify without errors, and you can preview it before installing.