Type something to search...
How Sanity Pricing Works: Free vs Growth vs Enterprise

How Sanity Pricing Works: Free vs Growth vs Enterprise

Sanity pricing has three plans. The Free plan costs nothing, includes up to 20 user seats, two public datasets and fixed monthly quotas for documents, API requests, bandwidth and assets, with no way to pay for more. The Growth plan costs $15 per seat per month, adds private datasets, more user roles, comments, tasks, scheduled drafts and longer history, and lets you pay for usage beyond the included quotas. Enterprise has custom pricing and adds features such as SSO, custom roles, content releases, an uptime SLA and dedicated support. Your bill depends mainly on how many editing seats you need and how much API traffic your site generates.

Sanity's pricing is simple at the top level but has a lot of detail underneath, and the details are what decide whether you'll stay free or pay. This guide explains each plan, the quotas that matter, how overages work, which features are plan-gated, how to estimate your monthly cost and how to keep usage down. Figures are taken from Sanity's pricing page in November 2026. Pricing changes from time to time, so always check sanity.io/pricing before making a decision.

The Three Plans at a Glance

FreeGrowthEnterprise
Price$0$15 per seat / monthCustom
User seatsUp to 20Up to 50Custom
Roles2 (Administrator, Viewer)5 (Administrator, Editor, Developer, Contributor, Viewer)Custom roles
Datasets2, public only2, public or privateCustom
Documents10,00025,000Custom
API requests / month250,000250,000Custom
API CDN requests / month1,000,0001,000,000Custom
Bandwidth / month100 GB100 GBCustom
Asset storage100 GB100 GBCustom
Pay for overagesNoYesCustom
SupportCommunityCommunity (paid add-on available)Dedicated, with SLA

Two things stand out. First, the Free and Growth plans share the same traffic quotas. You don't upgrade to Growth for more requests; you upgrade for collaboration features, private datasets and the ability to pay for overages. Second, Growth is priced per seat, so the number of people who edit content drives the base cost.

What Counts as a Seat

A seat is a user with access to your project. On the Free plan you can invite up to 20 people at no cost, but you can't buy more. On Growth, you pay $15 a month for each seat, up to 50.

Users with the Viewer role don't consume a seat on any plan. That's useful for stakeholders who only need to read content or review drafts. API tokens used by your website and scripts aren't seats either.

The Free Plan

The Free plan is genuinely usable for production, not just a trial. It includes:

  • Sanity Studio and hosting on a *.sanity.studio URL.
  • Two public datasets, typically production and staging.
  • Up to 20 users, as Administrators or Viewers.
  • 10,000 documents, which is plenty for most blogs and marketing sites.
  • 250,000 API requests and 1 million API CDN requests a month.
  • 100 GB of bandwidth and 100 GB of asset storage.
  • Two GROQ-powered webhooks, enough to trigger site rebuilds.
  • Visual Editing and the Presentation tool.
  • The Live Content API, with a limited number of live connections per dataset.
  • Three days of draft history in the Studio's review changes view.

The main limitations are that every user is either an Administrator or a Viewer (no Editor role with restricted permissions), datasets must be public, there are no comments or tasks, and you can't pay to go over a quota.

Who the Free Plan Suits

  • Personal sites and blogs.
  • Small business marketing sites with one or two editors.
  • Prototypes, side projects and learning.
  • Agencies building a proof of concept before a client commits.

If you're just getting started, how to set up your first Sanity project gets you running on the Free plan in a few minutes.

The Growth Plan

Growth is aimed at teams. At $15 per seat per month, it adds:

  • Five roles: Administrator, Editor, Developer, Contributor and Viewer, so you can let writers create drafts without letting them change settings.
  • Private datasets: every read requires a token. Useful for internal content or gated material.
  • Comments and tasks: field-level discussion and assignments inside the Studio.
  • Scheduled drafts: publish a draft automatically at a set time.
  • AI Assist in the Studio.
  • Longer history: 90 days of draft history and an activity feed.
  • More documents (25,000) and more unique attributes per dataset.
  • Four GROQ-powered webhooks.
  • Pay-as-you-go overages for requests, bandwidth and assets.

Growth Overage Rates

When you exceed the included quotas on Growth, you pay for the extra:

ResourceOverage price
API requests$1 per 25,000
API CDN requests$1 per 250,000
Bandwidth$0.30 per GB
Asset storage$0.50 per GB

Notice that CDN requests are ten times cheaper than uncached API requests. That's a strong hint about how to build your front end, covered below.

Growth Add-ons

  • Increased quota ($299/month): raises the limits to 50,000 documents, 1 million API requests, 5 million CDN requests, 500 GB bandwidth and 500 GB assets.
  • Extra datasets ($999 per dataset): for teams that need more than two environments.
  • Dedicated support ($799/month): direct support beyond the community.

The Enterprise Plan

Enterprise is a negotiated contract with custom quotas and pricing. On top of everything in Growth, the pricing page lists:

  • Custom roles and fine-grained access control.
  • Single sign-on (SSO).
  • Content Releases: group changes across many documents and publish them together, with rollback and previews of overlapping releases.
  • Media Library as an add-on, for organisation-wide asset management.
  • A full audit trail and History API, with longer retention.
  • Advanced request logs.
  • An uptime SLA, dedicated support and an onboarding programme.
  • Invoice and organisation-level billing rather than card payments.

Enterprise makes sense for large organisations with many editors, compliance requirements, multiple brands or high traffic.

Features by Plan

FeatureFreeGrowthEnterprise
Visual Editing / Presentation toolYesYesYes
Live Content APIYesYesYes
Private datasetsNoYesYes
CommentsNoYesYes
TasksNoYesYes
Scheduled draftsNoYesYes
Content ReleasesNoNoYes
Custom rolesNoNoYes
SSONoNoYes
Uptime SLANoNoYes

