Why Does Loofi Say JavaScript Is Required?

Loofi shows the "JavaScript Required" message because the web version of the app is built entirely with JavaScript. The page you receive from loofi.netlify.app is essentially a shell: the streaming interface, the audio player, and the LoFi stream itself are all loaded and controlled by JavaScript running in your browser. If JavaScript is disabled, blocked, or fails to run, that shell never fills in, so Loofi displays the fallback notice instead of the player. The fix is to enable JavaScript for the site, or to use the desktop app if you'd rather not.

What the message actually means

The notice on the page reads:

JavaScript Required — We're sorry, but Loofi doesn't work appropriately without JavaScript enabled.

This is not an error caused by a broken link, a missing file, or a server outage. It is a deliberate fallback. Loofi's page is designed so that the visible content and the audio playback are assembled by client-side JavaScript. When the browser refuses to execute that JavaScript, there is nothing left to render, so the site tells you why rather than showing a blank page.

Two things follow from this:

• The message is a browser-side condition, not a Loofi-side problem. The same URL will work on a browser with JavaScript enabled.
• Because playback depends on JavaScript, no amount of refreshing, clearing cache, or switching networks will change the outcome while JavaScript remains off.

How to enable JavaScript for loofi.netlify.app

The exact menu path differs by browser, but the goal is the same: allow JavaScript to run on loofi.netlify.app. A practical approach that works across most browsers is to allow JavaScript by default, then reload the page.

General steps

1. Open your browser's settings.
2. Find the privacy, security, or site settings section — look for an entry named something like JavaScript, Site settings, or Content settings.
3. Make sure JavaScript is allowed rather than blocked.
4. If your browser supports per-site exceptions, add loofi.netlify.app to the allowed list.
5. Return to the Loofi tab and reload the page.

Expected result: the "JavaScript Required" notice disappears and the streaming interface loads in its place.

If you use an extension that blocks scripts

Content blockers, privacy extensions, and script managers can disable JavaScript on a per-site basis even when the browser's own setting allows it. If the notice persists after enabling JavaScript in settings:

• Disable script-blocking extensions for loofi.netlify.app, or pause them entirely and reload.
• Check whether the browser is running in a restricted mode (for example, a hardened privacy mode) that turns JavaScript off by default.
• Try the site in a private/incognito window with extensions disabled to confirm whether an extension is the cause.

If the notice still appears

If JavaScript is enabled and no extension is interfering, the remaining possibilities are environmental:

• Corporate or school network policies that strip scripts from pages.
• Browser versions too old to run the JavaScript the app relies on.
• Content Security Policy or firewall rules that block the scripts Loofi loads.

In these cases the browser route may not be available to you at all, which is where the desktop option comes in.

The desktop app as an alternative

Loofi is described as open-source LoFi streaming for both web and desktop. If you cannot enable JavaScript in your browser — or you simply prefer not to — the desktop app is the intended alternative. It runs the same streaming experience outside the browser, so the JavaScript requirement of the web page no longer applies.

This is the more reliable choice when:

• You are on a managed device where browser settings are locked.
• A network policy blocks scripts on web pages.
• You want LoFi playback without keeping a browser tab open.

Quick reference

The short version: Loofi's web player is JavaScript-driven by design, so the notice is expected whenever scripts can't run. Enable JavaScript for the site and reload, and if that isn't possible on your setup, the desktop app is the supported way around it.