To promote safer and more intentional permission management, new DatoCMS projects will no longer generate a default full-access API token (i.e. one with both read and write permissions for all APIs).
Previously, new projects came with two tokens by default: a full-access token and a read-only token. From now on, only the read-only token will be created automatically. This change encourages users to explicitly define the scope of each token based on their specific needs.
🔒 Reminder: Existing projects still have this legacy token. If you’re using it, we strongly recommend ensuring it’s used only in trusted environments.
Starting May 14th, 2025, our legacy uploads batch operation endpoints — which have been deprecated for years — will be discontinued and will return error responses. Documentation for these endpoints can be found here:
If you're using any of these endpoints, please update your integration to use their replacements. Documentation for the current endpoints can be found here:
We’re introducing a unified fixed header across all CMS sections, ensuring a smoother, more predictable interface.
What’s New?
We’ve standardized the header behavior so that key navigation elements stay accessible at all times—no matter where you are in the CMS.
Fixed headers everywhere – The header now stays in place as you scroll.
Consistent UI patterns – The same styling, spacing, and interaction logic apply across all sections, reducing cognitive load.
Quick access to actions – Important buttons (like Save, Publish) remain within reach without unnecessary scrolling.
How Does It Work?
No setup is needed—just log in, and you’ll see the updated interface immediately!
Why Does It Matter?
This update eliminates inconsistencies, making the CMS more intuitive and reducing friction in your daily tasks. If you’ve ever lost time scrolling back up to access a button or felt disoriented by shifting layouts, this change will make navigation feel effortless.
With the release of the recent plugin its now possible to export JSON files of your models and blocks, and easily import them into another DatoCMS project.
To make it easier to get started with new projects and build out common schema models, we've released DatoCMS Recipes in the marketplace — a curated selection of ready-to-use models and blocks that you can import into your projects.
Simply choose a recipe, click install, choose which project you'd like it in, and we'll import the corresponding model with all blocks, relations, and plugins as required.
Want to create your own recipes? Install the plugin to export models and reimport them into another DatoCMS project!
Based on early feedback from the recent release of inline blocks for Structured Text fields, we're introducing a small but impactful update to how our Content Delivery API handles them.
Previously, inline blocks were included within the blocks GraphQL selector. With this update, they now have a dedicated inlineBlocks selector:
Before the update:
1
queryBefore{
2
blogPost {
3
content {
4
value
5
blocks {
6
__typename
7
...onBlockModelRecord{
8
title
9
}
10
...onInlineBlockModelRecord{
11
title
12
}
13
}
14
}
15
}
16
}
After the update:
1
queryAfter{
2
blogPost {
3
content {
4
value
5
blocks {
6
__typename
7
...onBlockModelRecord{
8
title
9
}
10
}
11
inlineBlocks {
12
__typename
13
...onInlineBlockModelRecord{
14
title
15
}
16
}
17
}
18
}
19
}
Why this change?
By separating inlineBlocks from blocks, developers gain more precise control over rich text content, making it easier to manage and render structured text accurately, especially when using TypeScript. This improvement enhances both flexibility and consistency when working with inline blocks in GraphQL queries.
We appreciate your feedback and will continue refining the experience to make content management even smoother! 🚀
We've recently rolled out the ability for enterprise customers to schedule frequent exports of their DatoCMS data to AWS S3 buckets.
While it's important to note that this is not an automatic backup & restore function, the Project Export feature allows Enterprise customers to export all content and assets from their DatoCMS project to their own AWS S3 bucket.
Here's some important considerations:
Not a Backup Solution: The export does not offer a one-click restoration process.
Primary Environment Only: Only the primary project environment is included in the export.
Automated and Scheduled: Exports occur on a predefined schedule, with a minimum frequency of once per month and a maximum of once per day.
AWS S3 Storage Required: Customers must configure their own S3 bucket to receive the exported data.
The exported data includes:
Schema Models: Fields and fieldsets.
Schema Blocks: Block definitions and fields.
Records: Current and published versions, including block records.
Uploads: Metadata and references for uploaded assets.
Project Settings: Locales, SEO settings, workflows, and installed plugins.
Asset Files: All uploaded files from the media area.
That being said, there's several existing methods for all users to ensure data integrity with some recommended DIY approaches to data exports, backups, and recovery options.
These include several options including Plugins, Scripts, and Environment clones. Refer to our docs on Available Export & Backup Options for more info.
Previously, the CMS displayed only the 30 most recent build events.
We have now improved this by providing options to view events from the past weeks, and to apply filters or custom ordering, while also updating the UI to align with the overall design of the CMS.
Content Management API Content Delivery API UI Improvement New
For quite some time now, you've asked for the ability to insert blocks as inline elements inside the Structured Text field. Actually, it's one of the most requested features on our forum.
Well, here we are 🎉
It's now possible to setup structured text fields and declare which blocks can be added as inline elements in the content.
What’s new? Stuctured text fields have a new setting that allows to select the types of block that can be used as inline element: that's very similar to what we already have for regular, stacked blocks.
Why does it matter? Inline blocks open infinite possibilities: from links with custom data to mentions, from hashtags to inline notes... Fantasy is the limit!
And that's just the beginning: Inline blocks can ALSO have structured text fields with inline blocks within: so you can nest blocks 🤯 (with the same limits you have on your plan for stacked blocks).
How do I enable it? Simply head over to any structured text field’s settings, locate the new "Allow adding Inline Blocks" in the “Validation” tab, and select the blocks you want to make available in the field.
API Changes
From the API perspective, the Dast changed a bit and it now supports inline blocks inside paragraphs and headers. You'll appreciate the difference, of course, only when you start using inline blocks: there's no impact on fields that keep using regular, stacked blocks.
We’ve been carrying around an issue for quite some time regarding how we manage SEO fallback data. Because the same fields used for internal previews—Title and Image Preview—are also used for SEO fallback data, it’s been causing confusion and often results in less-than-ideal search engine metadata.
To address this, we’re splitting the two settings and creating a dedicated “SEO Fallback” tab!
What’s new? We’re removing the overlap between “Presentation” fields and “SEO” fields. Now you can explicitly choose which fields feed into your SEO Title, Image, and Description. These are separate from the fields used for internal previews, giving you more granular control over how your content appears in search results.
Why does it matter? With dedicated SEO fields, you can optimize exactly how content appears on search engines—without affecting the quick, at-a-glance previews in the CMS. This ensures your internal workflow remains clear and uncluttered, while your SEO metadata stays fine-tuned for external audiences.
How do I enable it? Simply head over to any Model’s settings, locate the new “SEO” tab, and select the fields you want to use for SEO Title, Image, and Description.
We've introduced two new relationships on the item_type entity: presentation_title_field and presentation_image_field. These relationships are exclusively used for DatoCMS’s internal interface and preview functionality:
presentation_title_field supports fields of type: string, date, date_time, link, text, structured_text, color, lat_lon, integer, and float.
presentation_image_field supports fields of type: file, gallery, link, color, date, date_time, and lat_lon.
At the same time, the existing relationships — title_field, image_preview_field, and excerpt_field — are now dedicated solely to configuring SEO fallback settings. As a result:
title_field no longer accepts fields of type date, date_time, link, text, structured_text, or color. It now only supports string fields.
image_preview_field no longer accepts fields of type link or color. It now only supports file and gallery fields.
These changes only refine the accepted field types and do not affect functionality, as the previously accepted field types were already ignored for SEO purposes and if ie. a model had a date field set as title_field that field is now set as presentation_title_field.
We’ve heard from many of you that it’s tough to quickly grasp what’s inside each record or block at a glance when shown in preview mode —especially when those blocks or records lack text fields.
To address this, we’ve introduced a new approach to displaying previews across the entire CMS: inline blocks, link fields, and even the item index, all benefit from clearer at-a-glance content!
What's new?
First, we’ve aligned how the “Presentation” tab works for both models and blocks, letting you pick a Title preview field and an Image preview. And second, we introduced new field types that can be selected as title and/or preview fields:
Color fields show a handy swatch (with optional opacity);
Date/DateTime fields use a quick calendar icon and display the date itself;
Geolocation fields bring in a map preview;
Number fields can be used as title and show their integer or floating-point value.
How do I enable it? Just head to the “Presentation” tab in your model or block settings to choose your Title and Image preview fields. No extra steps required!
See it in action 👇
Color, Geolocation, and Date fields will also provide a much cleaner interface when set as Preview Fields.
Why does it matter?
This update makes it faster and clearer to see what’s inside each record or block at a glance. If you’ve ever found yourself repeatedly opening blocks just to check their contents, you’ll love these new previews!
