Short answer. Commerce Manager shows “Feed download speed is slow or exceeds file size” when the file is over the limit (100 MB for a one-time upload, 4 GB for a scheduled feed) or your server delivers it too slowly for the fetch to finish. Compress files over 1 GB as ZIP or GZIP, split very large catalogues into several feeds, and move the file to a faster host if the problem persists.
| Shown in Commerce Manager as | Feed download speed is slow or exceeds file size |
|---|---|
| Effect | Whole feed blocked |
| Where to find it | Catalog → Products → a product’s Status and issues; feed-level errors under Catalog → Data sources → Download issue report |
| Free check | Not something a feed file shows; see below for what the check can tell you instead |
What Commerce Manager means by “Feed download speed is slow or exceeds file size”
Meta’s data feed troubleshooting page gives the numbers: a one-time upload may be 100 MB, a scheduled feed 4 GB, and it recommends compressing files over 1 GB as ZIP or GZIP. The product data specification adds a recommended ceiling of one million items per feed and suggests splitting larger catalogues into several feeds. The message appears both when a file is over its limit and when the server delivers it so slowly that the fetch does not finish.
For most stores this is a speed problem, not a size problem: a feed built on request by a slow server takes minutes to start sending, and Meta gives up.
Why it happens
- A file over the limit for its upload type.
- An uncompressed multi-gigabyte file that would fit compressed.
- A feed generated on request by a server that takes too long to start responding.
- Throttling of Meta’s crawler by the host or CDN.
- Network problems between the host and Meta, which the page asks you to rule out.
How to fix it
In Shopify
Use the Facebook & Instagram channel’s sync for large catalogues; it does not move a file at all. If a feed app generates the file, check whether it can pre-generate on a schedule and serve a static file rather than build on each request.
In WooCommerce
Our free plugin builds the feed at request time, which is fast for catalogues of a few thousand products on ordinary hosting. For very large catalogues, or a slow host, use a feed service that pre-renders the file and serves it from a fast origin, and make sure the host does not rate-limit facebookexternalhit.
In a CSV or XML feed
Check the file size against the limit for your upload type. Compress anything over 1 GB. Split a catalogue over a million items into several feeds. Time the download of your feed URL from outside your network; if it is slow to start, move the file to a static host or a CDN.
How long until Commerce Manager clears it
On the next fetch that completes within Meta’s limits. A manual upload from the feed’s Settings tab is the quickest test.
What FeedRobin does about it
The free feed check reads up to 40 MB of a feed from a server of ours, so a URL that is too slow to answer fails the check the same way it fails Meta, and the report says the address could not be read. For connected stores the Meta feed is served from our servers, built from the catalogue we already hold, so the fetch never waits on your store.
Questions merchants ask
How many products can one feed hold?
Meta recommends up to one million items per data feed and says to split larger catalogues into several feeds uploaded separately.
Does compression change the size limit?
The limits apply to what Meta downloads, so a compressed file counts at its compressed size. Meta recommends ZIP or GZIP for anything over 1 GB.
My file is small but the fetch is still slow. Why?
The feed is generated on request and the server takes too long to start sending, or the host throttles Meta’s crawler. Pre-generate to a static file, or serve it from a CDN.
Sources
- Troubleshoot data feed errors in your catalog — Meta Business Help Centre
- Product data specifications for catalogs in Commerce Manager — Meta Business Help Centre