Spell checking not working in Portable Text Editor (PTE) in Sanity v2.27

5 replies
Last updated: Jan 27, 2026
Hi, from what I see in the doc , the PTE should allow spell checking. But from what I have in my studio that's not the case.Spell check is working in
text
fields.I'm working with v.2.27 of Sanity.
AI Update

You're right that spellchecking should work in the Portable Text Editor - and it does support it! The issue you're experiencing in Sanity Studio v2.27 is likely because spellcheck needs to be explicitly enabled in your schema configuration.

The Portable Text Editor does support spellchecking through the spellCheck option on the block type. While this option defaults to true, there have been cases in Studio v2 where it needs to be explicitly set to work properly.

Here's how to fix it - add the spellCheck option to your block type's options object:

{
  title: 'Content',
  name: 'content',
  type: 'array',
  of: [
    {
      type: 'block',
      options: {
        spellCheck: true
      }
    }
  ]
}

The key is placing spellCheck: true inside the options object at the block type level. This is a Boolean option that explicitly enables spellchecking in the Portable Text Editor.

After updating your schema with this configuration, restart your Studio development server. The spellcheck functionality should then work in your Portable Text fields just like it does in your regular text fields.

If you're still experiencing issues after adding this, double-check that:

  • The option is nested correctly within the options object
  • Your browser's spellcheck isn't disabled globally
  • You've fully restarted the Studio (not just refreshed the page)

This should resolve the spellcheck issue you're seeing in Studio v2.27's Portable Text Editor.

Show original thread
5 replies

Sanity – Build the way you think, not the way your CMS thinks

Sanity is the developer-first content operating system that gives you complete control. Schema-as-code, GROQ queries, and real-time APIs mean no more workarounds or waiting for deployments. Free to start, scale as you grow.

Was this answer helpful?