Fixing VS Code Lag: My Solution to the “Running ‘File Copy/Rename’ Participants…” Delay | by Toni Maxx | Nov 2025

Why File Operations in VS Code Can Be Slow

VS Code may lag when renaming, copying, or moving files due to certain extensions and features that participate in these operations. Key culprits include:

• TypeScript server (tsserver)
• ESLint server
• Import/path auto-updaters
• File watchers in large directories (e.g., node_modules)
• Extensions that hook into file operations

For large projects, like React Native and Next.js, these participants can spike CPU usage, causing temporary freezes.

The Solution: Optimize Your Settings

To enhance performance, consider adding the following settings to your settings.json:

{
"typescript.updateImportsOnFileMove.enabled": "never",
"files.watcherExclude": {"**/node_modules/**": true, ...}, 
"search.exclude": {"**/node_modules/**": true, ...}, 
"typescript.tsserver.maxTsServerMemory": 4096,
"editor.semanticHighlighting.enabled": false
}

Why These Fixes Work

• Disabling automatic import updates eliminates lag.
• Excluding heavy folders reduces background processing.
• Increasing TypeScript server memory prevents slowdowns.
• Turning off experimental diagnostics allows smoother operations.

After applying these settings, file operations should be instant. If you encounter similar issues, these adjustments may also bring significant relief!