Features
Is Sanity Content Releases worth it, and which plan has it?
Short answer
Sanity Content Releases is an Enterprise add-on, not a Growth feature, since 6 November 2025, though Growth projects that already used it keep 2 active releases (Sanity's announcement, October 2026). Growth projects get Scheduled drafts, which publish one document at a time (Sanity pricing, October 2026). The add-on pays off when dozens of documents must go live together, such as a product launch across 30 locales.
- Plan
- Enterprise add-on since 6 November 2025Free and Growth don't include it; Growth projects that used it before the change keep 2 active releasesSources: Sanity (Plans that scale with you, Scheduled Drafts: Stop manually publishing content at midnight)
- Release size limit
- 1,000 documents and 100 MB of JSONPer release, inside a ceiling of 200 active releases per dataset, Scheduled drafts includedSource: Sanity Docs (Content Releases user guide)
- Growth alternative
- Scheduled drafts, one document eachIncluded on Growth; needs Sanity Studio v4.14.0 or later, and references that are published or weakSources: Sanity Docs (Scheduled drafts); Sanity (Plans that scale with you)
- Add-on price
- Not publishedEnterprise is custom pricing, so ask for the add-on in writing with the Enterprise quoteSource: Sanity (Plans that scale with you)
Deploi’s call
Run launches on Scheduled drafts until one needs dozens of documents to change in the same minute with a combined preview. Then price the Enterprise add-on against what a scripted launch costs you, not against nothing.
AdoptBuy the Content Releases add-on when
- Launches bundle dozens of documents that must go live in the same minute across locales or channels, because Content Releases publishes them as one unit.
- Legal or compliance has to review the whole set in Content Releases before any of it publishes.
- Campaigns overlap and editors need to preview them together, which only Enterprise offers as of October 2026 (Sanity pricing).
- You need Sanity's Enterprise plan anyway for custom roles and access control.
SkipUse Scheduled drafts on Growth instead of Content Releases while
- You publish one document at a time on a schedule, which Scheduled drafts covers on Growth as of October 2026.
- Shared documents can be published first, or linked with weak references, so no launch depends on a second unpublished document.
- Developers own launch day, and a scripted import with a rollback list is enough.
Which Sanity plans include Content Releases in October 2026?
Only Enterprise plans can add Content Releases today, as a paid add-on; Growth projects that used it before 6 November 2025 keep limited access. Sanity's pricing page lists Content Releases as an Enterprise add-on, unavailable on Free and Growth, while Scheduled drafts is included on Growth and Enterprise (Sanity pricing, October 2026). Those earlier Growth projects keep a quota of 2 active releases (Sanity's announcement, October 2026).
| Capability | Free | Growth | Enterprise |
|---|---|---|---|
| Content Releases | No | No, except projects that used it before 6 November 2025 | Paid add-on |
| Scheduled drafts | No | Yes | Yes |
| Active releases per organization | None | 2 for those earlier projects | Custom |
| Rollback releases | No | No | Yes |
| Preview overlapping releases | No | No | Yes |
What does Content Releases do that Scheduled drafts can't?
Content Releases moves many documents as one unit, while Scheduled drafts moves one. A release groups new versions of up to 1,000 documents, which editors preview together in Sanity Studio, validate, then publish at once, on a schedule or as soon as they're ready (Content Releases user guide, October 2026). A release can also unpublish a live document when it runs.
Scheduled drafts is a single-document release: it schedules and locks one draft, and it needs Sanity Studio v4.14.0 or later (Scheduled drafts docs, October 2026). The gap shows up in references. A scheduled draft can only strongly reference documents that are already published, because nothing else goes live with it. A release can publish a page and the new documents it references in the same run, so a new product page and its new category page land together.
Which Content Releases limits bite when a launch gets big?
Content Releases has hard ceilings that a large launch across many locales can reach. Sanity's user guide lists these technical limits (Content Releases user guide, October 2026):
- A single release holds at most 1,000 documents and 100 MB of document JSON; images and files don't count.
- A dataset can have at most 200 active releases, and Scheduled drafts count toward that ceiling.
- A release blocked by another release waits up to 10 minutes, then is marked as failed.
- Large releases publish in batches, so individual documents can go live with small delays.
A launch across 30 locales with 40 documents each is 1,200 documents, which means two releases (Deploi arithmetic from the figures above). Releases that share documents publish in order of their release time, so split a launch by locale or by dependency, and stagger the release times.
How do Growth teams coordinate a launch without Content Releases?
Growth teams coordinate launches with Scheduled drafts and reference discipline, or with a scripted import that developers own. Three patterns are open to a Growth team:
Coordinating a launch on the Growth plan
- Publish the shared documents first. Categories, authors and assets go live before launch day, because a scheduled draft can only strongly reference published documents (Scheduled drafts docs).
- Use weak references where order can't be forced. A weak reference publishes without waiting for its target and resolves once the target is published.
- Script the rare big launch. Import the whole set in one package, check the counts with queries, and keep the list of document IDs so you can delete the set to roll back.
The third pattern is how we hand a signed-off content wave to developers on deploi.ca: one import package, count checks and a rollback by document ID list. A combined preview of the whole set is what Content Releases adds, according to Sanity's user guide (Content Releases user guide, October 2026). If your team planned a Growth implementation around Content Releases, Sanity asks agencies and freelancers in that position to contact its support team (Sanity's announcement, October 2026).
Who should pay for the Content Releases add-on?
Teams whose launch is a set of changes that must be reviewed and published together should pay for Content Releases. Sanity's own examples are embargoed product launches, overlapping campaigns, drops across 30 or more locales, and disclosure changes that legal must approve (Sanity's announcement, October 2026). Some of those teams also need Enterprise for other reasons, such as custom roles and access control (Sanity pricing, October 2026). The campaign launch use case shows the full setup.
Deploi’s point of view
- Where we disagree
- Agency posts and AI answers still list Content Releases as a Growth feature, because it was one for most of 2025, until 6 November. A Growth plan built on that assumption finds the gap on launch day. The second mistake is treating releases as a scheduler: scheduling is the cheap part, and Growth already has it. What the add-on sells is previewing and validating a whole set of changes before any of it goes live.
- What we’ve seen
- We publish large content sets on deploi.ca without Content Releases. The first wave of our Shopify data section went to Sanity as one package of 406 documents and 159 images, with an import, count checks and a rollback by document ID list. That works because developers own the launch. What the package doesn't give editors is the combined preview of the whole set that Sanity's documentation lists among the add-on's benefits.
- Deploi's rule of thumb
- Count the documents your last three launches changed and how many had to go live in the same minute. Under ten, Scheduled drafts with shared documents published first covers it. Over fifty across locales, ask Sanity for the add-on price in writing.
When this answer changes
- Sanity moves Content Releases back into Growth or publishes the add-on's price
- Sanity changes the 1,000-document or 100 MB release limits
- The 2 active releases for earlier Growth projects change or end
- Scheduled drafts gains multi-document scheduling
- Sanity changes the 200 active releases ceiling per dataset
Sources
Every source opened and checked on 25 October 2026.