How to disable auto-saving in Sanity Studio v3.43.0?

I totally understand your frustration with the slow typing experience! The good news is that Sanity Studio doesn't actually autosave on every single keystroke — there's no way to disable autosave because the lag you're experiencing isn't directly caused by saving behavior. Instead, the issue is typically related to performance bottlenecks elsewhere in your setup.

Based on the Sanity Answers thread and GitHub issue #7456, here's what's actually happening and how to fix it:

What's Really Causing the Lag

Sanity Studio debounces saves (waits for you to pause typing), so the keystroke lag is usually caused by:

1. Performance regressions in certain Studio versions — Some versions between 3.50.0 and 3.56.0 had known performance issues
2. Next.js integration issues — Running Studio embedded in Next.js dev mode can be slower than standalone
3. Complex schemas or custom components — Heavy validation, custom input components, or deeply nested fields
4. Portable Text with nested objects — This is particularly bad, as multiple users reported

Solutions That Have Worked

1. Update to the latest version
Since you're on 3.43.0, try updating to the latest Studio version. The team released v3.57.0 with up to 10x speed improvements (though that specific fix was for dev mode). More recent versions include additional performance fixes targeting the exact issue you're describing.

npm install sanity@latest

2. Try downgrading temporarily
If updating doesn't help, downgrade to 3.50.0 as a workaround while testing:

npm install sanity@3.50.0

3. Test Studio standalone
Run npx sanity dev directly instead of through your Next.js app to isolate whether it's a Next.js integration issue. If it's fast standalone, the problem is with your Next.js setup.

4. Check for the actual culprit
From the GitHub thread, one user discovered their setup was just incorrect — they fixed it by recreating their Next.js + Sanity project from scratch and copying over the code.

5. Build for production
Try running your Next.js app in production mode (npm run build && npm run start) — dev mode can be significantly slower.

Common Misconceptions

• It's not syncing every keystroke to the cloud — Studio batches and debounces changes
• Autosave can't be disabled — but you shouldn't need to since it's not the actual problem
• The lag is particularly bad in Portable Text with nested objects — this is a known pain point

The Sanity team is actively working on performance improvements for these scenarios. If none of the above helps, I'd recommend sharing your schema configuration in the Sanity Community so folks can help identify specific bottlenecks!