Quotas affected by importing/exporting datasets using Sanity CLI

When using sanity dataset export and sanity dataset import from the CLI, these operations affect your API quota, not your API CDN or Bandwidth quotas.

Here's what you need to know:

Which Quota is Affected

API requests are the primary quota impacted by dataset export and import operations. These CLI commands make direct requests to Sanity's data backend, which count toward your API request limits:

• Free plan: 100K API requests/month
• Growth plan: 250K API requests/month (1M with paid add-ons)
• Enterprise plan: Custom limits

What's NOT Affected

• API CDN requests: These are for cached content delivery and don't apply to CLI operations
• Bandwidth quota: While the export/import operations do transfer data, they primarily count against API requests rather than the bandwidth quota (which is mainly for serving content to end users)

Why This Matters

The sanity dataset export command has a maximum execution time of 5 minutes, and for large datasets, you may need to consider:

1. Breaking up large exports: For datasets approaching the 10 million document or 10GB limit, you might hit API request limits
2. Timing your operations: Run exports/imports during off-peak hours if you're concerned about quota usage
3. Enterprise options: For very large datasets, consider Cloud Clone (Enterprise feature) which duplicates datasets server-side without counting against your API quota

The CLI operations are authenticated direct API calls, which is why they count against API requests rather than the CDN or general bandwidth quotas that apply to public content delivery.