Discover Levi Launcher

Levi Launcher

Install, isolate, mod and launch Minecraft Bedrock versions from one Windows app

Levi Launcher is a desktop launcher for Minecraft Bedrock Edition (GDK) on Windows, built by the LeviMC community. Instead of managing a single Microsoft Store installation, it lets you keep several Release and Preview builds side by side, each with its own worlds, packs and settings. This guide explains what the launcher does, what Windows needs before it will run, how installation and isolation work, and what to check when something goes wrong. Everything here is written for players, in plain language, with links to the project’s own documentation.

Windows 10 & 11  •  Minecraft Bedrock Edition (GDK)  •  Community project by LeviMC  •  Independent guide, not an official site

Levi Launcher

Version manager for Minecraft Bedrock (GDK)

Release build

Your stable, everyday version — the one your long-term worlds live in.

Preview build

Test upcoming Minecraft features without touching your main setup.

Isolated instance

Worlds, packs and game files kept separate from the default AppData install.

Windows only

Built for Windows 10 and 11 desktops.

Licensed copy

Needs Bedrock owned by your Microsoft account.

Easy to understand

Plain-language explanations of what the launcher does, written for players rather than developers.

Feature focused

A section for each core workflow: versions, isolation, content, mods and world tools.

Checked against the docs

Requirements, install steps and fixes follow the project's own user documentation.

New-user friendly

Start with the quick steps, then read the full guide when you want the detail.

Overview

What Is Levi Launcher?

Levi Launcher is a desktop launcher for Minecraft Bedrock Edition (GDK) on Windows. It is developed under the LeviMC / LiteLDev umbrella and its purpose is narrow and practical: give players one place to install, organise, modify and start different Bedrock builds without fighting the default Microsoft Store installation.

On a standard Windows setup you effectively have one Bedrock installation at a time. Switching between a Release build and a Preview build, keeping a modded setup away from a vanilla survival world, or testing something risky without endangering a world you care about, all become awkward. Levi Launcher approaches this with a version-first workflow: you install a version, name it, launch it, and remove it when you are finished, while each setup stays under your control.

The second idea behind it is isolation. When you enable isolation for a version, its worlds, packs and game files are kept separate from the default AppData installation, so a broken mod or an experimental Preview build does not spill into your everyday game. Around those two ideas sits a content toolkit for worlds, resource packs, behaviour packs, skin packs, screenshots and server lists, plus mod support for .zip and .dll files, CurseForge browsing, and LIP or LeviLamina workflows for more advanced setups.

It is not a way to get the game for free. Levi Launcher works with Minecraft Bedrock Edition (GDK) and a legitimate licensed copy tied to your Microsoft account, and it depends on Windows components such as Microsoft Gaming Services, Microsoft GameInput and the WebView2 Runtime. It also does not cover Minecraft Java Edition, and the desktop app is Windows-only — separate community projects exist for Android under similar names.

Quick facts

Platform

Windows 10 and Windows 11 desktop.

Game edition

Minecraft Bedrock Edition (GDK), licensed to your Microsoft account.

Maintained by

The LeviMC / LiteLDev community, with public documentation and an issue tracker.

Connection

Needed for downloads, version metadata, mirror tests and update checks.

Please note: levilauncher.com is an independent community resource. It is not owned, operated or endorsed by LeviMC, Mojang Studios or Microsoft. Minecraft is a trademark of Mojang Studios. Always download software from the project’s own release pages.

Capabilities

Levi Launcher Features

Six things the launcher is genuinely built to do. Individual options can change between releases, so treat the project’s changelog as the final word.

Version-first workflow

Install, rename, launch and remove Minecraft Release or Preview builds from a single list. Each entry keeps its own name and configuration, so you always know which setup you are about to start and which one your world belongs to.

Clean isolation

Choose to keep worlds, packs and game files separated from your default AppData installation. Isolation gives risky experiments — new mods, Preview builds, borrowed worlds — a safer workspace that will not disturb your main game.

