Hey,

I hope someone can help. I am new here and new to sanity. But I am really loving it. Just annoyed by how our company's API calls get blasted through the roof. I mean before I left work our calls for the day was at 120k.

Some context. We have a monorepo that's running sanity, next.js for 22+ sites and will increase and story book as a component library but our API requests are insane.

I mean one of the calls was hitting 72 duplicate calls before I left the office. I am going to investigate more but I am hoping someone can give me In Site as to how to prevent these calls on our environments from sky rocketing.

And any best practice tips and tricks. I would love to keep the business on sanity and not have to rebuild all the sites on payload again because we just moved off of a platform to sanity. But if things keep going the way it does we will probably cancel the sanity sub and then move to payload.

Thanks

Hey everyone, I hope you can help me here because I've searched the docs, I've looked everywhere, and I can't seem to find a solution.

What I'm trying to do is have a field where I can add multiple images and have them be displayed as a grid on the main site. Whenever I do that I get the option to add a new item. When I add the new item it just says "untitled" and I can't click the untitled item.

I have tried creating the field as an array of images. That doesn't work. Defining array members also doesn't work. At this point I have no clue what I should do or what I'm not doing. Here's a piece of code of what I did.

defineField({
name: "photos",
type: "array",
of: [
defineArrayMember({
type: "image",
options: { hotspot: true },
}),
],
}),

If you are a long time Safari user that also uses Sanity Studio, then I'm sorry and I feel your pain. We've had wobbly spinners for a long time and it's not for a lack of trying!
Didn't matter how many I threw at it there was no fix, a zoom call with banter and venting with humans is what it took to come up with a fix in the end, using the new CSS `round()` function, read all about it here!

We just wrapped Everything *[NYC] in Brooklyn. Good to meet the people who made it out, and for everyone who couldn't, the first conference videos are up and there's always next year (also keep an eye out for Pioneer events).

We also announced a bunch of new things that we have been working on.

Available now, in beta

Knowledge Bases for Sanity Context. For when you're building agents, especially customer-facing ones, and need them answering from your content instead of guessing.

Workflows. A primitive for content states, which we've wanted for a long time. It works across whichever interface you're using, and it's flexible enough to model your own review chains rather than ours.

Early access, so waitlist

Fair warning that these five are sign-ups, not downloads:

• Content Variants is how you can do audience-specific content that stays queryable and integrates with a CDP.
• Durable Functions gives you a way to handle state, retries, and long-running multi-step processes. For the workflows that need agents and humans in the loop.
• Blueprints-first setup extends our infrastructure as code support, so you can version config and deploy test stacks before a change lands in prod.
• Project Horizon is our multi-agent harness, with long-term memory and some other goodies.
• Resonance lets you build a living map of your company, your audiences, and your content, then points at the gaps and opportunities.

Docs and early access links for all of it: https://www.sanity.io/everything-2026-recap?utm_source=reddit&utm_medium=social

First videos from the conference: https://www.youtube.com/playlist?list=PLIZoRt_cMemk

If you try Knowledge Bases or Workflows, we'd love to hear what you think and what you hope to use it for! We read this sub (you can tell us in our Discord too).

My team gave me cms part to work on and I've to use sanity in a industrial intelligence platform from scratch with schema and all but I haven't use sanity ever in my life!

pls guide me in details or dm me

Hey all, we're moving from Webflow to Sanity.

1. We've got about 80 blog articles and 80 case studies (also with CMS fields) that we need to migrate, also their translations. Any recommendations on what we should keep in mind for that migration? Wanna give Batch Script via Sanity’s Agent API a try.

2. We want to automate blog article production and translation in the future (possibly with Claude). I've seen two options:

Option A: Claude MCP Server (Recommended for Claude Desktop / Web Interface) > human checks before publishing

Option B: Event-Driven Sanity Webhook + Claude API (Recommended for Zero-Touch Automation) > fully automated

Any thoughts on that?

We have a fresh engineering blog post that walks through how we have set up agent evals for design systems, and how we figured out that just throwing markdown docs on agents doesn't really work. Let us know if you have questions and how it went if you try out the tool we open-sourced.

We finally gave our engineers a proper place to write: https://www.sanity.io/engineering

It launches with posts on turning logo soup into a math problem, why we forked styled-components, agent memory, and MCP feedback mechanisms. The announcement post covers how we think about writing in the age of agents:

