Where a new CMS would help, and which platform does it better
Storyblok is stronger on visual editing, device preview and media folders. Sanity is stronger on image cropping and video. The remaining points, preview links, slice availability, SEO fields and governance, can be improved within Prismic as well. On AI, Sanity is the more AI-ready platform, and Storyblok shows AI-made pages most immediately.
Where a new CMS helps
Mobile and tablet design controls are limited
Storyblok aheadThe frustration is checking a page on mobile and tablet. Prismic's preview opens the site in a normal browser tab, so editors have to resize their window.
Prismic today
No device preview. Editors resize the browser or use developer tools.
Sanity
The Presentation tool shows the page next to the editing form, with a desktop/mobile toggle. There's no tablet size.
Storyblok
Editors work directly on the page. It has Desktop, Mobile and Full-width views, plus a slider for any width, including tablet. Device checks are part of normal editing.
Media library organization can get messy
Storyblok aheadThe frustration is the lack of folders, which leads to duplicates and lost assets across many contributors.
Prismic today
Tags and search only. Prismic decided not to offer folders.
Sanity
The standard library uses tags and metadata (through a widely used plugin). Folders arrived in 2026 in Sanity's separate Media Library, but only as a beta add-on for Enterprise plans.
Storyblok
Folders on every plan, plus tags, search and alt text stored on the asset itself.
Image cropping and crop ratios are limited
Sanity aheadThe frustration is control over crop position, focal points and different ratios for each layout and screen size.
Prismic today
A fixed crop for each layout that developers define ("responsive views"). No focal point, so other ratios crop from the centre.
Sanity
Each image placement has its own crop area and a "hotspot" the editor sets once. Every ratio, on every screen size, keeps that point in frame automatically. The same photo can be cropped differently on different pages.
Storyblok
A focal point the editor clicks on, which keeps the subject in frame when resized. Manual cropping happens in a separate image editor rather than per placement.
Video hosting and embed controls feel limited
Sanity aheadThe frustration is that editors manage video settings outside the CMS, which adds a QA step and makes pages inconsistent.
Prismic today
Embeds by link, with settings managed on YouTube. Background loops are uploaded as large files.
Sanity
An official Mux plugin lets editors upload video inside the CMS. Mux then creates the thumbnails, captions and sizes for each device automatically, so one workflow covers films and background loops.
Storyblok
Vimeo and YouTube embeds through apps. There's no official Mux integration, so in-CMS video upload would need a custom plugin.
Slice/module-based design can feel limiting
Both solve itThe frustration is that custom layouts and interactions push the team to Ceros embeds.
Prismic today
Slices can't contain other slices, so each new layout needs a new slice built by developers.
Sanity
Content structures can be designed for each type of story, such as a project case study or a sector page. Developers can build custom editing tools for bespoke interactive pieces. This is strongest for designed, structured experiences.
Storyblok
Blocks can be nested inside each other, so editors can put sections, columns and media together on the page themselves. This is strongest for editor-built layouts.
Small content changes can have unexpected layout impacts
Both solve itThe frustration is a longer headline, a different crop or an empty field breaking a layout, which only shows up in QA and mostly on mobile.
Prismic today
Very little field validation: no length limits and no truly required fields. Problems show up in preview.
Sanity
Detailed rules on any field, such as "headline under 60 characters" or "image required", shown as errors or soft warnings while typing. This prevents problems.
Storyblok
Required fields and length limits, and every edit appears live on the page while typing, at any device width. This reveals problems the moment they happen.
AI-friendly, and creating a page with AI
How well the content works with AI tools and agents, and how easily an editor can go from a prompt or a draft to a finished page.
Sanity aheadPrismic today
A copywriting assistant in the page builder drafts and rewrites text inside slices, and can bring in drafts from Notion or Google Docs. Its other AI tools are aimed at developers building slices, not at editors creating pages.
Sanity
Most AI-ready. In Canvas, an editor writes or co-writes a page freely with AI, and Sanity maps the text into the page structure as they go. Content Agent can create pages that follow the site's rules from a request in plain language. It only prepares changes for a person to approve and can't publish. AI Assist adds help on individual fields, such as alt text and translation. AI tools such as Claude can also work with the content directly through Sanity's MCP server.
Storyblok
Easiest to see the result. The AI Suite generates and rewrites text, writes alt text and SEO fields, and translates, all inside the visual editor. Storyblok Agents and the MCP server can build a page from existing blocks, and the editor sees it on the page straight away. FlowMotion, a paid add-on, automates multi-step AI workflows such as translate, review, then publish.
Verdict. Both let an editor create a page with AI. Sanity's content is the most structured and its AI tools are the most deeply integrated, so AI output is more reliable and easier to reuse across channels. Storyblok's advantage is visual: whatever AI produces appears on the page at once, at every device size. AI features and credits depend on the plan on both platforms.
Improvements possible in Prismic
These points depend on configuration and editorial process rather than on the platform itself. They would be addressed as part of any rebuild, and the same improvements can be made in Prismic.
Setup
Preview and staging links are inconsistent
Prismic's preview works reliably when it's connected correctly. Previews that break after a couple of clicks usually mean some pages, or some links, weren't connected to the preview session. That's a developer fix in the site code.
If NBBJ switches anyway, Storyblok makes this hardest to get wrong, because its preview is the editing screen.
Setup
Slices need to be enabled page by page
In Prismic, slices come from one shared library and are switched on per page type, not per page. Enabling them page by page means the site was set up with many separate page types. Merging them into a few shared types makes every slice available everywhere.
As the feedback notes, a developer can fix this up front.
Setup
SEO controls depend on developers
In any headless CMS, editors only see the fields developers create. Prismic can hold meta titles, descriptions, share images, canonical URLs, noindex settings and a list of redirects that editors manage. These just haven't been added. Alt text already exists on every Prismic image.
Sanity and Storyblok work the same way. Both need these fields set up too.
Process
Training and governance
Entry guidelines, naming rules, image specs and publishing workflows are needed on every platform, as the feedback says. A new CMS can enforce some rules through validation and roles, but it can't replace an editorial standard.
Sanity can build guidance into the editing screens. Storyblok is easier to learn from day one.
Why each one
Choose
Sanity
for a fully customizable editing environment, where the content model, field rules, editing screens and review steps are all built to order.
- Custom content structure. Each content type, such as projects, people, sectors and news, gets its own fields, relationships and validation rules.
- Best image control. Crop and hotspot for each placement, so architecture photography holds up at every ratio and screen size.
- Video inside the CMS. Upload once through the official Mux plugin, and get captions, thumbnails and sizes for every device automatically.
- Prevents mistakes. Field rules stop layout-breaking content before it's published.
- Most AI-ready. Write a page freely in Canvas and it becomes structured content. Content Agent prepares pages that follow the site's rules, for an editor to approve.
- No ceiling. The editing tools can be shaped around NBBJ's workflow, and bespoke modules can replace Ceros embeds.
Trade-offs
- Best with an ongoing development partner. The editing experience is only as good as what gets built.
- Device preview is limited to desktop and mobile.
- Media folders need an Enterprise add-on.
Choose
Storyblok
for a visual, on-page editing experience that works out of the box, with layouts editors assemble themselves.
- Edit on the page. Click any block on the live layout and change it. What editors see is what gets published.
- Every device while editing. Desktop, mobile, full width and any width in between, including tablet, without resizing the browser.
- Editors build layouts. Nested blocks let the team put sections together themselves, with less developer help.
- Organized media. Folders, tags and focal points on every plan.
- AI on the page. Generate text, alt text, SEO fields and translations inside the visual editor, and see AI-built pages instantly.
- Fast to learn. Most editors are comfortable within a day.
Trade-offs
- Less suited to heavily linked content, such as projects connected to people and sectors.
- No official in-CMS video upload. Video stays embedded from Vimeo or YouTube unless a custom plugin is built.
- Custom workflows and roles are on higher-priced plans.