Sanity also includes newer platform features, such as Functions (serverless code triggered by content changes), AI credits and embeddings queries, with monthly allowances on each plan. Those allowances change more often than the core quotas, so check the pricing page if you plan to use them heavily.

How to Estimate Your Monthly Cost

Start with seats, then check traffic.

  1. Count editing seats. Everyone who needs to create or edit content needs a seat. Read-only reviewers can be Viewers.
  2. Decide if you need Growth features. Roles, private datasets, comments, tasks and scheduled drafts are the usual triggers.
  3. Estimate API usage. Static or cached sites use very few requests. Sites that query Sanity on every page view use many.
  4. Add any overages or add-ons.

Some worked examples on Growth:

TeamSeatsBase costLikely overagesMonthly total
Small agency site3$45None with CDNAbout $45
Content team of 1010$150SmallAbout $150 to $170
Busy publisher, 25 editors25$375Depends on traffic; may need the Increased quota add-on$375 to $700+

If two people edit a static marketing site, the Free plan will usually be enough, and your only costs are front-end hosting and your domain.

What Uses Your API Quota

Every request to the Content Lake counts: front-end queries, Studio activity, scripts, exports and webhooks triggering builds that query content. The biggest factor is how your front end fetches data.

Front-end approachAPI usage
Static build, rebuilt on publishVery low: queries only run at build time
Incremental revalidation with tag-based cachingLow: queries run when content changes
Server rendering on every request, uncachedHigh: one or more queries per page view
Client-side fetching in the browserHighest: every visitor's browser queries the API

How to Keep Your Sanity Bill Down

  • Use the API CDN: set useCdn: true for public content. CDN requests have a four-times-larger free allowance and are ten times cheaper over the limit.
  • Cache on your side: use static generation or framework caching so pages don't query Sanity on every visit. In Next.js, next-sanity integrates with cache tags and revalidation.
  • Fetch what you need: a single GROQ query with projections and dereferencing replaces several requests. See GROQ projections.
  • Optimise images: request resized, modern-format images through URL parameters instead of full originals to reduce bandwidth. Optimise Sanity images explains how.
  • Use Viewer seats for people who only review.
  • Watch the usage dashboard at sanity.io/manage, which shows current usage against quotas.
// A client set up for cheap, cached public reads
import { createClient } from 'next-sanity'

export const client = createClient({
  projectId: process.env.NEXT_PUBLIC_SANITY_PROJECT_ID!,
  dataset: process.env.NEXT_PUBLIC_SANITY_DATASET!,
  apiVersion: '2026-10-01',
  useCdn: true,
})

The Content Lake explained post covers the difference between the live API and the CDN in more detail.

Trials and Special Programmes

  • Trials: new projects get paid features free for a limited period, so you can try Growth features before deciding. When a trial ends, private datasets revert to public, so upgrade first if that matters.
  • Startup programme: eligible early-stage startups can apply for a year of the Growth plan free.
  • Non-profit plan: eligible non-profit organisations can apply for discounted access.

How Sanity Pricing Compares

Most headless CMSs combine a free tier with per-seat or per-space pricing and usage limits, so Sanity isn't unusual. Its free tier is generous on seats and storage, and its Growth plan is relatively cheap per editor, while traffic overages make caching important. For detailed comparisons, see Sanity vs Contentful and Sanity vs Strapi, which also covers the self-hosted alternative.


FAQ: Sanity Pricing

Yes. The Free plan costs nothing, has no time limit and doesn't require a credit card. It includes up to 20 users, two public datasets and monthly quotas that are enough for many small production sites.

The Free plan doesn't offer paid overages, so you can't simply pay for extra usage. If you regularly go over the quotas, you'll need to reduce usage, for example by using the API CDN and caching, or upgrade to Growth, where overages are billed.

Growth costs $15 per seat per month, for up to 50 seats. Users with the Viewer role don't count as seats. You also pay for any usage beyond the included quotas and for optional add-ons.

No. Seats are only for people with user accounts on your project. Your website, scripts and API tokens don't use seats, though their requests do count toward your API quotas.

Private datasets require the Growth plan or above. On the Free plan, both datasets are public, which means published documents can be read without a token. Drafts remain private on every plan.

According to the current pricing page, Content Releases is listed as an Enterprise feature, while Growth includes scheduled drafts for publishing individual documents at a set time. Check the pricing page, as plan features change.


Conclusion

Sanity's pricing comes down to two questions: how many people need to edit content, and how much API traffic your site creates. The Free plan covers small teams with fixed quotas, Growth adds team features and pay-as-you-go overages at $15 per seat, and Enterprise is for organisations that need SSO, custom roles, releases and guaranteed support.

For most projects, traffic costs are under your control. Serve public content through the API CDN, cache pages in your framework and fetch only what each page needs, and your bill will mostly reflect the size of your editorial team rather than the size of your audience.

Tags :
Share :

Related Posts

Building a Static Site With Astro and Sanity

Building a Static Site With Astro and Sanity

To build a static site with Astro and Sanity, keep Astro's default output: 'static', configure @sanity/astro with useCdn: false, and fetch

Dive Deeper
Common Sanity Mistakes and How to Fix Them

Common Sanity Mistakes and How to Fix Them

The most common Sanity mistakes are using the CDN where you need fresh data, fetching whole documents with ..., leaving slugs unvalidated, ship

Dive Deeper
How to Create a Custom Sanity Plugin

How to Create a Custom Sanity Plugin

To create a custom Sanity plugin, wrap a piece of Studio configuration in definePlugin from the sanity package and add it to the plugins ar

Dive Deeper