Why Butterchurn Visualizer Shows a Blank Page or Requires JavaScript

Updated

Butterchurn Visualizer is a WebGL app, so it cannot render anything until JavaScript runs in your browser. If you see only the message "You need to enable JavaScript to run this app," or a blank page, JavaScript is disabled, blocked, or failing to execute. The fix is almost always in your browser settings or extensions, not in the site itself.

What the message actually means

The site's own fallback text is:

You need to enable JavaScript to run this app.

That line is not an error from the visualizer. It is the static HTML that appears before any script runs. If you can read it, the page loaded — but your browser refused to execute the app. Because Butterchurn is a WebGL implementation of Milkdrop, both JavaScript and WebGL must be available before any visualization can appear.

Check these in order

1. JavaScript is enabled

  • Chrome / Edge: Settings → Privacy and security → Site settings → JavaScript → make sure sites can use JavaScript.
  • Firefox: Type about:config in the address bar, search for javascript.enabled, and confirm it is set to true.
  • Safari: Settings → Security → confirm JavaScript is on (it is on by default).

After changing this, reload the page. Expected result: the fallback text disappears and the visualizer canvas starts.

2. No extension is blocking scripts

Ad blockers, privacy extensions, and script blockers can block the app's bundle even when JavaScript is enabled globally. Test by opening the site in a private/incognito window, where extensions are usually disabled. If it works there, disable extensions one at a time to find the culprit, then allowlist the site.

3. WebGL is available

Butterchurn renders through WebGL. If your browser or GPU has WebGL disabled or unsupported, the script may run but produce nothing visible.

  • Visit a WebGL test page (for example, get.webgl.org) and confirm your browser reports WebGL support.
  • In Chrome, check chrome://gpu for WebGL status.
  • If WebGL is unavailable, update your browser and graphics drivers, or try another browser.

4. Try a different browser

If settings look correct and extensions are ruled out, open the site in a second browser. A clean browser install isolates whether the problem is your configuration or the environment. If it works elsewhere, the issue is in your original browser's settings or profile.

Quick diagnosis table

Symptom Likely cause First action
"You need to enable JavaScript" text JavaScript disabled or blocked Enable JavaScript in site settings
Blank page, no text Script blocked by extension, or WebGL failure Try incognito, then test WebGL
Loads then goes blank WebGL context lost or GPU issue Check chrome://gpu, update drivers
Works in one browser only Browser-specific setting or extension Compare settings between browsers

Common sticking points

  • Enabling JavaScript globally but not per-site: Some browsers let you block JavaScript for specific sites. Check the site-level exception list, not just the global toggle.
  • Corporate or managed devices: Group policies can disable JavaScript or WebGL. If you cannot change the setting, the app will not run in that browser profile.
  • Old browser versions: WebGL support and modern JavaScript features vary by version. Updating the browser resolves many blank-page cases.

Once JavaScript and WebGL are both working, the visualizer loads and responds to audio input without further configuration.