Why manual json validator & formatter fails on real files

A payload throws "Unexpected token" and nothing else. You scroll through 900 lines looking for a missing comma, and the browser console truncates the message right before the part that matters.

You see this most often in webhook payloads, API fixtures, config files copied from a chat message. Most online formatters pretty-print invalid JSON as far as they can parse it, which makes a broken file look almost fine.

What actually goes wrong

Manual handling fails in a specific way: it does not produce obviously broken output, it produces output that is almost right. Most online formatters pretty-print invalid JSON as far as they can parse it, which makes a broken file look almost fine. The mistake survives review because nothing looks wrong until an importer rejects the file or a report is quietly incorrect.

A cheaper habit

Check the file before it leaves your machine. That is the entire purpose of JSON Validator & Formatter — it reads the data you paste, applies the same rules an importer would, and shows the row that will break, rather than a summary of how many rows broke.

Because the parser reports the byte offset, a 900-line payload becomes a two-second fix instead of a scroll-and-squint session.

For the full picture — imports, feeds, variants, identifiers — see the pillar guide: Shopify product data management.

Try it on your own file

Open JSON Validator & Formatter and paste a sample. It is free, it does not store anything, and you do not need an account. If the file is sensitive, save the page locally and run it offline.

Questions people ask

Does it show where the error is?

Yes — it reports the line and column from the parser, not just "invalid JSON".

Can I minify instead?

Yes, there is a separate minify action on the same page.