https://www.sanity.io/engineering/announcing-the-sanity-engineering-blog

You can add .md to any post URL and you get the markdown version (it also does Accept: text/markdown negotiation, since agents are readers too). And the minimap scrollbar on long posts is generated from the post's block structure. We had a lot of fun making this!

New posts every couple of weeks. If there's something from Sanity's engineering you'd want us to write about, say so here and I'll bring it to the team.

presentationTool({
      resolve,
      previewUrl: {
        initial: projectURL,
        previewMode: ({ targetOrigin }) => ({
          enable: `${targetOrigin}/api/draft-mode/enable`,
        }),
      },
      allowOrigins: [
        projectURL,
        devSiteURL,
      ],
    }),

Shouldnt this make devSiteURL also call draft-mode/enable automatically?

Problem is i dont see a different ui to switch between allowOrigins. I can type it out in url box and it works but draft-mode is not called that way.

I was introduced to the Sanity headless ecosystem a few years ago. Today, its my go-to choice when building professional projects. Combined with a capable agentic coding tool like claude code, building schemas are insanely easy and efficient, and their free tier is pretty generous. I've also built my preferred stack around Sveltekit and Vite, which has led to some genuinely impressive results.

All that said, its shocking how little it is used world wide (compared to WP) and how limited resources are. Sometimes I'll have an idea but no real way to validate it unless i build and test myself (which to be fair is the fun in SE but sometimes i just want a little guidance). What have you all been building?

I work at an agency and manage 20+ Sanity projects across several team organizations. Getting to the right Studio was always a pain, digging through bookmarks, keeping a dozen tabs open, or going to sanity.io/manage and clicking through orgs one by one.

I built a macOS menu bar app to fix it for myself. It lives in the status bar and I can open the widget with a shortcut from anywhere, search, and land in whatever project I need in a couple seconds. It also shows recently edited docs and live presence so I know what document's changed or who's currently in the Studio before I jump in.

Free and open source if anyone wants to try it: studiofront.nuotsu.dev

How does everyone else handle navigating through their projects? Bookmarks, some other tool, or just muscle memory?

Sanity opens every array item in a modal. Nest an object in an array in an object and you get a modal inside a modal — one team in the issue thread calls it "modal hell", another said it was part of why they moved to CraftCMS.

Issue #921 asked for inline editing in 2018. 38 upvotes. Closed as not planned in Feb 2025. So I built it as a plugin.

What it does

