Does DatoCMS offer a free plan?

Yes, DatoCMS provides a free Developer Plan that includes 250,000 API requests, 100 GB CDN bandwidth, 2,000 content records, and 1 team member, suitable for small projects and evaluation.

What happens if I exceed the limits of my DatoCMS plan?

If you exceed the limits of your paid DatoCMS plan, you will incur overage charges for the additional usage. For the free Developer Plan, exceeding limits typically requires an upgrade to a paid plan.

Can I upgrade or downgrade my DatoCMS plan?

Yes, DatoCMS allows users to upgrade or downgrade their plans as their project needs change. This flexibility helps manage costs in line with actual resource consumption.

Does DatoCMS charge for image optimization and CDN?

Yes, CDN bandwidth for serving optimized images and other assets is a component of DatoCMS's usage-based pricing. Each plan includes a specific amount of CDN bandwidth, with overages charged separately.

How does DatoCMS pricing compare to Contentful or Storyblok?

DatoCMS's pricing model is similar to Contentful and Storyblok, featuring tiered plans based on usage metrics like API requests, bandwidth, and content records. Specific limits and pricing points vary, so a detailed comparison based on your project's expected usage is recommended.

Are there any hidden fees with DatoCMS?

DatoCMS aims for transparent pricing. All potential charges, including overage rates for exceeding plan limits, are typically detailed on their official pricing page. Reviewing their terms is recommended to understand all cost implications.

DatoCMS Pricing: Plans, Tiers, and Real-World Costs (2026)

Q: What are the main factors that determine DatoCMS pricing?

DatoCMS pricing is primarily determined by the number of API requests, CDN bandwidth consumed, total content records stored, the number of team members, and the number of locales supported.

Pricing overview

DatoCMS employs a tiered pricing structure designed to accommodate projects ranging from individual development to large-scale enterprise content operations. The model is primarily usage-based, with costs influenced by factors such as the number of API requests, CDN bandwidth consumed, total content records stored, and the size of the team requiring access. DatoCMS offers a free tier for developers, a mid-range plan for professional teams, and a customizable enterprise solution as detailed on their pricing page.

The core components driving cost include:

API Requests: The total number of requests made to the Content Delivery API (CDA) and Content Management API (CMA).
CDN Bandwidth: Data transferred via the global Content Delivery Network for serving optimized images and other assets.
Content Records: The total number of unique content entries stored within the CMS.
Team Members: The number of users with access to the DatoCMS administrative interface.
Locales: The number of language versions supported for content.

Each plan includes a set amount of these resources, with additional usage typically incurring overage charges. This approach allows users to scale their resource consumption as their project grows, paying for increased usage beyond the base plan limits.

Plans and tiers

DatoCMS offers three primary plans: Developer, Professional, and Scale. Each plan is structured to provide different levels of resources and features, catering to specific project requirements and team sizes. The following table provides a summary of the key differences and typical use cases for each tier based on DatoCMS's official pricing information.

Plan	Starting Monthly Price	Key Limits (Base)	Best For
Developer	Free	250,000 API requests/month 100 GB CDN bandwidth/month 2,000 content records 2 locales 1 team member	Personal projects, prototypes, small blogs, learning DatoCMS features.
Professional	€119 (approx. $128)	10,000,000 API requests/month 500 GB CDN bandwidth/month 50,000 content records 5 locales 5 team members	Small to medium-sized businesses, agencies, growing websites with moderate traffic.
Scale	€499 (approx. $538)	50,000,000 API requests/month 2 TB CDN bandwidth/month 250,000 content records 10 locales 15 team members	Large organizations, high-traffic applications, multi-brand content platforms.
Enterprise	Custom pricing	Custom limits and features	Global enterprises, highly complex content workflows, strict compliance needs.

All paid plans include features such as visual editing, image optimization, and global CDN. The Enterprise plan offers custom SLA, dedicated support, and advanced security features tailored to specific organizational requirements.

Free tier and limits

The DatoCMS Developer Plan is the designated free tier, suitable for individual developers, hobbyists, or those exploring the platform's capabilities. It provides a foundational set of resources for building small projects without incurring costs. Key limits for the Developer Plan include:

API Requests: 250,000 requests per month. This covers both content delivery and management operations.
CDN Bandwidth: 100 GB per month. This is sufficient for serving a moderate amount of images and assets.
Content Records: 2,000 content entries. This limit applies to all types of content, including pages, articles, products, and media assets.
Locales: 2 locales, allowing for content in two different languages or regional variations.
Team Members: 1 user, restricting access to a single administrator or developer.
Projects: Limited to 3 projects.