Content toolkit

Manage worlds, resource packs, behaviour packs, skin packs, screenshots and server lists from one place, instead of digging through folders in File Explorer to find where a pack was installed.

Mod-ready

Import .zip or .dll mods, browse CurseForge from inside the launcher, and use LIP or LeviLamina workflows for advanced setups. Keep modded versions separate so vanilla play stays clean.

World utilities

Export backups, inspect world data and edit selected level.dat fields without leaving the launcher. Making a backup before a big change is the single habit that saves the most worlds.

Settings you control

Tune language, appearance, download behaviour, privacy choices, update channel and component status. If a required Windows component is missing, the launcher can point you at it during setup.

Process

How Levi Launcher Works

Four stages, in the order you will meet them.

01

Prepare Windows

Install Minecraft Bedrock from the Microsoft Store at least once, then let the launcher check for Gaming Services, GameInput and the WebView2 Runtime.

02

Add a version

Open Download inside the launcher, pick Release or Preview, choose the version entry you want, and start the installation.

03

Decide on isolation

Enable isolation if you want that version’s worlds, packs and files kept apart from your default installation. Most players should start with one isolated Release version.

04

Launch and manage

Start the version from the launcher, then use the content and world tools to add packs, import mods and take backups as you go.

Search intent

Why People Search for Levi Launcher

Search traffic around this name is almost entirely practical. Players are mid-task — they have a download in front of them, or an error message, or a Preview build they do not want to install over their survival world — and they want a straight answer.

These are the six questions that come up most often. The rest of this page answers each one in more detail, and the FAQ near the bottom covers the shorter versions.

What it actually is

Most searches start here: is this a launcher, a mod, or a way to get the game without paying? It is a launcher, and it still needs a licensed copy of Bedrock.

Which features it has

People want to know whether it can run several versions, keep worlds apart, and handle packs and mods without manual folder work.

Whether their setup is supported

Windows edition, Bedrock GDK, and the Windows components the launcher depends on are the three usual blockers.

How to install it safely

Where the real download pages are, what to check before installing, and why anything else should be treated with suspicion.

Why something is not working

Missing Gaming Services, a missing GameInput redistributable, a non-writable install path, or a version that will not start.

How updating works

Whether the app updates itself, what happens to installed versions, and what to back up first.

Requirements

Levi Launcher Compatibility

Check these before you download anything. Details can change between releases, so confirm against the project documentation for the version you are installing.

Operating system

Windows 10 or Windows 11. There is no macOS or Linux desktop build of this launcher.

Game edition

Minecraft Bedrock Edition (GDK). Minecraft Java Edition is a different game and is not covered.

License

A legitimate licensed copy of Bedrock tied to your Microsoft account. Install it from the Microsoft Store at least once first.

Windows components

Microsoft Gaming Services, Microsoft GameInput and the WebView2 Runtime. Some Windows setups already have them.

Network

Required for downloads, version metadata, mirror tests and update checks. Installed versions can be launched afterwards.

Mobile

The desktop launcher is Windows-only. Android projects with similar names are separate community efforts with their own requirements.

Step by step

How to Use Levi Launcher

A sensible order for a first setup, based on the project’s quick-start guidance.

01

Set up Bedrock first

Install Minecraft Bedrock from the Microsoft Store and start it once. If Store installation or Gaming Services looks incomplete, launching the game once usually settles it.

02

Close the game

Quit Minecraft before you install or manage versions in the launcher. Files that are in use are the most common cause of an install that stalls.

03

Pick Release or Preview

Open Download inside the launcher and choose the channel. Release for stable, long-term play; Preview when you want to see upcoming features and accept the instability.

04

Turn isolation on

Decide whether the version should keep its own worlds, packs and files. For a first setup, one isolated Release version is the recommendation in the official guide.

05

Add your content

Import worlds, resource packs, behaviour packs and skin packs through the content tools, and set up server lists there rather than in the game folders.

06

Back up before changes

