Limitations

Soft size guidance, provider plan limits, and request-throttling limits that affect CrossWatch behavior.

CrossWatch is not built for very large libraries.

It is a UI-first tool with metadata enrichment, images, and safety checks.

It is not a bulk-sync engine. Big libraries create heavy API traffic and large JSON files.

For large libraries, try the CrossWatch CLI for syncs and monitoring.

Size guidance

These are approximate limits.

The tighter limits below are about API pressure and JSON file sizes

CW recommends these rough upper bounds for normal use:

• Watchlist: ~2,500
• Progress: ~2,500
• History: ~25,000
• Ratings: ~25,000
• Collections: ~25,000

The synchronization itself is usually not the issue. Problems are more likely to appear in the UI such as the widgets. As this require much more processing power on your host, depending on the amount of data being handled. If you have much data, just disable the widgets first.