StackBlitz Stuck on "Running start command" in Brave
Quick answer
Brave blocks cross-site cookies by default, which stops WebContainers at the "Running start command" step. Allow all cookies for the project in Brave Shields.
Most likely fix: Allow cookies in Brave Shields
How to fix it
Try these in order — the most common fix is first.
1. Allow cookies in Brave Shields
- Open a WebContainers project such as https://stackblitz.com/edit/nextjs
- Click the Shields icon at the right of the address bar, then Advanced View
- Change "Cross-site cookies blocked" to "All cookies allowed"
- Brave reloads the page and the project should run
Did this fix it?
Symptoms
Boot sequence sticks on "Running start command" and the project never starts in Brave.
Why it happens
- Brave Shields "Cross-site cookies blocked" default
This guide also covers
- stackblitz brave not working
- stackblitz running start command stuck
Still not working?
If StackBlitz keeps failing, you're not alone. See every StackBlitz 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 usOther StackBlitz errors
- StackBlitz Unable to Run Embedded Project: Third-Party Cookies Blocked
- StackBlitz Not Working in Firefox or Safari
- StackBlitz Out of Memory on Mobile or Large Projects
- StackBlitz "Cannot load native addon because loading addons is disabled"
- StackBlitz npm ERR! code ERESOLVE Conflicting Peer Dependency
- StackBlitz Preview Reloading in an Infinite Loop
- Bolt.new Preview Blank Screen or "Your Preview Will Appear Here"
- Bolt.new Tokens Running Out Too Fast