Export a world backup before adding mods, switching versions or editing level.dat fields. It takes a minute and removes most of the risk.

Installation

How to Install Levi Launcher

Installation has two halves: getting the launcher itself onto Windows, and then installing your first managed Minecraft version inside it. Do them in that order.

1. Check the requirements

  • Windows 10 or Windows 11.
  • Minecraft Bedrock Edition (GDK), licensed to your Microsoft account.
  • Microsoft Gaming Services, Microsoft GameInput and the WebView2 Runtime.
  • A working internet connection for downloads and update checks.

2. Prepare the game

  • Install Bedrock from the Microsoft Store at least once.
  • Start the game once if the Store installation or Gaming Services looks incomplete.
  • Close Minecraft before using the launcher to install or manage versions.

3. Install the launcher

The project publishes its installer on its GitHub Releases page, which is also where the release notes and changelog live. A Lanzou Cloud mirror is offered for regions where GitHub downloads are slow. Download the installer, run it, and finish the setup wizard. If you use a self-managed WebView2 Fixed Version Runtime rather than the Evergreen runtime, the documentation explains how to point the launcher at it with a command-line option or a webview2.json file.

4. Install your first version

  • Open Download inside Levi Launcher.
  • Choose Release or Preview.
  • Pick the version entry you want.
  • Decide whether to enable isolation.
  • Start the installation and wait for it to finish.

5. Verify and update

Launch the version once before adding anything to it, so you know the base setup works. The launcher can check for, download and install its own updates; if the installation directory is not writable, some environments will ask for elevated permission. Back up important worlds before a major update, and keep a known-good version installed while you test a new one.

Before you click download

  • Use the project’s own release page or its published mirror.
  • Check that the file name and version match the release notes.
  • Be wary of any site offering a “premium”, “unlocked” or “free Minecraft” build.
  • Keep Windows and your security software up to date.

If installation will not continue

  • Gaming Services missing or broken.
  • GameInput not installed.
  • Store ownership or installation state incomplete.
  • Install path not writable.
  • Downloads failing or the mirror timing out.

Each of these has a fix in the troubleshooting section below.

Isolation

One machine, several Minecrafts that never touch each other

Isolation is the feature most people install Levi Launcher for. Turn it on for a version and that setup keeps its own worlds, packs and game files instead of sharing the default AppData installation. A Preview build can break, a mod can misbehave, a downloaded world can bring odd settings with it — and your main survival world carries on unaffected.

It also makes testing reversible. Install a second isolated version, reproduce the problem there, and you have an answer without gambling anything you care about. If the test version is beyond saving, remove it and install it again.

Vanilla Release
Modded test
Preview build
Backup copy

World backups

Export a backup before mods, updates or level.dat edits. The fastest insurance there is.

Mods without mess

Import .zip or .dll mods into a specific version, browse CurseForge, keep vanilla clean.

Mirrors when GitHub is slow

A published Lanzou mirror exists for regions where the GitHub download crawls.

Comparison

Levi Launcher Comparison

How a managed setup differs from the default Microsoft Store experience. This compares workflows, not quality — the standard setup is the right choice for plenty of players.

AreaWith Levi LauncherStandard Store setupNotes
Multiple versionsInstall and keep several Release and Preview builds side by sideEffectively one installation at a timeEach managed version can be renamed and removed individually
Worlds and filesOptional isolation from the default AppData installationShared by whichever build is installedIsolation is chosen per version when you install it
Packs and worldsManaged from a built-in content sectionManual folder work or in-game importCovers resource, behaviour and skin packs, plus server lists
ModsImport .zip or .dll mods, CurseForge browsing, LIP / LeviLamina workflowsNot part of the standard experienceMods are third-party software; treat them with normal caution
Preview buildsInstalled and launched alongside Release buildsSeparate Store app, shared data by defaultPreview builds can break compatibility with packs and mods
RequirementsWindows 10/11, Bedrock GDK, Gaming Services, GameInput, WebView2Windows plus the Store appThe launcher can guide you through missing components
SupportCommunity Discord and a public issue trackerOfficial Microsoft and Mojang supportProblems caused by third-party tools are not Microsoft's responsibility
Balance

