Install Applio and check the engine

Applio has two interfaces. Desktop opens an installed application window and manages an engine environment on first launch. Gradio opens a local web page and needs its launch process to stay running. These steps cover Desktop and the compiled Windows Gradio package. Pick the interface shown in the instructions you want to follow.

Desktop

1. Open the official Desktop downloads. Find Assets and expand the list if the installer you need is hidden. Choose the asset for your operating system. The source-code archives are for developers.
2. On Windows, run the setup executable and choose a folder your account can write to. The packaged app uses a data directory beside its executable. On macOS, use the disk image for your processor, ARM64 for Apple Silicon or x64 for Intel. On Linux, install the available Debian package or make the AppImage executable and open it.
3. Start the app and review the first-run terms. Keep the app open while it sets up Python, installs the engine requirements, fetches assets and verifies the installation. Use Install / Repair if your build offers it when a check fails.
4. When verification completes, check the compute device detected in setup. Record the backend and hardware the app reports. A machine with more than one GPU can report a different device from the one you expected.
5. Open Models. If it opens and the engine is ready, continue to install a voice. Run the short conversion before trying live mode or training.

You can install an official Desktop package without Node.js or pnpm. Those tools are for building the app from source.

Gradio on Windows

1. Download a Windows package from the compiled Gradio downloads.
2. Extract the complete ZIP to a simple path you own, for example C:\Applio-Gradio. Open that folder in Explorer. If you see a second folder containing the launcher, open it.
3. Run run-applio.bat from the extracted folder. If a console opens, leave it running. Wait for it to print a local address and open that exact address in your browser.
4. Find Models or Download, depending on the release. Then open Convert Audio or Inference. If the browser loses its connection, check whether the launcher is still running before reopening the page.

If setup stops

What you see	First thing to check
Nothing opens from the ZIP	Extract every file before running the launcher.
Download or verification step fails	Read the earliest error in the setup log. Check connectivity, available disk space and write access before retrying the failed step.
Gradio stops before displaying an address	Read the console above the last line for the first relevant error. The browser cannot connect until the service starts.
Audio files fail to open or export	Check engine verification and FFmpeg status. Test with a local WAV you can play in another application.
File conversion starts but runs out of memory	Close competing jobs and test a few seconds of audio with effects off. Try a device supported by your build.

Before installing a new version or moving folders, save your working audio and back up custom models, indexes, datasets and full training experiments. After updating, use the same short recording and voice to confirm that the new engine produces a usable result.