Blocking data quality

Fix “Catalog feed too large” on Meta Commerce Manager

Feed file exceeds Meta's size limits. For scheduled fetches the cap is roughly 8GB compressed; for the Catalog Batch API it's per-batch limits typically around 5,000 items.

What you see in Meta Commerce Manager:

Catalog feed too large

Meta's practical feed file limit is around 8GB compressed. For catalogs over 1M items, scheduled fetches become unreliable past this size.

The fix: split into multiple feeds per brand or category, or switch to incremental updates via Catalog Batch API. Smaller feeds process faster; incremental updates avoid the full-file refresh entirely.

Top causes

  • 1

    Catalogs over 1M items as a single file

  • 2

    XML feeds with verbose markup inflating file size

  • 3

    Large image data inadvertently included in the feed file

How to fix it

  1. 1

    Split into multiple feeds

    Per-brand or per-category feeds, each under 8GB. Meta accepts multiple feeds per catalog.

  2. 2

    Switch to incremental updates via API

    For catalogs over 1M items, full-file refreshes are inefficient. Use the Catalog Batch API for incremental updates.

  3. 3

    Strip unnecessary content

    Remove HTML, condense whitespace, drop optional fields not in use.

Related tools

FAQ

How big is too big?

Practical: 5GB compressed. Theoretical max is 8GB but processing slows materially past 5GB.

Last reviewed: 26 May 2026

Free plan · No card

Why wait? Try it free today.

Stop managing feeds manually. Start optimising with AI in 30 seconds.

  • Free plan, no credit card required
  • 1 brand, 1 feed, 100,000 products per feed
  • Full AI Product Optimisation, Rule Engine, and 200+ channel exports
  • Pay only for AI credits when you need them