[▲ Vercel Community](/) · [Categories](/categories) · [Latest](/latest) · [Top](/top) · [Live](/live)

[v0](/c/v0/59)

# V0 very slow – context overload or known issue?

144 views · 1 like · 4 posts


Anthony Yang (@anthonyyang) · 2025-05-28 · ♥ 1

I've been encountering significant performance issues in v0 today, and I'm hoping someone can shed light on whether this is expected behavior or a bug.

* I'm currently on **version 86** of my project
* Using the model **v0-15-md**
* I **upgraded yesterday**, and have **11.30 out of 20 credits** remaining
* Performance is now **painfully slow** – frequent stalling, and in some cases, the browser tab crashes completely

My main concern is about how context is being handled:

> **Is the entire chat history with v0 being sent as context every time I type a follow-up?**

It feels like this might be the root cause. I previously used Firebase Studio Prototyper, where long context threads caused slowdowns, so I moved to v0 in hopes of a more performant experience – especially now that I’m paying for credits.

Would appreciate any insights from the team or community:

* Is this a **known issue**?
* Is there a recommended way to manage or reset context in long project threads?
* Any way to improve performance as the version count increases?

Thanks!

— Anthony


Marlon Vidal (@marlonvidal) · 2025-06-05

having the same problem here


Jacob Paris (@jacobparis) · 2025-06-05

You can clear the chat history at any time by clicking "Fork". This will create a fresh chat in the same project with your deployment settings, environment variables, integrations, etc all intact, and if you deploy the new fork it'll take over as the main deployment for that generation 

I rarely get beyond v20 before forking to a new chat and usually fork every time I deploy


Anthony Yang (@anthonyyang) · 2025-06-05

Thanks for getting back to me, Jacob — much appreciated.

I’ll give the “Fork” method a try, as it sounds like a logical way to maintain performance while preserving the project setup. I’ll return to the thread once I’ve tested it to share whether it resolves the slowdown.

Thanks again.