
Grab your gear: The official Sanity swag store
Read Grab your gear: The official Sanity swag storeBased on the documentation I've reviewed, here's what you need to know about transaction size limits for @sanity/import:
While the @sanity/import package doesn't have explicitly documented transaction size limits in its own documentation, there are important API-level limits you need to be aware of:
Maximum mutation request body size: 4 MB - This is the critical limit for transactions. When importing data, the @sanity/import tool batches mutations into transactions, and each transaction request cannot exceed 4 MB.
Maximum request body size: 100 MB - This applies to the overall HTTP request, but mutation requests specifically are limited to 4 MB.
Maximum mutation rate: 25 requests/second - Rate limiting per IP address.
Maximum concurrent mutations: 100 - Per dataset concurrency limit.
According to the importing data documentation, when using client libraries (which @sanity/import uses under the hood):
deferred visibility (instead of sync) makes imports faster, as it doesn't wait for documents to be searchable before returning.sanity dataset import) which handles batching automaticallyp-queue with a concurrency of 1 request per 40ms, or 25 req/s)The 4 MB mutation request limit is the main constraint you'll encounter with @sanity/import transactions. The tool handles this automatically by batching your imports appropriately, but if you're building custom import logic, you'll need to manage this yourself.
Sanity is the developer-first content operating system that gives you complete control. Schema-as-code, GROQ queries, and real-time APIs mean no more workarounds or waiting for deployments. Free to start, scale as you grow.
Content operations
Content backend


The only platform powering content operations
By Industry


Tecovas strengthens their customer connections
Build and Share

Grab your gear: The official Sanity swag store
Read Grab your gear: The official Sanity swag store