Why Does Womp Show "Loading... Preparing client content"?

Updated

Womp is showing that message because its browser client — the 3D engine and editor that run inside your tab — hasn't finished downloading or initializing. The page itself has loaded, but the application behind it hasn't. The site's own guidance for this state is to refresh the page, and if the message persists, to contact [email protected]. In most cases a refresh or a browser-side fix clears it; if it doesn't, the problem is usually on the network or client side rather than something you can fix from the page.

What the message actually means

Womp is a web-based 3D tool, so nothing is installed on your machine. When you open beta.womp.com, the server sends a small HTML shell, and that shell then pulls down the actual client content — the 3D viewport, modeling tools, and asset libraries. "Loading... Preparing client content" is the placeholder shown during that second step.

That means the message can appear for two different reasons:

  • Normal startup — the client is still downloading and will appear on its own.
  • Stalled startup — the download or initialization failed, and the placeholder will sit there indefinitely.

If the text never changes and no progress appears after a reasonable wait, you're in the second case.

Fixes to try, in order

  1. Refresh the page. This is the site's own recommended first step and resolves most transient stalls. A hard refresh (Ctrl+Shift+R on Windows/Linux, Cmd+Shift+R on macOS) forces the browser to re-fetch the client instead of reusing a broken cached copy.
  2. Check your connection. The client is a sizable download. A dropped Wi-Fi signal, a VPN that blocks the asset CDN, or a corporate firewall can interrupt it mid-transfer. Try another network or turn the VPN off.
  3. Disable extensions that block scripts. Ad blockers, privacy extensions, and script blockers can prevent the client from loading. Test in a private/incognito window with extensions disabled.
  4. Try a different browser. Web 3D tools depend on WebGL and modern JavaScript features. If your current browser is outdated or has hardware acceleration turned off, the client may fail to start. Chrome, Edge, and Firefox on current versions are the safest bets.
  5. Clear site data for beta.womp.com. A corrupted cached bundle can keep failing on every reload. Clearing cookies and cached files for that domain forces a clean fetch.
  6. Contact support. If none of the above works, email [email protected] — the site names this address specifically for the case where the loading message persists.

What to include if you contact support

Support can only diagnose a stalled client if they know what your browser saw. Before writing, gather:

  • The exact message text and how long it stayed on screen
  • Your browser name and version
  • Your operating system
  • Whether the browser console shows errors (open developer tools with F12, check the Console tab)
  • Whether you're on a VPN, corporate network, or restricted connection
  • Whether the same account works on another device or network

That last point is the most useful one: if Womp loads fine elsewhere, the issue is local to your browser or network, not your account.

When it's not something you can fix

If the client fails on every browser, every network, and every device you try, the stall is likely on Womp's side — a deployment in progress, a CDN outage, or a service issue. In that case refreshing repeatedly won't help; waiting and checking again later, or emailing support to confirm whether there's a known incident, is the practical move.

Note that this article describes the loading behavior and the remedies the site itself points to. It does not cover account, pricing, or feature questions, which are separate topics.