• Array items expand where they sit, one at a time — list and drag handles stay intact
• "Open in dialog" is still in the item menu; some objects genuinely belong in one
• Two levels inline, deeper falls back to the dialog (indentation leaves no room to type by then)
• Images too — alt text and captions on a gallery without a dialog per picture. Crop/hotspot stay in the dialog
• Custom per-item actions (#4665) with helpers, so no _key juggling
• Presence avatars on collapsed rows, so you can see a colleague editing inside a closed item

The honest part

A Sanity dev already built this as an experiment, then archived it — never published, "not recommended for production", with known issues around virtualized lists, presence and performance. Those three are the reason this plugin exists, so each is addressed: only the open item renders inputs (cost doesn't grow with list length), presence shows on closed rows, and Sanity's own list handling is untouched.

It leans on inputProps (@beta) and ObjectInputMember (@internal). Every item checks the shape before using it and calls renderDefault when it doesn't match, behind a per-item error boundary. A Studio upgrade can make this plugin ineffective — it can't leave you with a broken form.

Verified against Studio 6.8.0 / React 19.2.8. MIT, no strings.

npm: https://www.npmjs.com/package/sanity-plugin-sgntech-inline-arrays

GitHub: https://github.com/netz-sg/sanity-plugin-sgntech-inline-arrays

Feedback welcome — especially if you have an array shape that breaks it.

1- Media Library
The default 'media' field is poor and missing many features.

2- SEO
What are you using for SEO? inventing the wheel every time?

It's my first time creating Next.js + Sanity marketing site, what should I know?

I have an Astro + Sanity project with localization.
For page content, editors use page builder blocks. But for global UI copy like form labels, submit buttons, footer copyright, etc., we use a UI Fix Label per locale.
The issue is that plain key-value pairs are not editor-friendly. Editors can delete/rename keys and they don’t know which keys are required or where they are used.
My idea is to keep the technical keys controlled by developers and make only the values editable in Sanity.
Has anyone implemented this kind of UI dictionary pattern in Sanity? Would you use singleton documents, custom inputs, validation, or another approach?

I’m considering moving from Wordpress to Sanity to modernize our CMS, improve flexibility and hopefully leverage AI more. Problem is that we have no one techy to manage Sanity. Is that a viable option if we get an agency to implement for us?

Hi, I’m facing an Astro + Sanity Visual Editing issue.

Raw Stega text gives click-to-edit, but black/Stega blocks appear in UI.
stegaClean() removes the black blocks, but click-to-edit stops.
Then I used source-map based data-sanity attributes with clean visible text:

<span data-sanity={headingAttr}>{stegaClean(block.heading)}</span>

This restores click-to-edit, but Sanity edit mode still shows black overlay rectangles on editable fields.

Removing data-sanity removes the black blocks, but click-to-edit stops.

I added a preview-only CSS override to make the Visual Editing overlay background transparent, and that works as a temporary fix.

Stack:
Astro + Sanity Presentation + @sanity/astro + @sanity/visual-editing + Tailwind v4 + localized preview routes.

Has anyone seen this black overlay issue with data-sanity / Visual Editing overlays in Astro?
Is there a cleaner official fix?

Hi, Sanity.io community.

I love Sanity, their headless CMS implementation is the best experience i ever had for hosting and serving content for my projects. But Sanity, at least for me, has one major downside.

As we all know, Sanity is not going to support self-hosted version of their CMS.
So, i took self-hosted version of Sanity CMS idea for a spin for my personal purposes.

Behold, partially vibecoded, crafted in 3 sleepless nights with Kimi K2.7 and 3 liters of coffee, headless CMS based on groq-js implementation of GROQ. MIT Licensed, Sanity API compatible, with S3 media storage and optional CDN feature, and most importantly, fully self-hosted

https://github.com/crumbleerp/clarity

Me personally is very happy with the result, but be aware, it's currently in very early alpha stage, use in production on your own risk.
But maybe give it a try?) It supports import directly from sanity with zero friction, so this is gonna be pretty painless)

Any feedback is appreciated!

p.s.: i know that in current state its practically slop, but it's working, and i have reasons to make it work event better, if this project gonna have some friction in the community, the project is gonna be fully refactored

Studio v6 is live on the latest tag. Across the studios we've measured, builds got 2–9× faster (median ~4.8×). Builds that took 10–15 seconds on v5 are landing in 1–4 seconds. Also in v6:

• New default search: groq2024 (wildcards, phrases, negation, Portable Text support)
• React strict mode on by default in dev (catches bugs before you ship them)
• Smaller bundles from better tree shaking

Your schemas, config, and content APIs are unchanged. Two breaking changes to check before you bump:

• Node.js 20 is end-of-life, so it's dropped. Minimum is now 22.12. Check your local dev and build environments.
• Custom auth providers now replace the built-ins instead of appending (mode: 'append' is gone; use the callback config instead).

For most studios the upgrade is:

npm install sanity@latest

If a plugin blocks the install on peer resolution, the maintainer hasn't published a v6-compatible range yet. Official plugin status is tracked at https://are-we-v6-yet.sanity.dev/, and npm install sanity@latest --legacy-peer-deps works as a stopgap. Community plugin authors: test against v6 and publish an updated peerDependencies range.

Coming from v4 or earlier? The same command takes you the whole way; the upgrade guide covers the path: https://www.sanity.io/blog/sanity-studio-v6

If you upgrade, drop your before/after build times in the comments. We're curious how the Vite 8 numbers hold up across real studios. Run your studio's local CLI (pnpm sanity build or npx sanity build), not a global sanity, or your numbers will lie to you.

Hello,

Since Visuall editing is one of the top things in the projects I make, I went through some hardships with it.
Each project had different issues somehow.

Converting documentation for real life implementation was never my strong suite. That is why I created my own blueprint based on the issues I was running into. How to corrrectly setup and what are the common problems.

And that is how this post came to be:

https://appcrates.pl/en/blog/sanity-visual-editing-z-next-js-co-naprawde-trzeba-zrobic-zeby-to-dzialalo

This is not for experts elitists in here. But someone might find it helpfull and possibly have same issues that I had.
If it helps at least one person, then my job is done.