Meta Catalog Feed JSON Error — How to Fix It
Meta rejected your catalog JSON feed?
Most Meta catalog feed JSON errors are the same syntax problems as Google: a trailing comma, smart quotes in
title or description, or an unclosed { / [. Paste the feed
into a browser fixer, repair the flagged line, then upload again in Meta Commerce Manager.
Boundary: This page covers JSON that won't parse. Policy, image, or price mismatches after the file is valid JSON are separate Commerce Manager item issues.
Meta catalog feed vs Google Merchant JSON (one paragraph)
Both platforms need valid JSON first, but the schema differs. Google Merchant
Center often expects a top-level items array with fields like id,
title, link, and price. Meta catalog feeds (Commerce Manager / catalog API)
use their own product object shape — commonly id, title, description,
availability, condition, price, link, and
image_link — and may wrap rows differently depending on whether you upload a file or sync from
Shopify. Do not copy a Google feed file verbatim into Meta without mapping fields; fix JSON
syntax here, then align attribute names to Meta's catalog spec in Commerce Manager.
Common Meta catalog JSON feed errors
- Invalid JSON / parse error — trailing comma after the last product
- Unexpected token — curly quotes from Excel or ChatGPT exports
- Unclosed bracket — missing
}in the products array - Wrong file type — CSV uploaded while the integration expects JSON
- Markdown fences — LLM wrapped output in
```jsonblocks
Fix in 3 steps
- Download or copy the JSON catalog Meta Commerce Manager rejected.
- Paste into the product feed fixer → Validate → fix commas, quotes, and brackets on the reported line.
- Re-upload the valid JSON and confirm field names match Meta's catalog requirements.
FAQ
- What does a Meta catalog feed JSON error usually mean?
- The upload cannot be parsed as JSON. Fix syntax first (commas, quotes, brackets), then re-upload. Missing Meta required fields are a separate step after the file parses.
- Can I use the same JSON file for Google Merchant and Meta?
- Only if you map fields to each platform's schema. Syntax repair is shared; attribute names and required columns are not. See our Google Merchant JSON feed error page for GMC-specific notes.
- Why does Meta say my feed is invalid when JSON lint passes?
-
"Valid JSON" means the parser succeeded. Meta may still reject rows for bad URLs, currency format,
or missing
id/image_link. Fix syntax here, then use Commerce Manager's diagnostics for row-level issues. - Is it safe to paste my catalog into this tool?
- Validation runs in your browser; we do not upload your catalog. Redact API tokens or secrets if they appear in the file.
Related: Product feed JSON fixer · Google Merchant JSON feed error · Shopify product JSON invalid · WooCommerce product feed JSON invalid · Fix LLM JSON
Tools run in your browser; we don't store your feed.