V0 is unusable since Jan's update

Devs completely broke V0 in Jan. Usage is excruciating, I just abandon and don’t use it anymore.

-Previews still don’t work properly:

  1. On first prompt
  2. Frequently on iterations (repeated hard refresh required)
  3. Previews often show blank screen.
  4. Previews just crash repeatedly (not code related either)

-The entire portal lags. Every action is dial-up speed. Like 20-30sec per click is not atypical. This is on a fresh computer + browser too.
-Chats/forks are still auto-renaming, leaving projects in organization chaos.
-Design mode is barely usable. Like 20% as good as the old one.
-Models are brutally slow too. While I normally wouldn’t blame V0, since it’s entirely a Claude whitelabel….. Why is the same prompt directly in Claude Code like 5x faster than in V0?

I’m sure I’m missing items, because I’ve literally abandoned. Using V0 now is like trying to push a string. Friction overload. Like if you’re gonna do a major update, it should improve the service. I can’t name a single thing that has improved since Jan. Everything got markedly worse.

I’m very close to cancelling my account.

Sorry to hear you are having this experience. I can say that with the update there were a few things that the Team had to quickly fix up, but it has been running rather stable for quite some time now. I have not experienced (nor have I heard from any others from the Team or Ambassadors) any of the issue areas from the list you posted. So I am wondering if there is something else going on here.

To help the Team look into this and troubleshoot, it would be extremely helpful if you can share screenshots, screen video captures, and most importantly the link to a chat or two where you are experiencing these items. Then they can go in and diagnose properly.

My friend you were in the chat on one that still isn’t fixed. :face_with_tongue:

Auto-chat renaming after fork. Posted 2mth ago.

I’m sorry about these issues, this isn’t the experience we want you to have. Please share specific chat links with us so we can pass onto the v0 team!

Hmmm, odd, that issue is no longer an issue on my end.

As Pawlean has also said though, please share chats so the Team can help you out.
We are all here ready and wanting to help but we need to receive chat links to be able to make that happen.

I have same error

Can you share your v0 chat?

I guarantee it’s still broken!

Go test it.

  1. Fork a chat (duplicate).
  2. Use prompt 1 to add a new feature.
  3. The instant you hit enter on message 1 —> the entire new chat’s name will get auto-wiped. It will then be replaced with a variation of the feature you asked for in prompt 1. No project reference will exist in the chat name after that wipe, meaning I don’t know which project the chat belongs to now.

This happens every single time. It’s systemic, not a per chat issue.

Here’s a 1-min video of of both the preview glitching out, and the auto-rename occurring. This video link expires in 2-days so save it somewhere. It’s the only quick host I could find.

Here’s another of preview lag.

30-sec load time on an app with 550 lines of code.

Here’s another preview unresponsive. Over 1.5min lag, in-app refresh function unresponsive. Hangs on load, blank white screen. Even hard refresh barely loaded it. This is quite a lean app too. Some variation of preview load-lag happens probably 50% of the time I open an app/window. It happens on opens. Happens on new iterations. Happens on switching. Again, it’s a compounding issue, stacked on others that drive up platform friction.