Skip to content

XP event5x XPListening, games, ratings, comments and chat earn five times the XP

leftLeaderboard

juicewrld-desktopREADME.md

1.4.2Released Nov 21, 2026

README.md

219 lines12.1 KBMarkdownWritten for this page

juicewrld.io for Windows

This is the source code of the juicewrld.io desktop app for Windows. It is published so anyone can read what the app does, build it themselves, and check that a release came from this code.

This repository holds the desktop app only. The juicewrld.io website is not in it. The app shows the live site, so what the site does inside the window is the site's own code, the same as in a browser.

Version in this source: 1.4.2.

What the app is

  • One window with two parts. The top strip is the app's own title bar (ui/, built into the app). Below it is https://juicewrld.io, loaded live in Microsoft Edge WebView2, the browser engine built into Windows 11.
  • A Discord status: while a song plays on the site, your Discord profile can show "Listening to" that song.
  • Updates: the app checks juicewrld.io for a newer version, downloads it, checks its signature, and installs it.
  • Plugins in the studio (off until you turn them on): the site's studio can use the VST 3 effects already installed on your PC. They run in a separate process, juicewrld-plugins.exe.

It is built with Tauri 2 (Rust) and a small C++ part for the plugin host.

What it does on your computer

Everything below comes from the code in this repository. File names point to where each part lives.

The window (src-tauri/src/main.rs)

  • Only https://juicewrld.io and https://discord.com open inside the window, those two hosts exactly. Discord is there for its login pages.
  • Other http, https and mailto links open in your default browser or mail app. Links of any other kind are ignored. The window never shows data:, blob:, javascript: or file: pages.
  • The app adds JuiceWRLDDesktop/<major>.<minor> to the browser's user agent, so the site can tell it is the app.
  • Files you download from the site are saved by WebView2 to your Downloads folder, as in Edge.
  • The app adds one script to the site's pages (src-tauri/src/site.js). It runs only on https://juicewrld.io, in the top frame. It reads what is playing (the page's media session and the playing audio element's time) and passes it to the app for the Discord status and the title bar. When plugins can run, it also adds window.juicewrldDesktop.plugins (see Plugins below).
  • The site can call only the commands listed in src-tauri/capabilities/site.json: the "what's playing" report and the plugin commands. It cannot read or write files, run programs, or change settings through the app. The title bar (src-tauri/capabilities/bar.json) can move, maximize and close the window and use its own buttons.

Discord status (src-tauri/src/presence.rs)

  • The app talks to the Discord desktop app on the same PC through Discord's local pipe. It does not contact Discord's servers itself. It uses Discord application ID 1562418221972324372, which is public.
  • It connects only while a song plays. If Discord is not running, it tries again every 15 seconds while a song plays.
  • It sends: the song title, the artist, the album, the cover image address, the song's page on juicewrld.io, and the start and end times. The status shows a "Listen on juicewrld.io" button. It clears when you pause.
  • Discord then shows this on your profile, according to your Discord activity settings.

Sign-in (src-tauri/src/handoff.rs)

  • "Sign in with Discord" opens in your default browser, not in the app.
  • The app makes a random secret, keeps it in memory, and sends only its SHA-256 hash with the sign-in.
  • When you finish, the browser opens a juicewrld://signin?code=... link. The app sends that code and the secret to https://juicewrld.io/api/auth/app/claim, in its own window, to sign you in there.
  • The app accepts such a link only while a sign-in it started is waiting, for up to 10 minutes. Other juicewrld:// links are ignored.

Updates (src-tauri/src/update.rs, src-tauri/tauri.conf.json)

  • One minute after start, then every 4 hours, the app requests https://juicewrld.io/api/app/update/windows/x86_64/<version>, with its own version in the address.
  • The request carries no account, install ID or hardware details. Like any web request, the server sees your IP address. The site uses these requests to count active installs per version per day.
  • If there is a newer version, the app downloads the installer from juicewrld.io. It checks the installer's minisign signature against the public key in tauri.conf.json (plugins.updater.pubkey), and checks that the signature names that version. If either check fails, nothing is installed.
  • The update installs when you click "Update ready", or silently when you close the app. It never installs while the app is open.
  • A copy you build yourself checks for updates too. When juicewrld.io has a newer version, your copy will download and install the official build. To stop that, set a higher version in src-tauri/tauri.conf.json before you build, or take the updater out (src-tauri/src/update.rs and its plugin in main.rs).
  • Debug builds (npm run dev) never check for updates.

Plugins in the studio (src-tauri/src/plugins/, src-tauri/host/)

This is off until you turn it on in the title bar's menu (the three dots), or say "Turn on" when the site asks. The site can ask. It cannot turn plugins on by itself.