Pros and Considerations

Levi Launcher highlights

  • Several Minecraft Bedrock versions on one machine, each named and managed separately.
  • Optional isolation keeps worlds, packs and files away from your default installation.
  • Worlds, resource packs, behaviour packs, skin packs, screenshots and server lists in one place.
  • Mod support for .zip and .dll files, with CurseForge browsing and LIP / LeviLamina workflows.
  • World tools for backups, inspecting world data and editing selected level.dat fields.
  • Public documentation, a community Discord and an open issue tracker.

Things to consider

  • Windows only, and only for Minecraft Bedrock Edition (GDK) — not Java Edition.
  • You still need a legitimate licensed copy of the game on your Microsoft account.
  • It depends on Windows components that can be missing or broken on some systems.
  • Mods and Preview builds can break worlds; backups are your responsibility.
  • Third-party tools sit outside official Microsoft and Mojang support.
  • Features and behaviour change between releases, so check the changelog.
Fixes

Common Levi Launcher Problems & Solutions

Six issues that account for most reports, with the reason behind each one.

Gaming Services is missing or broken

Why: Windows is missing the component Bedrock depends on, or its Store installation state is incomplete.

Fix: repair or install it through the guided flow in the launcher, then re-check the Microsoft Store installation state for Minecraft Bedrock.

GameInput is missing

Why: the required redistributable has not been installed on this Windows setup.

Fix: install it when the launcher prompts you, then restart the launcher so the component check runs again.

Installation path is not writable

Why: the folder you chose for managed content needs permissions the launcher does not have.

Fix: move the managed content path to a writable location in Settings. If the launcher asks for elevation to install or self-update, allow it when you trust the action.

The launcher closes immediately

Why: startup can fail on some GPU and driver combinations before the interface appears.

Fix: retry once. If it keeps happening, check the startup log at %APPDATA%\levilauncher.exe\logs\startup.log and attach it to a GitHub issue.

A version will not launch

Why: usually a mod conflict, a missing Windows component, or an installation that did not finish.

Fix: test the same version without mods, confirm the required components still exist, verify the install completed, then retry with a clean isolated test version.

Downloads are slow or keep failing

Why: network routing to the default source is poor in your region, or the source is busy.

Fix: switch mirrors, retry later, or use a local package source if one is available to you.

Safe recovery order

  • Back up important worlds first.
  • Remove recently added mods or packs.
  • Test with a clean isolated version.
  • Reinstall the affected version if it still fails.

When you report a bug, include your Windows version, the launcher version, the exact steps you followed, and screenshots or logs. Reproducible reports get fixed; vague ones rarely do.

Good habits

Levi Launcher Tips & Best Practices

Start with one isolated Release version

The official recommendation for new users. Add a Preview build later, and only if you actually need to test something.

Name versions like you mean it

"Survival 1.21 vanilla" beats a bare version number six weeks later when you are deciding which one to launch.

Back up before every experiment

Export the world before adding a mod, switching versions or editing level.dat. Keep at least one backup off the same drive.

Add mods one at a time

If three mods go in together and the version stops launching, you have three suspects. One at a time gives you an answer in minutes.

Read the release notes

Behaviour changes between releases. Skimming the changelog before updating explains most surprises before they happen.

Stick to the project's own pages

Repackaged builds, "unlocked" versions and mirror sites you have never heard of are where the real risk sits.

Long read

Complete Levi Launcher Guide

Everything above, in one continuous read — what the launcher does, who it suits, and how to run it without losing anything.

What Levi Launcher is for

Levi Launcher exists because Minecraft Bedrock on Windows was never designed around having several installations. One Store app, one set of worlds, one version at a time. That is fine until you want to keep a modded setup away from a survival world, or try a Preview build without giving up the version your friends are on. The launcher puts a management layer on top: versions become entries in a list that you install, name, launch and remove as you like.

