Can't run Sanity Studio after recent changes

30 replies
Last updated: Jan 28, 2026
Hi, I wonder if anyone experienced the same issue? I can not recall when exactly it appeared but the last 2 days I could not run the studio. I have reinstalled node_modules but it has not solved the issue.
AI Update

I'd be happy to help you troubleshoot! Since you haven't mentioned the specific error message, I'll cover the most common issues that prevent Sanity Studio from starting:

Check Your Node.js Version

The most common issue lately is Node.js version compatibility. Sanity Studio v4 requires Node.js version 20 or higher. Check your version by running:

node -v

If you're on Node.js 18 or lower, you'll need to upgrade. Node.js 18 reached end-of-life in April 2024, which is why Studio v4 bumped the requirement.

Common Solutions

After checking your Node version, try these steps:

  1. Clear npm cache and reinstall:

    rm -rf node_modules
    npm cache clean --force
    npm install
  2. Clear Sanity cache:

    rm -rf .sanity
    npm run dev
  3. Update Sanity packages:

    npm update sanity @sanity/vision
  4. Check for port conflicts: If port 3333 is already in use, you might get startup errors. Try specifying a different port:

    npx sanity dev --port 3334

What Error Are You Seeing?

If none of these work, the specific error message would help narrow down the issue. Common errors include:

  • Build errors (often dependency-related)
  • Port conflicts
  • Schema validation errors
  • Authentication issues

If you can share the error message you're getting when you try to start the studio, that would help identify the exact problem. Also, if you're using a package manager like yarn or pnpm instead of npm, let us know as the commands would be slightly different.

Show original thread
30 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?