When it is on:

  • The app lists VST 3 plugin folders the way installers and DAWs record them: the standard VST folders, folders named in the registry under SOFTWARE\VST, FL Studio's plugin folders and plugin database, and folders you add. It only reads the registry. It never writes there or to FL Studio's files.
  • It reads plugin files to find out what they are. Files it cannot use (VST 2, 32-bit, ARM) are listed as unsupported and never loaded.
  • It looks at the folders again a few seconds after each start, and when the studio asks for the list (at most every 15 seconds). Only new or changed files are read.
  • To list a plugin it may have to load it. It does that in a short-lived child process, juicewrld-plugins.exe --scan, one file at a time. If loading opens a window (usually a licence window), the load is stopped 2 seconds after the window appears. A load that takes more than 30 seconds is stopped too. A file that failed is not loaded again until it changes or you click "Try again".
  • Plugins you use run in a separate process, juicewrld-plugins.exe --host. If a plugin crashes or hangs, only that process ends. It loads only files inside the plugin folders.
  • The site's studio page can: list the plugins found (names, vendors, versions and file names, never folders), open one, send audio through it, open its window, change its settings, and save and restore its state. It refers to plugins only by the IDs the scan gave them. It cannot name a file or a folder.
  • When you save a mix with a plugin in it to your account, the site keeps the plugin's ID, name, vendor and settings with the mix. That is done by the site's code, not by this app.
  • Plugins run with your user rights and are not sandboxed, as in any music program. A plugin's own code, such as its licence check, may do things of its own, including going online.

The portable exe cannot run plugins. It has no plugin host beside it.

Files and settings it writes

  • %LOCALAPPDATA%\io.juicewrld.desktop\EBWebView: WebView2's profile for the site (cookies, cache, site storage).
  • %APPDATA%\io.juicewrld.desktop\.window-state.json: the window's size and position.
  • %APPDATA%\io.juicewrld.desktop\plugins.json and plugin-scan.json: plugin settings and what the scan found. They are written only once you turn plugins on or change their settings.
  • HKEY_CURRENT_USER\Software\Classes\juicewrld: registers the juicewrld:// link, at every start.
  • The installer (src-tauri/nsis/installer.nsi) installs for your user only, without admin rights, to %LOCALAPPDATA%\juicewrld.io. It adds a desktop and a Start menu shortcut and an entry in Installed apps. If WebView2 is missing (some Windows 10 PCs), it runs Microsoft's signed WebView2 installer, which is inside it.

What it does not do

  • No analytics, telemetry or crash reports are sent by the app. Its log lines go to standard error and are not saved.
  • It starts no programs other than WebView2's own processes, juicewrld-plugins.exe (only with plugins on), your browser or mail app for links, and the installer during an update.
  • Debug-only test switches (JW_* environment variables) are compiled out of release builds.

Build it yourself

You need:

  • Windows 10 or 11, 64-bit
  • Rust, stable, with the x86_64-pc-windows-msvc target
  • Visual Studio 2022 Build Tools with "Desktop development with C++" (for the plugin host's C++)
  • Node.js 24
  • WebView2 Runtime (built into Windows 11)

Then, in this folder:

npm ci
npm run build:unsigned

This makes:

  • src-tauri/target/release/juicewrld.exe: the app, which also runs on its own (the portable exe)
  • src-tauri/target/release/juicewrld-plugins.exe: the plugin host
  • src-tauri/target/release/bundle/nsis/juicewrld.io_1.4.2_x64-setup.exe: the installer

The first build downloads Tauri's NSIS tools and Microsoft's WebView2 installer, which go into the installer.

npm run build:unsigned skips the update signature. Official releases are signed with a private key that is not in this repository. npm run build signs and needs that key in TAURI_SIGNING_PRIVATE_KEY.

Other commands:

npx tauri build --no-bundle      # the exes only, no installer
npm run dev                      # debug build with a console window
cd src-tauri && cargo test       # tests

The tests build a small test plugin and open hidden windows. They never load plugins installed on your PC.

Builds are not code-signed, so Windows SmartScreen warns the first time you run one.

Check a release

Check the file is the one published

In PowerShell, in the folder you downloaded to:

Get-FileHash .\juicewrld-windows-setup.exe -Algorithm SHA256
Get-FileHash .\juicewrld-windows.exe -Algorithm SHA256

Compare the result with the table below, or with the fingerprint on https://juicewrld.io/app.

Release 1.4.2, published 2026-11-21. It was built on the developer's PC.

FileSizeSHA-256
juicewrld-windows-setup.exe4,911,759 bytese2aef34e124e1e37d248e3a18c990d6608333aef8030af01cf81a2c25ab71283
juicewrld-windows.exe11,227,136 bytes72253b785b8f86385b9daa4687283c7d23948e831011c1636758cc56746fb262

Check it was built from this source

Releases are built on the developer's PC. The hash shows you have the published file, not that it was built from this source. Building the source yourself gives a different hash, because these builds are not byte-for-byte reproducible.

Check the update signature

Signed releases come with juicewrld-windows-setup.exe.sig. The app checks this signature before it installs an update. You can check it with minisign. In PowerShell:

$conf = Get-Content src-tauri\tauri.conf.json -Raw | ConvertFrom-Json
[IO.File]::WriteAllBytes("$PWD\updater.pub", [Convert]::FromBase64String($conf.plugins.updater.pubkey))
[IO.File]::WriteAllBytes("$PWD\setup.minisig", [Convert]::FromBase64String((Get-Content .\juicewrld-windows-setup.exe.sig -Raw)))
minisign -V -p updater.pub -x setup.minisig -m .\juicewrld-windows-setup.exe

Third-party code

See THIRD-PARTY-NOTICES.md.

Licence

The code is under the licence in LICENSE. The juicewrld.io name, logo, wordmark and app icons are not covered by it.

Security

See SECURITY.md.