Who it suits

It fits players who already own Bedrock on Windows and have outgrown a single installation. Builders who keep separate creative and survival setups, anyone testing add-ons or mods, players curious about Preview features but unwilling to risk their main world, and people who would rather use a content manager than hunt through AppData folders. If you play one world in one version and never touch packs, the standard Store setup is genuinely enough.

What you need before starting

Windows 10 or 11, Minecraft Bedrock Edition (GDK) licensed to your Microsoft account, and the Windows components the game depends on: Microsoft Gaming Services, Microsoft GameInput and the WebView2 Runtime. Install Bedrock from the Store at least once and start it once, so Windows finishes registering ownership. You also need a connection for downloads, version metadata, mirror tests and update checks.

Working with versions

Installing a version means choosing a channel — Release or Preview — picking an entry, deciding on isolation, and letting the download finish. Release builds are the sensible default for long-term worlds and for mod and pack compatibility. Preview builds are for testing upcoming features, and come with the instability that implies. Keeping the two apart is exactly the problem the launcher was built to solve.

Isolation in practice

Isolation keeps a version’s worlds, packs and game files separate from the default AppData installation. The practical benefit is blast radius: whatever goes wrong in an isolated version stays there. It costs some disk space, because content is not shared, and it means importing a world into the version you want to play it in rather than assuming everything sees everything.

Content, mods and world tools

The content side covers worlds, resource packs, behaviour packs, skin packs, screenshots and server lists. Mods can be imported as .zip or .dll files, CurseForge can be browsed from inside the launcher, and LIP or LeviLamina workflows are available for more advanced setups. World tools handle backup exports, inspecting world data and editing selected level.dat fields. Mods remain third-party software: read what you install, and keep a backup.

Updating without drama

The launcher can check for, download and install its own updates, and may need elevated permission if its installation directory is not writable. Before a significant update, back up worlds you care about and note which version each one belongs to. Keeping a known-good version installed while you test a new one means a bad update costs you an evening rather than a world.

When something breaks

Work in order: back up worlds, remove recent mods or packs, test in a clean isolated version, and only then reinstall. Most failures trace back to a missing Windows component, a non-writable path, or a mod conflict. If a problem is reproducible and survives those steps, open an issue on the project’s tracker with your Windows version, launcher version, steps and logs.

A note on official status

Levi Launcher is a community project. It is not published by Mojang Studios or Microsoft, and using third-party tools with the game is at your own risk. This site is an independent guide and is not an official channel for the launcher — the project’s own documentation and release pages always take precedence over anything written here.

Resources

Levi Launcher Download & Resources

Links to the project’s own pages. Replace or extend them in Elementor whenever the project moves something.

User documentation

The project’s own guide: quick start, requirements, version management, content, mods, world tools and troubleshooting.

Releases and changelog

The GitHub releases page for the launcher, with release notes for each version.

Report a problem

The public issue tracker. Include your Windows version, launcher version, steps and logs.

Before downloading: use the project’s own release page or its published mirror, check that the file matches the release notes, and confirm the version you want supports your Windows setup. Avoid any site advertising a free, cracked or “unlocked” copy of Minecraft — Levi Launcher is not a way to play without owning the game.

Answers

Levi Launcher Frequently Asked Questions

Twenty short answers to the questions people ask most.

Levi Launcher is a desktop launcher for Minecraft Bedrock Edition (GDK) on Windows, built by the LeviMC community. It lets you install, manage, isolate, mod and launch Release or Preview builds from one application, rather than relying on a single Microsoft Store installation. It is a management tool for a game you already own, not a copy of the game itself.

You install the launcher on Windows, and it checks that the components Bedrock depends on are present. From there you add versions: choose Release or Preview, pick an entry, decide whether to isolate it, and install. Each managed version appears in a list you can rename, launch or remove, with content and world tools attached to it.

