New schema documents not appearing in localhost or sanity.io/manage

23 replies
Last updated: Nov 29, 2025
I tried to add a a few new documents to the schema. I also added new types to the existing documents on my schema. The existing documents updated on the localhost:3333 studio but did not update on the sanity.io/manage site. Also, the new documents added did not update on the localhost nor on the sanity.io/manage site. I have imported them in the schema.js file as shown in the image but am not understanding why the new documents are not updating, image below for one new document created, both on the localhost and on the sanity.io/manage site? Any thoughts?
AI Update

Based on your description, I think there's some confusion about where you should see your schema changes. Let me clarify:

Important: The sanity.io/manage site is your project management dashboard - it's not your actual Studio where you edit content. You won't see your schema changes there. That's just for managing projects, datasets, team members, and billing.

Your actual content Studio is:

  • Running locally at localhost:3333 (dev environment)
  • OR deployed to a URL like yourproject.sanity.studio (production)

Why your new document types aren't showing up:

Since you mentioned you've imported them in schema.js, here are the most common issues:

1. Check your sanity.config.js file

Your schema needs to be registered in your sanity.config.js (or .ts) file, not just imported in a schema file. It should look something like this:

import { defineConfig } from 'sanity'
import { structureTool } from 'sanity/structure'
import { schemaTypes } from './schemas'

export default defineConfig({
  name: 'default',
  title: 'My Project',
  projectId: 'your-project-id',
  dataset: 'production',
  
  plugins: [structureTool()],
  
  schema: {
    types: schemaTypes, // Your schemas need to be here
  },
})

2. Restart your dev server

After adding new document types, you must restart your local Studio:

  • Stop your dev server (Ctrl+C)
  • Run sanity dev (or npm run dev) again

Schema changes don't always hot-reload properly.

3. Check for errors

Look at your terminal/console where you're running the Studio. Any schema validation errors will show up there and prevent types from loading. Common issues:

  • Syntax errors in your schema files
  • Missing required fields (like name or type)
  • Circular dependencies between schema types

4. Verify your schema exports

If you have a separate schema file, make sure you're properly exporting all types:

// schemas/index.js
import myNewDocument from './myNewDocument'
import anotherNewDocument from './anotherNewDocument'

export const schemaTypes = [
  myNewDocument,
  anotherNewDocument,
  // ... other existing types
]

About deployed Studios:

If you have a deployed Studio (using sanity deploy), you need to rebuild and redeploy to see schema changes there:

sanity deploy

The auto-updates feature only handles Sanity framework version updates - it doesn't automatically sync your custom schema changes.

Quick checklist:

  1. ✅ Schema types are exported from your schema file
  2. ✅ Schema types are registered in sanity.config.js under schema.types
  3. ✅ Dev server has been restarted
  4. ✅ No errors in the terminal/console
  5. ✅ Run sanity deploy to update your production Studio

If you're still stuck after checking these, share any error messages from your console - that'll help pinpoint the exact issue!

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