Why does Sanity have a 1 million document limit per dataset?

Good news! You're looking at outdated information. The current limit is actually 10 million documents per dataset, not 1 million. According to the technical limits documentation, the maximum number of documents is 10 million, with customization possible for enterprise customers.

Why does this limit exist?

The 10 million document limit exists for a few practical reasons:

1. Query Performance: Sanity needs to maintain fast query response times across all projects. The limit helps ensure that queries remain performant and don't exceed the 1-minute maximum execution time.

2. Working Set Management: The system has a maximum working set of 500 MB that can be retrieved from the data backend per query. Very large datasets can make it challenging to maintain this performance characteristic.

3. Infrastructure Efficiency: Having reasonable limits allows Sanity to optimize their infrastructure for the typical use case while maintaining reliability and speed.

Is 10 million actually limiting?

For most content management use cases, 10 million documents is quite generous. Consider that:

• A blog with 100 posts per day for 10 years = ~365,000 documents
• An e-commerce site with 100,000 products, each with 10 variants = 1.1 million documents
• Most content-heavy sites stay well under this limit

What if you need more?

If you're an enterprise customer and genuinely need more than 10 million documents, the documentation explicitly states that "customization possible for enterprise customers." You can contact Sanity to discuss your specific needs.

Other limits to be aware of:

While the document count limit is generous, you should also consider:

• Maximum document size: 32 MB
• Maximum total size of JSON documents: 10 GB
• Maximum unique attributes varies by plan (2,000 for Free, 10,000 for Growth, custom for Enterprise)

If you're concerned about hitting limits, it's worth reviewing your content architecture to ensure you're modeling your data efficiently!