Exceeding these limits on the free plan typically prompts an upgrade to a paid plan. While the free tier is generous for development and testing, it is not designed for production applications with significant user traffic or extensive content libraries.

Real-world cost examples

Understanding DatoCMS pricing involves considering how usage translates into actual costs. Here are a few scenarios:

Scenario 1: Small Business Website

Project: A small business website with approximately 100 pages, a blog with 50 articles, and 200 product listings, requiring content in English and Spanish.
Traffic: Moderate, around 50,000 unique visitors per month, generating roughly 2,000,000 API requests and 150 GB of CDN bandwidth.
Team: 3 content editors and 1 developer.
Analysis: The Developer Plan (free) would be insufficient due to limits on content records, API requests, bandwidth, and team members. The Professional Plan offers 10,000,000 API requests, 500 GB bandwidth, 50,000 records, 5 locales, and 5 team members. This plan comfortably covers the requirements.
Estimated Cost: €119/month (Professional Plan) as listed on DatoCMS.

Scenario 2: E-commerce Platform

Project: An e-commerce platform with 5,000 product SKUs, 1,000 blog posts, and dynamic content for personalized user experiences, across 3 languages.
Traffic: High, with 500,000 unique visitors per month, resulting in approximately 30,000,000 API requests and 1.5 TB of CDN bandwidth due to high-resolution product images.
Team: 10 content managers, 2 developers, 1 marketing specialist.
Analysis: The Professional Plan would be exceeded in API requests, bandwidth, and team members. The Scale Plan provides 50,000,000 API requests, 2 TB bandwidth, 250,000 records, 10 locales, and 15 team members. This plan aligns well with the projected usage.
Estimated Cost: €499/month (Scale Plan) according to DatoCMS's pricing.

Scenario 3: Global Media Company

Project: A global media company managing news articles, video metadata, and editorial content across 15 regions and 8 languages, with millions of content entries.
Traffic: Very high, requiring hundreds of millions of API requests and multiple TBs of bandwidth monthly.
Team: 50+ users across various departments.
Analysis: Neither Professional nor Scale plans would suffice due to the sheer volume of content, API calls, bandwidth, and team size. This scenario requires the custom limits and support provided by the Enterprise Plan.
Estimated Cost: Custom quote from DatoCMS.

How the pricing compares

DatoCMS operates in a competitive headless CMS market, with alternatives like Contentful, Storyblok, and Sanity.io also offering tiered, usage-based pricing models. While direct price comparisons can be complex due to varying metrics and feature sets, a general overview can highlight differences.

Contentful: Similar to DatoCMS, Contentful uses a tiered approach (Free, Team, Premium, Enterprise) with costs tied to content types, entries, API calls, and bandwidth. Contentful's free tier is often cited as being more restrictive in terms of content types and API calls compared to DatoCMS's Developer Plan, though specific limits vary by product iteration. For example, Contentful's free tier typically allows 3 users and 1,000 records, which is less than DatoCMS's 2,000 records as outlined on Contentful's pricing page.
Storyblok: Storyblok also offers a free tier (Community), followed by Team, Business, and Enterprise plans. Their pricing often emphasizes visual editor capabilities and workflow features. Storyblok's free tier generally allows for unlimited users for non-commercial projects and 25,000 requests, which can be more generous for team collaboration but less for API volume than DatoCMS's free tier per Storyblok's pricing details.
Sanity.io: Sanity.io's pricing is consumption-based, with a free tier (Standard) that includes 100,000 API requests, 10 GB bandwidth, and 100,000 documents. Paid plans (Advanced, Enterprise) scale these limits. Sanity's free tier can be more generous for document count but less for API requests and bandwidth compared to DatoCMS's Developer Plan, depending on the project's specific needs. Sanity also charges for dataset storage and editor usage as described on Sanity.io's pricing page.

When evaluating pricing, it is important to consider not just the base price but also the overage charges, the specific resource limits included in each tier, and the features that are bundled. For instance, some platforms might offer more generous API limits but charge extra for image optimization or advanced publishing workflows, while others might bundle these features into higher-tier plans. Developers should assess their project's anticipated usage across all metrics (API calls, bandwidth, content records, users, locales) to determine the most cost-effective solution. The flexibility of a headless CMS often means that the total cost of ownership also includes integration efforts, which can be influenced by factors like robust API documentation and SDK availability, as supported by the DatoCMS documentation and its Content Delivery API reference.