Windows-first Minecraft client

Every Minecraft era.
One clean client.

FoliaClient keeps versions, loaders, mods, packs and settings inside isolated profiles, so old experiments and current releases never have to collide.

v0.6.0 Windows installer Windows
FoliaClient
SELECTED PROFILE Folia 26.1.2
Ready

Folia 26.1.2

Fabric · Isolated profile

6 GB RAMJava 251280 × 720
Library
ModsProfile-scoped
Resource packsOrganized
ShadersManaged
Protection
Automatic safety snapshotBefore content changes
JAR inspectionMetadata and risk checks
Live consoleLaunch output in one place
Isolated by designEach profile keeps its own files and settings.
Built for old and newOfficial history, community metadata and imports.
Privacy-focused presenceNo server address, chat or inventory details.
Core workflow

A launcher that stays out of your way.

FoliaClient is organized around profiles, not a single shared game folder. Installations remain predictable, reversible and easier to diagnose.

01

Independent profiles

Versions, loaders, memory, resolution, JVM arguments, mods, resource packs, shaders and configuration stay attached to the profile that uses them.

02

Modrinth inside the client

Search compatible mods, resource packs and shaders, review the install plan and keep managed content tied to the selected profile.

03

Snapshots and rollback

Create restore points for mods, packs, shaders and configuration. Restoring a snapshot first creates an additional safety snapshot.

04

Live launch diagnostics

Follow Minecraft output in the built-in console and keep installation, launch and content activity visible in one timeline.

05

Java generation selection

Profiles can target Java 8, 16, 17, 21 or 25, matching the runtime generation required by different parts of Minecraft Java history.

Compatibility model

Automatic where metadata exists.
Importable where it does not.

FoliaClient does not pretend that every abandoned loader has a stable public API. It automates reliable catalogs and provides a controlled import path for the rest.

Automatic setup

Catalog-backed loaders

Vanilla Fabric Quilt Forge NeoForge Legacy Fabric Ornithe LiteLoader
Controlled import

Legacy and custom profiles

OptiFineRiftModLoaderBabricCursed FabricNilLoaderCleanroomFoxLoaderFishModLoaderMeddleWeave LoaderLitLaunchBetaLoaderBTA FabricCustom profiles
Version catalog

From Classic to current releases.

Browse official releases, snapshots, beta, alpha and Classic entries, add community-preserved metadata, or import a valid local version profile.

ClassicOfficial archive
AlphaOfficial archive
BetaOfficial archive
ReleasesStable versions
SnapshotsDevelopment versions
Safety boundaries

Useful warnings, not fake guarantees.

Third-party Minecraft content can be unsafe. FoliaClient treats external JAR files as untrusted input, requires explicit acknowledgement and inspects common loader metadata before import.

See how FoliaClient handles data

JAR risk acknowledgement

External JAR imports cannot proceed until the user accepts the malware risk.

Transactional profile import

Imported profiles use staging, path validation, backup and rollback instead of copying directly over live data.

Windows credential storage

Account tokens are stored through Windows Credential Manager rather than plain launcher configuration files.

Private Rich Presence

Presence can show launcher and gameplay state without exposing chat, inventory, server names or addresses.

Windows release

FoliaClient v0.6.0

FoliaClient v0.6.0 is available as a standard 64-bit Windows MSI installer.

Download for Windows