CodeSandbox VM Slow or Out of Memory
Quick answer
A slow or crashing VM Sandbox can be given more memory by raising its specs under the CodeSandbox menu, then Virtual Machine. Legacy Pro plans must first convert to usage-based billing.
Most likely fix: Increase VM specs
How to fix it
Try these in order — the most common fix is first.
1. Increase VM specs
- Click the CodeSandbox icon in the editor
- Choose Virtual Machine
- Pick a larger spec and restart the VM
Did this fix it?2. Convert a legacy Pro plan
- Legacy Pro workspaces cannot change VM specs
- Convert the workspace to the usage-based Pro plan first, then change the specs
Did this fix it?
Symptoms
Builds are slow, the dev server crashes or the VM restarts under load.
Why it happens
- VM specs too small for the project
- Legacy Pro plan cannot change VM specs
This guide also covers
- codesandbox slow
- codesandbox out of memory
- codesandbox vm specs
Still not working?
If CodeSandbox keeps failing, you're not alone. See every CodeSandbox problem users report or the alternatives people switch to.
Have an app idea? Our small team builds any software: web and mobile apps, games, desktop, AI tools. Price agreed together.
Talk to usThe same problem in other apps
All slow, laggy or resource-hungry guides →
StackBlitz Out of Memory on Mobile or Large Projects (StackBlitz)
Other CodeSandbox errors
- CodeSandbox 502 "Dev Server Has Not Started Yet" Error
- CodeSandbox Not Loading or Not Starting
- CodeSandbox VM Frozen: Credits Ran Out
- CodeSandbox Preview Not Showing for Private Sandbox
- CodeSandbox "Request Entity Too Large" Error on Import or Commit
- CodeSandbox "Only a Max of 250 Modules Is Allowed" Import Error
- CodeSandbox "Could Not Find Dependency" Error
- CodeSandbox Private Sandboxes on the Free Plan