# How are you handling Sanity dataset limits and document metering as your content grows?

Sanity Studio has been great for structured content: schema-driven UI updates, fast image transforms via URL params, hotspots for safer crops, and GROQ search that can find images by what’s in the frame. It’s also been easy to integrate with Next.js on Netlify and scripts hitting the API directly, and updating one description can flow everywhere. The hard parts for me are dataset limits (two included, then a big jump for a third), document metering shaping what I store, plus a GROQ gotcha that silently matched everything and schema changes that can arrive quietly. If you’ve hit these constraints, what patterns or workarounds have helped you most?

##### Post Metadata
- Posted at: 15 days ago
- Author title: --
- Net upvotes: 1



## Related Product
[Sanity](https://www.g2.com/products/sanity/reviews)

## Related Category
[Headless CMS](https://www.g2.com/categories/headless-cms)

## Related discussions
- [How well does Trello scale into a larger team?](https://www.g2.com/discussions/1-how-well-does-trello-scale-into-a-larger-team)
  - Posted at: over 13 years ago
  - Comments: 6
- [Can we please add a new section](https://www.g2.com/discussions/2-can-we-please-add-a-new-section)
  - Posted at: over 13 years ago
  - Comments: 0
- [Quantifiable benefits from implementing your CRM](https://www.g2.com/discussions/quantifiable-benefits-from-implementing-your-crm)
  - Posted at: over 13 years ago
  - Comments: 4