A version-first workflow for installing and organising builds, optional isolation from the default AppData installation, a content toolkit for worlds and packs, mod support for .zip and .dll files with CurseForge browsing, world utilities including backups and level.dat editing, and settings covering language, appearance, downloads, privacy and update channels.

The basic path is straightforward: install the launcher, add one isolated Release version, launch it. The more advanced areas — mod workflows, level.dat editing, custom WebView2 runtimes — assume you are comfortable with Windows file paths and are willing to read the documentation. Most players never need those parts.

The desktop launcher runs on Windows 10 and Windows 11 with Minecraft Bedrock Edition (GDK). There is no official macOS or Linux desktop build, and Minecraft Java Edition is not covered. Android projects with similar names exist in the community, but they are separate software with their own requirements.

Install Bedrock from the Microsoft Store at least once and start it once, then close it. Download the launcher installer from the project’s GitHub Releases page or its published Lanzou mirror, run it, and finish the setup wizard. Then open Download inside the launcher and install your first managed version.

The launcher can check for, download and install its own updates. If its installation directory is not writable, your system may ask for elevated permission first. Back up important worlds before updating, and keep a version you know works installed while you test the new one.

The usual causes are a missing or broken Microsoft Gaming Services component, a missing GameInput redistributable, an installation path that is not writable, or a mod conflict inside a specific version. If the launcher closes before its window appears, check the startup log at %APPDATA%\levilauncher.exe\logs\startup.log and include it in a bug report.

Confirm you are on Windows 10 or 11, that Bedrock (GDK) is licensed to your Microsoft account, and that Gaming Services, GameInput and the WebView2 Runtime are present. Install Bedrock from the Store once, start it once if the installation state looks incomplete, and close the game before managing versions.

Yes. Preview builds can break compatibility with packs and mods, and launcher behaviour changes between releases. Treat the release notes for the version you are installing as authoritative, and keep a stable Release version installed while you test anything experimental.

The project publishes user documentation covering quick start, requirements, first launch, version management, downloads and mirrors, content management, mods, world tools, settings and troubleshooting. Releases and the issue tracker are on GitHub, and there is a community Discord for discussion.

Work through it in order: back up important worlds, remove recently added mods or packs, test with a clean isolated version, and reinstall the affected version if the problem survives. Confirm required Windows components are still installed, and check whether the same version launches without mods.

Yes. Remove it like any other Windows application. Before you do, export backups of any worlds that live inside managed or isolated versions, because those files sit in the launcher’s managed content path rather than your default game folder. Once backed up, they can be imported again later.

Export backups of worlds you care about, note which version each world belongs to, and skim the release notes for anything that changes behaviour. If a specific version and mod combination is working well for you, keep it installed while you test the update on a separate version.

It relies on Windows components rather than extra applications: Microsoft Gaming Services, Microsoft GameInput and the WebView2 Runtime. Many Windows installations already have some of them. The launcher can guide you through anything missing during first launch or before an installation.

The launcher shows its own version inside the application, and the version of each managed Minecraft build appears in your version list. Both are worth including in a bug report, along with your Windows version, because most issues depend on that combination.

Gaming Services missing or broken, GameInput not installed, an install path that is not writable, the launcher closing before its window appears on certain GPU and driver combinations, a version that will not launch because of a mod conflict, and slow or failing downloads that a different mirror usually resolves.

Start with the project’s quick start guide, then requirements and installation, first launch, version management and content management, in that order. The troubleshooting page is worth reading before you need it, so you recognise the symptoms when something goes wrong.

No. This site is an independent community resource that explains what the launcher does and how to use it. It is not owned, operated or endorsed by LeviMC, Mojang Studios or Microsoft, and it does not host the software. Always download from the project’s own release pages, and treat its documentation as the final word.

Three things. You still need a licensed copy of Minecraft Bedrock. Start with a single isolated Release version rather than a complicated multi-version setup. And back up any world you would be upset to lose before adding mods, switching versions or editing world data — the tools are there, and they take a minute.

Scroll to Top