
TL;DR
- Sanity CMS pricing has three tiers: a Free plan for up to 20 users, a Growth plan at $15 per seat per month with metered overages, and custom-priced Enterprise contracts.
- On a typical marketing site, seats are the main cost, and the Viewer role is free, so stakeholders who only read and review content do not need a paid seat.
- Growth meters usage beyond its quotas at $1 per 25,000 API requests, $1 per 250,000 API CDN requests, $0.50 per GB of assets and $0.30 per GB of bandwidth.
- Queries sent through the API CDN cost a tenth of the live API rate, and a cached frontend with Next.js revalidation keeps both counts low as traffic grows.
- The increased quota add-on costs $299 a month and raises documents to 50,000, while Enterprise adds SSO, custom roles, dataset hot swap and cross-dataset references.
- Total cost of ownership adds the subscription, metered usage, frontend hosting, implementation and maintenance over two to five years.
What you actually pay for Sanity depends on seats, API traffic, documents and bandwidth. On most marketing sites the bill is the seat count, and two decisions keep it there: which people get a paid seat, and whether the frontend reads content through a cache.
Sanity pricing at a glance
The table summarizes the published limits on Sanity’s pricing page as of October 2026. Check the page before you budget, because limits and rates change. Self-serve plans are billed monthly only; annual billing is available on Enterprise.
| Item | Free | Growth | Enterprise |
| Price | $0 | $15 per seat per month | Custom contract |
| Seats | Up to 20 | Up to 50 | Custom |
| Datasets | 2, public only | 2, private or public | Custom |
| Documents | 10,000 | 25,000 | Custom |
| API requests per month | 250,000 | 250,000 | Custom |
| API CDN requests per month | 1 million | 1 million | Custom |
| Assets and bandwidth | 100 GB each | 100 GB each | Custom |
| Roles | 2 (Administrator, Viewer) | 5 (Administrator, Viewer, Editor, Developer, Contributor) | Custom roles and access control |
| Overages | None, usage stops at the limit | Metered, pay as you go | Custom |
How Sanity CMS pricing works
Sanity’s pricing is a hybrid model: a subscription tier plus usage-based billing. Sanity runs the Content Lake, the hosted database behind every project, so you do not manage backend infrastructure. You pay a baseline set by your plan and seat count, and on Growth, usage above the plan’s quotas adds metered charges.
Four levers drive the bill:
- User seats: Every account that writes, edits or publishes content in Sanity Studio. Users with the Viewer role do not take a paid seat.
- API requests: Read and write queries against the Content Lake through GROQ or GraphQL, counted separately for requests served through Sanity’s API CDN and requests sent to the live API.
- Documents: Every record in your datasets, including drafts and language versions.
- Assets and bandwidth: Stored media and the data transferred when images and files are served to your frontend.
Building with Next.js & Sanity? Know your total spend upfront.
What does the Sanity Free plan include?
The Sanity Free plan is a permanent plan rather than a trial, and it needs no credit card. It includes hosted infrastructure, real-time editing in Sanity Studio, GROQ and GraphQL APIs, and Sanity’s Content Agent, within these limits:
- Seats: Up to 20 users, with two roles, Administrator and Viewer.
- Documents: Up to 10,000, enough for a company blog or a marketing site.
- API traffic: 250,000 API requests and 1 million API CDN requests per month.
- Assets and bandwidth: 100 GB of asset storage and 100 GB of monthly bandwidth.
- Datasets: Two public datasets, usually production and staging.
Two limits matter before you launch something client-facing. The Free plan has no pay-as-you-go overages, so usage beyond a quota means upgrading to Growth. And both datasets are public: anyone can read their content without a token, so confidential content belongs on a paid plan with private datasets.
Sanity Growth plan costs and limits
Teams move to Growth when they need more editors, private datasets or more than the Free quotas. It costs $15 per seat per month for up to 50 seats, so a team of eight pays $120 a month and a team of 40 pays $600 a month before usage. Growth adds three more roles (Editor, Developer and Contributor) and lets both datasets be private.
The base quotas match the Free plan, except documents, which rise to 25,000. Beyond them, Growth meters usage instead of cutting off service. The published rates are:
- Extra API requests: $1 per 25,000.
- Extra API CDN requests: $1 per 250,000.
- Extra asset storage: $0.50 per GB.
- Extra bandwidth: $0.30 per GB.
Three add-ons cover larger projects. The increased quota add-on costs $299 a month and raises documents to 50,000, API CDN requests to 5 million, API requests to 1 million, and assets and bandwidth to 500 GB each. An extra dataset costs $999 a month, up to two. Dedicated Support costs $799 a month and gives direct technical support from Sanity’s support engineers without an Enterprise contract.
Growth also meters newer platform features above their monthly allowances: Sanity Functions at $1 per million invocations beyond the 500,000 included, compute at $1 per 20,000 GB-seconds beyond the 20,000 included, embeddings queries at $1.50 per 1,000 above the 1,000 included, and extra agent actions at $0.05 each. If your build uses Functions, semantic search or AI agents, add these lines to the budget.
Sanity Enterprise pricing and contracts
Sanity does not publish Enterprise prices; contracts are negotiated with Sanity’s sales team and depend on your seats, usage, datasets and support needs. What Enterprise adds is governance and scale rather than higher quotas alone:
- Single sign-on: SAML SSO is available on Enterprise only.
- Custom roles and access control: Roles beyond the five standard ones, and permissions scoped to specific documents or content types.
- Dataset hot swap: Switching which dataset serves production, for zero-downtime content migrations.
- Cross-dataset references: Content in one dataset can reference content in another, for shared content across brands or sites.
- SLA, support and AI credits: An uptime SLA, which no self-serve plan offers, dedicated support included rather than bought as an add-on, and 5,000 AI credits a month against 1,000 on Free and Growth. Growth charges $0.05 per extra AI credit; Free offers no extra credits.
Which factors drive Sanity CMS costs?
The headline rate is the predictable part of the bill. The rest depends on how many people use the Studio, how the frontend fetches content, and how much content you store.
Seats and editorial roles
On a typical marketing site, seats are the main cost, because traffic stays inside the quotas. Each translator, writer or reviewer who needs Studio access adds $15 a month on Growth. Decide early who needs a paid seat at all: on Sanity’s pricing, the Viewer role is free, so stakeholders who only read and review content can join as Viewers.
Frontend architecture and caching
Sanity is a headless backend, so every page the frontend renders may query the Content Lake. Two layers decide how many of those queries you pay for, and at which rate:
- Sanity’s API CDN: Queries sent through the API CDN (the
useCdnoption in Sanity’s client) count as API CDN requests, at $1 per 250,000 on Growth. Sanity recommends the CDN for content fetched from the browser, so client-side fetching on its own does not mean expensive requests. - The live API: Mutations, listeners and the Live Content API always go to the live API, as does any client set to
useCdn: false. These count as API requests, at $1 per 25,000, ten times the CDN rate. - Your frontend’s cache: On Vercel, Next.js static generation with on-demand revalidation (
revalidateTagorrevalidatePath, triggered by a Sanity webhook) rebuilds a cached page only when its content changes, so most visits never reach Sanity and both request counts stay low as traffic grows. - Live preview: Real-time preview keeps live connections open while editors work; Sanity’s plans include 1,000 live connections per dataset.
A cached frontend separates public traffic from Sanity usage, so a campaign spike raises hosting traffic rather than metered requests. For the hosting side of the same frontend, see the guide to Vercel hosting costs.
Documents, drafts and datasets
Every draft, language version and imported record counts as a document, and a second dataset for staging copies the content again. Sites that import large feeds or keep many locales reach the 25,000-document Growth quota sooner than their page count suggests, which is the point where the $299 add-on applies.
Large content estates do run on Sanity: Pagepro moved GP Notebook, a medical reference platform with more than 100,000 subpages used by UK GPs, from a legacy custom CMS to Next.js and Sanity, and its editorial team now publishes without developer help, which the case study credits with lowering content-management costs. At that scale, check the document quotas and the Enterprise threshold before you choose a plan.
Implementation and custom development
Sanity runs the database, backups and infrastructure, but it ships no frontend or templates. Your developers design the content schemas, configure Sanity Studio and build the public site, so implementation is usually the largest cost in the first year (the part a Sanity development agency quotes for), and it depends on scope rather than on the Sanity plan.
A good build also lowers the running cost. On the Darktools rebuild Pagepro delivered on Next.js and Sanity, editors manage pages with a page builder and live preview without a developer, so routine content changes stay off the development budget.
Worked Sanity cost examples
These examples use the published rates as of October 2026. They cover the Sanity subscription and usage only; implementation and frontend hosting come on top.
- Marketing site, 8 editors, cached frontend: 8 seats at $15 is $120 a month, with traffic, documents and bandwidth inside the Growth quotas, so the bill stays at $120.
- Content-heavy site, 8 editors, 60,000 documents: The $299 increased quota add-on covers up to 50,000 documents, so this site exceeds even the add-on. Either archive old drafts and imports to get below 50,000 and pay $419 a month ($120 for seats plus $299), or move to an Enterprise contract.
- Frontend that bypasses the API CDN, 8 editors, 1.25 million API requests above the quota: $120 for seats plus $50 in API overage at $1 per 25,000 requests. Sent through the API CDN, the same 1.25 million requests would cost $5 at $1 per 250,000, and a cached frontend would remove most of them.
Sanity vs other headless CMS pricing
Headless CMS vendors price in different ways: per seat, per space, per project or by license. The entry points below come from each vendor’s pricing page as of October 2026.
| CMS | Free tier | First paid plan | Pricing model |
| Sanity | Up to 20 users | $15 per seat per month (Growth) | Per seat, plus metered usage |
| Contentful | Up to 10 users, 100,000 API calls with no overages | $300 per month (Lite, 20 users) | Packaged plans |
| Storyblok | Starter plan | $99 per month per space (Growth) | Per space |
| Strapi | Community Edition, free under the MIT licence (self-hosted) | Strapi Cloud from $35 per project per month | Per project, or self-hosted |
| Payload | Free under the MIT licence (self-hosted) | Enterprise, priced on request | Self-hosted, plus an Enterprise tier |
| Hygraph | Hobby plan | $199 per month (Growth) | Packaged plans |
| Directus | Free to self-host for organizations under $5M revenue and 50 employees | Team at $499 per month, billed annually | License tiers, plus optional cloud hosting |
Sanity vs Contentful pricing
At the entry level, Sanity is cheaper for small teams: its Free plan allows 20 users against Contentful’s 10, and its paid plan starts at $15 per seat against Contentful’s $300 Lite plan. The models diverge as you grow. Sanity meters extra usage on Growth, while Contentful’s Free plan stops at its API and bandwidth limits with no overages. In editor-heavy teams, Sanity’s per-seat cost grows with every user, which narrows the gap. For the full comparison beyond price, see Sanity vs Contentful.
Sanity vs Strapi and Payload
Strapi’s Community Edition and Payload are free, open source and self-hosted, so their licence cost is zero and their real cost moves to hosting and developer time. Strapi Cloud starts at $35 per project per month for teams that want it managed. Sanity removes the server work but charges per seat. For a code-level comparison of the two approaches, see Payload vs Sanity.
Self-hosted vs managed headless CMS costs
A self-hosted CMS drops the subscription but moves three costs to your team:
- Infrastructure: Compute, a database, object storage and a CDN, which a managed platform bundles into its tiers.
- Operations: Version upgrades, backups, security patches and incident response, which need someone on your team or a support retainer.
- Scaling: Handling traffic spikes and database growth, which a managed vendor absorbs.
Whether self-hosting saves money depends on how many hours those tasks take your team each month, multiplied by its hourly cost. For a single site, compare that figure with the Growth bill from the worked examples; for an agency spreading one server setup across many client sites, the hours are shared, and the balance can tip toward self-hosting.
Skip the pricing guesswork. Get an unbiased estimate from Pagepro.
How to calculate total cost of ownership
The total cost of ownership of a headless CMS adds five lines over two to five years: the subscription, metered usage, frontend hosting, implementation, and ongoing maintenance. Model each one at today’s traffic and at a traffic spike, because usage costs do not scale in a straight line. For a Next.js frontend on Vercel, model the hosting line with the Vercel hosting costs guide: the same caching that keeps Sanity requests low also keeps Vercel function and bandwidth usage down.
Implementation and migration costs
Moving from another CMS adds a migration project on top of the build. It covers auditing and mapping content, migration scripts, quality assurance, redirects and launch. The redirect and SEO work deserves its own line in the budget, because losing rankings costs more than protecting them; the step-by-step CMS migration guide covers what that work includes.
Exit costs
Budget for leaving as well as arriving. Sanity content exports with the sanity datasets export CLI command as a gzipped archive: every document as NDJSON, plus your images and files. GROQ queries, Portable Text rendering and Studio customizations are written for Sanity, though, so a future move means rewriting them. Keeping queries and content mapping in a thin data layer in your Next.js code keeps that cost low.
The TCO decision threshold
A move to Sanity pays off when your current CMS costs more, over three to five years, than the migration plus running the new platform for the same period. Include the engineering time you spend today on maintenance and workarounds, because that is often the largest line on the current side.
Which Sanity plan should you choose?
Start on the Free plan, model your content and test roles, previews and workflows before you pay. Then choose by the first limit you hit:
- Stay on Free: Prototypes, side projects and small sites with up to 20 users, public content and traffic inside the quotas.
- Move to Growth: Commercial sites that need private datasets, editor and contributor roles, more than 10,000 documents, or metered overages instead of a hard stop.
- Talk to Sanity about Enterprise: Organizations that need SSO, custom roles, cross-dataset references, dataset hot swap or an uptime SLA.
To see what Sanity would look like on your own content before you commit, Pagepro offers to rebuild part of your website with your real content in 48 hours, with no cost and no commitment.
FAQ
Yes. Sanity’s Free plan is permanent, needs no credit card and includes up to 20 users, 10,000 documents, 250,000 API requests and 1 million API CDN requests a month. Its two datasets are public, so confidential content needs a paid plan.
Sanity Growth costs $15 per seat per month for up to 50 seats, billed monthly. A team of eight pays $120 a month before usage, users with the Viewer role are free, and metered overages apply only above the plan’s quotas.
The Free plan has no pay-as-you-go overages, so once a project needs more than its quotas you move to Growth, which meters extra API requests, CDN requests, assets and bandwidth instead of stopping service.
Because the bill combines seats with usage. Two teams on the same plan pay differently when one has more editors, more documents and language versions, or a frontend that sends every visit to Sanity’s live API instead of serving cached pages.
Serve pages from a cache and rebuild them only when content changes, for example with Next.js revalidation triggered by a Sanity webhook. Send read queries through Sanity’s API CDN, which costs a tenth of the live API rate on Growth, and keep the live API for mutations, listeners and preview.
Strapi’s Community Edition is free to self-host, so its cost is hosting and developer time; Strapi Cloud starts at $35 per project per month. Sanity charges $15 per seat but runs the infrastructure. Which is cheaper depends on how many editors you have and how many hours your team would spend running Strapi.
Add five lines over two to five years: subscription, metered usage, frontend hosting, implementation and maintenance. Model them at current traffic and at a spike, and include migration and redirect work if you are moving from another CMS.
